Mistake in MailScanner.conf ?

Kevin Spicer kevins at BMRB.CO.UK
Sun Nov 9 19:29:20 GMT 2003

On Sun, 2003-11-09 at 18:20, Julian Field wrote: At 17:37 09/11/2003,
>I *think* what happens (would have to study the source to prove it) is

>Allow   Convert Actions
>Yes             Yes/No  None
>Disarm  No              Disarm affected tags
>Disarm  Yes             Stripped
>No              Yes             Stripped
>No              No              Blocked

So, the behavior has changed then....?  Previously setting No for the
allow actions blocked the mail completely.

Anyway, I'm seeing odd behavior with this on the latest snapshot.  I was
previously using a ruleset for the Allow... options like this.

From:   /^172\.1[6789]\./       no
From:   /^172\.2[0123456789]\./ no
From:   /^172\.3[01]\./ no
From:   192.168.        no
From: default           yes

(The RE's match the private address ranges which we use internally)

And I had Convert Dangerous... set to yes

This produced the following behaviour...
Incoming offending mail: stripped (so our users still get the mail)
Outgoing offending mail: returned to sender (so we don't send out stuff
other sites will strip)

I just installed the latest beta and just changed the last line of the
ruleset to...
From: default           disarm

(I left all other settings as they were.)

But I'm seeing incoming offending mail is now blocked. Any idea why?

More information about the MailScanner mailing list