On Sat, 24 Oct 2015 12:12:34 PM Brian May wrote:
Craig Sanders <cas@taz.net.au> writes:
It's not mutt's job, or any MUA's job, to handle queueing and multiple delivery attempts for mail. An MUA should hand the mail to an MTA and forget about it. The MTA will queue the mail and attempt delivery as many times as it takes until it either succeeds or the delivery times out (in which case it will bounce it back to the sender with an "unable to deliver" message).
I think you might be confused, I wasn't talking about contacting the destination SMTP server directly, I was talking about contacting a remote authenticated queuing SMTP server directly.
Why not run a local queuing SMTP server?
Like it or not it is common practise to do this directly from the MUA. This offers advantages such as being able to enter the remote SMTP password when sending the email instead of saving it on disk (not that many people do this...)
Why would anyone want to do that? Anyone who can read the file on disk probably has access to exploit you in so many other ways that they are going to get the password anyway. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/