Messages sent to Facebook returning with POL-P8 - facebook

We have a desktop system that sends various e-mails to the users. These users have the option to choose to receive a copy of all these e-mails in his/her Facebook message inbox and we do this by sending a copy of the e-mail to the user's #facebook address.
For some time, this was working with no problems but recently a client reported that some of the messages sent to the user's Facebook address were failing and returning.
After analyzing the returned message, we found that the diagnostic code was "POL-P8":
554 5.7.1 POL-P8
http://postmaster.facebook.com/response_codes?ip=143.106.10.159#pol-m
Message refused (in reply to end of DATA command)
Looking at the code description page (http://postmaster.facebook.com/response_codes?ip=143.106.10.159#pol-m), we found that this particular code translates as "The message does not comply with Facebook's abuse policies and will not be accepted.", which seems to tell us that the message was considered spam and, therefore, not sent.
Still, we don't know exactly why this is happening. It doesn't appear to be related to the message content, since we tried manually sending an e-mail with the exact same content to the #facebook address and it was sent and received with no problems. We also thought that the problem could be caused by a large number of messages being sent to the user's inbox in a short period of time, but we also weren't able to reproduce this.
I did not find any detailed information about compliance to the "Facebook abuse policies" so I am a bit lost on what could be the problem and what could be done... any help someone can give me will be greatly appreciated!

Related

Sendgrid emails getting deferred

All the emails which I sent via SendGrid is getting deferred. On the SendGrid Activity dashboard it shows the message. "554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means."
It used to work 3 months ago. For the past 3 months, there were only very few email being sent out. Now All the emails sent are getting deferred.
Please let me know a fix for this.
Thanks in advance
I think I figured it out. I'm using shared hosting of SendGrid, so the server is being used by others as well. Go to the activity overview, and click the info icon. You will see more information, in my case it's like:
...Client host [149.72.39.137] blocked using Spamhaus. To request removal from this list see https://www.spamhaus.org/query/ip/149.72.39.137...
If you click the link, you can see the reason:
So here it's obvious that some phising was going on, therefore, mails are delayed and/or blocked.
I guess to solve this, we should upgrade to have a dedicated server...

Gmail: This message seems dangerous

Ok, I am working on an invite system for my work, the invite system sends an email to the recipient with a link containing a unique token allowing them to sign up.
The issue is, now that I am actually testing it, the emails are marked as "This message seems dangerous" by gmail, This looks really bad for the company. I have not been able to find any information on what triggers this.
The email is being sent via office365(SMTP) as that is what our email is set up with to try and avoid this kind of thing.
I have seen comments online that it may be due to the token link, If so, how else am I meant to do this?

reply emails are bounced due to URL in content

I have a client who communicates with me via email. Crazy, I know.
Here is the issue: When I send him an email from Mac Mail — with my URL in the footer – he receives it. However, when he tries to reply from his gmail account, my server bounces it back to him. The error is "554 rejected due to spam content". (a false-positive)
I can not collect the Spam Checker data from his email headers, as he is not tech savvy. I can not duplicate the error using a gmail account of my own. I have eliminated all possible problems, except the URL in my footer, which triggers this every time.
My email server is: 01-ah-r28u33-ss05.alphahosting.com
His gmail server is: mail-ob0-f172.google.com
Both of these (and also my test gmail server) are shared servers and have some blacklist reports. However, I have no such problems from other clients. My concern is that this could be a reporting problem, and I am failing to hear from those who would rather delete my email than give me a call. I think that you can understand my concern.
Please help, and do let me know if you need any other data that I might add in here.

Gmail blocked emails sent from Send Grid

We are trying to send mail on to Gmail account by using send grid api but Gmail has blocked the email which is sent from send grid. Please check the message given below:
550 5.7.1 [167.89.24.147 12] Our system has detected that this message is likely unsolicited mail. To reduce the amount of spam sent to Gmail, this message has been blocked. Please visit http://support.google.com/mail/bin/answer.py?hl=en&answer=188131 for more information. kw15si11591084pab.218 - gsmtp
We have checked all header parameter suggested by Send Grid and implemented it in our code. At the same moment, it works fine for other domain like AOL, Rediff etc.
Please suggest how we overcome with this problem as we have huge users on Gmail and we will send our emails to all those users as. Also, we have noticed that the email came after some time from Send Grid.
Many thanks in advance.
The recipient mail server analyzed your message and determined that the content of the message is spammy. My recommendation would be to run your formatted message through a third-party service, www.mail-tester.com , to identify ways to improve the reception of the message. It's also possible that your sending IP address, 167.89.24.147 based on the response message you've included, is listed on a black list. You'll want to scan your sending IP on a site like http://multirbl.valli.org/ and, if you see that your IP is listed anywhere, submit a delisting request with the black list.
SendGrid also has a Spam Checker app - Turning on SendGrid's Spam Checker app can help combat this, as you're able to set a predefined filter and get alerted when your content exceeds the filter that you set.

Mandrill Emails not reaching any mailbox, but Mandrill showing status 'Delivered'

Mandrill does not offer any support. I've sent them many tickets, but still no answer. I hope someone here will help me out.
I'm sending emails through SMTP. I'm able to send few thousand emails in start, but after few thousands, no email reaching any mailbox. Mandrill activity showing that the email is delivered, but it's not and there's no email in backlog. I have limits around 50K/hour.
I tried making another account after a day, and did some deposit too, but same thing happen with other account too. No error in SMTP client, no error in logs, nothing.
Other thing to notice is, when I hover over 'Delivered' it says "No SMTP event", but emails which are actually got delivered, showing some stats on hover over.
The Mandrill Delivered-status in the UI doesn't actually mean that it is sent, only that Mandrill have received the message for processing. This is of course extremely confusing.
The only way of seeing if an email is actually sent (i.e. successfully delivered to the receiving mail server) is to see if the message has smtp-events. Do note that it can take some time before the SMTP-events are available in the GUI/API (I have experienced a delay of between 2 minutes and 24 hours).
To see all emails that not currently confirmed delivered you can search for "NOT smtp_events.diag:250" in the search field.
After some research, one of the reason, I came to know that if TEST API KEY gets used to send emails, no mail is actually sent to inbox, but webhooks trigger normally and it shows status as delivered on the Mandrill UI. In order to check actual delivery of email to your inbox, please try to use different API KEY other than test account
It turns out to have been a delay in the emails being received by the mailserver (gmail). It appears as if they were accepted and not processed for a few hours.
I had run in to the same issue and this explanation given by OakHosting_James helped me a lot in understanding what is going on:
It turns out the message was sent from IP that is on an RBL (it happens - I get that). So the receiving server rejected the message at SMTP time.
They replied to say two things about that:
(i) Anyone can set up a blacklist and put any IP on for no good reason.
(ii) Some messages bounce in such a way that Mandrill is not able to detect that it's bounced - which is why their website said "delivered".
Let's take those issues:
(i) It's true, but this was UCEPROTECT-Level 1. They're not a pleasant blacklist to work with, but they're not a backyard project for someone with an axe to grind. I still get the fact that it's impossible for any sending network to remain 100% clean. I'm not frustrated that one of their IPs was listed temporarily. But I did feel fobbed off by being told that there are some tiny blacklists out there that no-one in their right mind would use. UCEPROTECT is not one of those, and they should have come clean: "Even with the best spam protection, we get blacklisted occasionally; we detect this very quickly and switch to other IPs."
(ii) I'm sure there are some after-the-fact bounces that Mandrill's system can miss. But this was rejected at SMTP time. How can they mark a message that never left their sending server as "delivered"?
So the solution (to some degree) to the RBL IP problem (i) could be an "Dedicated IP $29.95 / month" for your account in Mandrill. But using a dedicated IP can be a problem on it's own and is for most cases not advised.
In your mail.rb file you need to do the following :
ActionMailer::Base.smtp_settings = {
address: "smtp.mandrillapp.com",
port: 587,
enable_starttls_auto: true,
user_name: "yourname#gmail.com",
password: "apipassword",
authentication: "login"
}