Quey wrote:
DAve wrote:
I discovered something interesting the other day, something I really
should have been paying attention to earlier.
It would seem I cannot get an abuse address to work using qmail
aliases in the /var/qmail/alias directory. Of course vadddomain does
not create them for
Hello here is something very strange I have seen this morning.. I have
dspam and tmda and when I looked a the logs of tmda this domain did not
even showed up downloadsapple.com but I found the info in the smtp logs
listed below so my question is how to prevent this one to come through?
Does anyone
So you add all your new domains by hand ?? most of us have
intergrated systems and something central that connects and doe sit all,
be it a local custom CRM or one of the off shelf ones, so everything is
linked, maybe you should be writing a wrapper :)
DAve wrote:
Quey wrote:
DAve
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 affect
Trey Nolen wrote:
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 us
I would suggest starting another instance of qmail-smtpd on port 587 that
does not use the rbls, and has its own tcp.submpt.cdb that allows anyone
to connect, but does not ever set RELAYCLIENT. This allows all addresses,
but will only allow relay for authenticated users.
Port 587, is the defa
On 8/17/2007 9:13 PM, Trey Nolen wrote:
being affected by the rblmtpd? For instance, is there a way to pass a
variable to tcpserver if the connection is authenticated via smtp-auth?
Not without patching. the process goes like this:
user -> tcpserver -> rblsmtpd -> qmail-smtpd (with smtp-auth)
