Opened 12 months ago

Last modified 12 months ago

#13633 assigned Bug/Something is broken

Greylisting issue

Reported by: Thiago de Mello Bueno Owned by: JaimeV
Priority: Medium Component: Tech
Keywords: Cc: Jamie McClelland
Sensitive: no



I've recently had some issue receiving emails from some groups I'm a member of. I imagine it has something to do with greylisting, and their servers not retrying on failed attempts after 30 mins.

The speicifc email was from the north brooklyn boat club from the domain '' sent on Apr 11, 2018 at 9:26 PM but there are possibly other wildapricot addresses and other groups I simply didn't know about. Can we white list these? and check to make sure we're not filtering out others?

I appreciate efforts to reduce span, but doesn't the greylisting policy go against the "I have the right to receive every message sent to me" declaration in Mayrfirsts "organic internet" treatise (found a copy on the street last fall!)

Hope alls well, T

Change History (4)

comment:1 Changed 12 months ago by JaimeV

Cc: Jamie McClelland added
Owner: set to JaimeV
Status: newassigned

Hi T, Greylisting works because normally only spam servers will give up after one delivery attempt. In the logs I see only 4 attempts to deliver mail from that domain in the past week. Two attempts were greylisted and each subsequent attempt passed.

The e-mail related DNS entries for that domain are assigned to google servers. Normally those servers would retry after being greylisted once. However the mail server being used to deliver mail from that domain identifies as client Also it is using a different ip address every time so I'm not sure if adding to an exception list is an option here.

comment:2 Changed 12 months ago by Jamie McClelland

Resolution: fixed
Status: assignedfeedback

Wow - glad to hear that the organic internet is still in circulation :) and yes you should receive all the email that is sent to you!

Email senders that will attempt redelivery from multiple IP addresses fall through the grey listing cracks and really suggest that we may need to give it up at some point (or figure out how to patch postgrey so that it treats email sent from different sub-domains of the same domain as the same IP address).

But fortunately, postgrey does allow us to maintain a local clear list using regular expressions (that's how we get around the problem Jaime identifies) - so I just added (and all subdomains) after I saw that it redirects to wildapricot.

I've pushed these changes to rose and restarted postgrey so hopefully these messages won't get delayed again.

comment:3 Changed 12 months ago by Thiago de Mello Bueno

Resolution: fixed
Status: feedbackassigned


Strangely another one seemed to slip by "Failure text: 450 4.1.8 <>: Sender address rejected: Domain not found"

It's likely a mess of ip addresses, and reply to's but would love to clear it up. Emails sent from the "Events" automated module seem to go through, but those sent from email templates bounce. I suppose that has more to do with the way wildapricot is configured than with the m1 servers but any whitelisting we can do to circumvent the issue would be well appreciated.

comment:4 Changed 12 months ago by Jamie McClelland

Can you share the full error message? I think this is a different problem.

I can't be sure - but it appears that you tried to send an email to <>, relayed through our servers, but rejected the message because the from address had a domain name that is not a registered domain name. Or maybe it was our server that rejected it for that reason? Can you tell from the error message what the From address was?

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.