>>> 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.
>Gordon Messmer writes: >>A cron job might not have output for a very long time, but cron launches >>sendmail before it runs jobs, and connects the job's output to >>sendmail's input. On 23.10.12 08:31, Sam Varshavchik wrote: >The correct way to handle that is to redirect the message into a >temporary file. When you're ready to send the message, then make the >connection, and send it on the way. the SSMTP is supposed to take the mail body, send it to SMTP server and return error code according to what the server replied. This way the sending program can know if the mail was accepted or not. The downside is the timeout. Maybe SSMTP could do something moreto avoid timeouts, hower this is a case where it's not courier, ssmtp or cron can make the decision which behaviour is the correct one. Therefore I think the request for increasing DATA timeout has its logic. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Enter any 12-digit prime number to continue. ------------------------------------------------------------------------------ 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
