Skip to content
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

Open
stevejenkins opened this issue Nov 28, 2015 · 20 comments
Open

Suggested Additions to Whitelist #2

stevejenkins opened this issue Nov 28, 2015 · 20 comments

Comments

@stevejenkins
Copy link
Owner

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!

@ghost
Copy link

ghost commented Dec 2, 2015

How about Yahoo (yahoo.com)?

@stevejenkins
Copy link
Owner Author

Hi, @davidcarollo. I'd love to be able to include yahoo.com - but check the first "Known Issue" in the README: https://github.com/stevejenkins/postwhite/blob/master/README.md :(

@ghost
Copy link

ghost commented Dec 2, 2015

Oops! Now that you mention it again I do recall reading that the other day. My bad.

@stevejenkins
Copy link
Owner Author

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. :)

@K2rool
Copy link

K2rool commented Dec 13, 2015

Hi,been useing postwhite for a few day now thanks for the very useful project

Here's a few Suggestions
mailgun.com transactional email from rackspace
mailjet.com a other transactional email provider
github.com

@stevejenkins
Copy link
Owner Author

Thanks, @K2rool. I like those suggestions, and have added options for them to 1.22 (they are enabled by default).

@6qw
Copy link

6qw commented Jun 1, 2016

Thanks for the project!

I'd like to suggest fastmail.com

@stevejenkins
Copy link
Owner Author

stevejenkins commented Jun 13, 2016

Hi, @6qw. I've added fastmail.com and it's now included as of v1.33. See commit 9a1ada3.

Thanks for the suggestion.

@dajones70
Copy link

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.

@dajones70
Copy link

Consider adding facebookmail.com to social_hosts= list.

stevejenkins added a commit that referenced this issue Feb 12, 2017
Added facebookmail.com to social_hosts (suggested by @dajones70 on #2)
@stevejenkins
Copy link
Owner Author

Done and done! Please see new version. Thanks for the suggestion, @dajones70 :)

@qskousen
Copy link

How about Sparkpost and parent company Momentum/MessageSystems?

stevejenkins added a commit that referenced this issue Feb 20, 2017
Adding sparkpost.com (suggested in #2). Query result also includes messagesystems.com.
@dajones70
Copy link

comcast.net centurylink.net embarqmail.com rr.com to webmail_hosts
amazonses.com mxlogic.net messagelabs.com messagegears.net authsmtp.com to bulk_hosts

@stevejenkins
Copy link
Owner Author

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. :)

stevejenkins added a commit that referenced this issue Mar 26, 2018
Added amazonses.com, messagelabs.com, messagegears.net, and authsmtp.com as bulk_hosts. Thanks @dajones70.
@toslan
Copy link

toslan commented May 14, 2018

Biggest RU-Net bulk mailers:
mail.ru yandex.ru qip.ru rambler.ru

@incase
Copy link

incase commented Mar 21, 2020

I'd suggest Steam:
smtp-62.steampowered.com[208.64.202.62] and various others, apparently all in 208.64.202.0/24
I know of at least:
smtp-59.steampowered.com 208.64.202.59
smtp-62.steampowered.com 208.64.202.62
smtp-01-tuk1.steampowered.com 208.64.202.37
smtp-02-tuk1.steampowered.com 208.64.202.47

@xpunkt
Copy link

xpunkt commented Jun 1, 2021

https://dmarcian.com/spf-survey/?domain=yahoo.com sadly no ips at all is valid
https://dmarcian.com/spf-survey/?domain=gmail.com do we trust to many ips ? :/

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 :=)

@skipperblue
Copy link

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
The page has links to a json file that lists all IPs and their use cases (including non-mail sending IPs such as imap migration) as well as an RSS feed for automatic updates.
In my opinion Office365 is extra important to whitelist because they do not follow the resend policy in rfc5321. They attempt resends from a random different IP in their pool each time so mail is never delivered and after enough failures they will blacklist the receiving mail server from sending to Office365 domains.

@6r1d
Copy link

6r1d commented Sep 16, 2023

Tutanota should be added if it wasn't.

Domain list:

w1.tutanota.de - v=spf1 ip4:81.3.6.160/28 -all
w2.tutanota.de - v=spf1 ip4:81.3.6.160/28 -all
w3.tutanota.de - v=spf1 ip4:81.3.6.160/28 -all
w4.tutanota.de - v=spf1 ip4:81.3.6.160/28 -all

Generally, should I write a PR to the postwhite script, patching the webmail_hosts section for this to work?

@lquidfire
Copy link

Hi, @davidcarollo. I'd love to be able to include yahoo.com - but check the first "Known Issue" in the README: https://github.com/stevejenkins/postwhite/blob/master/README.md :(

Hi @stevejenkins, I've included a query for Yahoo in my fork. Would you be interested in a PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests