Sendmail Jilter

Logged In: YES
user_id=343449

Need to use envrcpt instead of connect for the custom
status. The Sendmail MTA intentionally overrides custom
status codes on the connect callback.

Logged In: YES
user_id=6616

From the discussion on the mailing list:

I took a quick look at the Sendmail 8.13.2 source and saw the following
in sendmail/milter.c :

/*
** SMFIR_REPLYCODE can"t work with connect due to
** the requirements of SMTP. Therefore, ignore the
** reply code text but keep the state it would reflect.
*/

So the bottom line is I think what I was mumbling about before -- due to

the fact that the connect response is "well formed", the MTA is
restrictive about what can be put in here.

Final answer is "you can't customize the banner -- sorry".

Logged In: YES
user_id=343449

I did some additional testing and found out something
interesting:

If I put a custom status on the connect method of the
processor, I get the generic response:
reason: 554 jamm3.JAMMConsulting.com ESMTP not
accepting messages

But, when I put the custom status on the envrcpt method of
the processor, I get the rejection with the custom status
code.

It seems from this that the sendmail daemon on the sending
server is not correclty picking up the custom reply code on a
connect command to the remote daemon. I think this is a
bug in the sendmail code.

Logged In: YES
user_id=343449

I tried tracing through the jilter sources where it is generating
the custom status message and it looks like it is generating
correctly but the failure report still has a different response
code.

Could this be the sending mail server (sendmail on Fedora
Core 2) is over-riding the failure code? Why would it do that?

I have a test environment set up if you need to play with it.