[TriLUG] help with mail logs

Ryan Wheaton ryan.wheaton at comcast.net
Fri Jan 16 10:52:19 EST 2004


I thought so as well.  I assumed that the error message just meant that 
their site cert couldn't be verified, hence the log entry..  But, I 
just wanted to be sure.  Thanks!

-r
On Friday, Jan 16, 2004, at 07:56 America/Denver, Jon Carnes wrote:

> On Fri, 2004-01-16 at 08:56, Ryan Wheaton wrote:
>> Good morning all.
>>
>> I was perusing the logs on one of my list servers, and I came across
>> the following entries:
>>
>> STARTTLS=client, relay=mx1c1.megamailservers.com., 
>> version=TLSv1/SSLv3,
>> verify=FAIL, cipher=DHE-RSA-AES256-SHA, bits=256/256: 1 Time(s)
>>     STARTTLS=client, relay=webmail.vanion.com., version=TLSv1/SSLv3,
>> verify=FAIL, cipher=DES-CBC3-SHA, bits=168/168: 1 Time(s)
>>     STARTTLS=client, relay=mail.randomwalk.com., version=TLSv1/SSLv3,
>> verify=FAIL, cipher=DHE-RSA-AES256-SHA, bits=256/256: 1 Time(s)
>>     STARTTLS=client, relay=davegrover.com., version=TLSv1/SSLv3,
>> verify=FAIL, cipher=AES256-SHA, bits=256/256: 1 Time(s)
>>
>>
>> there are people from the randomwalk.com and davegrover.com that are
>> members of lists on the box.  Does this mean that the messages did not
>> reach them?  Or is it their mail servers responding, probing me to see
>> if I'm an open relay?
>
> My guess is that their MTA's are dropping off mail and looking for the
> best protocol to use.  Of course they are starting with the most secure
> and then dropping down to the least secure.
>
> Jon
>
> -- 
> TriLUG mailing list        : 
> http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ  : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc
>




More information about the TriLUG mailing list