This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Postfix message restrictions

Hello all,

Assuming users here run Puremessage for Unix and are running Postfix as the MTA I was wondering, Does anyone here implement addtional custom message restrictions to the stock Postfix config provided by Sophos?   We are getting a lot of forged spam coming from our own domain that isn't being picked up by Puremessage and we are considering implementing message restrictions.  I am aware that all these customizations will be non-supported and we are on our own with Postfix but just curious how many people here run the stock Postfix config.

Thanks

:1519


This thread was automatically locked due to age.
Parents
  • Hey mrdky,

    One thing to note, there is the "From:" and there is the "Envelope From:" that can be used in this test.  It would be best to use both of these within your test.

    Erric has touched on this with the test:

        # attr NAME=Check for fake senders
        if anyof(address :all :matches :comparator "i;ascii-casemap" ["from"]                                             

                   ["**xyz.com"],
        envelope :comparator "i;ascii-casemap" :all :matches ["from"]
                                                             ["**xyz.com"])
        {
            pmx_quarantine "Fake Sender";
            stop;
        }

    One other thing to note is that if you have external users connecting via SMTP Auth or some other mechanism, the internal/external host test may route them to the external policy and would quarantine their mail.

    You could do a dry run where you don't quarantine but simply mark the logs.  This will give you a better sense of how many of these emails are coming from outside trying to get in. 

    Using the following:

    pmx_mark1 "RULEHIT";

    ... in any tests, will populate the Policy Mark Hits report.  This is a great way to use PureMessage to custom reporting.  This is also a great way to verify your suspicions and put forward a sound and researched policy rule.

    :1623
Reply
  • Hey mrdky,

    One thing to note, there is the "From:" and there is the "Envelope From:" that can be used in this test.  It would be best to use both of these within your test.

    Erric has touched on this with the test:

        # attr NAME=Check for fake senders
        if anyof(address :all :matches :comparator "i;ascii-casemap" ["from"]                                             

                   ["**xyz.com"],
        envelope :comparator "i;ascii-casemap" :all :matches ["from"]
                                                             ["**xyz.com"])
        {
            pmx_quarantine "Fake Sender";
            stop;
        }

    One other thing to note is that if you have external users connecting via SMTP Auth or some other mechanism, the internal/external host test may route them to the external policy and would quarantine their mail.

    You could do a dry run where you don't quarantine but simply mark the logs.  This will give you a better sense of how many of these emails are coming from outside trying to get in. 

    Using the following:

    pmx_mark1 "RULEHIT";

    ... in any tests, will populate the Policy Mark Hits report.  This is a great way to use PureMessage to custom reporting.  This is also a great way to verify your suspicions and put forward a sound and researched policy rule.

    :1623
Children
No Data