Norman,
Thanks for the info.
One last question regarding the SPF SMTPHandler. If I get the latest trunk
build, is SPF just inherently built into server, and it automatically checks
all incoming mail against SPF records, etc. for the sending domain? Or is
it an option that must be enabled? (And
Hi Guys!
I just thought I'd mention that I've got an implementation of the
Domain Keys sender verification standard about 95% completed (it
correctly validates most messages, but some systems don't correctly
interpret the signature).
I wanted to include it with JAMES itself, but there was a ques
How does Domain Keys Sender Verification differ from SPF? Do they work in
parallel? Or do you chose one or the other?
-Original Message-
From: Tom Brown [mailto:[EMAIL PROTECTED]
Sent: Friday, December 22, 2006 10:32 AM
To: James Users List
Subject: Re: jSPF and James?
Hi Guys!
I just
Tom Brown wrote:
Hi Guys!
I just thought I'd mention that I've got an implementation of the
Domain Keys sender verification standard about 95% completed (it
correctly validates most messages, but some systems don't correctly
interpret the signature).
I wanted to include it with JAMES itself, bu
JWM schrieb:
> Norman,
>
> Thanks for the info.
>
> One last question regarding the SPF SMTPHandler. If I get the latest trunk
> build, is SPF just inherently built into server, and it automatically checks
> all incoming mail against SPF records, etc. for the sending domain? Or is
> it an option
SPF is a system for specifying which servers are allowed to send mail
on behalf of any domain. SPF publishes a list of servers in the DNS
system. The receiving server verifies that the sending server is in
the list.
Domain keys uses public/private key encryption to accomplish the same
task. The d