It may take more than one step to fix this issue
Take the step mentioned earlier. Log into your google email account and then go to this link: https://www.google.com/settings/security/lesssecureapps and set "Access for less secure apps" to ON. Test to see if your issue is resolved. If it isn't resolved, as it wasn't for me, continue to Step #2.
Go to ...
Once DKIM was setup (for help, see this guide) and verified successfully on my domain I still had to enable it in the AWS console at SES -> Domains -> DKIM
Once that was done mails to Gmail no longer show up with the via bounces address.
You can see it still shows as mailed by: amazonses.com when you view details of the sender but that's OK since ...
Check the current protocols:
net_protocols = all
Edit cf File if it returns all
grep 'inet_protocols' /etc/postfix/main.cf
inet_protocols = ipv4
service postfix restart
Check it again
inet_protocols = ipv4
From Google's point of view, they are trying to verify the identity of the IP address connecting to them, so they will attempt to look up the PTR record for 2a01:4f8:212:27c8::2.
When they resolve that to staging.findix.com, they will then attempt to check that this resolves back to 2a01:4f8:212:27c8::2 - which it doesn't - see this lookup result.
I discovered that the problem was that although we had SPF records set up for our domains, we did not have a DKIM record associated with our domain. In order to add a DKIM record in Google Apps, you need to do the following:
Go to the Admin Console
Click on "Google Apps"
Click on "Gmail"
Scroll down until you see "Authenticate Email" and click that
How about the smtp.gmail.com, why isn't it included?
Because smtp.gmail.com doesn't receive email for the gmail.com domain. You asked for the MX record for gmail.com. The answer you got was exactly that. The MX record designates which host(s) receives email for a given domain. The MX record tells you nothing about client submission SMTP servers, etc. A ...
Well it is not the one liner I wanted, but this is how to fetch and import a certificate from scratch:
# Create a certificate directory
~]$ mkdir certs
# Create a new database in the certs dir
~]$ certutil -N -d certs
# Need now a chain certificate - May 18, 2015
~]$ wget https://www.geotrust.com/resources/root_certificates/certificates/...
The delay appears to be within google's network. However, this is technically not a problem. SMTP delivery is not and should never be viewed as an instant method of communication. It's a store and forward with multiple stops along the way which means multiple queues and multiple locations where delays might occur. SMTP is designed this way and delays can (...
Your SPF record isn't affecting this.
By the looks of it, you have a DMARC record set up, and you are not signing outgoing mail with DKIM. To remedy the problem, either sign the outgoing mail, or remove the DMARC policy.
The DMARC record is a TXT record like the SPF record, but it is at _dmarc.example.net where example.net is your domain. If you don't ...
Your message is being rejected as spam because it precisely matches the profile of a very common malware distribution scheme: messages claiming to be order or shipping confirmations, with PDF attachments.
Clean up the grammar. "This is purchase order document for purchase order #1001"? Broken English sounds incredibly spammy, and although I ...
This worked for me.
1) Login to your gmail account.
2) Go to https://www.google.com/settings/security/lesssecureapps and Turn On this feature.
3) Go to https://accounts.google.com/DisplayUnlockCaptcha and click Continue.
Then you can authenticate your Additional Email Address from your Gmail Account.
Edit: In my case it helped to write smtp.gmail.com ...
Disclaimer: This answer was speculation one until GMail person confirmed it.
Looks like it's GMail mishandle your fetched email here. Some peoples also report similar case with yours in here, here or here
The problem is: GMail also deploying SPF measure when scanning email after fetching it via POP3.
Normally SPF-checking take place in SMTP transaction ...
I solved this by adding both these lines to Postfix's main.cf:
smtp_tls_security_level = may
smtpd_tls_security_level = may
(I had only set smtpd_tls_security_level because of a misleading article that said all smtp_ values were depreciated in favour of smtpd_.)
As joeqwerty rightly points out, it doesn't show smtp.google.com because a MX record indicates where mail servers should send messages destined for that domain. This is not the same as the servers that should be used by an end-user's e-mail client to transmit outgoing messages to arbitrary destinations.
RFC 6186 describes a method for automatically ...
This issue, at least on Ubuntu 12.04, is caused by the /etc/postfix folder not being owned by the postfix user. (as inferred above).
The error message is caused because you should not directly create the .db file yourself. If you did, delete it.
postmap: fatal: cannot remove zero-length database file /etc/postfix/sasl_passwd.db: Permission denied.
Mailchimp have an excellent article on How To Avoid Spam Filters
Update: Ok, seeing as I got slammed for just giving this link (to be fair its contents probably wouldn't solve your problem here), I've added more specific to what you're sending.
I suspect its the text you're using. 'Please confirm your email address by clicking the link' - I think you ...
You want to prevent this sort of thing in the future? Use a real MTA instead of Google Apps. As you've discovered, it is certainly possible to relay emails through a GApps account, but it's far from ideal, and frankly, it's not what that service was built to do. They give you zero visibility into logs of any sort, which you'd need in order to troubleshoot ...
Here is the text from google's help page:
Additional guidelines for IPv6
The sending IP must have a PTR record (i.e., a reverse DNS of the sending IP) and it should match the IP obtained via the forward DNS
resolution of the hostname specified in the PTR record. Otherwise,
mail will be marked as spam or possibly rejected.
The sending domain ...
If gmail doesn't like your messages your issue is with Google. You need to talk to them.
Refusing to provide us troubleshooting details just ensures that we can't help you.
If you are a bulk sender, this link is for you.
If you're not a bulk sender you want this link
(If that second link doesn't work it's the part of the first link that says "Not a bulk ...
Your application can send mail directly from its application server, provided you take some steps to ensure that your outbound mail doesn't get flagged as spam. This includes setting reverse PTR (DNS) records for the sending server's IP address. Possibly some manipulation of headers and maybe an SPF record...
Another option is to relay your application's ...
You can not configure some other company's email server to hand off emails unless you have an actual account there. Even if you do have an account monit isn't the best program to deal with submitting email. What I would suggest is to just install a local MTA to listen on 127.0.0.1 and then configure monit like this:
set mailserver 127.0.0.1
In that case ...
Let's follow the trail of evidence here:
$ whois toafinish.com | grep "Name Server"
Name Server: DNS1.HOST1PLUS.COM
Name Server: DNS2.HOST1PLUS.COM
Those are the authoritative nameservers for your domain. Let's look at the current SPF records:
$ dig txt toafinish.com +short
"v=spf1 a mx include:e2ma.net ~all"
"spf2.0/pra a mx include:e2ma.net ~all"
Just like snail mail letters, SMTP email has two different sets of address information: the envelope headers (like the addresses printed on the outside of an envelope) which are used by the SMTP servers to route and deliver the email, and the normal headers, which are part of the mail message and which are only read and interpreted by the user in his mail ...
SES is not designed for this - SES is primarily for automated sending email, with the facility to receive email and send it to automated systems via Lambda, SNS, or stored on S3. Sending would actually work fine from email clients. The thing that won't work is receiving email, as below - it doesn't store it for collection by IMAP or similar.
You can use ...
Is there an easy way to gain a Trusted TLS connection instead of untrusted, do I need to buy something or this free certificate should work?
This is not about your certificate, so you don't need to buy anything. It's about: How does your Postfix verify the cert of Gmail?
Try to add:
smtp_tls_CApath = /etc/ssl/certs
smtpd_tls_CApath = /etc/ssl/certs
DomainKeys Identified Mail (DKIM) is for ensuring that mail content hasn't tampered during transmission. Unlike Sender Policy Framework (SPF) it's not trying to validate the source of the message as permitted sender. RFC 5585, 1.1 DKIM's Scope explains this:
DKIM is intended as a value-added feature for email. Mail that is not
signed by DKIM is handled ...
It turns out the problem here was GMail not showing e-mails forwarded back to it. Sending an e-mail from other addresses were correctly forwarded. GMail seems to discard the messages that are forwarded back to it.
The terms modern security standards standards was "little" vague here. No one except google can explain what is the exact meaning of modern security standards standards.
However, after lurking the internet about this term, here some explanation about this incident.
apsillers answer on Security.SE
In my understanding, "less secure apps" refers to ...