Hi folks. We have noticed a number of domains in NZ have entered in their NS's domain.co.nz IN TXT "v=spf1 mx -all" This means domain.co.nz will never attempt to send emails at all. (but valid emails are trying to be sent). I've talked to a couple of domain holders who had this and they've fixed them but most said it was done ages ago and they where playing and never expected it to catch on (but it has a lot looking at the number) We (Orcon) have started to use SPF (for testing inbound email) and found it helps with identifying spam. _ALOT_ of people have published valid SPF records. Thanks Craig Whitmore Orcon Internet
SPF = Sender Policy Framework.. http://spf.pobox.com/ It's a new sort of spam filter, that is better than the Microsoft offering. On Tue, 2004-10-19 at 16:03, Craig Whitmore wrote:
Hi folks.
We have noticed a number of domains in NZ have entered in their NS's domain.co.nz IN TXT "v=spf1 mx -all"
This means domain.co.nz will never attempt to send emails at all. (but valid emails are trying to be sent). I've talked to a couple of domain holders who had this and they've fixed them but most said it was done ages ago and they where playing and never expected it to catch on (but it has a lot looking at the number)
We (Orcon) have started to use SPF (for testing inbound email) and found it helps with identifying spam. _ALOT_ of people have published valid SPF records.
Thanks Craig Whitmore Orcon Internet
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
Just to be clear : SPF is not and never will be a 'spam filter'. It is only helpful in defining which machines are allowed to send mail for a given domain. It's anti-forgery, not anti-spam per se. Murray On Tue, 2004-10-19 at 16:07, Chris Hodgetts wrote:
SPF = Sender Policy Framework..
It's a new sort of spam filter, that is better than the Microsoft offering.
On Tue, 2004-10-19 at 16:03, Craig Whitmore wrote:
Hi folks.
We have noticed a number of domains in NZ have entered in their NS's domain.co.nz IN TXT "v=spf1 mx -all"
This means domain.co.nz will never attempt to send emails at all. (but valid emails are trying to be sent). I've talked to a couple of domain holders who had this and they've fixed them but most said it was done ages ago and they where playing and never expected it to catch on (but it has a lot looking at the number)
We (Orcon) have started to use SPF (for testing inbound email) and found it helps with identifying spam. _ALOT_ of people have published valid SPF records.
Thanks Craig Whitmore Orcon Internet
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
My bad -- Apologies all round.. On Tue, 2004-10-19 at 16:19, Murray Fox wrote:
Just to be clear : SPF is not and never will be a 'spam filter'. It is only helpful in defining which machines are allowed to send mail for a given domain.
It's anti-forgery, not anti-spam per se.
Murray
On Tue, 2004-10-19 at 16:07, Chris Hodgetts wrote:
SPF = Sender Policy Framework..
It's a new sort of spam filter, that is better than the Microsoft offering.
On Tue, 2004-10-19 at 16:03, Craig Whitmore wrote:
Hi folks.
We have noticed a number of domains in NZ have entered in their NS's domain.co.nz IN TXT "v=spf1 mx -all"
This means domain.co.nz will never attempt to send emails at all. (but valid emails are trying to be sent). I've talked to a couple of domain holders who had this and they've fixed them but most said it was done ages ago and they where playing and never expected it to catch on (but it has a lot looking at the number)
We (Orcon) have started to use SPF (for testing inbound email) and found it helps with identifying spam. _ALOT_ of people have published valid SPF records.
Thanks Craig Whitmore Orcon Internet
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
______________________________________________________________________ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
Chris Hodgetts
SPF = Sender Policy Framework..
It's a new sort of spam filter, that is better than the Microsoft offering.
SPF is merely designed to tell you whether an email has come from an authorised server for that domain. If an SPF check fails, it's probably spam. (Or a roaming user and someone hasn't got their config right.) If email passes an SPF check, it doesn't mean it's not spam - spammers can buy their own domains for a couple of bucks and publish their own SPF records. cheers, Jamie -- James Riden / j.riden(a)massey.ac.nz / Systems Security Engineer Information Technology Services, Massey University, NZ. GPG public key available at: http://www.massey.ac.nz/~jriden/
If email passes an SPF check, it doesn't mean it's not spam - spammers can buy their own domains for a couple of bucks and publish their own SPF records.
True.. not anti-spam as such.. but anti-forgery, but stops a lot of spam. True, spammers can put their own SPF records in.. but then they'll have to send it from their own domain (not someone else's which seems to happen a lot now) Thanks Craig
-----Original Message----- From: James Riden [mailto:j.riden(a)massey.ac.nz]
SPF is merely designed to tell you whether an email has come from an authorised server for that domain. If an SPF check fails, it's probably spam. (Or a roaming user and someone hasn't got their config right.)
I've wanted to setup SPF in the past but have always wondered what happens when you have a roaming user sending via paradise for example. Would you need to add all the outbound mx servers; for example paradise receives mail to smtp.paradise then it could come from one of many hosts that do anti virus and spam protection. Would one need to know every internet facing ip for all ISP's mailservers? Barry
At 16:21 19/10/2004, James Riden wrote:
Chris Hodgetts
writes: SPF = Sender Policy Framework..
It's a new sort of spam filter, that is better than the Microsoft offering.
SPF is merely designed to tell you whether an email has come from an authorised server for that domain. If an SPF check fails, it's probably spam. (Or a roaming user and someone hasn't got their config right.)
Just to be clear here - roaming users are not compatible with SPF *unless* the ISP's mailserver supports an authentication scheme like SMTP AUTH, and the users use it. This is probably the single biggest stumbling block for widespread adoption of SPF. If you advertise SPF records but don't provide SMTP AUTH, you effectively lock out your roaming users, or those that obtain services from multiple ISP's. (Jetstream with one ISP, webhosting + email with another for instance) The ideal situation would be that all ISP's that support roaming POP3 access (eg: everyone except Xtra and Clear(?) ) also support SMTP AUTH and therefore roaming SMTP, and also (eventually) publish SPF records. An ISP shouldn't even consider adding SPF records until they support SMTP AUTH. We (iGRIN) have had SMTP AUTH for a long time now, but don't currently have any SPF records. How many other ISP's support SMTP AUTH ? Last time I did a quick check about 6 months ago, (looking at the response to the EHLO command) less than a quarter of the NZ ISP's I tried reported SMTP AUTH being available. (Orcon and IHUG spring to mind as two who did support SMTP AUTH at the time) Widespread support for SMTP AUTH would be a good first step in the right direction towards schemes such as SPF... Regards, Simon
"Craig Whitmore"
Hi folks.
We have noticed a number of domains in NZ have entered in their NS's domain.co.nz IN TXT "v=spf1 mx -all"
Working through http://spf.pobox.com/wizard.html seems to suggest that "v=spf1 mx -all" means that only the MXs for the hypothetical 'domain.co.nz' are allowed to send email - otherwise it would be "v=spf1 -all" wouldn't it? (Confusingly, there is a real 'domain.co.nz' and it doesn't seem to publish SPF.) -- James Riden / j.riden(a)massey.ac.nz / Systems Security Engineer Information Technology Services, Massey University, NZ. GPG public key available at: http://www.massey.ac.nz/~jriden/
Working through http://spf.pobox.com/wizard.html seems to suggest that "v=spf1 mx -all" means that only the MXs for the hypothetical 'domain.co.nz' are allowed to send email - otherwise it would be "v=spf1 -all" wouldn't it?
Yes.. your right :-) (I was wrong) "v=spf1 -all" = I will not send any email. "v=spf1 mx -all" = I will only send from mx.domain... Domain.co.nz was only an example :-) (not a real one with wrong records) even so.. there are some domains in NZ (and outside NZ) who have incorrect sfp records. Thanks Craig
On Tue, 2004-10-19 at 16:25 +1300, Craig Whitmore wrote:
Working through http://spf.pobox.com/wizard.html seems to suggest that "v=spf1 mx -all" means that only the MXs for the hypothetical 'domain.co.nz' are allowed to send email - otherwise it would be "v=spf1 -all" wouldn't it?
Yes.. your right :-) (I was wrong) "v=spf1 -all" = I will not send any email. "v=spf1 mx -all" = I will only send from mx.domain...
Domain.co.nz was only an example :-) (not a real one with wrong records)
even so.. there are some domains in NZ (and outside NZ) who have incorrect sfp records.
Whew! I have a _heap_ of domains here that have "mx -all" or "a mx -all" for their SPF and these were all originally generated from the spf.pobox.com web based helper. We too have found SPF somewhat useful as further grist for SpamAssassin - not trustable for a variety of reasons, but something that is very susceptible to the sorts of heuristics that SpamAssassin does quite well. Regards, Andrew McMillan. ------------------------------------------------------------------------- Andrew @ Catalyst .Net .NZ Ltd, PO Box 11-053, Manners St, Wellington WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St DDI: +64(4)803-2201 MOB: +64(272)DEBIAN OFFICE: +64(4)499-2267 Expect the worst, it's the least you can do. -------------------------------------------------------------------------
Craig Whitmore wrote:
We have noticed a number of domains in NZ have entered in their NS's domain.co.nz IN TXT "v=spf1 mx -all"
This means domain.co.nz will never attempt to send emails at all. (but valid emails are trying to be sent). I've talked to a couple of domain holders who had this and they've fixed them but most said it was done ages ago and they where playing and never expected it to catch on (but it has a lot looking at the number)
Hi Craig, I'm not certain that's quite right I've been experimenting with it too and the spf wizard (at spf.pobox.com) says of domain.co.nz, which is incidentally real: v=spf1 This identifies the TXT record as an SPF string. mx This wizard found 2 names for the MX servers for domain.co.nz: domain.co.nz and mx2.cedant.com. (A single machine may go by more than one hostname. All of them are shown.) The servers behind those names are allowed to send mail from domain.co.nz. -all No other servers are allowed to send mail from domain.co.nz. This is a good default. This seems to me to be a quite possible situation? Happy to be corrected, I'm certainly no expert on this. Cheers Bob -- Robert Gray bob(a)brockhurst.co.nz
http://www.ietf.org/internet-drafts/draft-iab-dns-choices-00.txt skip straight to Section 4 if you want the punch-line. Abstract This note discusses how to extend the DNS with new data for a new application. DNS extension discussion too often circulate around reuse of the TXT record. This document lists different mechanisms to accomplish the extension to DNS, and comes to the conclusion use of a new RR Type is the best solution.
On Tuesday 19 October 2004 16:03, Craig Whitmore wrote:
We have noticed a number of domains in NZ have entered in their NS's domain.co.nz IN TXT "v=spf1 mx -all"
This means domain.co.nz will never attempt to send emails at all. (but valid emails are trying to be sent).
No it means that the only hosts that should be sending mail for the domain domain.co.nz are those listed in MX records for domain.co.nz. Mail coming from any other hosts claiming to be from that domain should be considered bogus. See the SPF setup wizard at spf.pobox.com for details. cheers mark
Without want to sound too negative, there are some serious shortcomings with SPF in its current form. The proposed SRS solution is just making the problem worse. http://homepages.tesco.net/~J.deBoynePollard/FGA/smtp-spf-is-harmful.html I have already struck a couple of sites where our relay solution broke because of strick adherence to SPF, juno.com being one that comes to mind. While everyone will admit that SPAM is a serious problem, I don't believe that SPF is the silver bullet. If you intent to put in SPF rules for a domain, use the option that says mail should probably come from here but don't block it if it doesn't i.e. "v=spf1 +mx ?all" ( I think this is the right incantation
participants (11)
-
Andrew McMillan
-
Barry Murphy
-
Chris Hodgetts
-
Craig Whitmore
-
Glen Eustace
-
James Riden
-
Mark Davies
-
Matthew Luckie
-
Murray Fox
-
Robert Gray
-
Simon Byrnand