My email signature has a link to my company website and it's formatted correctly. If someone replies to an email I sent them, very often SpamAssassin marks the reply as spam. I'm also getting reports that my emails land in recipients' junk folders.
Here's the relevant part of the header in a reply to my email:
URIBL_SBL_A Contains URL's A record listed in the Spamhaus SBL * blocklist * [URIs: (the domain)] * 1.6 URIBL_SBL Contains an URL's NS IP listed in the Spamhaus SBL * blocklist * [URIs: (the domain]
Here's the thing: my domain is not listed on the Spamhaus SBL. When I look up my domain on the Spamhaus SBL lookup it reports "(the domain) has no issues."
So, essentially, Spamassassin is marking my emails as spam because I have a link to my website in my signature and that link is apparently on the SBL list, but in reality it's not. There's no way that I know of to contact Spamhaus about this. Any ideas? Thank you in advance.
Related
Couple of days back someone used our domain to send spam emails, Now we are using mailgun to send emails but none of email is going to inbox, because previously it was involved in spam activity, how we can now prevent this issue that our email should land to the inbox folder right away! We have other domains to for the purpose of sending emails we can use those too!
It's a matter of notoriety of domain and IP address.
If you use another domain on the same server (ip address), it will end up in the spam folder too.
Using a mail relay like mailgun, and especialy with a dedicated IP option, will help over time to get out of the spam folder if not right away.
You can also help fix your issue by asking some of your users to mark your emails as "not a spam".
No other quicker solutions.
I am trying to synchronize customer entities of an online store with MailChimp e-commerce service. Most of them synched successfully, but some others failed. The response of API is as below:
{"status_code":400,"operation_id":"855","response":"{\"type\":\"http:\/\/developer.mailchimp.com\/documentation\/mailchimp\/guides\/error-glossary\/\",\"title\":\"Customer Was Not Saved\",\"status\":400,\"detail\":\"Customer could not be imported to the list associated with this store.\",\"instance\":\"\"}"}
I couldn't find any explanation for this error in official documentation.
I've posted a ticket in the MailChimp support system about my problem. This is their answer, just for the information of any other person facing this issue:
The email address is blacklisted from signing up
The email address is invalid
The email address is not UTF-8 encoded
The address was added to the list too many times in a short period of time
I did a lot of research through internet but I didn't found the solution. I'm trying to send a confirmation email using Mail::send() in laravel 5.1, I don't want to use any third party like mailgun or mandrill because they are not free sometimes limited of usage. The problem with this is all of the confirmation of the users is in their spam folder in gmail, and trash folder in outlook. Sometimes they didn't receive the confirmation. Why is that? Do you have any idea with this? My website is also registered to https so I don't think this is the problem.
.env
MAIL_DRIVER=smtp
MAIL_HOST=mail.mywebsite.com
MAIL_PORT=587
MAIL_USERNAME=email#mywebsite.com
MAIL_PASSWORD=mypassword
MAIL_ENCRYPTION=tls
Landing of an email into Spam is nothing to do with Laravel.
Either you have to change the TXT record of your domain.
You can check it on mail-tester which values need to be changed.
https://www.mail-tester.com/
You might wanna try testing at Mail Tester. This can reveal a lot of information on why your emails are ending up in spam. I also recommend checking SPF and DKIM checking at SPF & DKIM checking at the same site.
Also are you hosting your emails with your hosting provider or some other third-parties like GSuite or Microsoft Exchange? These providers can influence the mail quality and spam checking greatly.
The spam classification of emails is to the discretion of the receiving mail server. There are a couple of best pratices to follow, when trying to avoid being marked as spam:
Make sure the sending server (smtp server) is allowed through
SPF
DKIM
DMARC
MX records
Further, the recipient server may check for bulk content with decentralized solutions like razor, pyzor or DCC. So, try to personalize the messages and not send bulk content. Its hard to evaluate your situation without specifics. Another problem may be the sending webserver if its in or from a country with "bad reputation" (like Russia, China). Since mail server also check the Original-IP of the email and potentially flag them as well.
SPF:
https://mxtoolbox.com/SPFRecordGenerator.aspx
DKIM:
https://dkimcore.org/tools/keys.html
DMARC:
https://mxtoolbox.com/DMARCRecordGenerator.aspx
To check your settings, it helps to use mail testing solutions visualizing those mentioned factors as mentioned by other answers.
Current email deliverability professional here. If you are willing to share the domain you are sending from, and the IP address initiating the sends I'm happy to check for any obvious problems.
I also heartily recommend mail-tester.com as I use it almost daily. If you want to share the link to the report I'm happy to help interpret.
The other thing to be aware of is, that IP addresses have a sender reputation that is tracked in the Email ecosystem at large. If it's a new sending IP address it has to get warmed up. Just like you cannot get a credit card with no limit as soon as you turn 21, Inbox Providers like Gmail and Hotmail are not just going to deliver everything a new sending IP starts trying to deliver to their recipients. They will essentially do some A/B testing by delivering some to the Inbox and some to the Spam/Promotions folder, and see how their recipients interact with your mailings. Gmail and thus other inbox providers are primarily concerned with how recipients interact with your mailings. Do they open, do they click links, do they add you to safe senders, etc.
-LB
From what I've been reading the SPF can be used to validate email addresses by sending commands (rather than an actual email) such as HELO. I've managed to pick up a basic grasp of the policy but I can't get my head around how I'd go about solving the following problem:
I've got a number of email addresses attached to contacts in a CRM system and I'd like to find out if the email addresses are valid and still in use.
Currently we're using a REST Web Service (http://emailinspector.co.uk/) which returns "Ok" (if its ok... duh), "Bad" (if its not valid or not in use) or "Unknown". For Unknown, you are also provided some notes on why it came back with that, i.e. you are told if the Mailbox is full or if its a well known DEA.
I'd like to be able to program a script that can replicate this functionality and from what I've worked out it should use the Sender Policy Framework to do this? The problem is I don't know how I'd go about returning such precise information for "Unknown" email addresses.
Ideas and thoughts?
Actually SPF is just a text record, with some "hints" to let you know if an IP address or mail server is "allowed/Authorized" to send email for that domain. It doesn't tell you anything about an individual email address in that domain..
for example
[doon#qix:~] host -t txt labratsoftware.com
labratsoftware.com descriptive text "v=spf1 a -all"
The SPF record for one of my domains says that only the a record for the domain is authorized to send email for labratsoftware.com, and that if it doesn't come from that IP then it should be rejected (-all).
So the best you can do with SPF is tell that a received email came from an authorized host, and then use that information to help decide if you want to reject it or not.
The best way To test the validity of an email address you have, is to email it, and see if it bounces. You can use options like VERP (http://en.wikipedia.org/wiki/Variable_envelope_return_path) to automate the bounce handling. You can also try and connect to the MX records listed for the domain and try to deliver a message that way. Some Mail servers support verify (But most admins disable this to prevent information leakage). You can use RCPT TO to see if the server accepts it, but even if it does , you have no way of knowing if it will actually make it to their INBOX. My guess is that is what the API you are currently using is doing. And unknown are just ones that either don't answer, greylist, etc.
My Question:
How does Outlook 2007 decide if it
should redirect an e-mail to the Junk
E-mail folder?
Background Story:
When I send a simple HTML e-mail from my domain mailbox, it's being redirected to the Junk E-mail folder.
Here are two sub questions:
Does Outlook 2007 care if the sender's outbound mailbox's reverse PTR is incorrectly configured? [If so, how can it check?]
Does Outlook 2007 care if the sender doesn't provide a plain text version of the HTML content?
EDIT: It turns out, I'm not the only one wondering about Outlook's junk algorithm. See the comments attached to this answer.
Here's a helpful answer.
"...The technology used for message
content analysis is also far from
being perfect. Microsoft has created a
dictionary of several tens thousand
words, and assigned different weights
to the words in the dictionary. The
message content analysis is nothing
more than mere summation of weights of
words contained in the message."
And here's another one.
But bear in mind:
Microsoft intentionally keeps
Outlook's spam filtering rules
secret.
Because if they didn't, spammers would have a playbook for
which they could circumvent the
rules.