Gordon Messmer writes:

On 10/22/2012 04:26 PM, Sam Varshavchik wrote:
> I'm not sure I understand the problem. Why would it take Courier more
> than 30 minutes to accept a single message?

Sorry.  SSMTP doesn't do any local queing.  It connects to the
destination server and sends output as it is received.  Where we have
long-running cron jobs, cron will launch ssmtp, and the resulting SMTP
session will remain open until the job finishes and output is closed.
The submit timeout causes submit to close, while the SMTP session stays
open and fails later, unable to write to the pipe to the submit process
(IIRC).

If it's connecting via SMTP, the SMTP timeout is much shorter, and should kick in much earlier. If it's a local connection, I don't see the point of SSMTP. What value does it add, exactly, versus sending mail directly.

And, in any case, starting sendmail/submit, then doing nothing for half an hour, that seems rather broken to me. The timeout is not issue, here. Something's wrong with this entire concept.


Attachment: pgpAvstUFMo3z.pgp
Description: PGP signature

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to