I'll stick with grep.

Thank you for taking the time to help and answer my questions.

Regards
Paul

On Sun, 2010-07-04 at 10:58 +0200, Thomas Eckardt wrote:
> >Is there a way to log only messages of this nature (warning/errors of
> >assp self - not the content it's handeling) to a seperate file.
> 
> Not in a separate file - but you can use the 'Notify' feature - to send 
> you emails in case of a specific contents of a logged message.
> Or you may use the MaillogTail to search for specific contents.
> Or you may use 'grep' to extract specific lines from maillog.txt.
> 
> >Is this where the syslog facility comes in or will the same info as in
> >(logfile) just be repeated there ?
> 
> SysLog will log the same.
> 
> Thomas
> 
> 
> 
> 
> Von:    Paul Schutte <[email protected]>
> An:     ASSP development mailing list <[email protected]>
> Datum:  04.07.2010 10:46
> Betreff:        Re: [Assp-test] Strange SMTP synchronization problem
> 
> 
> 
> 
> Hi Thomas.
> 
> Thanks for your explanation. It put me on the right track.
> I know (and checked) that the MTA will timeout only at 5 min. 
> I have a haproxy (which I forgot about - testament to how well it
> works), between assp and load balanced MTAs. 
> 
> It turned out that haproxy was set to timeout at 50s.
> 
> Can you give some indication (in a log file) that the backend went away
> unexpectedly ?
> 
> Question about the logging:
> At this stage everything gets logged to (logfile:=logs/maillog.txt)
> 
> Is there a way to log only messages of this nature (warning/errors of
> assp self - not the content it's handeling) to a seperate file.
> 
> Is this where the syslog facility comes in or will the same info as in
> (logfile) just be repeated there ?
> 
> Regards
> Paul
> 
> On Sun, 2010-07-04 at 09:27 +0200, Thomas Eckardt wrote:
> > >Can this be a tcp setting ?
> > 
> > No. The only reason could be, that your MTA has closed the connection to 
> 
> > assp before.
> > The 220..... greeting received by assp from your MTA sets the 
> > 'greetingSent' flag in the internal connection data of the MTA 
> connection. 
> > This flag is checked at the first command the peer has sent. If the MTA 
> > closes the connection before, the internal connection data for the MTA 
> > connection are deleted (also this flag).
> > 
> > I'll change the code to prevent the error message in this case - but how 
> 
> > ever, if the connection was closed by your MTA - assp will close the 
> > peer-connection after the next command sent by the peer or at 
> > 'connectionTimeOut'.
> > 
> > Thomas
> > 
> > 
> > 
> > 
> > Von:    Paul Schutte <[email protected]>
> > An:     ASSP development mailing list <[email protected]>
> > Datum:  03.07.2010 15:05
> > Betreff:        [Assp-test] Strange SMTP synchronization problem
> > 
> > 
> > 
> > 
> > EHLO all
> > 
> > I came across this strange behaviour while investigating some
> > intermittend response problems with assp.
> > 
> > I telnet to port 25 of the assp server. If I issue a quit (or any
> > command) within +/-50s, everything is fine:
> > 
> > telnet mail.up.ac.za 25
> > Trying 137.215.6.44...
> > Connected to mail.up.ac.za.
> > Escape character is '^]'.
> > 220 mail.up.ac.za ESMTP Exim 4.69 Sat, 03 Jul 2010 14:30:15 +0200
> > quit
> > 221 mail.up.ac.za closing connection
> > Connection closed by foreign host.
> > 
> > 
> > If I wait more than +/-50s before issuing a command I get the following:
> > 
> > telnet mail.up.ac.za 25
> > Trying 137.215.6.44...
> > Connected to mail.up.ac.za.
> > Escape character is '^]'.
> > 220 mail.up.ac.za ESMTP Exim 4.69 Sat, 03 Jul 2010 14:31:16 +0200
> > quit
> > 554 5.7.1 Misbehaved SMTP session (EarlyTalker)
> > 451 4.7.1 Please try again later
> > Connection closed by foreign host.
> > 
> > 
> > There is no setting in the config that is at 50s (or close to). The only
> > settings that are related are:
> > 
> > smtpIdleTimeout:=180 
> > smtpNOOPIdleTimeout:=60 (Did change this with no effect)
> > ConnectionTransferTimeOut:=30 (Did change this with no effect)
> > 
> > Can this be a tcp setting ?
> > 
> > It does not cause any problems, but the behaviour does not seem right.
> > 
> > Regards
> > Paul
> > 
> > 
> > 
> > 
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Sprint
> > What will you do first with EVO, the first 4G phone?
> > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> > _______________________________________________
> > Assp-test mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/assp-test
> > 
> > 
> > 
> > 
> > DISCLAIMER:
> > *******************************************************
> > This email and any files transmitted with it may be confidential, 
> legally 
> > privileged and protected in law and are intended solely for the use of 
> the 
> > 
> > individual to whom it is addressed.
> > This email was multiple times scanned for viruses. There should be no 
> > known virus in this email!
> > *******************************************************
> > 
> > 
> > 
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Sprint
> > What will you do first with EVO, the first 4G phone?
> > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> > _______________________________________________ Assp-test mailing list 
> [email protected] 
> https://lists.sourceforge.net/lists/listinfo/assp-test
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Assp-test mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/assp-test
> 
> 
> 
> 
> DISCLAIMER:
> *******************************************************
> This email and any files transmitted with it may be confidential, legally 
> privileged and protected in law and are intended solely for the use of the 
> 
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no 
> known virus in this email!
> *******************************************************
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________ Assp-test mailing list 
> [email protected] 
> https://lists.sourceforge.net/lists/listinfo/assp-test


------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to