I Know the below things
To: is to the person who is receiving the email or taking action regarding email received
CC: is "Carbon Copy" which basically is for information so that they know the "To" person recieved the email and the action should be taken on the mail received
BCC: Blind Carbon Copy meaning that the others who recieved the email will not know that the BCC person got the email.
But My actual doubt is that,
Yahoo is blocking the mails received by there user, send using third party tools/servers. Here is more info from Yahoo
When a send a mail from some site in the below format
From: xxx#yahoo.com
To : yyy#yahoo.com
Sender is receiving error message.
But if i send in below format yahoo is accepting mails
Edit
From: xxx#yahoo.com
To : zzz#gmail.com
CC : yyy#yahoo.com
The error you mention is purely caused by a policy with Yahoo that states, from the link you give,
Your message wasn't delivered because Yahoo was unable to verify that
it came from a legitimate email sender.
So Yahoo's concern is to make sure spam is not sent using forged addresses unknowingly to the legitimate address owner.
If you include the CC field with the same address as From, it means at least the "maybe forged" sender is receiving a copy of the sent email. And that seems to be sufficient for Yahoo to accept to forward your email.
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.
I tried to send an email through sendgrid. I have a custom domain myself#contoso.com. If i try to send an email to user1#gmail.com with the from address as myself#contoso.com,then,the email is delivered to gmail with "via". When i try sending email to myself#contoso.com with the from address being myself#contoso.com the activity says the email is delivered however, in outlook client i have not received the email. What is it that I can try or do?
I have tried whitelisting contoso.com but it did not work
This is not an answer, as it doesn't help work out why the emails that are "Delivered" have not been received, but this is SendGrid's note on why Email messages with the “Delivered” status are not received:
Twilio SendGrid posts the Delivered event after the destination server accepts the message with a 250 OK response. Once an email is accepted by the destination server, we are unable to see what happens to the message. The receiving server could send it to the inbox, queue it for later delivery, put it into the spam folder, etc.
Often times, a recipient domain will initially accept a message for delivery, and then apply additional filtering afterwards. In this situation, we would have posted the Delivered event, but not have any insight into the additional filtering. Any additional Twilio SendGrid events for your email message would be triggered by recipient engagement (i.e. open/click events, unsubscribes, etc.).
Also note that at the time of writing, that answer had 26 downvotes (and zero upvotes) on the SendGrid website, probably indicating that many other users have experienced this problem.
I had several issue solving this problem. The most important part is to set "Sender Authentication" from sendgrid to your domain dns. There is a instruction here. I'm using godaddy, so the link to set dns is https://dcc.godaddy.com/manage//dns .
I got this bounce back email whenever try to send to a specific sender..
Any help would be appreciate..Thanks :D
mail content:
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
example#example.com.mm
No Such User Here
Reporting-MTA: dns; mail.example.net
Action: failed
Final-Recipient: rfc822;example#example.com.mm
Status: 5.0.0
Unless there is something odd going on, the bounce back message is clearly telling you that the email address "example#example.com.mm" doe not exist. Perhaps "No Such User Here" is not the best wording, but it means that the email address is non-existant.
Is the .mm at the end of the email address part of the problem? Are you actually sending email to Myanmar?
I have never seen this bounceback message when the email address actually existed. Since this is unusual, I would send the email headers to the ISP of the intended recipient, since it is highly likely that is where the problem exists, and ask them to investigate. Also, I do think that you can get the same message if the users Inbox is full. Ask the intended recipient about that.
the problem has to do with your websites DKIM and SPF keys (Email deliverability in CPanel), if they are not added to the server it cannot verify the authenticity of your email.
The best solution is to contact your server support or CPanel support to fix the issue. There is almost nothing you can do via programming.
I had this issue and I spoke to my server's support team and it was fixed
At this point my email deliverability has not been marked as VALID, so the email
Mail delivery failed :returning message to sender kept persisting.
so I spoke to the server support team as the tooltip in the image suggested and it was finally fixed
if you noticed the VALID mark there
Part of our product involves sending users a weekly email with a status report about their account, and once in a while we get the following reply from their spam filtering service saying the following:
LSMSGCV: You just sent an email to foo#bar.com - please reply
Did you send an email to: foo#bar.com from: foo2#bar.com?
If yes, it got caught as unsolicited email by our spam blocker. You can release the mail from spam quarantine by simply replying to this message. At the same time the spam blocker will recognize you as a trusted sender (from this email address) and automatically add you to my Allow list for this and any future communication.
Many illegal spammers forge email addresses to try to get past spam blocking software. These spammers send hundreds of millions of spam messages a day, clogging email servers and wasting people’s time. We regret that these spammers have forced us to send this message to you.
Original From: foo2#bar.com
Original To: foo#bar.com
LSMSGCV For more information about our spam blocking software please visit www.lightspeedsystems.com
The problem is that our from email address is not a real inbox, it's actually a google group (set up through google apps) that we use to make sure everybody who needs to can receive the reply to this email and answer from their personal company accounts.
For LSMSGCV, does it matter if the "unblocking" reply comes NOT from the original from address? Would that successfully whitelist our from address or would that be insufficient?
I've been looking for documentation on the standard behaviour for mail servers who fail to deliver their mail.
I want the 'From' field to be different from the account that receives emails when there is a delivery failure.
E.g.
My program sends an email from 'donotreply#example.com', and on failure to deliver I want to be sent the delivery failure bounceback at 'failedemails#example.com'.
Is this accomplished by setting the reply-to? Or should I login with the 'failedemails' account and therefore it will receive the email back?
Thanks.
There are several things you can try, but I think that bounces are typically going to be sent to the envelope sender. This means that sending the mail from donotreply#example.com using your failedemails account is probably your best bet.
You can also try these headers:
Reply-To: failedemails#example.com
Errors-To: failedemails#example.com
Return-Path: failedemails#example.com
A similar question was also asked here: Set email headers so bounced emails go to a specific address