On Saturday, April 25, 2020 at 8:22:46 PM UTC-3, Michael Orlitzky wrote: > > Can we please change how our Trac notification emails are sent? SendGrid > is absolutely atrocious. I currently have six of their shared IPs > whitelisted on our mail server to allow these notifications through, > because they would otherwise be blocked by the many many many blacklists > that SendGrid is always on for sending spam. Here are those IPs, and the > number of blacklists that they're on right now (it fluctuates). > > Six blacklists: > > https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a167.89.100.130 > https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a167.89.100.175 > > Four blacklists: > > https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a167.89.100.176 > > Three blacklists: > > https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a167.89.100.129 > https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a168.245.72.219 > https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a198.21.6.101 > > Those are all IPs that are actively sending Trac notifications. There > are two problems with this: > > 1. I don't want to be whitelisting spammers on our mail server. > > 2. Every once in a while, SendGrid will pick a new IP to start > sending Trac notifications from, and the only way I know to > whitelist them is that I start missing important notifications. > > It's impossible to do worse than this with a five-minute outgoing-only > local postfix instance. You get a PTR record for the server, make sure > it's not on any blacklists, and pick one poor sucker to receive the > "bounced" mail (when someone's Trac email address stops working, we need > to know and disable it). You might get rate-limited by Microsoft/Gmail > at first (what kind of volume are we talking about?), but those > notifications won't get lost forever, and that problem eventually > corrects itself unlike this one. And it's free. > > Here's the entire postfix main.cf for such an instance: > > compatibility_level = 2 > inet_protocols = ipv4 > home_mailbox = .maildir/ > myhostname = hostname.example.com > smtp_skip_5xx_greeting = no > unknown_address_reject_code = 550 > fast_flush_domains = > error_notice_recipient = postm...@example.com <javascript:> > > Then postm...@example.com <javascript:> would go to whoever is in charge > of the server. > > I was wandering if anything happened to this. I have been receiving some trac e-mails and missing some others silently, some during the same day so it does not seem to me that trac is choosing these IPs sequentially.
Here's a typical entry for a blocked e-mail (blocked by spamcop): Jul 20 14:06:04 whiskey postfix/smtpd[7254]: NOQUEUE: reject: RCPT from o1.3nn.shared.sendgrid.net[167.89.100.129]: 554 5.7.1 Service unavailable; Client host [167.89.100.129] blocked using bl.spamcop.net; Blocked - see https://www.spamcop.net/bl.shtml?167.89.100.129; from=<bounces+3351942-2958-heluani=potuz....@mail.sagemath.org> to=<helu...@potuz.net> proto=ESMTP helo=<o1.3nn.shared.sendgrid.net> Perhaps someone here has already written a postfix rule to allow traffic based on some metadata from the trac servers (say something like from=bounces+.*@mail.sagemath,org)? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/2312f3de-9785-4de7-a15a-06cd6e693103o%40googlegroups.com.
