Best approach to "whitelist" Precedence: bulk mails

(Carlo Kok) #1

Normally I’m fine with the filters discourse has setup to avoid posting data for maillings, however how would I best approach allow discourse to create a post anyway with a “Precedence: bulk” header set for a specific domain?

The reason I’m asking, one of our resellers is sending all mails with mandril and has a Precedence: bulk header set which doesn’t get posted as a discourse app. We obviously do want to deal with these mails, anyone have an idea on what best to do here?

(Régis Hanol) #2

I will be adding a new setting today to deal with that specific issue. Instead of rejecting “auto generated” emails, they will be marked as such but will be processed like any other emails.

6 Likes
(Michael Downey) #3

Cool! But hopefully this doesn’t mean the return of “out of office” replies. :wink:

(Régis Hanol) #4

It’ll be a site setting. But we’re experiencing about 50% false positives and want to feel the pain in order to understand it more.

1 Like
(Jared Needell) #5

So to confirm this is related to Google Apps as well,

User sends an email to an email address and the mail gets flagged as “Email::Receiver::AutoGeneratedEmailError”

(Jared Needell) #6

Also is there a feature not send reject emails for the auto-generated stuff? I think it causes confusion when an out of office email gets caught.

(Sam Saffron) #7

You should configure bounce email, cause that should eliminate the majority

1 Like
(Michael Downey) #8

Not entirely sure I follow what you’re suggesting…

(Sam Saffron) #9

See

Most software sends out of office replies to the return path, some does not

1 Like
(Régis Hanol) #10

Here’s the new block_auto_generated_emails site setting (defaults to true) :e-mail:

4 Likes
(system) automatically bumped #11
(Jeff Atwood) closed #12