-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggested Additions to Whitelist #2
Comments
How about Yahoo ( |
Hi, @davidcarollo. I'd love to be able to include |
Oops! Now that you mention it again I do recall reading that the other day. My bad. |
No biggie. I wish Yahoo! would get on the bandwagon. But their mailers have marched to the beat of their own drum for a long time now. :) |
Hi,been useing postwhite for a few day now thanks for the very useful project Here's a few Suggestions |
Thanks, @K2rool. I like those suggestions, and have added options for them to 1.22 (they are enabled by default). |
Thanks for the project! I'd like to suggest fastmail.com |
Great tool. Thank you! Please consider allowing custom/local lists be put in a local conf file for options like simplify= and the *_hosts= to allow for easy updating of the main postwhite script. I have added to the *_hosts= lists so updates are difficult. Something like a postwhite.conf file would be very helpful so I could keep my local *_hosts= lists that would be appended to the default lists. |
Consider adding facebookmail.com to social_hosts= list. |
Added facebookmail.com to social_hosts (suggested by @dajones70 on #2)
Done and done! Please see new version. Thanks for the suggestion, @dajones70 :) |
How about Sparkpost and parent company Momentum/MessageSystems? |
Adding sparkpost.com (suggested in #2). Query result also includes messagesystems.com.
comcast.net centurylink.net embarqmail.com rr.com to webmail_hosts |
Thanks for the suggestions, @dajones70! Those bulk hosts all appear like good potential candidates, but I'm hesitant to include ISPs like Comcast, CenturyLink, and RoadRunner since they are much more than simple webmail hosts. Those residential networks are teaming with botspam from soccer moms' computers who downloaded some toolbar or app or cute game. Postwhite doesn't create a whitelist for Postfix, just for Postscreen. And since the primary purpose of Postscreen is to be a quick frontline defense against botspam, I feel like forcing everyone who uses Postwhite to skip Postscreen analysis of connections from botspam-heavy networks is a bit too aggressive for the average Postfix admin. As far as I know, the webmail hosts you suggested don't do outbound screening for botspam. The "mega" webmail hosts like Google, Yahoo, and Microsoft do. The ability to easily include custom hosts is there for users like you who are comfortable with more aggressive whitelisting. Again, thank you for the suggestions. I'll take a closer look at those bulk hosts to make sure, but at first glance I don't see anything wrong with including them. :) |
Added amazonses.com, messagelabs.com, messagegears.net, and authsmtp.com as bulk_hosts. Thanks @dajones70.
Biggest RU-Net bulk mailers: |
I'd suggest Steam: |
https://dmarcian.com/spf-survey/?domain=yahoo.com sadly no ips at all is valid i use sqlgrey with 3600 sec delay time, but not for known maillists that is not spaming ips, is postwhite possible to make sqlgrey local skip files ? eq no greylist for known maillists, postfix maillist have no spf, just to be fun :=) |
Office365, which is used for outlook.com and all private businesses that use Office365 business email has a page with links to their IPs here: https://docs.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide |
Tutanota should be added if it wasn't. Domain list:
Generally, should I write a PR to the |
Hi @stevejenkins, I've included a query for Yahoo in my fork. Would you be interested in a PR? |
If you know of a high-volume mailer with a valid SPF record that deserves to be included in Postwhite's whitelist, please comment on this issue. Thanks!
The text was updated successfully, but these errors were encountered: