|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: mouss (mlist.only
free.fr)
Date: Wed Aug 15 2007 - 19:16:33 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
John Thomas wrote:
>> If you want per sender check, then there is no need for a restriction
>> class. just use smtpd_sender_login_maps.
>
> [Embarrassed that I should know this] Does the above mean:
>
> 1. Add reject_sender_login_mismatch into smtpd_sender_restrictions.
> 2. Add smtpd_sender_login_maps = hash:/etc/postfix/restrict_senders
> 3. Into /etc/posfix/restrict_senders, put ? I don't know what to put,
> sorry.
>
while there is no example in
http://www.postfix.org/postconf.5.html#smtpd_sender_login_maps
you can get the answer by seeing that the search is performed on an an
email address and that the "result ... or a list of SASL logins ...".
Anyway:
the left-hand side (the key) is an email address. the right-hand side
(result) is a list of logins.
for example:
jjj
domain.example joe,jim,jane
- You'll only rarely need more than one login in the RHS.
- for local domains (mydestination), you can omit the '
domain.example'
part.
Depending on your setup, you may have a list like this:
# local domain setup
joe joe
jane jane
jim jim
or
# virtual domain setup
joe
domain.example joe
domain.example
jane
domain.example jane
domain.example
jim
domain.example jim
domain.example
In either case, you can generate the map with a script. If you have a
mysql server running, you can make it generate the "identity" for you
(whether you use mysql to store users or not!).
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]