I tested my SPF configuration that I added to my DNS. I ran the test
through http://senderid.espcoalition.org/
Here are the results:
http://senderid.espcoalition.org/results.php?ToAddress=fkUYd I4P%40senderid.espcoalition.org
Is this sufficient even though DomainKey and DKIM don't show as
success?
I am just trying to get emails we send out from being thought of as
SPAM.
PhxVyper
>I am just trying to get emails we send out from being thought of as
>SPAM.
SPF keys won't help with that. Anyone can set up an SPF key for a
domain, spammers included. If you create an SPF record then it will be
easier to spot spam when it has your address forged into it as the
sender, that's all., Spam filters cannot assume that a valid SPF key
means the mail is respectable in any way.
In an earlier thread you said your mails were being blocked as spam
but still haven't indicated why that is. If someone is telling you
that your mails are being blcoked then surely they ought to be able to
tell you why as well. Unless you really are sending out spam and the
people blocking it don't wish to assist you.
On May 13, 4:13 am, Landmark
> PhxVyper
> >I am just trying to get emails we send out from being thought of as
> >SPAM.
>
> SPF keys won't help with that. Anyone can set up an SPF key for a
> domain, spammers included. If you create an SPF record then it will be
> easier to spot spam when it has your address forged into it as the
> sender, that's all., Spam filters cannot assume that a valid SPF key
> means the mail is respectable in any way.
>
> In an earlier thread you said your mails were being blocked as spam
> but still haven't indicated why that is. If someone is telling you
> that your mails are being blcoked then surely they ought to be able to
> tell you why as well. Unless you really are sending out spam and the
> people blocking it don't wish to assist you.
Hi,
Thanks for the info on SPF and its limitation.
What we get are complaints from people who send us emails that they
were told on the registration page that they would receive a
confirmation email with instructions on verifying their account (also
meaning it verifies that the email address they entered in is valid),
but they never get the email. We know the email is getting sent. I
have verified it via our logs. Now here is something that is
interesting - when the email is sent from the code, these people don't
get the email (the code sends it via php's mail function which uses
sendmail). But if I send an email to them - not through code, but
just as a normal email via an email client through our mail server,
they get the email.
PhxVyper
>Now here is something that is
>interesting - when the email is sent from the code, these people don't
>get the email (the code sends it via php's mail function which uses
>sendmail). But if I send an email to them - not through code, but
>just as a normal email via an email client through our mail server,
>they get the email.
The most likely reason for that is that the sendmail you use on the
webserver is a different mailer to the mailer you use when you send
out your normal mail, i.e. different IP address. Maybe the two
machines are being treated differently the the recipients spam
filtering service.
If your website is hosted for you then it may well be that there is a
mailer used by dozens of different websites and therefore it may, for
reasons entirely beyond your control, get tagged as a spam source from
time to time. It may be that your provider had a reputation as a spam
source in the past and people are using blacklists which still list it
as a spam source, even though it is no longer emitting spam.
Landmark
>The most likely reason for that is that the sendmail you use on the
>webserver is a different mailer to the mailer you use when you send
>out your normal mail,
Looking at your posting, it looks like your ISP is cox.net and you
probably use cox for your email, but your webserver looks like it is
hosted on rackspace.
I've no idea what rackspace is like as a spam-source or as an enforcer
of antispam policies, no personal experience of them, but this page
says:
http://www.rahul.net/falk/quickrefh.html#R
Pro-spam network service provider. Has anti-spam policy but is
extremely lax about enforcing it. Clients have included
herbmeister.net, Alan Ralsky, penisgrowth.com and many others.
Now that page may be accurate, or it may be hopelessly out of date,
but I'll bet that there are people blocking rackspace because, at some
unspecified time in the past, they had spam from them. If you search
Google Groups for "Rackspace Spam" then you find a lot of reports but
mostly dated 2004 or earlier.
More great info! Thanks.
With regard to when I send emails to members of the site, I'm actually
sending it directly from our mail server on the machine (using the
simple webmail client in Webmin). So, I think your assessment about
sendmail sending email through some other mailer than our smtp server
(which is qmail) is 100% correct. I'll have to test this. I may just
have to modify our mailer class to use smtp to send email through our
qmail service.