We are looking at two ISP's to manage our incoming/outgoing mail.
One uses Qmail and the other Sendmail as the MTA's.
I have heard that Qmail has shortcomings in terms of trying only one IP per MX, one MX per domain, and also not bundling messages to multi- recipients in the same domain.
Does anyone know if Sendmail has similar/worse issues, or is better in any way?
Melpa wrote: > We are looking at two ISP's to manage our incoming/outgoing mail. > One uses Qmail and the other Sendmail as the MTA's.
If the ISPs are managing the mail, you shouldn't care what MTA they use. Just be sure you pick a competent ISP.
If *you* are in charge of picking an MTA, I'd certainly recommend Sendmail over Qmail. Qmail is essentially no longer maintained and hasn't bothered keeping up with newer RFCs. It has its own non-standard delivery status notification format. It needs to be patched to reject nonexistent recipients at RCPT time. It doesn't like to bundle messages for multiple recipients at a given domain, preferring to send one message per recipient.
>If *you* are in charge of picking an MTA, I'd certainly recommend >Sendmail over Qmail. Qmail is essentially no longer maintained and >hasn't bothered keeping up with newer RFCs. It has its own non-standard >delivery status notification format. It needs to be patched to reject >nonexistent recipients at RCPT time. It doesn't like to bundle messages >for multiple recipients at a given domain, preferring to send one message >per recipient.
Thanks for the info.
How do you mean it needs to be pached to reject nonexistence recipients? And the RFC's you are referring to, are they RFC 2821/2822, Qmail instead preferring their predecessors?
>> If *you* are in charge of picking an MTA, I'd certainly recommend >> Sendmail over Qmail. Qmail is essentially no longer maintained and >> hasn't bothered keeping up with newer RFCs. It has its own non-standard >> delivery status notification format. It needs to be patched to reject >> nonexistent recipients at RCPT time. It doesn't like to bundle messages >> for multiple recipients at a given domain, preferring to send one message >> per recipient.
> Thanks for the info.
> How do you mean it needs to be pached to reject nonexistence > recipients?
> >If *you* are in charge of picking an MTA, I'd certainly recommend > >Sendmail over Qmail. Qmail is essentially no longer maintained and > >hasn't bothered keeping up with newer RFCs. It has its own non-standard > >delivery status notification format. It needs to be patched to reject > >nonexistent recipients at RCPT time. It doesn't like to bundle messages > >for multiple recipients at a given domain, preferring to send one message > >per recipient.
> Thanks for the info.
> How do you mean it needs to be pached to reject nonexistence > recipients? And the RFC's you > are referring to, are they RFC 2821/2822, Qmail instead preferring > their predecessors?
Melpa wrote: > How do you mean it needs to be pached to reject nonexistence > recipients?
Depending on the environment, using a "sink" user, which gets all messages for non-existent recipients, can be a good idea. This behavior can be configured with sendmail without any patch.
