Mailing List Archive: Help qmail-smtpauth

Help qmail-smtpauth

Jul 17, 2017, 5:22 AM

Post #1 of 13 (3717 views)

Hi,

I have a server running smtpauth for many years and it works fine,
however I am reinstalling/upgrading to another qmail server (another
version of OS etc). I am basically using the same settings as the
current server and everything is working fine except for qmail-smtp-auth
. Could anyone give a hint of what might be wrong?

# telnet 192.168.0.1 587
Trying 192.168.0.1
Connected to 192.168.0.1
Escape character is '^]'.
220 192.168.0.1 ESMTP
ehlo host
250-192.168.0.1
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250-STARTTLS
250-SIZE 10000000
250-PIPELINING
250 8BITMIME
AUTH PLAIN <crypt-auth>
Connection closed by foreign host.

#openssl s_client -connect 192.168.0.1:587 -starttls smtp
<cut>
<cut>
Start Time: 1496784102
Timeout : 300 (sec)
Verify return code: 18 (self signed certificate)
---
250 8BITMIME
ehlo host
250-192.168.0.1
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250-SIZE 10000000
250-PIPELINING
250 8BITMIME
AUTH PLAIN <crypt-auth>
read:errno=0

ps: cryp-auth generate by command: echo -ne
"user@mydomain\0user@mydomain\0userpasswd" | openssl base64

Some parameters for file /var/qmail/qmail-smtp-auth/run :
<cut>
SSL_CERT="/var/qmail/control/servercert.pem"
CDBF="/var/qmail/tcpcontrol/smtpauth.cdb"
SSL=0
FORCE_TLS=1
DENY_TLS=0
AUTH=1
REQUIRE_AUTH=1
ALLOW_INSECURE_AUTH=1
AUTH_CDB="/var/qmail/tcpcontrol/auth.cdb"
CERTFILE="/var/qmail/control/server.crt.pem"
KEYFILE="/var/qmail/control/server.key.pem"
DHFILE="/var/qmail/control/server_dhparam.pem"
<cut>

My /var/qmail/tcpcontrol/smtpauth.rules is:
:allow,DATABYTES="10000000",LOGLEVEL="3",QMAILQUEUE="/var/qmail/bin/qmail-queue"

Permissions files for cdb are OK:

# l /var/qmail//tcpcontrol/smtpauth.cdb
-r--r--r-- 1 root root 2143 Jun 6 17:10
/var/qmail//tcpcontrol/smtpauth.cdb

My /var/qmail/tcpcontrol/auth.rules format is:
user@mydomain <cript-password>

# l /var/qmail/tcpcontrol/auth.cdb
-rw-r----- 1 root nofiles 2130 Jun 6 17:09 /var/qmail/tcpcontrol/auth.cdb

Thanks any tips.

Re: Help qmail-smtpauth [ In reply to ]

rejaine at bhz

Jul 17, 2017, 12:54 PM

Post #2 of 13 (3714 views)

Permalink

well, I'm using the same jms patch and qmail-smtpauth (with checkpasswd
etc) in another linux install, but 32 bitis (opensuse 10.1) the
difference now is that I'm installing a new server using the same
installation of qmail and same patches and everything works ok except
qmail-smtp-auth. I think it may be related to something because it is 64
bits, as you mentioned ... it is difficult to find out what. I will try
to upgrade to a newer version of the jms patch (although the changelog
of the new version has nothing to do with changing the code relative to
qmai-smptauth)

Em 17-07-2017 11:22, Erwin Hoffmann escreveu:
> Hi Rejaine,
>
> without any logs, things get difficult ....
>
> But from what I can see, I guess:
>
>
>> Am 17.07.2017 um 14:22 schrieb Rejaine Monteiro <rejaine@bhz.jamef.com.br>:
>>
>>
>> Hi,
>>
>> I have a server running smtpauth for many years and it works fine, however I am reinstalling/upgrading to another qmail server (another version of OS etc). I am basically using the same settings as the current server and everything is working fine except for qmail-smtp-auth . Could anyone give a hint of what might be wrong?
>>
>> # telnet 192.168.0.1 587
>> Trying 192.168.0.1
>> Connected to 192.168.0.1
>> Escape character is '^]'.
>> 220 192.168.0.1 ESMTP
>> ehlo host
>> 250-192.168.0.1
>> 250-AUTH LOGIN PLAIN
>> 250-AUTH=LOGIN PLAIN
>> 250-STARTTLS
>> 250-SIZE 10000000
>> 250-PIPELINING
>> 250 8BITMIME
>> AUTH PLAIN <crypt-auth>
>> Connection closed by foreign host.
> a) This is an ancient version of the SMTP Auth patch. Maybe some parts are not 64 bit save.
>
>
>> #openssl s_client -connect 192.168.0.1:587 -starttls smtp
>> <cut>
>> <cut>
>> Start Time: 1496784102
>> Timeout : 300 (sec)
>> Verify return code: 18 (self signed certificate)
>> ---
>> 250 8BITMIME
>> ehlo host
>> 250-192.168.0.1
>> 250-AUTH LOGIN PLAIN
>> 250-AUTH=LOGIN PLAIN
>> 250-SIZE 10000000
>> 250-PIPELINING
>> 250 8BITMIME
>> AUTH PLAIN <crypt-auth>
>> read:errno=0
>>
>> ps: cryp-auth generate by command: echo -ne "user@mydomain\0user@mydomain\0userpasswd" | openssl base64
> b) Old version of the SMTP Auth patch don't follow the checkpasword interface (see: http://www.fehcom.de/qmail/smtpauth.html)
>
> Maybe you are using now version which are different.
>
>> Some parameters for file /var/qmail/qmail-smtp-auth/run :
>> <cut>
>> SSL_CERT="/var/qmail/control/servercert.pem"
>> CDBF="/var/qmail/tcpcontrol/smtpauth.cdb"
>> SSL=0
>> FORCE_TLS=1
>> DENY_TLS=0
>> AUTH=1
>> REQUIRE_AUTH=1
>> ALLOW_INSECURE_AUTH=1
>> AUTH_CDB="/var/qmail/tcpcontrol/auth.cdb"
>> CERTFILE="/var/qmail/control/server.crt.pem"
>> KEYFILE="/var/qmail/control/server.key.pem"
>> DHFILE="/var/qmail/control/server_dhparam.pem"
>> <cut>
>>
>> My /var/qmail/tcpcontrol/smtpauth.rules is:
>> :allow,DATABYTES="10000000",LOGLEVEL="3",QMAILQUEUE="/var/qmail/bin/qmail-queue"
>>
>> Permissions files for cdb are OK:
>>
>> # l /var/qmail//tcpcontrol/smtpauth.cdb
>> -r--r--r-- 1 root root 2143 Jun 6 17:10 /var/qmail//tcpcontrol/smtpauth.cdb
>>
>> My /var/qmail/tcpcontrol/auth.rules format is:
>> user@mydomain <cript-password>
>>
>> # l /var/qmail/tcpcontrol/auth.cdb
>> -rw-r----- 1 root nofiles 2130 Jun 6 17:09 /var/qmail/tcpcontrol/auth.cdb
> c) You should ask the creator(s) of the patches you are using. This is a heavily tweaked qmail.
>
> Better move to a more recent version (like my s/qmail).
>
> Regards.
> --eh.
>
>
>> Thanks any tips.
>>
> Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: EE00CF65
>
>
>
>
>

--
Rejaine da Silveira Monteiro
Suporte - Tecnologia Digital
Tel: (31) 2102-8854
Jamef Encomendas Urgentes - Matriz - Belo Horizonte/MG
www.jamef.com.br

Re: Help qmail-smtpauth [ In reply to ]

rejaine at bhz

Jul 28, 2017, 8:25 AM

Post #3 of 13 (3681 views)

Permalink

Well, I tried again today to solve the problem, but it seems to me that
maybe the error is occurring not related to openssl or password file
(auth.cdb), but to something in qmail-smtp.

Just after passing the AUTH PLAIN passwod, qmail-smtp gives segmentation
error.

2017-07-28T12:18:57.170144-03:00 server kernel: [ 2998.641480]
qmail-smtpd[2805]: segfault at c3e140 ip 000000000040e450 sp
00007ffcf2aea628 error 4 in qmail-smtpd[400000+16000]
2017-07-28T12:18:57.526793-03:00 server systemd-coredump[2807]: Process
2805 (qmail-smtpd) of user 365 dumped core.

I need to insist on this jms patch, since I already use it in other
installations successfully .. all the features are ok in this new
installation, except for qmail-smtp-auth, but I would like to continue
using qmail with this combined jms-patch , because it is very
effective in my environment and always worked very well.

Em 17-07-2017 11:22, Erwin Hoffmann escreveu:
> Hi Rejaine,
>
> without any logs, things get difficult ....
>
> But from what I can see, I guess:
>
>
>> Am 17.07.2017 um 14:22 schrieb Rejaine Monteiro <rejaine@bhz.jamef.com.br>:
>>
>>
>> Hi,
>>
>> I have a server running smtpauth for many years and it works fine, however I am reinstalling/upgrading to another qmail server (another version of OS etc). I am basically using the same settings as the current server and everything is working fine except for qmail-smtp-auth . Could anyone give a hint of what might be wrong?
>>
>> # telnet 192.168.0.1 587
>> Trying 192.168.0.1
>> Connected to 192.168.0.1
>> Escape character is '^]'.
>> 220 192.168.0.1 ESMTP
>> ehlo host
>> 250-192.168.0.1
>> 250-AUTH LOGIN PLAIN
>> 250-AUTH=LOGIN PLAIN
>> 250-STARTTLS
>> 250-SIZE 10000000
>> 250-PIPELINING
>> 250 8BITMIME
>> AUTH PLAIN <crypt-auth>
>> Connection closed by foreign host.
> a) This is an ancient version of the SMTP Auth patch. Maybe some parts are not 64 bit save.
>
>
>> #openssl s_client -connect 192.168.0.1:587 -starttls smtp
>> <cut>
>> <cut>
>> Start Time: 1496784102
>> Timeout : 300 (sec)
>> Verify return code: 18 (self signed certificate)
>> ---
>> 250 8BITMIME
>> ehlo host
>> 250-192.168.0.1
>> 250-AUTH LOGIN PLAIN
>> 250-AUTH=LOGIN PLAIN
>> 250-SIZE 10000000
>> 250-PIPELINING
>> 250 8BITMIME
>> AUTH PLAIN <crypt-auth>
>> read:errno=0
>>
>> ps: cryp-auth generate by command: echo -ne "user@mydomain\0user@mydomain\0userpasswd" | openssl base64
> b) Old version of the SMTP Auth patch don't follow the checkpasword interface (see: http://www.fehcom.de/qmail/smtpauth.html)
>
> Maybe you are using now version which are different.
>
>> Some parameters for file /var/qmail/qmail-smtp-auth/run :
>> <cut>
>> SSL_CERT="/var/qmail/control/servercert.pem"
>> CDBF="/var/qmail/tcpcontrol/smtpauth.cdb"
>> SSL=0
>> FORCE_TLS=1
>> DENY_TLS=0
>> AUTH=1
>> REQUIRE_AUTH=1
>> ALLOW_INSECURE_AUTH=1
>> AUTH_CDB="/var/qmail/tcpcontrol/auth.cdb"
>> CERTFILE="/var/qmail/control/server.crt.pem"
>> KEYFILE="/var/qmail/control/server.key.pem"
>> DHFILE="/var/qmail/control/server_dhparam.pem"
>> <cut>
>>
>> My /var/qmail/tcpcontrol/smtpauth.rules is:
>> :allow,DATABYTES="10000000",LOGLEVEL="3",QMAILQUEUE="/var/qmail/bin/qmail-queue"
>>
>> Permissions files for cdb are OK:
>>
>> # l /var/qmail//tcpcontrol/smtpauth.cdb
>> -r--r--r-- 1 root root 2143 Jun 6 17:10 /var/qmail//tcpcontrol/smtpauth.cdb
>>
>> My /var/qmail/tcpcontrol/auth.rules format is:
>> user@mydomain <cript-password>
>>
>> # l /var/qmail/tcpcontrol/auth.cdb
>> -rw-r----- 1 root nofiles 2130 Jun 6 17:09 /var/qmail/tcpcontrol/auth.cdb
> c) You should ask the creator(s) of the patches you are using. This is a heavily tweaked qmail.
>
> Better move to a more recent version (like my s/qmail).
>
> Regards.
> --eh.
>
>
>> Thanks any tips.
>>
> Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: EE00CF65
>
>
>
>
>

--
Rejaine da Silveira Monteiro
Suporte - Tecnologia Digital
Tel: (31) 2102-8854
Jamef Encomendas Urgentes - Matriz - Belo Horizonte/MG
www.jamef.com.br

Re: Help qmail-smtpauth [ In reply to ]

kp at lists

Jul 29, 2017, 3:12 AM

Post #4 of 13 (3676 views)

Permalink

On 2017-07-28 17:25, Rejaine Monteiro wrote:
> Well, I tried again today to solve the problem, but it seems to me
> that maybe the error is occurring not related to openssl or password
> file (auth.cdb), but to something in qmail-smtp.
>
> Just after passing the AUTH PLAIN passwod, qmail-smtp gives
> segmentation error.
>
> 2017-07-28T12:18:57.170144-03:00 server kernel: [ 2998.641480]
> qmail-smtpd[2805]: segfault at c3e140 ip 000000000040e450 sp
> 00007ffcf2aea628 error 4 in qmail-smtpd[400000+16000]
> 2017-07-28T12:18:57.526793-03:00 server systemd-coredump[2807]:
> Process 2805 (qmail-smtpd) of user 365 dumped core.
>
Did you search for this explicit error message? Out of my head it's
something with file access error, but maybe I'm wrong.

> I need to insist on this jms patch, since I already use it in other
> installations successfully .. all the features are ok in this new
> installation, except for qmail-smtp-auth, but I would like to
> continue using qmail with this combined jms-patch , because it is
> very effective in my environment and always worked very well.
>

--
Sent with eQmail-1.10

Re: Help qmail-smtpauth [ In reply to ]

rejaine at bhz

Jul 31, 2017, 7:16 AM

Post #5 of 13 (3671 views)

Permalink

Em 29-07-2017 07:12, Kai Peter escreveu:
> Did you search for this explicit error message? Out of my head it's
> something with file access error, but maybe I'm wrong.
Yes, I researched this error in several places and compared the issue of
file permissions with an existing installation, I can not find anything
different (except that the version I am installing is a newer version in
64bit and the version that is Running is 32 bits) even the patch is the
same.

Re: Help qmail-smtpauth [ In reply to ]

kp at lists

Jul 31, 2017, 10:01 AM

Post #6 of 13 (3671 views)

Permalink

On 2017-07-31 16:16, Rejaine Monteiro wrote:
> Em 29-07-2017 07:12, Kai Peter escreveu:
>> Did you search for this explicit error message? Out of my head it's
>> something with file access error, but maybe I'm wrong.
> Yes, I researched this error in several places and compared the issue
> of file permissions with an existing installation, I can not find
> anything different (except that the version I am installing is a newer
> version in 64bit and the version that is Running is 32 bits) even the
> patch is the same.

I would expect that this error appears in dmesg (by glibc) too, does it?

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.

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.

--
Sent with eQmail-1.10

Re: Help qmail-smtpauth [ In reply to ]

rejaine at bhz

Aug 1, 2017, 12:14 PM

Post #7 of 13 (3664 views)

Permalink

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)

Re: Help qmail-smtpauth [ In reply to ]

feh at fehcom

Aug 1, 2017, 2:02 PM

Post #8 of 13 (3664 views)

Permalink

Hi Rejaine,

> Am 01.08.2017 um 21:14 schrieb Rejaine Monteiro <rejaine@bhz.jamef.com.br>:
>
>
> 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

Re: Help qmail-smtpauth [ In reply to ]

kristen at atmyhome

Aug 1, 2017, 4:06 PM

Post #9 of 13 (3662 views)

Permalink

On 7/28/17 7:25 AM, Rejaine Monteiro wrote:
> Well, I tried again today to solve the problem, but it seems to me that
> maybe the error is occurring not related to openssl or password file
> (auth.cdb), but to something in qmail-smtp.
>
> Just after passing the AUTH PLAIN passwod, qmail-smtp gives segmentation
> error.
>
> 2017-07-28T12:18:57.170144-03:00 server kernel: [ 2998.641480]
> qmail-smtpd[2805]: segfault at c3e140 ip 000000000040e450 sp
> 00007ffcf2aea628 error 4 in qmail-smtpd[400000+16000]
> 2017-07-28T12:18:57.526793-03:00 server systemd-coredump[2807]: Process
> 2805 (qmail-smtpd) of user 365 dumped core.
>
> I need to insist on this jms patch, since I already use it in other
> installations successfully .. all the features are ok in this new
> installation, except for qmail-smtp-auth, but I would like to continue
> using qmail with this combined jms-patch , because it is very
> effective in my environment and always worked very well.
>

Your not running recordio are you? That is known to cause SSL failures.
If you are running it, disable and see if your problems are gone.

Kristen

Re: Help qmail-smtpauth [ In reply to ]

amb-sendok-1504231980.fgjooklkenmmgbmbpdmd at bradfo

Aug 1, 2017, 7:13 PM

Post #10 of 13 (3662 views)

Permalink

Thus said Kristen R on Tue, 01 Aug 2017 15:06:37 -0800:

> Your not running recordio are you? That is known to cause SSL failures.
> If you are running it, disable and see if your problems are gone.

I believe recordio by itself doesn't cause the failures, it's the
additional resource requirements that typically cause the problem (e.g.
not enough file descriptors or some such).

Andyk
--
TAI64 timestamp: 4000000059813550

Re: Help qmail-smtpauth [ In reply to ]

rejaine at bhz

Aug 2, 2017, 5:25 AM

Post #11 of 13 (3661 views)

Permalink

I'm not using recordio. I tried to increase smpt-softlimit too, but it
did not work.

The last strace lines show something like this:

write(1, "220 mailserver ESMTP\r\n", 29) = 29
alarm(0) = 1200
alarm(1200) = 0
read(0, "auth plain AHVzZXJAdGVzdC5jb20AM"..., 1024) = 41
alarm(0) = 1190
lseek(3, 1640, SEEK_SET) = 1640
read(3, "\211\10\0\0\2\0\0\0", 8) = 8
lseek(3, 2193, SEEK_SET) = 2193
read(3, "\315\245\7\223B\10\0\0", 8) = 8
lseek(3, 2114, SEEK_SET) = 2114
read(3, "\r\0\0\0\"\0\0\0", 8) = 8
read(3, "user@mydomain.com", 13) = 13
read(3, "$1$pwoAo6SA$KAtCiI2d9ogMdlogCEyE"..., 34) = 34
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x7fbdd140} ---
+++ killed by SIGSEGV (core dumped) +++

Em 01-08-2017 23:13, Andy Bradford escreveu:
> Thus said Kristen R on Tue, 01 Aug 2017 15:06:37 -0800:
>
>> Your not running recordio are you? That is known to cause SSL failures.
>> If you are running it, disable and see if your problems are gone.
> I believe recordio by itself doesn't cause the failures, it's the
> additional resource requirements that typically cause the problem (e.g.
> not enough file descriptors or some such).
>
> Andyk

Re: Help qmail-smtpauth [ In reply to ]

feh at fehcom

Aug 2, 2017, 2:22 PM

Post #12 of 13 (3649 views)

Permalink

Hi ,

hm. Seems base64/auth plain has a problem:

echo -n "AHVzZXJAdGVzdC5jb20AM" | base64 -d

Input file incomplete.

echo -n "AHVzZXJAdGVzdC5jb20A" | base64 -d
user@test.com

Or did you edit the input to obfuscate the result?

...

read(3, "user@mydomain.com", 13)

Regards.
--eh.

> Am 02.08.2017 um 14:25 schrieb Rejaine Monteiro <rejaine@bhz.jamef.com.br>:
>
>
> I'm not using recordio. I tried to increase smpt-softlimit too, but it did not work.
>
> The last strace lines show something like this:
>
> write(1, "220 mailserver ESMTP\r\n", 29) = 29
> alarm(0) = 1200
> alarm(1200) = 0
> read(0, "auth plain AHVzZXJAdGVzdC5jb20AM"..., 1024) = 41
> alarm(0) = 1190
> lseek(3, 1640, SEEK_SET) = 1640
> read(3, "\211\10\0\0\2\0\0\0", 8) = 8
> lseek(3, 2193, SEEK_SET) = 2193
> read(3, "\315\245\7\223B\10\0\0", 8) = 8
> lseek(3, 2114, SEEK_SET) = 2114
> read(3, "\r\0\0\0\"\0\0\0", 8) = 8
> read(3, "user@mydomain.com", 13) = 13
> read(3, "$1$pwoAo6SA$KAtCiI2d9ogMdlogCEyE"..., 34) = 34
> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x7fbdd140} ---
> +++ killed by SIGSEGV (core dumped) +++
>
> Em 01-08-2017 23:13, Andy Bradford escreveu:
>> Thus said Kristen R on Tue, 01 Aug 2017 15:06:37 -0800:
>>
>>
>>> Your not running recordio are you? That is known to cause SSL failures.
>>> If you are running it, disable and see if your problems are gone.
>>>
>> I believe recordio by itself doesn't cause the failures, it's the
>> additional resource requirements that typically cause the problem (e.g.
>> not enough file descriptors or some such).
>>
>> Andyk
>>
>

Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: EE00CF65

Re: Help qmail-smtpauth [ In reply to ]

rejaine at bhz

Aug 2, 2017, 2:26 PM

Post #13 of 13 (3649 views)

Permalink

yes, was edited :)

Em 02-08-2017 18:22, Erwin Hoffmann escreveu:
> Hi ,
>
> hm. Seems base64/auth plain has a problem:
>
> echo -n "AHVzZXJAdGVzdC5jb20AM" | base64 -d
>
> Input file incomplete.
>
> echo -n "AHVzZXJAdGVzdC5jb20A" | base64 -d
> user@test.com
>
> Or did you edit the input to obfuscate the result?
>
> ...
>
> read(3, "user@mydomain.com", 13)
>
>
> Regards.
> --eh.
>
>
>> Am 02.08.2017 um 14:25 schrieb Rejaine Monteiro <rejaine@bhz.jamef.com.br>:
>>
>>
>> I'm not using recordio. I tried to increase smpt-softlimit too, but it did not work.
>>
>> The last strace lines show something like this:
>>
>> write(1, "220 mailserver ESMTP\r\n", 29) = 29
>> alarm(0) = 1200
>> alarm(1200) = 0
>> read(0, "auth plain AHVzZXJAdGVzdC5jb20AM"..., 1024) = 41
>> alarm(0) = 1190
>> lseek(3, 1640, SEEK_SET) = 1640
>> read(3, "\211\10\0\0\2\0\0\0", 8) = 8
>> lseek(3, 2193, SEEK_SET) = 2193
>> read(3, "\315\245\7\223B\10\0\0", 8) = 8
>> lseek(3, 2114, SEEK_SET) = 2114
>> read(3, "\r\0\0\0\"\0\0\0", 8) = 8
>> read(3, "user@mydomain.com", 13) = 13
>> read(3, "$1$pwoAo6SA$KAtCiI2d9ogMdlogCEyE"..., 34) = 34
>> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x7fbdd140} ---
>> +++ killed by SIGSEGV (core dumped) +++
>>
>> Em 01-08-2017 23:13, Andy Bradford escreveu:
>>> Thus said Kristen R on Tue, 01 Aug 2017 15:06:37 -0800:
>>>
>>>
>>>> Your not running recordio are you? That is known to cause SSL failures.
>>>> If you are running it, disable and see if your problems are gone.
>>>>
>>> I believe recordio by itself doesn't cause the failures, it's the
>>> additional resource requirements that typically cause the problem (e.g.
>>> not enough file descriptors or some such).
>>>
>>> Andyk
>>>
> Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: EE00CF65
>
>
>
>
>

--
Rejaine da Silveira Monteiro
Suporte - Tecnologia Digital
Tel: (31) 2102-8854
Jamef Encomendas Urgentes - Matriz - Belo Horizonte/MG
www.jamef.com.br

Mailing List Archive

Attached Files:

Attached Files: