Google usually displays why it thinks an email is spam when an email marked as spam is opened.
As Laura says, that and possibly headers might be a better clue to identify it rather than blindly arguing about SPF setup without actually even knowing the domain and it's setup. M. Omer GOLGELI --- AS202365 https://as202365.peeringdb.com (https://as202365.peeringdb.com) https://bgp.he.net/AS202365 (https://bgp.he.net/AS202365) NOC: Phone: +90-533-2600533 Email: [email protected] (mailto:[email protected]) January 24, 2020 2:27 PM, "Laura Atkins via mailop" <[email protected] (mailto:[email protected]?to=%22Laura%20Atkins%20via%20mailop%22%20<[email protected]>)> wrote: On 24 Jan 2020, at 10:59, Gregory Heytings via mailop <[email protected] (mailto:[email protected])> wrote: Hi, This is not optimal, your SPF record should be "v=spf1 mx ?all". I disagree. "v=spf1 mx ..." requires a DNS lookup which their existing SPF record doesn't. Lots of people telling you how to set up SPF will say 'use v=spf1 mx' because they don't want to explain the entire SPF record format, and the 'mx' mechanism works for a large proportion of people. Using specific IP addresses is more 'optimised' than using 'mx'. As we often see here, your network your rules. The OP asks for advice, The OP asked for advice on delivery, not his SPF setup. His SPF setup is fine and is absolutely not the problem here. And, in all honesty changing from his more exact and specific SPF record to a vague one that indicates the record is just in testing mode is not going to improve anything. The issue is the unexpected emails to new recipients. Overall, the advice to contact the recipients (it’s only 15) and have them check their spam folder and move the message out is what’s going to fix things the fastest. Also, the recipients should be putting the 5322.from address in their address books. Another good way to get the messages whitelisted for those recipients is to have the user reply to the message or have some level of discussion with the sender. When you’re little the neighborhood you reside in has a big impact on your delivery. Linode is generally responsive when they are alerted to abuse issues, but they have a LOT of spammers set up shop there. The recent SendGrid phishing spam mostly came through Linode IPs, for instance. And as fast as Linode would shut down one IP address, the spammers would move to a new, fresh Linode IP. I don’t blame Google at all for treating unexpected bulk mail from a Linode IP as suspicious. 15 emails is exactly the volume that spammers will use to test, for instance. laura -- Having an Email Crisis? We can help! 800 823-9674 Laura Atkins Word to the Wise [email protected] (mailto:[email protected]) (650) 437-0741 Email Delivery Blog: https://wordtothewise.com/blog (https://wordtothewise.com/blog)
_______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
