A BUGNOTE has been added to this bug. ====================================================================== http://www.dbmail.org/mantis/bug_view_advanced_page.php?bug_id=0000212 ====================================================================== Reported By: sty Assigned To: ====================================================================== Project: DBMail Bug ID: 212 Category: LMTP daemon Reproducibility: always Severity: trivial Priority: normal Status: new ====================================================================== Date Submitted: 02-Jun-05 06:39 CEST Last Modified: 02-Jun-05 09:25 CEST ====================================================================== Summary: lmtp doesn't conform RFC on return code after DATA Description: After DATA, lmtp replies with "215 Recipient <[EMAIL PROTECTED]> OK" when the correct response would be "250 OK".
Although the RFC implies that the server "interpret only the first digit of the reply and MUST be prepared to deal with unrecognized reply codes by interpreting the first digit only." Anyways, not all servers are prepared to deal with non-standard return codes and crash/barf, which I found out with the DSpam LMTPd (fixed now in cvs of dspam). ====================================================================== ---------------------------------------------------------------------- paul - 02-Jun-05 09:25 CEST ---------------------------------------------------------------------- I don't get it. The title of the bug reports states that dbmail-lmtpd doesn't conform to the RFC, whereas the report indicates it's dspams that didn't adhere. Where's the bug here??? RFC821 is very clear on this issue, but maybe I'm looking at the wrong section. Aaron?? Bug History Date Modified Username Field Change ====================================================================== 02-Jun-05 06:39sty New Bug 02-Jun-05 09:25paul Bugnote Added: 0000721 ======================================================================
