In regards to this, the record should look as follows from the cmd line:
$ host -t txt interop.p0.com
interop.p0.com text "v=spf1 a ptr include:_spf.postdirect.com -all"
interop.p0.com text "spf2.0/mfrom a ptr include:_spf.postdirect.com -all"
On 7/19/06, Erik Espinoza <[EMAIL PROTECTED]> wrote:
Oh and you don't have to patch Qmail for hotmail to receive your
SenderID, just publish the DNS records.
So if your spf record looks like this:
"v=spf1 a mx -all"
Just add a second entry that looks like this:
"spf2.0/mfrom a mx -all"
Erik
On 7/19/06, Erik Espinoza <[EMAIL PROTECTED]> wrote:
> SenderID isn't necessary for sending to Hotmail Inbox. In fact I think
> the only way to get into a Hotmail Inbox (instead of going straight to
> Junk Mail) is by only sending spam.
>
> Hotmail doesn't even publish SenderID, they publish SPF records.
>
> $ host -t txt hotmail.com
> hotmail.com text "v=spf1 include:spf-a.hotmail.com
> include:spf-b.hotmail.com include:spf-c.hotmail.com
> include:spf-d.hotmail.com ~all"
>
> FYI: From Wikipedia (http://www.wikipedia.org/wiki/SenderID)
> Syntactically SPF and SenderID are almost identical: Replacing the
> string v=spf1 in a valid SPF policy by one of...
>
> 1. spf2.0/mfrom
> 2. spf2.0/mfrom,pra
> 3. spf2.0/pra,mfrom
> 4. spf2.0/pra
>
> ...yields a syntactically valid SenderID policy, and vice versa.
>
>
> On 7/17/06, bb. <[EMAIL PROTECTED]> wrote:
> > Thank you,
> >
> > As i remember, someone replied the same topic as
> > Hotmail does NOT checks for DomainKeys but i am not
> > sure.
> >
> > Ok, adding to adress book maybe prevents but customers
> > (Foregion email owners) would dislike this.
> >
> > I wonder those: 1-I set up SPF and reverse DNS but can
> > not send to inbox with that 8 month old QmailToaster
> > installation, if i update to new release with
> > DomainKeys will it be OK; and 2-If we patch
> > QmailToaster with SenderID, could we send to Hotmail
> > Inbox instead of Junk? (Is there a SenderID patch?)
> >
> > Many thanks...
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --- fuzzy <[EMAIL PROTECTED]> wrote:
> >
> > > Jake Vickers wrote:
> > > > bb. wrote:
> > > >> Hi,
> > > >>
> > > >> Is there any one who subscribed this list with
> > > Yahoo
> > > >> adress? I used to get QmailToasterList emails
> > > rigth
> > > >> inbox but for couple days i used to get ALL
> > > >> QmailToasterList emails in my Bulk folder.
> > > >>
> > > >> Also my ALL QmailToaster server emails goes to
> > > Yahoo
> > > >> Bulk and Hotmail Junk; and as i searched in
> > > >> dnsstuff.com, my IP is not in black list, i have
> > > a
> > > >> reverse DNS record and SPF record. My only guess
> > > is i
> > > >> installed QmailToaster 8 months ago so last
> > > version
> > > >> MAY work well OR do we have an other problem??!
> > > >>
> > > >> Is there anyone who has a server uses
> > > QmailToaster
> > > >> LAST or any previous version and emails are NOT
> > > >> delivered to Yahoo Bulk nor Hotmail Junk? Let we
> > > >> follow him / her for solition as what he / she
> > > did...
> > > >>
> > > >>
> > > > There have been a couple people who have broached
> > > similar questions. I
> > > > don't have an account with either of those, so I
> > > can't say for sure,
> > > > but I think they may have changed their mail
> > > filtering schema.
> > > > Hopefully someone has already encountered this and
> > > maybe has a working
> > > > solution?
> > > curious question for the MOTU, have you setup domain
> > > keys on the mailer box?
> > >
> > > qmt-mail shows up:
> > >
> > > Received: from unknown (HELO ns1.qmailtoaster.com)
> > > (38.99.66.144)
> > >
> > > dnsstuff.com shows:
> > > Answer:
> > > *No TXT records exist for www.qmailtoaster.com.*
> > > [Neg TTL=2560 seconds]
> > > Answer:
> > > *No TXT records exist for ns1.qmailtoaster.com.*
> > > [Neg TTL=2560 seconds]
> > >
> > > i assume the toaster mailer then is sending; and
> > > yahoo is receiving as domainkey-status:bad,
> > > therefore tossing it into the bulk folder.
> > >
> > >
> > > i toast for a small company as the company computer
> > > geek.
> > > i know that yahoo/hotmail use domainkey status to
> > > pre-sort incoming mail
> > > with domainkey-status:bad as bulk.
> > > i do not have domain keys setup for our company for
> > > various reasons.
> > > in testing, i found that mail from my domain to my
> > > yahoo account ends up in the bulk folder.
> > >
> > > by effectively "white-listing" (adding my domain
> > > sender to my yahoo contacts list),
> > > i short-circuit the bulk folder pre-sort...all mail
> > > from that sender goes straight to the inbox.
> > >
> > > bb, try to add the qmt sender to your contact
> > > list...that should solve your problem.
> > >
> > > also, this implies that anyone using ezmlm to mail
> > > out to those hosts
> > > (and probably others) needs to setup domain keys, if
> > > they do not want their
> > > mailings ending up in the bulk/junk folders of
> > > intended recipients.
> > >
> > > any of this sound plausible?
> > >
> > > fuzzy
> > >
> > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > QmailToaster hosted by: VR Hosted
> > > <http://www.vr.org>
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > > [EMAIL PROTECTED]
> > > For additional commands, e-mail:
> > > [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
> >
> > ---------------------------------------------------------------------
> > QmailToaster hosted by: VR Hosted <http://www.vr.org>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
