Re: [PATCH] dma: Update to 0.13

[Tom Rymes <tom@rymes.net>]

[-- Attachment #1: Type: text/plain, Size: 2175 bytes --]

On Jan 28, 2021, at 5:54 PM, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi Peter & *
> 
> On 28/01/2021 21:36, Peter Müller wrote:

[snip]

>> 4. Change RCPT TO to split up multiple addresses
>> The latter is especially - um - interesting as the full commit message (available online at
>> https://github.com/corecode/dma/commit/450d4b68d3295d2ef50fa5c9576f5c4e043c0c80) states:
>>> RFC5321 section 4.1.1.3 states that RCPT TO only takes one address at a time.
> That does sound a bit fundamental to have been missed previously but then this software is also a long way from version 1.0. It's taken 10 years to get from V0.1 V0.13
>> Seriously?! Not even an MTA programmer is reading most basic mail RFCs anymore?!?!
>> Yes, DMA might be a lightweight replacement for Postfix on machines just needing a better smarthost.
>> However, the commit above means DMA behaved RFC-ignorant as soon as a message had more than one
>> recipient - which apparently does not seem to happen that often to DMA users.
>> RFC 5321 is not about rocket science or some exotic corner cases at all, it is one of the most basic
>> internet standards regarding e-mail communication. We have lost the complexity battle years ago,
>> apparently, we cannot count on application programmers to have a slightest clue about what they are
>> doing as well.
>> I am shocked about the quality of that piece of software.
>> Embittered,
>> Peter Müller

[snip]

I have run Communicate Pro as our MTA for years, and it has a tendency to be RFC compliant to a fault, even occasionally breaking interactions with other widely available mail servers ([cough] Exchange [cough]) when those mail servers are not 100% compliant, and I can say that it doesn’t surprise me that this sort of thing would be out there. I suspect that most servers accept the mail when submitted the way that dma has been doing it up to now, but someone found a particular piece of software that refused to accept messages with multiple recipients because that is not RFC compliant, necessitating the fix.

At least the silver lining here is that they have identified and fixed the problem.

Tom