Re: smtp authentication fails

Marc Greene <[email protected]> Mon, 10 Dec 2007 02:18:08 -0800 (PST)
Newsgroups gmane.mail.pine.general
Message-ID <[email protected]>
On Mon, 10 Dec 2007, Chris Wilson wrote:

> Hi Marc,
>
> On Sun, 9 Dec 2007, Marc Greene wrote:
>
>>> The certificate will not install into Pine, but into Linux/Windoozz
>>> for Thunderbird anyway. But once found by Pine in the pinerc
>>> directory, & you provide Pine MainMenu-Setup-Config smtp-server with
>>> the correct smtp-server name & domain entry, it should work.
>>
>> Tell me about it :)
>>
>> The pine compile output gave me this warning:
>>
>>   File /etc/ssl/certs/factory.pem is missing
>>   This might indicate that CA certs did not get properly
>>   installed.  If you get certificate validation failures
>>   in Pine, this might be the reason for them.
>>
>> I think that might be the problem, but I haven't been able to find out
>> what factory.pem is or why it wasn't installed by openssl, I'm still
>> looking into that.
>
> You could try installing your GoDaddy certificate as
> /etc/ssl/certs/factory.pem.
>
>>> After the certificate is located & provided for Pine to find, for
>>> any further problems, double check certificate info, inbox-path &
>>> SMTP-server name, domain name, for any prefixes - xxxx.lavabit.com,
>>> etc. If the certificate is written wrong compared to the system it
>>> certifies, the correct server name or certificate entry must be
>>> determined & corrected. An SSH access into lavabit may offer a clue
>>> as to correct server name via the command prompt.
>>
>> I don't have SSH access into lavabit, but like I said, I'm pretty dang
>> sure "lavabit.com" is the correct server name to use.
> Try "openssl s_client -connect lavabit.com:465" if you want to make sure.
>
> The output will include the details of the certificate chain. The CN is
> the hostname that the server should be using, i.e. it should be
> lavabit.com.

I got it working. The openssl s_client command you suggested 
worked this time (I got a verify return code 0 (ok)). 
Though I did have to give it the  -CApath /etc/ssl/certs 
flag.

Under certificate chain in the output it said CN=*.lavabit.com, 
and I had to change my pine setting to:

smtp-server = mail.lavabit.com:465/ssl/user=marc

I also had made a mistake and linked the 
valicert_class2_root.crt to bcdd5959.O instead of bcdd5959.0 in 
/etc/ssl/certs. After I fixed those two things, it started 
working fine.

Thanks for everyone's help!

Marc

_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info