Re: LDAP_ROUTE feature with access db
- From: Andrzej Adam Filip <anfi@xxxxxxx>
- Date: Sat, 10 Nov 2007 12:31:50 +0100
Jim McCullars <jim@xxxxxxxxxxxxx> writes:
Greetings:
We make extensive use of the LDAP_ROUTE feature of sendmail to
allow our users to have firstname.lastname@xxxxxxx email addresses
when their username on our email server (Solaris) can have only
eight-character usernames. This has worked well for us but I have
noticed one thing not working as I expected and wondered if this
was a bug or just the way it works.
When someone leaves, we will disable their email account and
prevent them from receiving new messages by putting something like
this in the access file:
To:vanilla1@ REJECT
before actually deleting their account. But what I found is that if
mail is routed to that host and the address has an LDAP_ROUTE domain
and the lookup resolves to that address, it will deliver anyway. [...]
Have you considered using
* aliases to mark invalid addresses
* virtusertable to specify custom error message
aliases file:
vanilla1: no-longer-valid@xxxxxxxxxxxxxxxxxxxxx
virtusertable:
no-longer-valid@xxxxxxxxxxxxxxxxxxxxx error:nouser No longer valid email
In short: AFAIK access checks email presented in "RCPT TO:" command in
SMTP session.
--
[pl>en: Andrew] Andrzej Adam Filip : anfi@xxxxxxxxxxxx : anfi@xxxxxxxx
Open-Sendmail: http://open-sendmail.sourceforge.net/
.
- Follow-Ups:
- Re: LDAP_ROUTE feature with access db
- From: Jim McCullars
- Re: LDAP_ROUTE feature with access db
- References:
- LDAP_ROUTE feature with access db
- From: Jim McCullars
- LDAP_ROUTE feature with access db
- Prev by Date: Re: LMTP not adding domain
- Next by Date: Re: LMTP not adding domain
- Previous by thread: Re: LDAP_ROUTE feature with access db
- Next by thread: Re: LDAP_ROUTE feature with access db
- Index(es):
Relevant Pages
|
|