|Griffiths, Jon||Jul 24, 2001 7:28 am|
|Sam Varshavchik||Jul 24, 2001 2:56 pm|
|Daniel Roesen||Jul 24, 2001 4:21 pm|
|Oliver Blasnik||Jul 25, 2001 12:44 am|
|Griffiths, Jon||Jul 25, 2001 2:33 am|
|Griffiths, Jon||Jul 25, 2001 2:56 am|
|Daniel Roesen||Jul 25, 2001 3:30 am|
|Xavier Beaudouin||Jul 25, 2001 3:41 am|
|Sam Varshavchik||Jul 25, 2001 4:46 am|
|Oliver Blasnik||Jul 25, 2001 7:30 am|
|Daniel Roesen||Jul 25, 2001 8:29 am|
|Griffiths, Jon||Jul 25, 2001 10:00 am|
|Sam Varshavchik||Jul 25, 2001 2:15 pm|
|Oliver Blasnik||Jul 25, 2001 2:58 pm|
|Subject:||[courier-users] Re: Unknown User = EX_TEMPFAIL??|
|From:||Griffiths, Jon (Jon....@sunrise.net)|
|Date:||Jul 25, 2001 2:33:33 am|
Thanks. This is a good point, and I will check it over. The most likely reason is that I have not configured the LDAP rules properly for this function in the test layout. It currently uses just the standard Sendmail 8.11.4 rules at the moment, which provide for LDAP mail routing, not user identification. Obviously it will be easy enough to put a sendmail lookup for each individual user in to my m4 config. However I would like the back up from the LDA being able to bounce for the same reason, and not return what appears to be an incorrect error code. I have always tried to keep Sendmail out of the user id function, since it is supposed to do the MTA work, and not delivery. This is for a big rollout, with some very unique requirements :-(. I will understand a good reason for not amending maildrop to make this bounce, I just do not understand why it reported EX_TEMPFAIL, when the error is clearly fatal. Perhaps I am missing something.
I will follow your comments, and change the system structure to perform this check, on the relevant box, at reception time, however I would really appreciate an explanation for this behaviour in maildrop. I do not like having to mod the source code for an application, it brings everything closer to being unsupportable by the team who will follow me, and represents a divergence from the version control you are performing, albeit in this instance a very small one. Not to mention making the documentation more complicated!
-----Original Message----- From: Sam Varshavchik [SMTP:mrs...@courier-mta.com] Sent: Tuesday, July 24, 2001 11:57 PM To: 'cour...@lists.sourceforge.net' Subject: [courier-users] Re: Unknown User = EX_TEMPFAIL??
Griffiths, Jon writes:
However, this is the crux of the matter. If I get an incorrectly addressed user, with the correct domain, I get this in the logs:
Jul 24 13:56:52 jon maildrop: Invalid user specified. Jul 24 13:56:52 jon sendmail: f6OANx626166: to=<comp...@XXYY.com>, delay=01:32:53, xdelay=00:00:00, mailer=local, pri=392405, dsn=4.0.0, stat=Deferred: local mailer (/usr/local/bin/maildrop) exited with EX_TEMPFAIL
Now it seems to me that maildrop is not presenting the correct error code for invalid user.
If it's an invalid user, why did you mail server accept the message for delivery in the first place?
If this is a nonexistent mailbox, the mail server should refuse to accept the message, and return it as undeliverable, and maildrop should not even be run.