Tag Info

New answers tagged

1

I see several issues: PTR record returns shoplucro2.smtpilimitado.info which does not lookup to 23.88.121.82. It should likely return mail.fluidvector.com. With few exceptions this would be a good indicator of Spam. Envelope address and From: address don't match. If you aren't resending email, they should match. If you don't want auto-replies (as I ...


3

You cannot authorize some domain to send mail from gmail addresses, only Google can do that. If everyone could authorize their own server to send some other domain's email, then SPF would serve no purpose. Spammers would just authorize themselves. You need to use a source email address whose credentials you control.


0

Are you sending email back to the same gmail account that you are posting the email from? If a message goes from abc@gmail.com to def.whatever and then back to abc@gmail.com, gmail will not put the message in the inbox. https://support.google.com/mail/answer/6588?hl=en You can change this behavior by specifying the def@whatever as an alternate email address ...


0

Apparently after a few days it start working fine. Right now, I guess what really matters in GMAIL is actually passing this tests: SPF check: pass DomainKeys check: neutral DKIM check: pass Sender-ID check: pass SpamAssassin check: ham And wait 3 or 4 days so google can update their servers. Seems like the spam filter does some kind ...


0

We confirmed a bug related to encryption in our smtp library, which only affected some SMTP hosts (including google). We have temporarily switched smtp libraries and confirmed that SecAst can now send through google using TLS and SSL. SecAst version 1.0.4 is now available for download on the www.generationd.com website, and should work fine with google. ...



Top 50 recent answers are included