Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 948 views
  • Users 0 members are here
Options
Suggested
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

ASL tagging all Pattern Up2Date messages as *SPAM*

WLK
I have different email filtering rules that seperate messages sent by my firewall (Executive reports, Pattern Up2Date messages, etc.) and spam into different folders.  Everything worked fine at first.  Then, after several months, most (but not quite all) of the Executive Reports and Pattern Up2Date message starting showing up marked as spam (i.e., in the wrong folder).

I searched the ASL forums, and on the advice I found, I inserted by external WAN IP address (Network, Interfaces) in my Spam Sender Whitelist (Proxies, POP3).  Unfortunately, that worked for a short while and then reverted back.

Any ideas?

Thanks in advance.

P.S.  I'm currently running ASL 6.201, although this problem has been haunting me for a while.


This thread was automatically locked due to age.
Parents
  • 0
    Why are they marked as spam? The Spam-Score listing should be in the header of the mail.
  • 0 in reply to NimmdirKeks
    Here's the information from the Pattern Up2date messages:

    Subject:  *SPAM*[my firewall's name][INFO-361] Pattern Up2Date succeeded: Virus Protection Pattern Up2Date installed

    X-spam-score:  3.7(+++)
    X-spam-report:  2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address [00.00.000.00 listed in dnsbl.sorbs.net] 1.7 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP [00.00.000.00 listed in combined.njabl.org] ==============

    The message for Executive reports is only slightly different

    Subject:  *SPAM*[my firewall's namel][INFO-720] Executive report

    X-spam-score:  3.8(+++)
    X-spam-report:  0.1 HTML_TAG_EXIST_TBODY BODY: HTML has "tbody" tag 0.0 MIME_HTML_ONLY BODY: Message only has text/html MIME parts 2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address [00.00.000.00 listed in dnsbl.sorbs.net] 1.7 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP [00.00.000.00 listed in combined.njabl.org] ==============

    (firewall name and WAN IP removed)
  • 0 in reply to WLK
    I was able to eliminate the problem by increasing the Pass value -- it really should be called the Warn value -- from "3 (aggressive)" to "5 (reasonable)".

    I know my solution works, although it may let more spam in.  But is it the best solution?
  • 0 in reply to WLK
    They should enter a Spam-Sender Whitelist in the POP3 Proxy
Reply Children
No Data
Cookie Information Banner