Re: Help qmail-smtpauth

Erwin Hoffmann <[email protected]> Tue, 1 Aug 2017 23:02:22 +0200
Newsgroups	gmane.mail.qmail.general
Message-ID	<[email protected]>
Hi Rejaine,


> Am 01.08.2017 um 21:14 schrieb Rejaine Monteiro <[email protected]>:
> 
> 
> Em 31-07-2017 14:01, Kai Peter escreveu:
>> I would expect that this error appears in dmesg (by glibc) too, does it?
> 
> dmesg only show a lot of sefault for qmail-smtpd process (tcpserver looping after authentication)
> 
> [350247.947609] qmail-smtpd[29824]: segfault at b907140 ip 000000000040e450 sp 00007fff045da058 error 4 in qmail-smtpd[400000+16000]
> [350248.036554] qmail-smtpd[29825]: segfault at 4d7140 ip 000000000040e450 sp 00007ffd21a08258
> etc...
> 
>> 
>> As the cdb files are binary compatible I suggest to copy the credentials file temporarily to the 64bit machine and test it. And perhaps vice versa. From the given info I'm pretty sure the auth.cdb is not found because your checkpassword tool looks at the wrong location or it is even not found itself. Reason could be a wrong pointer (integer) size also.
> I have already tested by copying the auth.cdb file from my old server,   but I was not successful .. the same problem occurs, that is, qmail-smtp continues to fall after authentication.
> 
> The authentication seems to work because when i enter an incorrect password it writes to the log and shows "user or password incorrect" but when  pass the correct password, then qmail-smtp down with segfault.
> 
> The qmail-smtp process itself is also OK.. when i remove the authentication requirement, it works normally as well.
> 
> 
> I think I'm going to give up this patch because it's very complicated to solve (I thought about using it because I already use it in other installations successfully), but as it's getting complicated I'm going to get another temporary solution (pbs, esmtp or something)
>> If it is really a 32/64bit issue than you can try to recompile all with march=i586 (or so). Other wise you have to debug the code.
>> 
>> Anyway, move on to an actively maintained fork. By using s/qmail or eQmail you will be able to update to the upcoming aQmail easily ;-) - ok, it's another assumption.
>> 
> In fact, not intending to continue with qmail for a long time * (we will migrate to a cloud solution soon) I just need to upgrade this server to the latest hardware and OS, just to gain some extra time from some months.
> And, honestly, I do not intend to dedicate myself for now in another solution, since we will soon migrate to a cloud solution (no time for new adventures)

Good luck! But the learning curve will probably not be different, rather to understand the problems you have.

Regards.
--eh.

> 

Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: EE00CF65
signature.asc (application/pgp-signature, 842 B)