🚀 go-pugleaf

In article <5i3osh$9r@squiznet.demon.co.uk>,
paulc@squiznet.demon.co.uk (Paul Colclough) wrote:

> Alan Staniforth (alan@bones.demon.co.uk) wrote:
> 
> : If I were to scan the body DATA for possible bounce targets during recipt 
> : of a message and get a hit, given that 554 is given as an allowable 
> : failure response to DATA, I suppose the correct way to bounce would be:
> 
> : 554 Transaction failed
> 
> : sent after receipt of the <CR><LF>.<CR><LF> terminating the DATA.
> 
> If your bouncing after receiving the terminating dot, then you've allready
> received the message so what would be the use in deleting it? You might as
> well load it into your favourite mail reader and delete from there.

Although I phrased my question in terms of a kill file hit, the original 
thought (as I've just mentioned in another follow-up) was to do with how to 
handle mail that had a malformed RFC 822 header. This may seem a minor 
point, but as my server may be acting as a mail relay or passing mail onto 
third party code modules for handling there may be benefits in guarantying 
that headers in forwarded/delegated messages are valid. The mail kill 
possibilities only struck me later.

-Alan.

-- 
Alan Staniforth ** alan@bones.demon.co.uk ** alan_s@cix.compulink.co.uk
"Meum est propositum/In taberna mori,/Ut sint vina proxima/Morientis ori."
       -- Anon.