Simple Recipient Verification - once and for all
- From: scott.cressman@xxxxxxxxx
- Date: 29 Jan 2006 18:11:28 -0800
Hi all,
I know this topic has been dealt with alot on this list, and I know of
various solutions that have been put forward, but what I want to know
is the simplest way to perform recipient verification in sendmail, with
the following requirements:
1. No local mail - the server acts only as a relay for a number of
domains (ie/ test.com & example.com).
2. A textfile list of valid recipient addresses for both domains is
available for use in the appropriate sendmail file (ie/ access,
virtusertable, whatever).
3. The server must reject any RCPT TO address that is not in the
available list of valid recipient addresses, and relay any addresses
that are in the list to the appropriate downstream server (assume this
mapping is also known ahead of time ie/ test.com forwards to one
server, example.com to another).
Given these requirements, I'm wondering what the simplest solution is
to acheive this (essentially it's the same as using the
relay_recipients list in Postfix). I've seen the following solutions
suggested in the past, but none of them seem as staightforward as they
should be:
1. The relay-domains file: This is obviously not granular enough since
anything in the domain gets accepted and relayed.
2. Using the access list: This would be fine, but I can't get it to
work. Apparently the following entry should work:
To:scottc@xxxxxxxx RELAY
but for some reason it doesn't - I still get the following message when
testing:
rcpt to: scottc@xxxxxxxx
550 5.7.1 scottc@xxxxxxxxxxx Relaying denied
with the following log entry:
Jan 29 18:59:28 vm1 sendmail[29415]: k0U2xDb5029415:
ruleset=check_rcpt, arg1=scottc@xxxxxxxx, relay=192.168.99.19,
reject=550 5.7.1 scottc@xxxxxxxxxxx Relaying denied
though I've got the address in the access file as shown and an entry in
the mailertable that specifies where to forward mail from test.com. If
this worked, I would assume that would be the easiest way to acheive
what I'd like to do.
3. Using virtusertable + aliases: This works, but it feels like a hack
to me, since for a typical address that you'd just like to accept and
relay, you need to create some dummy intermediate value to link the
virtusertable entry to the aliases entry (or at least that's how I've
gotten it to work).
4. Using LDAP routing: I'm not using an LDAP server, so this seems
counterintuitive as well - I just want to have a list of valid users
for a specific domain!
There may be others that I've missed, but that's probably why I'm
sending this message. I'm just surprised that I haven't been able to
track down a very simple and straightforward way to do this with one or
two entries in the sendmail.mc and a textfile full of valid addresses.
Thanks,
.
- Follow-Ups:
- Re: Simple Recipient Verification - once and for all
- From: Claus Aßmann
- Re: Simple Recipient Verification - once and for all
- Prev by Date: Re: Cyrus virtual mailboxes and aliases.
- Next by Date: Re: Simple Recipient Verification - once and for all
- Previous by thread: collect: unexpected EOM...
- Next by thread: Re: Simple Recipient Verification - once and for all
- Index(es):
Relevant Pages
|
