On Wed, 5 Nov 1997, Rahul Dhesi wrote:
> No need to supply any of the message headers -- let the smtphook
> function do its own parsing as needed, reading from the message file.
Nope. The headers are not held in the body file. At all points you are
talking about, they are only in store.
> Any time smtphook() returns with a non-zero value, we take this to mean
> that we should reject the message with a 500 series code, and print
> contents of 'text' as the error string.
Note (as I have said many times) that giving a 5xx code after the final
"." that terminates the data does *not* stop certain MTAs from trying to
send the message again. The only sure stop is 5xx after RCPT TO, I find.
There are other complications: SMTP input doesn't always come from a
remote host. There may be no host name or IP address. Also, anything
designed now has to cope with IPv6 as well as IPv4 addresses. An
unsigned long isn't good enough.
OK, what I'm raising are specifics; what I'm trying to say is that I
don't think it is quite as easy as it might sound. I have put the
suggestion on the list, but the list is very long and my judgement at
the moment is that there are other things I ought to be working on
first. There are only so many hours in the day...
Philip
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
--
* This is sent by the exim-users mailing list. To unsubscribe send a
mail with subject "unsubscribe" to exim-users-request@???
* Exim information can be found at http://www.exim.org/
