Windows binaries took care of this problem as with Message ID: 66157.

Problem solved, thanks!

Unfortunately can't validate this right now. I'm at a remote network trying to get ELOG on my Windows laptop working with e-mail notifications. Either my normal ISP will not allow the SMTP to accept relaying from external networks, or something else is wrong.

The Windows binary is behaving somewhat differently, it seems to behave like earlier versions. I.e. the error message seen on the browser (Error sending Email via "smtp.xxx.xxx") is very limited. Logging (level 6) will not revile much and -v doesn't output any hints either. Assuming the first possible cause, I registered a account at gmail to try see if their SMTP would allow e-mail relaying. Trying with the Windows binary version I seemingly leads to the same result (i.e. I don't see much and the error seen at the browser is the same). However, when trying to run ELOG on a machine at my home network the message is different:

Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. w40sm7583927ugc.6

The message does not surprise me (from previous experience, TLS was what made made postfix complicated to set up too). But what does surprise me is that the messages differ between the two (ELOG V2.7.5 running on a Linux machine and the Windows binary of the same version). Does Linux/Windows versions differ by conditionals in the code or did I somehow get an older Windows binary?

It would also be helpful knowing if ayone has got ELOG working with smtp.gmail.com.

Regards /Michael

The Windows Binaries are not recompiled for each minor modification. You should check the SVN revistion (the number which shows up at the very bottom of the page, which is 2153 in this case). It might well be that the Windows Binaries do not yet contain the modification for extended SMTP error report.

Furthermore, TLS is not supported in elogd, only plain SMTP is possible. 

Importing dates from CSV files was not implemented for a good reason: There are dozens of date formats (such as "1/22/09", "Jan 1 2009", "Mon 1 January '09") and it is almost impossible to handle all formats. I changed now the code to catch at least some formats, such as the internal RFC2822 compliant date which is also used internall by elog. An example of this format is "Thu, 22 Jan 2009 09:26:00". This date format will also be used if you export a logbook via a CSV file. Another format I added is "1/22/09". So give a try to the new code (I made an intermediate release for windows V2.7.5-3) and see if it works for you.

hi there,

Is it possible to attach a default value for a radio button when submitting a new form/record, for example: 
I now have an item "Confirmed" Yes/No, and I want the "no" option to be selected by default when a new form/record is created.
Does anyone know how to arrange this?

Thanks in advance!

RJ

You need something along these lines:

Attributes = ..., Confirmed
Options Confirmed = boolean
Preset Confirmed = 1 

Great software.

Okay, so I've done my reading through the forum and got a couple of nuggets along the way but I am still unable
to get the e-mail function to work.  I am using Windows IIS to make an SMTP virtual server to shimmy around the
IT firewall.  That appears to work as I can see the response from the external SMTP server while running elogd
with the -v flag.  The elogd -v details are below:  

Email from xxxxxxxxxxxx@xxxxxxxxxxxx.com to xxxxxx.XXXXXXX@XXXXX.com,XXXXX.XXXXX X@XXXXX.com, SMTP host
XXXXXXXXXXXXXX.XXXX.XXXXX.com: 
220 smtp.xxxxx.com Microsoft ESMTP MAIL Service, Version: 6.0.2600.2180 ready at   Mon, 26 Jan 2009 10:56:35 -0500 
EHLO xxxxxxxxxxxxxx.xxxx.xxxxx.com 
250-smtp.xxxxx.com Hello [xxx.xxx.xxx.xxx] 
250-AUTH=LOGIN 
250-AUTH LOGIN 
250-SIZE 2097152 
250-PIPELINING 
250-DSN 
250-ENHANCEDSTATUSCODES 
250-8bitmime 250-BINARYMIME 
250-CHUNKING 250-VRFY 
250 OK AUTH LOGIN 
Username: 
xxxxxxxxxxxx@xxxxxxxxxxxx.com 
Password: cm9jaGVsb2dib29r 
535 5.7.3 Authentication unsuccessful 
==== Return ================================  

From the SMTP server response it is not logging in, but I don't know why.  I can log in to the webmail app with
the username/password provided to ELOG, but it doesn't appear to work through ELOG. The SMTP provider includes
the following info to setup e-mail accounts via SMTP: "Please note: To send e-mail using the SMTP-Server,
activate SMTP Authentication. Please do not use the Secure Password Authentication (SPA) option. Optionally,
port 587 can also be used in addition to the default port (25) RFC 2476." 

For authentication via the Windows IIS I have "basic authentication" with no TLS encryption required - I'm not
sure if that meets the provider's "SMTP authentication" requirement.  When I was using the previous version of
ELOG (sorry, I did not note the version number) the username was encrypted along with the password.  With the
2168 build, the password is still encrypted but the usernamer is not; should the password be in "plain text" as
well?  

I can provide you with a username/password for the SMTP provider I'm using if that will help.  Please send me a
separate e-mail and I will reply with the information.  

Thank you,  

Topher Congdon

Attributes = ..., Confirmed
Options Confirmed = boolean
Preset Confirmed = 1 

 Good Morning Stefan,

This was very helpful, it works as aspected! Thank you :-)

With regards, Robert-Jan.