I use Google Service for work, my domain is ".com" I need send mail to ".com.br". The mails of ".com" arrive normal, but the ".com.br" return. I don't know where the mistake is.
In the Route S3 - type MX: Values: below
1 ASPMX.L.GOOGLE.COM
5 ALT1.ASPMX.L.GOOGLE.COM
5 ALT2.ASPMX.L.GOOGLE.COM
10 ALT3.ASPMX.L.GOOGLE.COM
10 ALT4.ASPMX.L.GOOGLE.COM
10 ASPMX3.GOOGLEMAIL.COM
10 ASPMX2.GOOGLEMAIL.COM
Related
I already have an email_sender function using Celery; each email takes 3 seconds to send, and i want to improve my function.
so i need Celery to do something like this:
send email_num[1:500] ---> each email send in 20 second send email_num[500:1500] ---> each email send in 15 second send email_num[1500:5000] ---> each email send in 10 second send email_num[5000:] ---> each email send in 5 second
is there any solution?
I tried to set dynamic time for a task.
Hello I have a google docs document where I installed a simple emailing code on as follows:
function sendMail() {
var file = DriveApp.getFileById('XXXXXXXX');
var recipients = "mymail#group1.com" + "mymail#group2.com" + "mymail#group3.com";
MailApp.sendEmail(recipients, 'Daily Notes', 'Please see file Attached.', {
name: file.getName(),
attachments: [file.getAs(MimeType.PDF)]
});
}
The code works fine it sends the email to multiple group emails which I want it to send. It has done this for a month now. But until recently, I keep receiving this Mail Delivery Subsystem after 20 minutes or 1 hour from the original email which is sent out and inside the error message email it says:
"The following addresses had permanent fatal errors"
and it points to only one of the emails I send daily mails to. It also says something like this: (reason: 554 5.4.6 Too many hops). and then this:
554 5.4.6 Too many hops 53 (50 max).
The Good Doc's file has Google's time-driven trigger as you can see in the image below. I wonder if somehow the trigger is running twice in the time interval I gave to it. Could it be why this is happening?
In almost all cases 554 5.4.6 Too many hops 53 (50 max) means loop along email delivery path e.g. server A forwards to server B, server B forwards to server A, server A forwards to sever B, …. It is detected by counting Received: headers in message passing via give SMTP/email server.
Suggested fixing procedure:
Inspect Reveived: headers in email bounce message to locate server(s) responsible for the loop.
contact the relevant postmaster
In many years I have seen just one "real life" case when bounce message/email like that was not caused by email delivery loop.
I've set up MX records as such:
5 # ALT1.ASPMX.L.GOOGLE.COM
5 # ALT2.ASPMX.L.GOOGLE.COM
10 # ALT3.ASPMX.L.GOOGLE.COM
10 # ALT4.ASPMX.L.GOOGLE.COM
1 # ASPMX.L.GOOGLE.COM
CNAME as such:
www xxxx.rhcloud.com
The problem is that xxxx.com does not resolve to www.xxxx.com in a web browser.
The second problem is that emails sent to xxxx.com return with "DNS Error: Address resolution of xxxx.ca. failed: DNS server returned answer with no data". And before, "The recipient server did not accept our requests to connect.".
Another thing was this. Not sure what that is.
I've seen some hints on the internet to set up an A record to route # to the IP of the server, but rhcloud dosen't have one IP, I don't think.
I'm completely out of my depth here. I just want my google apps emails to work, and website to direct trafic to my rhcloud server.
You can't set your root domain as CNAME, only subdomain can be CNAME.
Root domain must have A-record if you want correct redirect to www.yoursite.com in web browser.
I've seen some hints on the internet to set up an A record to route # to the IP of the server, but rhcloud dosen't have one IP, I don't think.
Symbol "#" in DNS zone means "root domain without subdomains, so this two record are equal:
NAME TYPE VALUE
--------------------------------------------------
someexample.com. A 55.33.11.22
# A 55.33.11.22
I don't know how openshift works, but looks like you can have only subdomain directed to your xxx.openshift.com application.
Issues with MX records in is unrelated to first question and I can't say what actually wrong.
Will be better if you show your real domain name so I can look on real zone configuration.
What I Want
We send out bulk renewal notices via email and it would be ideal if we could link any bounce messages with the corresponding record in our database. I recently learned about VERP (wiki) and thought that would be the perfect solution for us.
What I Tried
I did a test before making any changes and the message is bounced back to sender, as expected. Then I uncommented this line in /etc/postfix/main.cf and restarted Postfix.
recipient_delimiter = +
The Problem
Unfortunately, I can't seem to get it to work. Messages sent to addresses that include the delimiter are no longer rejected, but they don't appear to be delivered anywhere either. Here's an excerpt from the maillog:
Jul 8 12:14:36 cl-t082-392cl postfix/smtpd[28723]: 6E98A1A404CC: client=mta02.eastlink.ca[24.224.136.13]
Jul 8 12:14:36 cl-t082-392cl postfix/cleanup[28727]: 6E98A1A404CC: message-id=<6.1.2.0.2.20130708131351.24958960#pop.eastlink.ca>
Jul 8 12:14:36 cl-t082-392cl postfix/qmgr[28717]: 6E98A1A404CC: from=<me#example.com>, size=1343, nrcpt=1 (queue active)
Jul 8 12:14:36 cl-t082-392cl postfix/pipe[28752]: 6E98A1A404CC: to=<bounces+test#ourdomain.com>, relay=plesk_virtual, delay=0.22, delays=0.15/0/0/0.07, dsn=2.0.0, status=sent (delivered via plesk_virtual service)
Jul 8 12:14:36 cl-t082-392cl postfix/qmgr[28717]: 6E98A1A404CC: removed
So it appears that Postifx is doing its job, but that the plesk_virtual service is dropping the ball. No message is returned to sender. No message shows up in bounces/Maildir/cur. If plesk_virtual is writing an error somewhere, I don't know where (I checked /var/log/messages).
My Search Efforts
I searched Google, here, and the Parallels forums. I got several hits in Google for the same problem I am having, but they are all for the same message which is dated almost 3 years ago. And there was no solution given. I posted to the Parallels forums several days ago. I've gotten a few views, but zero responses.
What I Don't Want
I've seen similar problems where the suggestion was to forward all undelivered mail to a particular address. That's a catch-all. And that is not a realistic solution in today's world of spam.
Question
How do I get Plesk to correctly recognize and deliver messages to addresses with the delimiter? I can't imagine that I am the only one who wants to do this on a Plesk server.
I answered this on the Plesk forums. For anyone still interested there is a postfix workaround.
Added the following to the main.cf:
recipient_canonical_classes = envelope_recipient
recipient_canonical_maps = regexp:/etc/postfix/recipient_canonical_map
Created a file /etc/postfix/recipient_canonical_map with this regex:
/^(.+)\+.+#(.*)/ ${1}#${2}
Granted, it assumes + is the only VERP delimiter but it works. The only caveat is that it does not bounce bad addresses, which may not be a bad thing..
RFC1893 claims that status codes will come in the format below you can read more here.
But our bounce management system is having a hard time parsing error status code from bounce messages. We are able to get the raw message, but depending on the email server the code will come in different places. Is there any rule on how to parse this type of messages to obtain better results. We are not looking for the 100% solution but at least 80%.
This document defines a new set of status codes to report mail system
conditions. These status codes are intended to be used for media and
language independent status reporting. They are not intended for
system specific diagnostics.
The syntax of the new status codes
is defined as:
status-code = class "." subject "." detail
class = "2"/"4"/"5"
subject = 1*3digit
detail = 1*3digit
White-space characters and comments
are NOT allowed within a status-
code. Each numeric sub-code within
the status-code MUST be expressed
without leading zero digits.
The quote above from the RFC tells one thing but then the text below from a leading tool on bounce management says something different, where I can get a good source of standard status codes:
Return Code Description
0 UNDETERMINED - (ie. Recipient Reply)
10 HARD BOUNCE - (ie. User Unknown)
20 SOFT BOUNCE - General
21 SOFT BOUNCE - Dns Failure
22 SOFT BOUNCE - Mailbox Full
23 SOFT BOUNCE - Message Too Large
30 BOUNCE - NO EMAIL ADDRESS. VERY RARE!
40 GENERAL BOUNCE
50 MAIL BLOCK - General
51 MAIL BLOCK - Known Spammer
52 MAIL BLOCK - Spam Detected
53 MAIL BLOCK - Attachment Detected
54 MAIL BLOCK - Relay Denied
60 AUTO REPLY - (ie. Out Of Office)
70 TRANSIENT BOUNCE
80 SUBSCRIBE Request
90 UNSUBSCRIBE/REMOVE Request
100 CHALLENGE-RESPONSE
I'm not sure that it's a full answer, but this algorithm for detecting bounces might be useful.