Hi
Try to regenerate your cert issuing something like
openssl req -new -newkey rsa:2048 -days 3650 -nodes -x509 -keyout servercert.pem -out servercert.pem

and copy the generated pem file to /var/qmail/control and restart

Who knows ... :)

Eric "Shubes" wrote:
I don't really know what's supposed to be happening, but guessing from the
trace, it's not liking what it got in servercert.pem, so it's looking for
clientca.pem and clientcrl.pem files. I don't have these files and I'm using
TLS successfully, so I doubt you need them.

Can you try reversing the keys in servercert.pem and see what that does? I
don't know why yours is reversed from mine, or if it even matters, but it's
worth a shot. Try putting the RSA private key first, followed by the
certificate. Be very careful when doing this not to introduce any extra
spaces linefeeds or anything, and be sure to make a backup copy of your
existing file first.

Lazaro Ferreira wrote:
Hi,

I'm running latest version qmail-toaster-1.03-1.3.10
But the same problem with previous version qmail-toaster-1.03-1.3.7

I have made strace like you said this is the output , any ideia ?

...
select(1, [0], NULL, NULL, {1200, 0}STARTTLS
)   = 1 (in [0], left {1188, 766000})
read(0, "STARTTLS\n", 1024)             = 9
brk(0)                                  = 0x6bf000
brk(0x6e0000)                           = 0x6e0000
open("control/servercert.pem", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=1693, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2a95557000
read(3, "-----BEGIN CERTIFICATE-----\nMIIC"..., 4096) = 1693
getpid()                                = 28774
read(3, "", 4096)                       = 0
close(3)                                = 0
munmap(0x2a95557000, 4096)              = 0
open("control/clientca.pem", O_RDONLY)  = -1 ENOENT (No such file or
directory)
open("control/clientcrl.pem", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/dev/tty", O_RDWR|O_NONBLOCK|O_NOCTTY) = 3
writev(3, [{"*** glibc detected *** ", 23}, {"free(): invalid
pointer", 23}, {": 0x", 4}, {"00000035520306b8", 16}, {" ***\n", 5}],
5*** glibc detected *** free(): invalid pointer: 0x00000035520306b8
***
) = 71
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
tgkill(28774, 28774, SIGABRT)           = 0
--- SIGABRT (Aborted) @ 0 (0) ---
+++ killed by SIGABRT +++
Process 28774 detached







On 1/11/07, Jean-Paul van de Plasse <[EMAIL PROTECTED]> wrote:
Guess this is going to be very difficult to figure out this way.

Last thing I can think of to get some kind of idea is run a strace on
qmail-smtpd
Make sure you have strace installed.
Then run
strace /var/qmail/bin/qmail-smtpd

That will give a bunch of data on your screen, wait till it stops with
something like
select(1, [0], NULL, NULL, {1200, 0}
then type
starttls
(and put an enter after just like you did with telnet)

Normally that would give you the last system calls done before crashing.
I guess you could do this alot better with gdb but then you need a debug
compiled version of qmail-smtpd.

I do not know what qmail-toaster version you have installed, but besides
that I have exactly the same versions as you.




----- Original Message -----
From: "Eric "Shubes"" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, January 11, 2007 8:09 PM
Subject: Re: [qmailtoaster] Stop receiving email from most servers after
Qmail update


Jake Vickers wrote:
Lazaro Ferreira wrote:
Hi,

Interestingly I can send from these servers using telnet qmail_ip 25,
but if I try from command line using the command "mail " it produces
the gcc error

Any ideia or guess is welcome ?
So if you use a client like Thunderbird or Outlook it works okay? But
when you try and mail from the command line it gives you the error?
Does
it only do it when you mail from the command line on the Toaster
machine, or when you send from another host to this machine?
You may want to check and make sure sendmail has been removed (rpm
-qa |
grep sendmail), and then make sure that Toaster installed the "fake"
sendmail (/var/qmail/bin/sendmail and /use/sbin/sendmail should
just be
a symlink to the /var/qmail/bin/sendmail one).

I think we've determined that the problem lies when the starttls
command
is
issued by the sending client.

--
-Eric 'shubes'





---------------------------------------------------------------------
    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