mail-in-a-box / mailinabox

Mail-in-a-Box helps individuals take back control of their email by defining a one-click, easy-to-deploy SMTP+everything else server: a mail server in a box.
https://mailinabox.email/
Creative Commons Zero v1.0 Universal
13.99k stars 1.44k forks source link

Ability to whitelist domain or email in system UI #1192

Closed geekafy closed 7 years ago

geekafy commented 7 years ago

Hi Guys,

I would be great to have the ability to whitelist a domain or email in the system UI. Until then, is there another way to do this?

I have a legit email that always go to spam.

Thanks!

(I'm loving mail-in-a-box!) :-)

wioxjk commented 7 years ago

There is always a reason that emails is placed in the spamfolder thou :)

geekafy commented 7 years ago

Yep, agreed! But my kid's camp coordinator does not spam me. :-)

wioxjk commented 7 years ago

Just curious, why does the message go to spam? What does your logs say?

geekafy commented 7 years ago

No clue, will take a look, where is the log situated?

wioxjk commented 7 years ago

/var/log/mail.log I think

geekafy commented 7 years ago

Just checked, nothing in the logs :-(

yodax commented 7 years ago

Check the headers of the email. That should contain more information. Also moving the mail from spam to inbox should train the filter. Setting a rule for the from address in roundcube should work as a whitelist I think.

geekafy commented 7 years ago

Here are the headers below. It's interesting what I found.... the sender has a gmail account but the mail is sending from what looks like a VPS from GoDaddy who's IP was flagged... The camp must be using some sort of hosted management system that sends out mail on the camps behalf....

How... I doubt they will change anything on their end... Will the creations of filters in RoundCube teach the server to not flag as spam even when I'm usually using IMAP to get my email?


X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on box.xxxxxxxx.com X-Spam-Flag: YES X-Spam-Level: ***** X-Spam-Status: Yes, score=5.4 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, FREEMAIL_FROM,FROM_LOCAL_NOVOWEL,HK_RANDOM_FROM,HTML_MESSAGE, HTML_MIME_NO_HTML_TAG,MIME_HTML_ONLY,NML_ADSP_CUSTOM_MED,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.0 X-Spam-Report:

wioxjk commented 7 years ago

Whoever the genius who did it... They are propably sending out BULK emails, and therefore they are getting blacklisted,

tbhi commented 7 years ago

Might work for you to create extra spamassassin config, e.g.

$ cat /etc/spamassassin/local2.cf whitelist_from example@example.org

$ /etc/init.d/spampd restart

geekafy commented 7 years ago

OK so based on what was mentioned by stan3, I got some documentation from https://wiki.apache.org/spamassassin/ManualWhitelist

I added the following code to the bottom my global config file /etc/mail/spamassassin/local.cf

# whitelist:
whitelist_from  name@email.com

If you want to add multiple addresses, you just add a space and add the following one right after.

# whitelist:
whitelist_from  name@email.com name2@email.com

It is important to run /etc/init.d/spampd restart after you save the file to enable the changes.

The old "spam" email comes right in the inbox.

This is what is now in the headers:

X-Spam-Report: 
    * -100 USER_IN_WHITELIST From: address is in the user's white-list
    *  0.0 SPF_HELO_FAIL SPF: HELO does not match SPF record (fail)
    *      [SPF failed: Please see http://www.openspf.org/Why?

Thanks for the help!