Did you install all the
dependencies before installing the packages?

Yes, I did, i followed the instructions in the SuSE 10.1 tutorial like i did before on the other server with the same hard- & software.

I increased the softlimit of the submission process and the error is now gone, but its a strange behavior. I also have done that on the other server but due to another error, increasing the memory limit seems to fix several errors.

Another small question, is POP/IMAP with TLS supported?

Thanks


Jake Vickers schrieb:
Stefan wrote:
Hi,
today i installed QmailToaster, everything is working fine but TLS.

220 mail.xxx.de - Welcome to Qmail Toaster Ver. 1.3 SMTP Server ESMTP
EHLO testing
250-mail.xxx.de - Welcome to Qmail Toaster Ver. 1.3 SMTP Server
250-STARTTLS
250-PIPELINING
250-8BITMIME
250-SIZE 20971520
250 AUTH LOGIN PLAIN CRAM-MD5
STARTTLS
454 TLS unable to initialize ctx: error:140A910D:lib(20):func(169):reason(269) (#4.3.0)

Same with IMAP/POP.

Ive installed qmailtoaster a month ago on another server and TLS is working fine there. Is there a bug in one of the new packages since then?

The packages have not been updated in a year.
What it looks like to me is you copied binary packages to this machine and installed them - the error your receiving has to do with not being able to use ctx (re: SSL_CTX) meaning that your SSL libraries are either broken or missing from what I can see. Did you install all the dependencies before installing the packages?

---------------------------------------------------------------------
    QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
    QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to