We have been using smtp-after-pop for a long time, but are also using
smtp-auth for some purposes. When users authenticate via POP, a line like
the following gets added to open-smtp:
ww.xx.yy.zz:allow,RELAYCLIENT="",RBLSMTPD="",WHITELIST="" 1187395788
This keeps the users from being affected by rblsmtpd.
We added sorbs to our rblsmtpd to block "dynamic IP pools", but it seems to
be blocking our users that use smtp-auth. Our smtp-after-pop users work
fine using the same dynamic IPs. We have some users that need to be able
send via our servers but that do not have a POP account to authenticate
against. Is there a way to get smtp-auth excluded from the rblsmtpd blocks?
Trey Nolen
