rectly. It's like the MX lookup I want to see
happen never took place so I can satisfy the conditions for the table
lookup.
Is the "smtpd_check_recipient_mx_access" more for incoming connections
rather than outgoing mails?
Any ideas or suggestions? Googles on the subject aren't being very
fruitful on
s a good basic reference for a Python
n00b? I am even tendering the thought of just ditching this thing in
favor of writing a script in a language I do know, Perl.
Thanks.
--Ian.
--
Ian R. Justman
UNIX hacker. Anime fan. Any questions?
ianj (at) ian-justman.com
sages (spam/virus/banned
attachments) to kill messages dead in their tracks during the SMTP
sesssion. As such, I will have to change to something like D_DISCARD so
I can keep my mail queue clean.
Any thoughts?
Thanks!
--Ian.
--
Ian R. Justman
UNIX hacker. Anime fan. Any questions?
ianj (at
Ian R. Justman wrote:
Sahil Tandon wrote:
See the example here, in particular the section that begins with "If
for some reason SASL users connect to port 25":
http://www200.pair.com/mecham/spam/bypassing.html#10
The example is specific to amavisd-new as a content_filter but you
ad on the system.
--Ian.
--
Ian R. Justman
UNIX hacker. Anime fan. Any questions?
ianj (at) ian-justman.com
Sahil Tandon wrote:
Ian R. Justman <[EMAIL PROTECTED]> wrote:
I'd like to know whether it is possible to bypass content_filter
based on whether someone has authenticated via SASL.
If users authenticate via the submission (587) port, you can modify the
service in master.cf wit
is one because of possible ways of subverting this setup, but that's a
risk I'm willing to take.
Thanks!
--Ian.
--
Ian R. Justman
UNIX hacker. Anime fan. Any questions?
ianj (at) ian-justman.com
