Dear List,
Gmail has made some changes so with emails that are not sent from the domain of the email address (eg: an email from donald@duck.com sent by an SMTP server smtp.alligator.com) I get warnings such as "This message may not have been sent by: donald@duck.com", and/or the sender is displayed as " donald@duck.com via alligator.com". I've made some research and all this is because of increasing protection against email spoofing. The solution is to add a so-called SPF (Sender Policy Framework) record to your DNS records. (More info: http://www.openspf.org/) Some ISPs like Godaddy support it with their DNS editor, some others need to add a TXT record manually (in my case something like this: "v=spf1 mx mx: smtp.myisp.net include:smtp.gmail.com include:myotherisp.net -all").
Hope this helps some of you.
Andras
András,
Firstly, I cannot see this being relevant to anyone on the list.
Secondly, from my personal experience SPF doesn't help very much - you will need DomainKey and that need to be setup in the MTA.
My personal solution to all mail delivery issues is to use Google Apps with my domain name. If your SMTP server has potentially or really bad reputation (spam history, shared hosting, home ISP IP) - the chances that your mail arrives at gmail/hotmail/other are terribly unstable. I know this from my work experience at a shared hosting company.
The solution to this is to have private IP on a private host or use gmail/hotmail/other.
Cheers,
Ilya
On Wed, Jul 06, 2011 at 07:15:50PM +0200, András Murányi wrote:
Dear List,
Gmail has made some changes so with emails that are not sent from the domain of the email address (eg: an email from donald@duck.com sent by an SMTP server smtp.alligator.com) I get warnings such as "This message may not have been sent by: donald@duck.com", and/or the sender is displayed as " donald@duck.com via alligator.com". I've made some research and all this is because of increasing protection against email spoofing. The solution is to add a so-called SPF (Sender Policy Framework) record to your DNS records. (More info: http://www.openspf.org/) Some ISPs like Godaddy support it with their DNS editor, some others need to add a TXT record manually (in my case something like this: "v=spf1 mx mx: smtp.myisp.net include:smtp.gmail.com include:myotherisp.net -all").
Hope this helps some of you.
Andras
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Wed, Jul 6, 2011 at 23:29, errordeveloper@gmail.com wrote:
András,
Firstly, I cannot see this being relevant to anyone on the list.
It is - I see the warning attached to many people's mails (on this mailing list). Actually your mail has arrived with the warning: "This message may not have been sent by: errordeveloper@gmail.com - Learn more - Report phishing"
Secondly, from my personal experience SPF doesn't help very much - you will need DomainKey and that need to be setup in the MTA.
I'll need to see if SPF has a positive effect on this - at the moment, I just thought this is an emerging issue and people better hear about it from a mailing list than having person-to-person mails lost in nowhere.
My personal solution to all mail delivery issues is to use Google Apps with my domain name. If your SMTP server has potentially or really bad reputation (spam history, shared hosting, home ISP IP) - the chances that your mail arrives at gmail/hotmail/other are terribly unstable. I know this from my work experience at a shared hosting company.
The solution to this is to have private IP on a private host or use gmail/hotmail/other.
Yep, Google Apps mail has SPF (and maybe other things) built in, simple Gmail not.
Andras
On Thu, Jul 07, 2011 at 03:09:09AM +0200, András Murányi wrote:
On Wed, Jul 6, 2011 at 23:29, errordeveloper@gmail.com wrote:
Firstly, I cannot see this being relevant to anyone on the list.
It is - I see the warning attached to many people's mails (on this mailing list). Actually your mail has arrived with the warning: "This message may not have been sent by: errordeveloper@gmail.com - Learn more - Report phishing"
Yes, that's because the message was sent via the list server. SPF won't help, the warning which you is an awfull non-sense.
Secondly, from my personal experience SPF doesn't help very much - you will need DomainKey and that need to be setup in the MTA.
I'll need to see if SPF has a positive effect on this - at the moment, I just thought this is an emerging issue and people better hear about it from a mailing list than having person-to-person mails lost in nowhere.
Nope, you had been mislead by those silly warnings. I am not going to explain how email delivery works.
As I said, the reason why this sort of warning may come-up, is because the message from the list arrive with senders address in 'From:' from field, however it goes via the mailing list server, hence other fields do not match the domain name of the sender.
Whoever coded the software you are using, haven't placed an exception for mailing lists. There are RFC-coliant header fields which must be looked at by that software, but they are being ignored, which is wrong.
On Thu, Jul 7, 2011 at 04:27, errordeveloper@gmail.com wrote:
On Thu, Jul 07, 2011 at 03:09:09AM +0200, András Murányi wrote:
On Wed, Jul 6, 2011 at 23:29, errordeveloper@gmail.com wrote:
Firstly, I cannot see this being relevant to anyone on the list.
It is - I see the warning attached to many people's mails (on this
mailing
list). Actually your mail has arrived with the warning: "This message may not have been sent by: errordeveloper@gmail.com - Learn more - Report phishing"
Yes, that's because the message was sent via the list server. SPF won't help, the warning which you is an awfull non-sense.
I get the warning with many people's mails on the list, but definitely not all of them.
Secondly, from my personal experience SPF doesn't help very much - you will need DomainKey and that need to be setup in the MTA.
I'll need to see if SPF has a positive effect on this - at the moment, I just thought this is an emerging issue and people better hear about it
from
a mailing list than having person-to-person mails lost in nowhere.
Nope, you had been mislead by those silly warnings. I am not going to explain how email delivery works.
As I said, the reason why this sort of warning may come-up, is because the message from the list arrive with senders address in 'From:' from field, however it goes via the mailing list server, hence other fields do not match the domain name of the sender.
Whoever coded the software you are using, haven't placed an exception for mailing lists. There are RFC-coliant header fields which must be looked at by that software, but they are being ignored, which is wrong.
Google coded the software - I'm using Gmail. I agree that these warnings are way unnecessary (so far 100% of them), but as I said, if they joined the hype, there's a risk that others will join it too and the nonsense will become a general practice. I didn't want to annoy you or anyone, however.... :o)
Andras
You should then post a ticket in the support forum ;)
On 7 Jul 2011 14:54, "András Murányi" muranyia@gmail.com wrote:
On Thu, Jul 7, 2011 at 04:27, errordeveloper@gmail.com wrote:
On Thu, Jul 07, 2011 at 03:09:09...
I get the warning with many people's mails on the list, but definitely not all of them.
Secondly, from my personal experience SPF doesn't help very much - you will need Do...
Google coded the software - I'm using Gmail. I agree that these warnings are way unnecessary (so far 100% of them), but as I said, if they joined the hype, there's a risk that others will join it too and the nonsense will become a general practice. I didn't want to annoy you or anyone, however.... :o)
Andras
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
András Murányi -
error developer -
errordeveloper＠gmail.com