Closed jailbird777 closed 4 years ago
RFC5321 section 4.1.1.3 https://tools.ietf.org/html/rfc5321#section-4.1.1 seems to explicitly require one address per RCPT TO, so it seems like the existing dma behavior is non-compliant.
please share your patch in a pull request. Why do we even have multiple RCPT TO? shouldn't the mail have been split up into multiple deliveries?
On 01/02/2020 07:24, jailbird777 wrote:
RFC5321 section 4.1.1.3 https://tools.ietf.org/html/rfc5321#section-4.1.1 seems to explicitly require one address per RCPT TO, so it seems like the existing dma behavior is non-compliant.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/corecode/dma/issues/73?email_source=notifications&email_token=AABLOO47VSNTWXWYQQDVDZTRAUITJA5CNFSM4KORG5DKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKQVUDY#issuecomment-580999695, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABLOO47ACXIHTD5GKPHSPDRAUITJANCNFSM4KORG5DA.
PR @ https://github.com/corecode/dma/pull/74
It looks like the only splitting is when sending to different multiple hosts. In the case of multiple addresses to the same MX or using smarthost, it doesn't appear that it's normally split up.
Looks like Netscape/Sun/iPlanet/Oracle SMTP server doesn't like multiple addresses in a RCPT TO: line. Eg, it'll completely reject:
RCPT TO:addr1@example.com,addr2@example.com,addr3@example.com
But it WILL accept multiple RCPT TO:'s with one address each, eg:
RCPT TO:addr1@example.com RCPT TO:addr2@example.com RCPT TO:addr3@example.com
it looks like sSMTP does the multiple RCPT TO thing, probably for the same reason (or maybe so that it can tell which addresses get accepted and which don't?): https://github.com/ajwans/sSMTP/blob/master/ssmtp.c#L1642
I did the same basic hack locally to dma to make it work the same way, pull out a nasty strtok() for a comma :(.