I'm mostly avoiding this conversation, as I avoid most, because my mutt contributions are at the level of "several patches, only a few accepted into mutt itself". One point I'll comment on, with my MTA developer/maintainer hat on:
On 2012-08-02 at 16:38 +0200, Vincent Lefevre wrote: > And queue management is better done globally (how does > Mutt's SMTP support manage temporary errors due to grey-listing?). Grey-listing is a solution for the MX port to deal with previously-unseen-IP(-some-tuple) unauthenticated senders. Mail submission from an MUA should be going to the submission port (587/tcp) and probably authenticating with SMTP AUTH; if not AUTHenticating, it should be on a trusted IP and implicitly authenticated by being on an internal network. If your mail admin has configured greylisting to apply to such a case, then it's time to have a quiet polite word with them until clue strikes and they wince and fix the problem. Similarly for anything else which introduces delays in the sending process which is visible to the user of the mail-client. (Eg, reverse DNS checks on client IP). MX != Submission. Even though the core protocol is mostly the same, the policies and controls should be very different. -Phil
