On 04/26/2011 09:16 PM, Michael Thomas wrote:
On 04/26/2011 05:08 PM, J.D. Falk wrote:
On Apr 25, 2011, at 10:12 AM, Jeff Mitchell wrote:
If you trust the issued certificates(!) being used to sign the mail, you at
least have a good indication that the spam is coming from the domain that it
On 04/22/2011 07:24 PM, Lynda wrote:
Non existent, it's SPF only.
My point.
Nearly all of the spam I see is DKIM signed. It just makes messages
bigger. I'd just as soon our volunteers spend their times on other
things, myself.
DKIM isn't designed explicitly to stop spam, it's designed to id
Eric Tow wrote:
I submitted a ticket to Comcast yesterday around 10:00 AM EST regarding
this issue (ticket #151689315), received a standard reply last night,
but as of yesterday 14:45 EST, the issue seems to have resolved itself.
I can verify that it was still happening as of about 12:10 AM EST t
Tony Finch wrote:
That's not entirely true. SMTP over TLS is intended to work for
inter-domain SMTP, and it is in fact quite frequently used.
My understanding is that Comcast uses it simply for encryption, not for
authentication.
* Most SMTP software does not check certificates and many certifi
I've been seeing some odd behavior today with some of the servers that
respond to smtp.comcast.net on port 587. Some, but not all, of the
servers are presenting self-signed certs, causing my own server to balk
at making a connection. (The Organization is RTFM, Inc. -- it'd be funny
if mail wasn
5 matches
Mail list logo
