DK was abandonded by Yahoo awhile ago, but DKIM is very stable.
Twitter runs DKIM signing and verification code on all of our mail
servers, as does Google, Facebook, Yahoo, and many other major sites.
OK. Will study further and implement the necessary check.
And Dale - I somehow missed
I do have to question having your client verify DKIM again, though.
These activities should be dealt with inside of your MTA and not a
mail destination script hanging off of the MTA. What exactly are you
trying to protect against? A user forging an email to your MTA as
twitter?
Yes -
On May 4, 2009, at 10:14 PM, Arik Fraimovich wrote:
You're right. After doing a quick reading yesterday, I realized that I
can configure Postfix to do this validations for me.
The only reason I'm still considering doing the DomainKeys validation
in my code is because I heard more than once
On May 4, 2009, at 12:02 AM, Dale Cook wrote:
So my question is, is there anyway to authenticate that the email is
actually coming from twitter and not someone else?
It's pretty easy to prove the mail was sent from us. We use
DomainKeys. Validate our domainkey signature at the top of the
On May 4, 1:26 pm, John Adams j...@twitter.com wrote:
On May 4, 2009, at 12:02 AM, Dale Cook wrote:
So my question is, is there anyway to authenticate that the email is
actually coming from twitter and not someone else?
It's pretty easy to prove the mail was sent from us. We use
On May 4, 2009, at 5:15 AM, Arik Fraimovich wrote:
The from address is always of the form: twitter-dm-[name]=[domain]
@postmaster.twitter.com, so if your email address is u...@example.com
the from address will be: twitter-dm-
user=example@postmaster.twitter.com. If you set the address to be
Great, I knew I was probably wrong on this. Thanks to both of you guys
for the feedback and suggestions, really appreciate it.
Dale
On May 4, 9:58 am, John Adams j...@twitter.com wrote:
On May 4, 2009, at 5:15 AM, Arik Fraimovich wrote:
The from address is always of the form:
user=example@postmaster.twitter.com. If you set the address to be
something random and non public, like MD5(time)@yourdomain.com, it
Ah, but then your email address wouldn't be very human readable and
you'd have to change your email address all the time (if you were
using the
Arik,
From my limited searching so far there's a good entry at Wikipedia
(http://en.wikipedia.org/wiki/DomainKeys) and you can check out a
bunch of libraries and tools at http://domainkeys.sourceforge.net/
Other than that it will probably depend on which mail server you're
using since the mail
On May 4, 2009, at 1:28 PM, Arik Fraimovich wrote:
The MD5(time) was just a suggestion for _one time_ generation of the
mailbox name.. of course they can pick up something more readable, as
long as they keep it private and unguessable.
That's what I figured - I just wanted to indicate why it
10 matches
Mail list logo