Since last one week I am having issue of not sending emails through my gmail google app for business. Every time I sent mail it gives me following error. Sometimes it works well but then for 24 hours it gets block. I tried all google support links still issue remains same.
Strange Point:
Our other email address from same domain working well.
Mail Delivery Subsystem
4:09 PM (19 minutes ago)
to me
Delivery to the following recipient failed permanently:
****#****.com
Technical details of permanent failure:
Message rejected. See https://support.google.com/mail/answer/69585 for more
Message-ID:
Related
I manage a server with Plesk 12.5 since a couple of years.
Everything (emails, websites, etc.) works perfectly with our main domain (let's call it myfirstdomain.com).
Since a couple of weeks, I added a new domain (let's cal it myseconddomain.fr) and everything seems to work too (emails and websites), except the following error: when a sender sends an email to us, he receives the following error after 5 days:
This is the mail system at host myfirstdomain.com.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<fabrice#myseconddomain.fr>: Message can not be delivered at this time
Reporting-MTA: dns; myfirstdomain.com
X-Postfix-Queue-ID: DC0B1702585
X-Postfix-Sender: rfc822; xxx#xxx.net
Arrival-Date: Tue, 5 Mar 2019 21:18:00 +0100 (CET)
Final-Recipient: rfc822; fabrice#myseconddomain.fr
Original-Recipient: rfc822;fabrice#myseconddomain.fr
Action: failed
Status: 4.2.1
Diagnostic-Code: x-unix; Message can not be delivered at this time
De: XXX XXX <xxx#uxxxvi.net>
Objet: Testing title
Date: 5 mars 2019 à 21:17:58 UTC+1
À: Fabrice Troilo <fabrice#myseconddomain.fr>
Testing body
You can see that the reporting-MTA is myfirstdomain.com, so maybe there is confusion between the two domains?
Here is our SPF:
"v=spf1 a mx include:_spf.google.com ip4:XX.XX.XX.XX ~all"
I will try with this update for the two domains:
"v=spf1 +a +mx +a:myfirstdomain.com +a:myseconddomain.fr include:_spf.google.com ip4:62.210.16.40 ~all "
Also, the email address is simply forwarding to a gmail address.
Do you please have any clue to look at?
If you can send mail from the domain, but not receive it, it's not related to SPF. SPF authenticates when you send mail, not receive it.
Have you ensured that an MX record is set up for the secondary domain?
You can test this using the terminal on Linux or macOS with host -t MX myseconddomain.fr
If you are on Windows, then open a command prompt, type nslookup. Then when in nslookup, switch to query MX types with set q=mx and press enter. Then enter your domain myseconddomain.frand press enter.
If the MX records looks correct, then it must be some configuration in Plesk. We can test this by trying to deliver mail ourselves with telnet.
Open a terminal/command prompt and type telnet <myserverIP> 25 and press enter. This connects to your mailserver. It should respond with a line beginning with 220, and it's hostname. Then you can try and deliver a simple test mail, let's say from account1#example.net
EHLO example.NET
MAIL FROM:<account1#example.net>
RCPT TO:<fabrice#myseconddomain.fr>
DATA
This is a test email. To test delivery.
.
QUIT
The first few lines introduces yourself, sender and receiver to the mail server. DATA indicates you want to start the body of your email. And the period on a line by itself indicates that you are done with the body. QUIT then terminates the connection.
Then watch what your server says in reply to each command. If you can successfully deliver this way, then it's like a problem with your MX record.
I don't know if you have solve this Problem. If you have please let me know. We have a similar error.
I found out that is has to do with the E-Mail-Header because it may have two domains in it because it gets forwarded. Google don't like this :)
Google has opened a thread about it and they say you can enter the Domain that forward to the gmail address so it is not detected as some kind of spam.
I can not test it because I it is an gmail account from an client and I have no access.
May my executions help. I hope you have an better answer.
Greets Matt
Q: Anyone know any working method, or alternate URL, to create an Authorize.Net Sandbox Account?
After filling out the Sandbox Account form at, https://developer.authorize.net/hello_world/sandbox/ , I received the error message:
URL: https://developer.authorize.net/hello_world/sandbox/
Complete Page Body:
ERROR
The request could not be satisfied.
This distribution is not configured to allow the HTTP request method that was used for this request. The distribution supports only cachable requests.
Generated by cloudfront (CloudFront)
Request ID: eA28WPE73_KAV2p91ixOhETSVWssiFeOdvnr0az40wxLVIT2bDBhBw==
==EOF==
Edit 2017-12-04:
While not an answer to my question (which may be “There is none.”), I ‘mis’-used Authorize.Net’s contact form to request a manual account creation. As opposed to the ~2 days they give for reply ETA, the above form was ‘fixed’ and they replied, “I just tested the page and I could not recreate the error” within ~5 hours.
I’ll leave the question open for a week in case someone knows an answer, and afterwards close it with ‘None.’
I messed up something on my code and made my server send 10k+ emails to my own email address last night.
After receiving ~8k this morning, I barely haven't received any mail in the last 8 hours besides sometimes one of the automated ones at a rate of ~10/hour.
Has anyone already experienced this?
I haven't found how to tell gmail about this. Nowhere I have a message saying "your mailbox is slowed down because of abusing use" or something.
Can anyone help or should I wait and go on vacation for a few days?
Edit:
Thanks for the help. To add more details:
Those emails have been sent from a non-gmail SMTP server, say example.com to me#example.com, which I automatically redirect to myaddress#gmail.com.
I thought at first that the problem was coming from the example.com mail server, but it happens this parts works very well for sending and receiving for any other email#example.com.
My emails sent from myaddress#gmail.com are also sent. It is only to receive a mail in myaddress#gmail.com inbox that it won't work.
This makes me guess that this is not a SPAM-filtering issue, since sending works fine.
Edit2:
#bearacuda13, there ain't much code to show. The sequence of failures are:
A delayed_job that calls itself recursively every hour, silently increasing the number of jobs in the database, without any error
A heroku API sunset that starts to make them fail all at once.
An exception mailer to tell me about the exception raised
Done :)
Try https://mxtoolbox.com/blacklists.aspx to see if you've been added to a blacklist. If you have, it's a serious pain to get off of those lists.
When you send mail, it gets routed through several areas on the internet before winding up in your gmail. Any of those routes has the possibility to flag and blacklist emails from someone they think is a spammer. If you're sending 10k emails in an hour, you've probably triggered the "spammer" criteria.
To get off the lists, you need to contact the organization that has blacklisted you. It might be easier to get a new static IP or domain name.
So the solution has been to wait. In 24 hours I still had not received them all, but at got some message:
which made me feel like messages were on their way.
48 hours later, I now have the feeling I caught up with all my emails.
If this occurs to you, be patient!
Using SendGrid through Azure (free version).
I recently disabled a user's email because it was receiving way too much SPAM. Prior to doing this my activities list was about 1-2 pages long with recognizable e-mails my system was sending out per customer input in a website (there is a workflow for forms which the user inputs, then my system sends out an e-mail confirming input).
Now that I have disabled that e-mail, I am seeing upwards of 59 pages of activity just for one day (since I disabled the e-mail address), most of which is listed as "Deferred" or "Processed". The lists include SPAM e-mail addresses (something-reverse-mortgage#whatever.net, etc.).
Reading the SendGrid documentation, it seems that "Deferred" activities just mean that the receiving ISP is asking SendGrid to slow down. I take this to mean that my server is sending these e-mails.
This is worrisome obviously. Disabling that e-mail has this unintended consequence of seeing hundreds of "Defered" activity listings in SendGrid.
I am confused, however, if this is just the system getting these e-mails and then trying to bounce them back through my server. Since it's SPAM and likely not a real e-mail address, is SendGrid just trying to return the e-mails? Hence the activity?
If so, is this something that will eventually die down, or should I do something to prevent SendGrid from returning these obviously bogus SPAM e-mails to what it thinks is the originating sender?
Thanks in advance.
I send about 100K emails a month with sendgrid and I don't worry at all about deferred. About 1/3 of my outgoing emails are gmail and gmail is very agressive at blocking emails when you send more than 50 or so at once. They simply reject and sendgrid tries again later. They all seem to go thru within about 24 hours.
Just read on Google's Group for Wallet merchant support that the forum was being moved here, to stack overflow. Anyway, this is really a question for google's engineers. I have updated the postback URL multiple times from our google wallet merchant account, and every time have been greeted with the following message: "An unexpected error has occurred. Please try again later."
Later, when I refresh the page a few minutes following, the new postback url that I entered will appear to have taken. However, our merchant account will still not postback to the right URL. Sometimes this corrects itself 6-8 hours after entry --- other times it does not.
What gives? I'm very frustrated with google's in-app digital goods service for the preceding reason and am close to seeking out an alternate solution (even after 10+ developer hours implementing this with our subscriptions registration system)