1

Topic: logwatch for mail went to spam?

==== Required information ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- Related log if you're reporting an issue:
====
Any clue why this would go to spam? figured if anything would be safe it would be it's own report.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: logwatch for mail went to spam?

We need SpamAssassin scan result. Could you please update Amavisd setting to get it?
FYI: http://www.iredmail.org/docs/no.x-spam.headers.html

3 (edited by Lexa83 2016-10-13 18:24:58)

Re: logwatch for mail went to spam?

X-Virus-Scanned: Debian amavisd-new at mydomain.com
X-Spam-Flag: YES
X-Spam-Score: 1.95
X-Spam-Level: *
X-Spam-Status: Yes, score=1.95 tagged_above=-100 required=1.55
    tests=[BAYES_00=-1.9, NO_RELAYS=-0.001, URIBL_ABUSE_SURBL=1.25,
    URIBL_BLOCKED=0.001, URIBL_DBL_SPAM=2.5, URIBL_SBL_A=0.1]
    autolearn=no autolearn_force=no

4

Re: logwatch for mail went to spam?

When you get a new logwatch email which is marked as spam, check its mail headers. Header like below will tell you why it's considered as spam:

X-Spam-Status: Yes, score=1.95 tagged_above=-100 required=1.55
    tests=[BAYES_00=-1.9, NO_RELAYS=-0.001, URIBL_ABUSE_SURBL=1.25,
    URIBL_BLOCKED=0.001, URIBL_DBL_SPAM=2.5, URIBL_SBL_A=0.1]