I've run into a problem when trying to implement LMTP deliver from
dspam... the problem seems to be quite simple, dbmail returns code
215 at the end of the communication and dspam expects to get 250.
IMO 215 is also right answer, but would there be a way to stab the
sources (I'm not a programmer myself so...) so that dbmail would just
return the 250 and make dspam happy?
debug from dspam:
--clip--
39944: [06/01/2005 15:30:15] RECV: 220 vanessa.blosphere.net DBMail
LMTP service ready to rock
39944: [06/01/2005 15:30:15] SEND: LHLO localhost
39944: [06/01/2005 15:30:15] RECV: 250-vanessa.blosphere.net
39944: [06/01/2005 15:30:15] RECV: 250-PIPELINING
39944: [06/01/2005 15:30:15] RECV: 250-ENHANCEDSTATUSCODES
39944: [06/01/2005 15:30:15] RECV: 250 SIZE
39944: [06/01/2005 15:30:15] SEND: MAIL
FROM:<[EMAIL PROTECTED]> SIZE=1469
39944: [06/01/2005 15:30:15] RECV: 250 Sender
<[EMAIL PROTECTED]> OK
39944: [06/01/2005 15:30:15] SEND: RCPT TO:<[EMAIL PROTECTED]>
39944: [06/01/2005 15:30:15] RECV: 250 Recipient
<[EMAIL PROTECTED]> OK
39944: [06/01/2005 15:30:15] SEND: DATA
39944: [06/01/2005 15:30:15] RECV: 354 Start mail input; end with
<CRLF>.<CRLF>
39944: [06/01/2005 15:30:15] SEND:
.
39944: [06/01/2005 15:30:16] RECV: 215 Recipient
<[EMAIL PROTECTED]> OK
39944: [06/01/2005 15:30:16] Invalid data waiting for code 250: 215
Recipient <[EMAIL PROTECTED]> OK
39944: [06/01/2005 15:35:09] Got error 215 in response to message
data: 215 Recipient <[EMAIL PROTECTED]> OK
--clip--
or should the lines
39944: [06/01/2005 15:30:15] RECV: 250 Recipient
<[EMAIL PROTECTED]> OK
and
39944: [06/01/2005 15:30:16] RECV: 215 Recipient
<[EMAIL PROTECTED]> OK
be reversed?
since RFC says:
X.1.5 Destination address valid
This mailbox address as specified was valid. This status code
should be used for positive delivery reports.
shouldn't this be the answer to the earlier 'Recipient' line?
--
br,
Sty
