/cOn Wed, 2005-06-29 at 19:31 +0200, Beat Rubischon wrote:
Hello!
Am 28.06.05 schrieb Daniel Lorch:
Do you have more information?
This documents were very short and summarized Sender-ID very well:
...
Thanks for the links.
Indeed nice M$-marketing.
And here is the part which
Hello!
Am 28.06.05 schrieb Daniel Lorch:
Do you have more information?
This documents were very short and summarized Sender-ID very well:
...
Thanks for the links.
And here is the part which is
incompatible with Classic SPF. The records are the same, but while
Classic SPF ONLY used them
On Tue, 2005-06-28 at 03:44 +0200, Daniel Lorch wrote:
SNIP M$ marketing bull, yup in this case I don't like the M$ way...
Coincidentially, I checked aol.com's SPF record today and I found this.
I don't have the full bigger picture yet, but I believe these are
Classic SPF records AND a
Hello!
Am 26.06.05 schrieb Jeroen Massar:
http://www.mail-spf.org/
Which has quite some up-to-date info.
There is a lot of political and rare technical discussions on the
net. I found a nice discussion while Googeling:
http://www.gossamer-threads.com/lists/spf/deployment/13622
I was
There is a 'small' problem with this. AOL uses SPFv1, while Microsoft
is pushing SPFv2, which is not really SPFv2, but their own version
of the thing which clashes with the real SPFv1 (openspf.org one) also
called classic and that is the one people have been deploying the last
2 years, not
Hi
I'm still looking for a deeper explanation. The one I found at
Microsoft [1] exactly explains SPF as I know and the wizard [2]
creates the same records as the wizard on spf.pobox.com.
[1]
http://www.microsoft.com/mscorp/safety/technologies/senderid/default.mspx
[2]
Hi
The Sender ID Framework (SIDF) is the name of the product, not the
technology. SIDF uses SPF records and solves some of the problems with
forwarding mails and stuff by introducing new mail headers and a new
command in the SMTP transaction, which allows you to do all the funky
SPF
Hi
http://www.microsoft.com/downloads/details.aspx?FamilyId=8FE5AAF3-6E5B-478C-9303-6E1E9BBEC94Ddisplaylang=en
Reminds me: microsoft.com is definately not Cool URI compliant :)
http://www.w3.org/Provider/Style/URI.html
Daniel
___
swinog mailing
Ignore it and if a hotmail customer complains to you, tell them their
hotmail SPAM filter is busted and you can not do anything against it.
The hotmail users should start yelling at Microsoft and not at anybody
else.
I wouldn't see it so bad. First, they'll start in november which leaves
On Sun, 2005-06-26 at 13:06 +0200, Jean-Pierre Schwickerath wrote:
Ignore it and if a hotmail customer complains to you, tell them their
hotmail SPAM filter is busted and you can not do anything against it.
The hotmail users should start yelling at Microsoft and not at anybody
else.
Jean-Pierre Schwickerath wrote:
Ignore it and if a hotmail customer complains to you, tell them their
hotmail SPAM filter is busted and you can not do anything against it.
The hotmail users should start yelling at Microsoft and not at anybody
else.
I wouldn't see it so bad. First,
On Sun, 2005-06-26 at 15:52 +0200, Beat Rubischon wrote:
Hello!
Am 26.06.05 schrieb Jeroen Massar:
There is a 'small' problem with this. AOL uses SPFv1, while Microsoft is
pushing SPFv2, which is not really SPFv2, but their own version of the
thing which clashes with the real SPFv1
On Fri, Jun 24, 2005 at 10:22:46PM +0200, Chris Burri wrote:
http://www.infoweek.ch/news/NW_single.cfm?news_ID=11162sid=0
darn renegades from Redmond again
Ignore it and if a hotmail customer complains to you, tell them their
hotmail SPAM filter is busted and you can not do anything
13 matches
Mail list logo