Re: [courier-users] submission problems

[Sam V. <mr...@co...>]

co...@ec... writes:

> Hi,
>
> > I'm pretty clueless, where to look.
> > The system logs of courier show nothing during the connection attempt  
> (neither with my mail client nor with openssl's s_client).
>
> I had one more idea: look at systemd's log in total (i.e. not only courier  
> units) and noticed this cause of the issue:
>
> --8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<--
> Jan 05 22:28:42 szilassi.eckner.net systemd-coredump[136284]: [🡕] Process  
> 136282 (couriertls) of user 72 dumped core.
>
>                                                               Stack trace of  
> thread 136282:
>                                                               #0   
> 0x00007f74575cc430 n/a (libtasn1.so.6 + 0x4430)
>                                                               #1   
> 0x00007f74575cc6f1 n/a (libtasn1.so.6 + 0x46f1)
>                                                               #2   
> 0x00007f74575d5f22 asn1_der_decoding2 (libtasn1.so.6 + 0xdf22)
>                                                               #3   
> 0x00007f7457cf1697 gnutls_x509_crt_import (libgnutls.so.30 + 0xf1697)

So, it's crashing in the gnutls library, specifically in the code that
sets the server certificate.

Given that this is working on a different port, it's time to compare the ssl  
configuration between imap-ssl and esmtp-ssl configuration file. Find the  
difference.

Another possibility is that imap reads the certificate as root, but esmtp as  
a non-privileged user so file access permissions could be the factor, but I  
would expect this to manifest differently. Here, it looks like it read the  
certicicate, but crashed inside gnutls.

Once the difference between the ssl configurations is determined, it's a  
toss-up as to whether this can be further isolated to either a gnutls bug,  
or a courier bug.