Ohai,
The latest snapshot has a few new features you will want to look at, and
make sure they do not introduce regressions.
Eric has implemented hostnames mapping for "listen", which allows you to
do the following:
table myname { 192.168.1.1 = mx1.x.y, 192.168.1.2 = mx2.x.y }
listen on all hostnames <mynames>
and OpenSMTPD will use the mapping to know what name to print in the
welcome banner depending on the address the client connect to:
220 mx1.x.y ESMTP OpenSMTPD 220 mx2.x.y ESMTP OpenSMTPD
While at it, he renamed "helo" to "hostnames" in relay rules for clarity
purposes as the same mapping may be used in both listen and relay rules.
I have implemented negations in rules so that some use-cases which were
not possible before can be implemented now.
Negations allow you to:
accept from local [...] # accept mail from localhost
accept from ! local [...] # accept mail from any BUT localhost
accept from ! <blacklist> [...] # accept mail from addresses not in
# table <blacklist>
It also works on tags:
accept tagged ! DKIM [...]
sender:
accept sender ! "@opensmtpd.org"
and destinations:
accept for ! domain opensmtpd.org [...]
Of course it can be chained and/or used on reject rules too:
# reject senders from domain opensmtpd.org if not local
#
reject from ! local sender "@opensmtpd.org" for any
# accept to relay from any address NOT in blacklist and
# for any domain BUT foobar.org
#
accept from ! <blacklist> for ! domain foobar.org relay
Voila, let us know how it goes for you
--
Gilles Chehade
https://www.poolp.org @poolpOrg
--
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]
