Gary Bainbridge wrote:
In article <[email protected]>, [email protected] (Ralf) wrote:
Sorry Davide, but I _must_ use SPF. That's the policy here.
The problem with SPF is too many false positives.
For example, you might send me an email. I check the email using my
mobile phone, then reply.
But my mobile phone is not on my domain so SPF will reject my reply.
Similarly if I use a mail to web service from an internet café or a
hotel.
It's a problem I've had several times with my emails being rejected by
the recipient.
As Davide rightly said, it's far less effective than black listing or
other techniques.
Try and get the policy changed.
Hmm... I think there are some misunderstandings here.
SPF is intended for servers only, not for end users.
If the user sends his mail via his mail server then
the receiving mail server just checks in the DNS DB
whether the sending mail server (not the user!) is
really permitted to send mails for that domain.
Nothing less, nothing more.
If you deliver your mail directly then you act as a server,
and consequently you should add an SPF record to your domains'
DNS entries. If that's not possible or is impractical
then just send your mail via your mail server.
I would say 99+% of the users send their mails thru their
mail servers instead of sending it directly.
And: nowadays most mail servers have also a web interface,
so you can access your mail server where your account is
from anywhere in the world directly, without using
any 3rd party service. I also wonder how you can send
mail from an 'alien' system with your credentials of your
'home' mail server. Surely you have to give your mail password
to this other site, isn't it? :-) How insecure! I never would do so.
_______________________________________________
xmail mailing list
[email protected]
http://xmailserver.org/mailman/listinfo/xmail
