I'm using the SendGrid API to send the mail. It is working fine if, from and to domains are different. But it is not working if both from and to domains are same.
If the sent "from" email address' domain name is #yahoo.com or other large email provider, then all "DMARC" compliant mail servers will bounce the email unless the email was originated from the email provider's mail servers.
Otherwise, their should be no issue with sending emails where the "from" and "to" domain is the same.
For reference, this is yahoo's DMARC policy currently (as of 2/5/2019):
(https://help.yahoo.com/kb/SLN24050.html)
Yahoo recently updated the DMARC record with "p=reject" for Yahoo domains. This was done to protect our users from increasing email spam that uses Yahoo email addresses from other mail servers.
All DMARC compliant mail receivers (including Yahoo, Hotmail, and Gmail) are now bouncing emails sent as Yahoo email addresses that aren't sent through Yahoo servers.
Related
When someone signs up they receive an email with a link they need to click to verify their email. The email comes from no_reply#domain.com
So far all clients receive this email with the exception of clients using their own domain with Office365. With these clients it's not an issue of emails going to spam - they don't receive anything at all in either their spam or their inbox.
The email is sent from a domain that uses Google Business for email.
Any ideas how to solve this issue?
I should add that if the email is forwarded manually, it does come through, just not when automatically sent.
since a few days our internal email info#ourdomain.com seems to go bananas and sends out emails to all sort of email addresses. Some of those emails bounce and we receive Mail Delivery Failed emails every minute.
Here is our setup:
Domain hosted at Germany's 1und1 provider
Nameserver configured on Amazon Route 53
MX server mx01.kundenserver.de and mx00.kundenserver.de
Rails application hosted on heroku
I called the support at 1und1 and they told me to set a SPF record which I did:
"v=spf1 a mx ~all"
after researching the topic via http://www.spf-record.de/
Unfortunately this did not resolve the problem.
Honestly I am cluesless now what to do to prevent this random email sending.
Our account could have been hacked but the password was already changed.
Any of your email account or script/code compromise can cause outgoing spam emails. If outgoing emails are originating from particular email account and you find large outgoing email account from particular email account, you should consider to reset the password of that email account immediately. Also, compromised email sending script/code can can cause outgoing spam.
If "from" email address on spam email is none of your existing account then "From" email address is getting authenticated from any of your existing email account for which you should inspect SMTP logs of mail server(you should have administrative access of mail server)
Mail server IP address should not be blacklisted,please check IP here :- http://mxtoolbox.com/blacklists.aspx
If IP address is blacklisted, you can request IP whitelist after you identify and fix the outgoing spam source as RBL keeps IP address blacklisted until they find the spamming activity relaxed.
SPF and PTR record should be correct so that email recipient server can trust the sender mail server.
Bounce back email and spam email header can help to identify the issue more preciously.
This happened to me before, I had a "refer a friend" feature on my website and someone use an automated script to send emails to a ton of people. My server wasn't comprised, it was just bad coding in the feature that I installed that allowed my mail server to send mail to different people on my behalf.
Since the email is coming from you, your SPF/DKIM will check out just fine.
So thing about all the points on your website that can send email and see if any of them can be compromised.
Also you'll want to do a blacklist scan, I use this service it does more then 200+ blacklist: https://www.unlocktheinbox.com/blacklist/bl/
Make sure you scan both your domain name and IP address. But before you take any action to remove yourself, you should wait 24 hours until after you fix the exploit on your system. Requesting removal and popping up again can get you permanently listed.
I'm building a web app. In this web app users sign up for an account. These users use this app because it's a tool for organizing their end customers.
On of the features of this app is sending emails. Some of these mail are sent from me (the app author) to the users... And some other mails are sent on behalf of the users to their end customers.
Regarding spam, and deliverability, when the app is sending mails on behalf of it's users, should it mimic their company domain and senders instead of its own?
Should the from field be: my-app-name <noreply#myapp.com> or user-name <noreply#usersdomain.com>
I reality all mail will be sent from the domain myapp.com. The questions is if I should mimimc users domain.
You will be likely to run into problems with messages not being delivered if you attempt to send messages from other domains from your mail server, because of SPF records and DMARC policies. Most large email providers such as Yahoo and Gmail have SPF records setup, which advise receiving mail servers to treat mail from senders at these domains as spam unless the messages are sent from mail servers within these domains. Yahoo has even taken it a step further with a DMARC policy that they recently started - see https://support.sendgrid.com/hc/en-us/articles/201876356-Yahoo-DMARC-Changes-Message-not-accepted-for-policy-reasons- for more info.
I am trying to send email from PHP using mail function to gmail ID, but email is not being delivered to the recipient if sender defined in header is yahoo ID, but if sender is hotmail then email comes fine. IF it goes sometime then it gets delivered at spam and the message on top of the message is 'This message may not have been sent by: xxx#xxx.com'
I have also tried phpmailer with smtp and ssl is also enabled on server, but no luck. Server is linux based hosted on godaddy
Thanks
This is because you can't send mail from a yahoo address unless you send it through a yahoo server - documented here. It will be bounced with a DMARC failure.
I am using the Mandrill mail server for sending emails to users and I have my own domain added to Mandrill to send out mails. Suppose I have configured Mandrill to use info#mydomain.com to send out emails and then it should send emails which it does. And any replies sent to info#mydomain.com will be forwarded to traditional mailboxes.
Now I have a doubt on receiving emails via Mandrill, once I add an inbound domain and route its path to my desired location, it should be ready to receive emails. Well I have read questions on SO and it has been said that if someone wants to use traditional mailboxes for receiving mails then it's better not to use Mandrill or use a custom sub domain.
Also it has been said that it is not possible for Mandrill to receive email which is already configured or forwarded to some other traditional mailboxes.
So I added a sub domain to Mandrill's inbound domain like inbound.mydomain.com and receive emails on this domain which will be received by Mandrill and will be send to the desired route which we set up. Now I will have to change my sender domain with the same that is inbound.mydomain.com to make users reply to this domain which will be received at Mandrill. What I want is :
Send emails using info#mydomain.com
Receive emails to my location using inbound domains