Re: Sender ID Framework SPF Record Wizard

In news:O5rIUZxeFHA.1036@xxxxxxxxxxxxxxxxxxxx,
Phil <hostsafe@xxxxxxxxxxxxxxx> stated, and I replied below:

I'm sure Microsoft didn't make the decision lightly and without
considering all the ill effects it would cause providers out there.
How else would you suggest to combat spam?


Ace,

My whole complaint deals with the poor instructions and support by
Microsoft for those of us who aren't DNS experts. I do not take issue
on Microsoft's attempt to reduce SPAM.


There have been some suggestions to combat spam, such as SPF.
Microsoft had one similar to SP called SenderID


I'm once more confused.  I assumed Sender ID and SPF were one and the
same technology.
http://www.microsoft.com/mscorp/safety/technologies/senderid/technology.mspx

There is that option XML component. I don't think many will jump to use that quite yet, but that's a possibility.



So would you strike at AOL as well as Microsoft for adopting SPF? 

That's news to me.  My server sends thousands of emails to AOL every
day, and I've never heard a single recipient complain that their
incoming email from our server is being tagged as SPAM.

No, not yet. If your system is on an RBL or doesn't have a PTR, they just deny the email. If you are getting thru, fine. They are not requireing SPF quite yet, but they are heading in that direction.



Neither does Exchange. So I guess it would bother admins that use
Exchange as well, about adopting SPF. Unfortunately, a 3rd party
tool will be required for an Exchange server, as well as Imail, to
check against an SPF TXT record.


I thought all I needed to do was tweak my DNS records.  Now you are
telling me I most obtain a 3rd party tool in order to comply with MSN
and Hotmail?

To send to them, you will need an SPF record, is what they are saying. I am saying is if this is adopted industry wide, for you to receive ONLY SPF'd domains, you will need to have a 3rd party tool. I've been using Vamsoft ORF for myself and my clients and it halts about 99% of junk coming in before it hits the INformation Store. It doesn't support SPF yet, but they will eventually offer that feature. I don't know what you are using at this time to prevent spam at the MTA, but checking for SPF can help, but it may also hurt and may stop you from receiving legit mail. Until the industry adopts this as a mandate, that is something you will need to decide if you want it.



I guess it comes down to understanding what the product is, and
doing a search on it instead of directly blaming MIcrosoft for
something that's not theirs to begin with


Look, I don't mean to sound rude, but I have better things to do than
spend 3 hours trying to uncover the meaning of the latest acronym
technology being trumpeted by Microsoft.  I am now on day 4 on my
trek, and I'm still as confused today as I was on Friday when I came
across the news that MSN and Hotmail will be flagging incoming email
as SPAM unless mail servers start complying.

As with any industry, everyone has their own terminology. Microsoft is just using terminology for this industry.

Hotmail and MSN are just saying you need an SPF record, that's it.


They are not strong arming anyone. They are just saying, this is
what we are going to do, (as well as others out there), and for MSN
and Hotmail servers to know your server is legit, you'll need to
take that step into the future.

I believe your 'strong arm' comment came from this article talking
about SenderID:


That's correct.  And even the expert in the article uses the term
"strong arm" in regards to Microsoft.  Why then am I incorrect in
echoing an expert's opinion?

Misunderstanding? I'm not necessarily a follower, so I don't necessarily agree with most things I read out there. I just try to analyze it to see how it affects me or my clients, especially knowing that this SPF stuff will eventually be adopted industry wide sooner or later.

But I'm sorry to hear you feel that way.


Phil 

I hope you were able to get your SPF records in order.

Ace 

.

Relevant Pages

  • RE: OMA and Outgoing Spam
    ... Someone hacked a user account and use it to spam emails; ... Your Exchange server is open relaying emails;(You have checked it ... Your server is under RNDR Attack. ... Microsoft is providing this information as a convenience to you. ...
    (microsoft.public.windows.server.sbs)
  • Re: SMTP irritation Exchange Server 2000...
    ... *nix fixes SPAM, I would be very interested in learning it. ... Microsoft MVP - Directory Services ... > with a Microsoft server and I have to *pay* to fix it? ... if this is the answer then Linux is looking better ...
    (microsoft.public.exchange2000.admin)
  • RE: Inbound email sender substitution?
    ... Is this legitimate email or SPAM? ... likely not an issue with you server but an issue with the way the email was ... Microsoft Online Support Engineer ... >to the correct internal recipient, however it also seems to be labeled as ...
    (microsoft.public.windows.server.sbs)
  • Re: Sender ID Framework SPF Record Wizard
    ... My whole complaint deals with the poor instructions and support by Microsoft ... attempt to reduce SPAM. ... > There have been some suggestions to combat spam, such as SPF. ... My server sends thousands of emails to AOL every day, ...
    (microsoft.public.windows.server.dns)
  • Re: Sender ID Framework SPF Record Wizard
    ... current growing spam problem. ... I'm sure Microsoft didn't make the decision lightly and without considering ... There have been some suggestions to combat spam, such as SPF. ... required for an Exchange server, as well as Imail, to check against an SPF ...
    (microsoft.public.windows.server.dns)
Loading