Hello Julien,

Wednesday, July 27, 2011, 09:42:38, Julien Escario wrote:
JE> Hello,
JE> I also have an issue with a base64_decode() function which seems 
incompatible
JE> with amd64 arch.

JE> I'm using the patch from milkys (http://www.mcmilk.de/qmail/)

JE> Try to print the return string after base64 decoding has been done to check 
if
JE> your auth string is correct. If it's not, that's qmail-smtpd fault, not 
vpopmail's.

JE> Regards,
JE> Julien Escario


JE> Le 26/07/2011 23:05, a...@ltmd.org a écrit :
>> Hello Rick,
>>
>> Sunday, July 3, 2011, 17:15:29, Rick Macdougall wrote:
>> RM>  On 03/07/2011 5:11 AM, a...@ltmd.org wrote:
>>>> Hello Rick,
>>>>
>>>> Saturday, July 2, 2011, 16:59:09, Rick Macdougall wrote:
>>>>> User vpopmail realy exists. I also cannot find the
>>>>>> difference between working x86 server configuration and the new
>>>>>> amd64 one. I tried to reconfigure my system from no-multilib to
>>>>>> multilib and to reemerge netqmail and vpopmail ebuilds, but still no
>>>>>> success. :( Is there some way to debug that plain SMTP-AUTH to figure
>>>>>> out what is really happening?
>>>>
>>>> RM>   You can use recordio (part of one of djb's packages) to log 
>>>> everything
>>>> RM>   that happens within an smtp conversation.
>>>>
>>>> RM>   http://cr.yp.to/ucspi-tcp/recordio.html
>>>>
>>>> Thank you for your assistance, Rick. I tried to use that nice tool.
>>>> And here goes the result:
>>>>
>>>> @400000004e1029d019fc59f4 22218>   220 mail.domain.com ESMTP
>>>> @400000004e1029d035004684 22218<   EHLO [10.1.1.177]
>>>> @400000004e1029d035017b1c 22218>   250-mail.domain.com
>>>> @400000004e1029d03501b1cc 22218>   250-STARTTLS
>>>> @400000004e1029d03501e494 22218>   250-PIPELINING
>>>> @400000004e1029d03502175c 22218>   250-8BITMIME
>>>> @400000004e1029d03502463c 22218>   250-SIZE 0
>>>> @400000004e1029d035027904 22218>   250 AUTH LOGIN PLAIN
>>>> @400000004e1029d10834940c 22218<   AUTH PLAIN
>>>> @400000004e1029d108356ecc 22218>   334
>>>> @400000004e1029d109252dcc 22218<   c2VuZGVyLmNvbXBhc3N3b3Jk
>>>> @400000004e1029d6092f863c 22218>   535 authentication failed (#5.7.1)
>>>> @400000004e1029d60994146c 22218<   RSET
>>>> @400000004e1029d60994e374 22218>   250 flushed
>>>> @400000004e1029d60b8495e4 22218<   AUTH LOGIN
>>>> @400000004e1029d60b85ca7c 22218>   334 VXNlcm5hbWU6
>>>> @400000004e1029d60c5eadec 22218<   c2VuZGVyLmNvbQ==
>>>> @400000004e1029d60c5ff9f4 22218>   334 UGFzc3dvcmQ6
>>>> @400000004e1029d60d4acf24 22218<   cGFzc3dvcmQ=
>>>> @400000004e1029db0d59619c 22218>   535 authentication failed (#5.7.1)
>>>> @400000004e1029db0e782f7c 22218<   RSET
>>>> @400000004e1029db0e78cbbc 22218>   250 flushed
>>>> @400000004e1029db10ef51cc 22218<   MAIL FROM:<sen...@domain.com>   SIZE=524
>>>> @400000004e1029db10f0f3c4 22218>   250 ok
>>>> @400000004e1029db281154f4 22218<   RCPT TO:<receip...@domain.com>
>>>> @400000004e1029db2812eb34 22218>   250 ok
>>>> @400000004e1029db2a9afd74 22218<   DATA
>>>> @400000004e1029db2aa021dc 22218>   354 go ahead
>>>> @400000004e1029db2b9f619c 22218<   Date: Sun, 3 Jul 2011 11:35:32 +0300
>>>> @400000004e1029db2ba00d7c 22218<   From: Name Surname<sen...@domain.com>
>>>> @400000004e1029db2ba08e64 22218<   Reply-To: Name 
>>>> Surname<sen...@domain.com>
>>>> @400000004e1029db2ba10b64 22218<   X-Priority: 3 (Normal)
>>>> @400000004e1029db2ba1847c 22218<   
>>>> Message-ID:<86092590.20110703113...@domain.com>
>>>> @400000004e1029db2ba1fd94 22218<   To: receip...@domain.com
>>>> @400000004e1029db2ba276ac 22218<   Subject: test
>>>> @400000004e1029db2ba2efc4 22218<   MIME-Version: 1.0
>>>> @400000004e1029db2ba364f4 22218<   Content-Type: text/plain; charset=utf-8
>>>> @400000004e1029db2ba3de0c 22218<   Content-Transfer-Encoding: 
>>>> quoted-printable
>>>> @400000004e1029db2ba45724 22218<
>>>> @400000004e1029db2ba5ba9c 22218<   test
>>>> @400000004e1029db2ba9f88c 22218<   .
>>>> @400000004e1029db376d0894 22218>   250 ok 1309682129 qp 22222
>>>> @400000004e1029db3888d4ec 22218<   RSET
>>>> @400000004e1029db3889cb04 22218>   250 flushed
>>>> @400000004e1029db3982d104 22218<   QUIT
>>>> @400000004e1029db398a79f4 22218>   221 mail.domain.com
>>>> @400000004e1029db398a81c4 22218>   [EOF]
>>>> @400000004e1029db399445c4 tcpserver: end 22217 status 0
>>>> @400000004e1029db39944d94 tcpserver: status: 0/40
>>>>
>>>> Right now I see that there is something goes wrong with a
>>>> authentication process in qmail and this dump is not very useful for
>>>> me. :( Are there any other ideas I can try?
>>>>
>>
>> RM>  Hi,
>>
>> RM>  I'd trying asking on a spamdyke mailing list.  If it was plain
>> RM>  qmail-smtpd then you'd see in the logs why it failed.
>>
>> RM>  Rick
>>
>> I was done fresh clean install on gentoo amd64 netqmail and vpopmail
>> with mysql support. No any clamav, spamassassin, spamdyke and others.
>> SMTP-AUTH still not working. Trying to figure out what is really
>> happening.

Finally I have found the situation when SMTP-AUTH not working. Seems
like it's not arch dependent. By some reason SMTP-AUTH fails when
/var/vpopmail is mounted as another logical volume. If qmail and
vpopmail is on the same logical volume SMTP-AUTH works fine. So I
guess it's not a vpopmail, but qmail fault. Thanks to everyone who
tried to help me.


!DSPAM:4e31b1d832711891912209!

Reply via email to