> On 14 Jan 2015, at 20:10, Robert Blayzor <rblayzor.bulk@???> wrote:
>
> When using LTMP transport for delivery, what happens if LMTP kicks back an error condition to Exim? For instance in the following LTMP conversation:
There are two ways to do LMTP delivery with exim: with the LMTP transport, or with the SMTP transport in LMTP mode. Either way, by the time you’re delivering the email, it’s too late to reject it. If you can’t deliver it, your options are to (a) queue it and try again later, (b) queue it frozen, (c) drop the message, (d) generate a bounce message, (e) deliver it somewhere else.
The exception would be if you’re using cutthrough delivery, which is available only when there is a single recipient.
PRDR might change all this, if the connecting server is using PRDR.
NB:
http://www.exim.org/exim-pdf-current/doc/spec.pdf isn’t the current documentation: it’s still at 4.82. The PDF documentation is available at
ftp.exim.org
> => LHLO ...
> <= 250 OK
> => MAIL FROM:<>
> <= 250 OK
> => RCPT TO:<user@???>
> <= 250 OK
> => DATA
> <= 354 OK
> => ... <message> ...
> => . <cr><lf>
> <= 550 rejected
>
>
> What exactly happens? Is a SMTP error (4xx or 5xx) generated back to the sending MTA or is it to late by then?
>
> If it's too late to return an SMTP error, does Exim handle the 4xx and 5xx at LMTP differently? Meaning a 5xx would generate a bounce and a 4xx would be queued for later delivery attempts?
>
>
> --
> Robert
> inoc.net!rblayzor
> http://inoc.net/
>
>
>
>
> --
> ## List details at https://lists.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://wiki.exim.org/
--
Ian Eiloart
Postmaster, University of Sussex
+44 (0) 1273 87-3148