1 # CHUNKING transmission, short messages, PIPELINING
25 MAIL FROM:<sender@source.dom>
35 # Error case: server wrongly expected more data, client gets timeout for data-ack
36 # XXX This is a problem with data/quit pipelining. The succeeding SMTP command cannot
37 # be distinguished from the data, by the errroneous server.
38 # Of course, we could avoid such pipelining on the client side, when BDAT is used.
39 # But - is this any worse than a server failing to spot the data-dot under DATA?
40 # I think not; both are culpable, and there is only so much the client can do.
55 #MAIL FROM:<sender@source.dom>
65 # Error case: server wrongly expected less data
66 # client get the data-ack, sends quit - but server
67 # sees a munged quit due to the outstanding data tail
86 MAIL FROM:<sender@source.dom>
96 # server rejects MAIL cmd
97 # transport coding does not handle the possible RSET-and-another transaction,
109 550 unacceptable mail-from
110 550 rcpt ungood lacking mail-from
111 500 bdat ungood lacking mail-from
117 MAIL FROM:<sender@source.dom>
127 # server tmp-rejects MAIL cmd
138 450 greylisted mail-from
139 550 rcpt ungood lacking mail-from
140 500 bdat ungood lacking mail-from
146 MAIL FROM:<sender@source.dom>
156 # server rejects RCPT cmd
168 550 no such recipient
175 MAIL FROM:<sender@source.dom>
186 # server rejects BDAT cmd
205 MAIL FROM:<sender@source.dom>
215 # server tmp-rejects BDAT cmd
228 400 not right now bdat
234 MAIL FROM:<sender@source.dom>