OT: Modified access and relay-domains file, still get 550 5.7.1

[Kai Schaetzl]

Chris W. Parker wrote on Thu, 24 May 2007 15:41:10 -0700:

> Having said all that, email appears to be flowing normally even though I
> commented the swatgear.com REJECT line. I guess there's something to be
> said about my documentation practices but for now is there anything that
> you can think of that might have been messed up by me commenting that
> line in /etc/mail/access?

Looking a second time at your list I now understand why you did that.
You want to reject mail to non-existing users @swatgear.com and REJECT all 
mail to it and then build an OK list from AD. I didn't really notice that 
part of your message the first time.
*Now* there's obviously a chance that you get mail for existing local 
users that should not get mail as the general blockage is gone.

Probably there was no OK for swiftmail at swatgear.com and so it got rejected 
at the check_mail (from) stage.

I'm not sure if the way you do it is optimal and works in all cases. I may 
be wrong but I believe that using a construct like

somedomain.com REJECT
someaddress at swatgear.com OK

will likely *reject* mail from somedomain.com to someaddress at swatgear.com 
as there is no way for sendmail to know which of the two should have 
priority.

Using

swatgear.com REJECT
someaddress at swatgear.com OK

as you do should encounter the same problem. It may work because usually 
the swatgear.com address will be in the rcpt to *only* and sendmail then 
overrides the REJECT with the OK. But you were getting *mail from* 
swiftmail at swatgear.com to swatgear.com and then the priority problem hits.

There are extensions to the access.db like "Spam: Friend" that assure that 
mail gets always delivered.

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com