I am running into problems when I try and use the

Use Email From = $user_email 

setting in my individual logbook configs. I had to set this field as I set a 

Use Email From = real_email_address 

in my global config so that the email would be sent out by the
CommunigatePro mail server.

When I made those changes though the mail was not sent and I got the
following errors in the elog log:

06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} NEW entry #0
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} Email from
john.habermann@wilderness.org.au to john.habermann@wilderness.org.au,
SMTP host localhost:
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} 220
tanami.wilderness.org.au ESMTP CommuniGate Pro 4.2.8 is glad to see you!
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog}
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} HELO tanami.wilderness.org.au
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} 250
tanami.wilderness.org.au your name is not tanami.wilderness.org.au
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} MAIL FROM:
john.habermann@wilderness.org.au
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} 555 syntax error in MAIL
FROM parameters
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} RCPT TO:
<john.habermann@wilderness.org.au>
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} 501 Unknown command
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} DATA
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} 501 Unknown command
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} To:
john.habermann@wilderness.org.au
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} From:
john.habermann@wilderness.org.au
Subject: [twslog: Elog] will it work on tanami from konqueror
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} X-Mailer: Elog, Version
2.5.6-1
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} X-Elog-URL:
http://tanami.wilderness.org.au:8080/Elog/36
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} X-Elog-submit-type: web|elog
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} Date: Sun, 06 Feb 2005
13:48:34 +1100
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} Content-Type: TEXT/PLAIN;
charset=US-ASCII

06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} .
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} 501 Unknown command
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} QUIT
06-Feb-2005 13:48:34 [john@137.219.117.245] {Elog} 501 Unknown command

It looks like Communigate Pro doesn't like what is being put in the From as
it complains about the syntax. 

I tried the same elog.conf file on my laptop which uses a qmail server as
its SMTP and the mail was sent ok but I got mailto appearing in the from
header. I saw that elog:333 reported a similar problem but this was listed
as fixed. This is the headers from a message sent by the qmail server:

X-Gmail-Received: 04395b7bf4189dd6e4c23606ee6adbd5fdcb0e53
Delivered-To: john.haberman@gmail.com
Received: by 10.54.43.19 with SMTP id q19cs16478wrq;
        Sat, 5 Feb 2005 18:44:47 -0800 (PST)
Received: by 10.54.43.11 with SMTP id q11mr64342wrq;
        Sat, 05 Feb 2005 18:44:47 -0800 (PST)
Return-Path: <john.habermann@wilderness.org.au>
Received: from mx-1.netregistry.net (mx-1.netregistry.net [203.202.16.27])
        by mx.gmail.com with ESMTP id 33si43805wra.2005.02.05.18.44.45;
        Sat, 05 Feb 2005 18:44:47 -0800 (PST)
Received-SPF: neutral (gmail.com: 203.202.16.27 is neither permitted nor
denied by best guess record for domain of
john.habermann@wilderness.org.au)
Received: from mail.ngogeeks.com ([216.17.101.59])
	by mx-1.netregistry.net with esmtp (Exim 4.20 #2 (Debian))
	id 1CxcPj-0003zY-Io
	for <john.habermann@wilderness.org.au>; Sun, 06 Feb 2005 13:44:43 +1100
Received: (qmail 5486 invoked by uid 1021); 6 Feb 2005 00:45:04 +0000
Received: from john.habermann@wilderness.org.au by ngogeeks.com by
uid 1012 with qmail-scanner-1.22-st-qms 
 (clamdscan: 0.75. spamassassin: 2.20.  Clear:RC:1(10.3.0.2):. 
 Processed in 0.363281 secs); 06 Feb 2005 00:45:04 -0000
X-Antivirus-MYDOMAIN-Mail-From: john.habermann@wilderness.org.au via
ngogeeks.com
X-Antivirus-MYDOMAIN: 1.22-st-qms (Clear:RC:1(10.3.0.2):. Processed in
0.363281 secs Process 5482)
Received: from unknown (HELO localhost) (10.3.0.2)
  by mail.ngogeeks.com with SMTP; 6 Feb 2005 00:45:03 +0000
To:
john.habermann@wilderness.org.au
From: john.habermann@wilderness.org.au
Subject: [twslog: Email] test of new elog version
X-Mailer: Elog, Version 2.5.6-1
X-Elog-URL: http://localhost:8080/Email/79
X-Elog-submit-type: web|elog
Date: Sun, 06 Feb 2005 13:43:31 +1000
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Antivirus-MYDOMAIN-1.22-st-qms: added fake MIME-Version header
MIME-Version: 1.0
X-Antivirus-MYDOMAIN-Message-ID: <11076507048355482@ngogeeks.com>
Message-Id: <E1CxcPj-0003zY-Io@mx-1.netregistry.net>
X-Spam-Score: 0.3 (/)
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
*1CxcPj-0003zY-Io*13Qgra0rAPA*

A new entry has been submitted on localhost

Logbook             : Email
Author              : John Habermann
Subject             : test of new elog version
Type                : Other
Todo                : 

Logbook URL         : http://localhost:8080/Email/79

=================================

Testing 

Hi!

This just started happening here also.  Some users can't get on to a SSL=1 config'd elog using either IE or firefox 10 (win7 or linux) or chrome.  SAFARI works.  Occurs in 2.8.0 and a newly built (even after

ssl yum updates) 2.9.0 version on SL5.5 system.  Seems to accept self signed cert then nothing.. (connection reset message).   Tried an stunnel from one port to port running elog

with SSL=0.  Same behavior.  Doesn't work on some browsers.  Any clues?

Thanks,

-John

Andreas Luedeke wrote:

John Doroshenko wrote: Olaf Kasten wrote:  Hi there, I have a connection problem with an actual elog installation. Many Browsers like as Chrome, Firefox and IE don't  connect to the elog server with ssl = 1 in elogd.cfg.  I tested with Firefox 3.6 and IE 7 installations and there are no problems. I guess it's a bug. Does someone have a suggestion to solve that problem? Thx. Olaf  Hi! This just started happening here also.  Some users can't get on to a SSL=1 config'd elog using either IE or firefox 10 (win7 or linux) or chrome.  SAFARI works.  Occurs in 2.8.0 and a newly built (even after ssl yum updates) 2.9.0 version on SL5.5 system.  Seems to accept self signed cert then nothing.. (connection reset message).   Tried an stunnel from one port to port running elog with SSL=0.  Same behavior.  Doesn't work on some browsers.  Any clues? Thanks, -John Hi everyone, it appears that many people have this problem. I believe this is simply a problem of your firewall settings. There are two simple checks you can do to test if I'm right or wrong: Run your logbook on the standard port 443 and retry. If the special port has been opened on the firewall, it has been likely only opened for specific clients like firefox 3.6, IE 7, etc. If you use a different client (FF 10, IE 9) the port can be blocked. Or just run the browser that does not work on the ELOG server. If it works to access ELOG via localhost, then you know for sure that it is the firewall. I've actually tested it here at my institute: I've downloaded firefox 10 and could access ELOG on port 443 but couldn't access it on port 444, unless I've started FF10 on the ELOG host. To John, Olaf and Christian: If you need to be able to use a special port and a certain set of browsers then just contact your computing division or whoever maintains your firewalls.   I hope this settles the matter. Cheers Andreas   Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   PS: I've solved this with the help of google  : have a look at http://forums.mozillazine.org/viewtopic.php?p=2295421#2295421 about firewalls

 Hi,

Thanks for the reply. 

The elog server is running SL5.5 (updates applied).  As you suggested, I ran firefox 3.6.26 on the elog server via https://localhost:port and it worked fine.   Downloaded firefox 10.0.1 and retried

on elog server and get error again:  The connection was Reset; The connection to the server was reset while the page was loading.

-John

John Doroshenko wrote:

Andreas Luedeke wrote: John Doroshenko wrote: Olaf Kasten wrote:  Hi there, I have a connection problem with an actual elog installation. Many Browsers like as Chrome, Firefox and IE don't  connect to the elog server with ssl = 1 in elogd.cfg.  I tested with Firefox 3.6 and IE 7 installations and there are no problems. I guess it's a bug. Does someone have a suggestion to solve that problem? Thx. Olaf  Hi! This just started happening here also.  Some users can't get on to a SSL=1 config'd elog using either IE or firefox 10 (win7 or linux) or chrome.  SAFARI works.  Occurs in 2.8.0 and a newly built (even after ssl yum updates) 2.9.0 version on SL5.5 system.  Seems to accept self signed cert then nothing.. (connection reset message).   Tried an stunnel from one port to port running elog with SSL=0.  Same behavior.  Doesn't work on some browsers.  Any clues? Thanks, -John Hi everyone, it appears that many people have this problem. I believe this is simply a problem of your firewall settings. There are two simple checks you can do to test if I'm right or wrong: Run your logbook on the standard port 443 and retry. If the special port has been opened on the firewall, it has been likely only opened for specific clients like firefox 3.6, IE 7, etc. If you use a different client (FF 10, IE 9) the port can be blocked. Or just run the browser that does not work on the ELOG server. If it works to access ELOG via localhost, then you know for sure that it is the firewall. I've actually tested it here at my institute: I've downloaded firefox 10 and could access ELOG on port 443 but couldn't access it on port 444, unless I've started FF10 on the ELOG host. To John, Olaf and Christian: If you need to be able to use a special port and a certain set of browsers then just contact your computing division or whoever maintains your firewalls.   I hope this settles the matter. Cheers Andreas   Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   PS: I've solved this with the help of google  : have a look at http://forums.mozillazine.org/viewtopic.php?p=2295421#2295421 about firewalls  Hi, Thanks for the reply.  The elog server is running SL5.5 (updates applied).  As you suggested, I ran firefox 3.6.26 on the elog server via https://localhost:port and it worked fine.   Downloaded firefox 10.0.1 and retried on elog server and get error again:  The connection was Reset; The connection to the server was reset while the page was loading. -John

 Hi,

One of our sys admins discovered that Firefox 10 appeared to send parts of the initial GET in two parts.  As if there was a flush() after the "G" and this caused elog problems.  By making the change in

the patch below, the read loop is re-entered again after the 2nd part of the GET comes in.   Firefox 10.0.1 then works with ELOG with SSL.   Stefan... perhaps you can take a look to see if there is a

better way to accomplish this? 

One side effect with it done this way is that if you start a connection (ie, telnet localhost port) and type a single character,  the elog will block further connections until the telnet is terminated.

Thank you,

-John Doroshenko

 Thank you Stefan!  I put up your new svn revision and we're back in business.  Seems to be working perfectly.

And thank you again for your efforts with regards to ELOG.  It is an incredibly handy tool.

-John

 Hi, I have a question regarding the Protect Selection option. I have the option enabled and I have to login to get into the logbook. What I would like to accomplish is that the page does not display anything (none of the posts) when it is opened. The only option should be to login.

Is this possible?

Regards,

John