Gordon Messmer writes:
On 10/23/2012 05:31 AM, 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.I agree, but I didn't write cron or ssmtp. They're intentionally designed not to write output to disk, and patching those on embedded devices is much more difficult than patching submit to extend the timeout. > The problem here is that there are processes that remove old files in > the temporary directory where the incoming message gets initially saved. It looks like courierd does that for files older than 48 hours. Extending the submit timeout shouldn't cause a problem here.
I'll look into it.
pgp0FFSbO1A05.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
