Re: [vchkpw] SMTP-AUTH problem with vchkpw

2011-07-28 Thread anf
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:

 @40004e1029d019fc59f4 22218>   220 mail.domain.com ESMTP
 @40004e1029d035004684 22218<   EHLO [10.1.1.177]
 @40004e1029d035017b1c 22218>   250-mail.domain.com
 @40004e1029d03501b1cc 22218>   250-STARTTLS
 @40004e1029d03501e494 22218>   250-PIPELINING
 @40004e1029d03502175c 22218>   250-8BITMIME
 @40004e1029d03502463c 22218>   250-SIZE 0
 @40004e1029d035027904 22218>   250 AUTH LOGIN PLAIN
 @40004e1029d10834940c 22218<   AUTH PLAIN
 @40004e1029d108356ecc 22218>   334
 @40004e1029d109252dcc 22218<   c2VuZGVyLmNvbXBhc3N3b3Jk
 @40004e1029d6092f863c 22218>   535 authentication failed (#5.7.1)
 @40004e1029d60994146c 22218<   RSET
 @40004e1029d60994e374 22218>   250 flushed
 @40004e1029d60b8495e4 22218<   AUTH LOGIN
 @40004e1029d60b85ca7c 22218>   334 VXNlcm5hbWU6
 @40004e1029d60c5eadec 22218<   c2VuZGVyLmNvbQ==
 @40004e1029d60c5ff9f4 22218>   334 UGFzc3dvcmQ6
 @40004e1029d60d4acf24 22218<   cGFzc3dvcmQ=
 @40004e1029db0d59619c 22218>   535 authentication failed (#5.7.1)
 @40004e1029db0e782f7c 22218<   RSET
 @40004e1029db0e78cbbc 22218>   250 flushed
 @40004e1029db10ef51cc 22218<   MAIL FROM:   SIZE=524
 @40004e1029db10f0f3c4 22218>   250 ok
 @40004e1029db281154f4 22218<   RCPT TO:
 @40004e1029db2812eb34 22218>   250 ok
 @40004e1029db2a9afd74 22218<   DATA
 @40004e1029db2aa021dc 22218>   354 go ahead
 @40004e1029db2b9f619c 22218<   Date: Sun, 3 Jul 2011 11:35:32 +0300
 @40004e1029db2ba00d7c 22218<   From: Name Surname
 @40004e1029db2ba08e64 22218<   Reply-To: Name 
 Surname
 @40004e1029db2ba10b64 22218<   X-Priority: 3 (Normal)
 @40004e1029db2ba1847c 22218<   
 Message-ID:<86092590.20110703113...@domain.com>
 @40004e1029db2ba1fd94 22218<   To: receip...@domain.com
 @40004e1029db2ba276ac 22218<   Subject: test
 @40004e1029db2ba2efc4 22218<   MIME-Version: 1.0
 @40004e1029db2ba364f4 22218<   Content-Type: text/plain; charset=utf-8
 @40004e1029db2ba3de0c 22218<   Content-Transfer-Encoding: 
 quoted-printable
 @40004e1029db2ba45724 22218<
 @40004e1029db2ba5ba9c 22218<   test
 @40004e1029db2ba9f88c 22218<   .
 @40004e1029db376d0894 22218>   250 ok 1309682129 qp 2
 @40004e1029db3888d4ec 22218<   RSET
 @40004e1029db3889cb04 22218>   250 flushed
 @40004e1029db3982d104 22218<   QUIT
 @40004e1029db398a79f4 22218>   221 mail.domain.com
 @40004e1029db398a81c4 22218>   [EOF]
 @40004e1029db399445c4 tcpserver: end 22217 status 0
 @40004e1029db39944d94 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 

Re: [vchkpw] SMTP-AUTH problem with vchkpw

2011-07-26 Thread anf
Hello,

Wednesday, July 27, 2011, 00:05:10, anf wrote:

alo> Hello Rick,

alo> Sunday, July 3, 2011, 17:15:29, Rick Macdougall wrote:
RM>> On 03/07/2011 5:11 AM, anf 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:
>>>
>>> @40004e1029d019fc59f4 22218>  220 mail.domain.com ESMTP
>>> @40004e1029d035004684 22218<  EHLO [10.1.1.177]
>>> @40004e1029d035017b1c 22218>  250-mail.domain.com
>>> @40004e1029d03501b1cc 22218>  250-STARTTLS
>>> @40004e1029d03501e494 22218>  250-PIPELINING
>>> @40004e1029d03502175c 22218>  250-8BITMIME
>>> @40004e1029d03502463c 22218>  250-SIZE 0
>>> @40004e1029d035027904 22218>  250 AUTH LOGIN PLAIN
>>> @40004e1029d10834940c 22218<  AUTH PLAIN
>>> @40004e1029d108356ecc 22218>  334
>>> @40004e1029d109252dcc 22218<  c2VuZGVyLmNvbXBhc3N3b3Jk
>>> @40004e1029d6092f863c 22218>  535 authentication failed (#5.7.1)
>>> @40004e1029d60994146c 22218<  RSET
>>> @40004e1029d60994e374 22218>  250 flushed
>>> @40004e1029d60b8495e4 22218<  AUTH LOGIN
>>> @40004e1029d60b85ca7c 22218>  334 VXNlcm5hbWU6
>>> @40004e1029d60c5eadec 22218<  c2VuZGVyLmNvbQ==
>>> @40004e1029d60c5ff9f4 22218>  334 UGFzc3dvcmQ6
>>> @40004e1029d60d4acf24 22218<  cGFzc3dvcmQ=
>>> @40004e1029db0d59619c 22218>  535 authentication failed (#5.7.1)
>>> @40004e1029db0e782f7c 22218<  RSET
>>> @40004e1029db0e78cbbc 22218>  250 flushed
>>> @40004e1029db10ef51cc 22218<  MAIL FROM:  SIZE=524
>>> @40004e1029db10f0f3c4 22218>  250 ok
>>> @40004e1029db281154f4 22218<  RCPT TO:
>>> @40004e1029db2812eb34 22218>  250 ok
>>> @40004e1029db2a9afd74 22218<  DATA
>>> @40004e1029db2aa021dc 22218>  354 go ahead
>>> @40004e1029db2b9f619c 22218<  Date: Sun, 3 Jul 2011 11:35:32 +0300
>>> @40004e1029db2ba00d7c 22218<  From: Name Surname
>>> @40004e1029db2ba08e64 22218<  Reply-To: Name Surname
>>> @40004e1029db2ba10b64 22218<  X-Priority: 3 (Normal)
>>> @40004e1029db2ba1847c 22218<  
>>> Message-ID:<86092590.20110703113...@domain.com>
>>> @40004e1029db2ba1fd94 22218<  To: receip...@domain.com
>>> @40004e1029db2ba276ac 22218<  Subject: test
>>> @40004e1029db2ba2efc4 22218<  MIME-Version: 1.0
>>> @40004e1029db2ba364f4 22218<  Content-Type: text/plain; charset=utf-8
>>> @40004e1029db2ba3de0c 22218<  Content-Transfer-Encoding: 
>>> quoted-printable
>>> @40004e1029db2ba45724 22218<
>>> @40004e1029db2ba5ba9c 22218<  test
>>> @40004e1029db2ba9f88c 22218<  .
>>> @40004e1029db376d0894 22218>  250 ok 1309682129 qp 2
>>> @40004e1029db3888d4ec 22218<  RSET
>>> @40004e1029db3889cb04 22218>  250 flushed
>>> @40004e1029db3982d104 22218<  QUIT
>>> @40004e1029db398a79f4 22218>  221 mail.domain.com
>>> @40004e1029db398a81c4 22218>  [EOF]
>>> @40004e1029db399445c4 tcpserver: end 22217 status 0
>>> @40004e1029db39944d94 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

alo> I was done fresh clean install on gentoo amd64 netqmail and vpopmail
alo> with mysql support. No any clamav, spamassassin, spamdyke and others.
alo> SMTP-AUTH still not working. Trying to figure out what is really
alo> happening.

Just want to add that I tested right now and found that the same fresh
programs configurations and settings on the clean 32-bit system
working pretty good. Should I try once again to use recordio program
on a 64-bit system?


!DSPAM:4e2f462332714910253358!



Re: [vchkpw] SMTP-AUTH problem with vchkpw

2011-07-26 Thread anf
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:
>>
>> @40004e1029d019fc59f4 22218>  220 mail.domain.com ESMTP
>> @40004e1029d035004684 22218<  EHLO [10.1.1.177]
>> @40004e1029d035017b1c 22218>  250-mail.domain.com
>> @40004e1029d03501b1cc 22218>  250-STARTTLS
>> @40004e1029d03501e494 22218>  250-PIPELINING
>> @40004e1029d03502175c 22218>  250-8BITMIME
>> @40004e1029d03502463c 22218>  250-SIZE 0
>> @40004e1029d035027904 22218>  250 AUTH LOGIN PLAIN
>> @40004e1029d10834940c 22218<  AUTH PLAIN
>> @40004e1029d108356ecc 22218>  334
>> @40004e1029d109252dcc 22218<  c2VuZGVyLmNvbXBhc3N3b3Jk
>> @40004e1029d6092f863c 22218>  535 authentication failed (#5.7.1)
>> @40004e1029d60994146c 22218<  RSET
>> @40004e1029d60994e374 22218>  250 flushed
>> @40004e1029d60b8495e4 22218<  AUTH LOGIN
>> @40004e1029d60b85ca7c 22218>  334 VXNlcm5hbWU6
>> @40004e1029d60c5eadec 22218<  c2VuZGVyLmNvbQ==
>> @40004e1029d60c5ff9f4 22218>  334 UGFzc3dvcmQ6
>> @40004e1029d60d4acf24 22218<  cGFzc3dvcmQ=
>> @40004e1029db0d59619c 22218>  535 authentication failed (#5.7.1)
>> @40004e1029db0e782f7c 22218<  RSET
>> @40004e1029db0e78cbbc 22218>  250 flushed
>> @40004e1029db10ef51cc 22218<  MAIL FROM:  SIZE=524
>> @40004e1029db10f0f3c4 22218>  250 ok
>> @40004e1029db281154f4 22218<  RCPT TO:
>> @40004e1029db2812eb34 22218>  250 ok
>> @40004e1029db2a9afd74 22218<  DATA
>> @40004e1029db2aa021dc 22218>  354 go ahead
>> @40004e1029db2b9f619c 22218<  Date: Sun, 3 Jul 2011 11:35:32 +0300
>> @40004e1029db2ba00d7c 22218<  From: Name Surname
>> @40004e1029db2ba08e64 22218<  Reply-To: Name Surname
>> @40004e1029db2ba10b64 22218<  X-Priority: 3 (Normal)
>> @40004e1029db2ba1847c 22218<  
>> Message-ID:<86092590.20110703113...@domain.com>
>> @40004e1029db2ba1fd94 22218<  To: receip...@domain.com
>> @40004e1029db2ba276ac 22218<  Subject: test
>> @40004e1029db2ba2efc4 22218<  MIME-Version: 1.0
>> @40004e1029db2ba364f4 22218<  Content-Type: text/plain; charset=utf-8
>> @40004e1029db2ba3de0c 22218<  Content-Transfer-Encoding: quoted-printable
>> @40004e1029db2ba45724 22218<
>> @40004e1029db2ba5ba9c 22218<  test
>> @40004e1029db2ba9f88c 22218<  .
>> @40004e1029db376d0894 22218>  250 ok 1309682129 qp 2
>> @40004e1029db3888d4ec 22218<  RSET
>> @40004e1029db3889cb04 22218>  250 flushed
>> @40004e1029db3982d104 22218<  QUIT
>> @40004e1029db398a79f4 22218>  221 mail.domain.com
>> @40004e1029db398a81c4 22218>  [EOF]
>> @40004e1029db399445c4 tcpserver: end 22217 status 0
>> @40004e1029db39944d94 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.


!DSPAM:4e2f2c0c32714376791534!



Re: [vchkpw] SMTP-AUTH problem with vchkpw

2011-07-03 Thread anf
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:

@40004e1029d019fc59f4 22218 > 220 mail.domain.com ESMTP
@40004e1029d035004684 22218 < EHLO [10.1.1.177]
@40004e1029d035017b1c 22218 > 250-mail.domain.com
@40004e1029d03501b1cc 22218 > 250-STARTTLS
@40004e1029d03501e494 22218 > 250-PIPELINING
@40004e1029d03502175c 22218 > 250-8BITMIME
@40004e1029d03502463c 22218 > 250-SIZE 0
@40004e1029d035027904 22218 > 250 AUTH LOGIN PLAIN
@40004e1029d10834940c 22218 < AUTH PLAIN
@40004e1029d108356ecc 22218 > 334
@40004e1029d109252dcc 22218 < c2VuZGVyLmNvbXBhc3N3b3Jk
@40004e1029d6092f863c 22218 > 535 authentication failed (#5.7.1)
@40004e1029d60994146c 22218 < RSET
@40004e1029d60994e374 22218 > 250 flushed
@40004e1029d60b8495e4 22218 < AUTH LOGIN
@40004e1029d60b85ca7c 22218 > 334 VXNlcm5hbWU6
@40004e1029d60c5eadec 22218 < c2VuZGVyLmNvbQ==
@40004e1029d60c5ff9f4 22218 > 334 UGFzc3dvcmQ6
@40004e1029d60d4acf24 22218 < cGFzc3dvcmQ=
@40004e1029db0d59619c 22218 > 535 authentication failed (#5.7.1)
@40004e1029db0e782f7c 22218 < RSET
@40004e1029db0e78cbbc 22218 > 250 flushed
@40004e1029db10ef51cc 22218 < MAIL FROM: SIZE=524
@40004e1029db10f0f3c4 22218 > 250 ok
@40004e1029db281154f4 22218 < RCPT TO:
@40004e1029db2812eb34 22218 > 250 ok
@40004e1029db2a9afd74 22218 < DATA
@40004e1029db2aa021dc 22218 > 354 go ahead
@40004e1029db2b9f619c 22218 < Date: Sun, 3 Jul 2011 11:35:32 +0300
@40004e1029db2ba00d7c 22218 < From: Name Surname 
@40004e1029db2ba08e64 22218 < Reply-To: Name Surname 
@40004e1029db2ba10b64 22218 < X-Priority: 3 (Normal)
@40004e1029db2ba1847c 22218 < Message-ID: 
<86092590.20110703113...@domain.com>
@40004e1029db2ba1fd94 22218 < To: receip...@domain.com
@40004e1029db2ba276ac 22218 < Subject: test
@40004e1029db2ba2efc4 22218 < MIME-Version: 1.0
@40004e1029db2ba364f4 22218 < Content-Type: text/plain; charset=utf-8
@40004e1029db2ba3de0c 22218 < Content-Transfer-Encoding: quoted-printable
@40004e1029db2ba45724 22218 <
@40004e1029db2ba5ba9c 22218 < test
@40004e1029db2ba9f88c 22218 < .
@40004e1029db376d0894 22218 > 250 ok 1309682129 qp 2
@40004e1029db3888d4ec 22218 < RSET
@40004e1029db3889cb04 22218 > 250 flushed
@40004e1029db3982d104 22218 < QUIT
@40004e1029db398a79f4 22218 > 221 mail.domain.com
@40004e1029db398a81c4 22218 > [EOF]
@40004e1029db399445c4 tcpserver: end 22217 status 0
@40004e1029db39944d94 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?


!DSPAM:4e10323332711707610120!



Re: [vchkpw] SMTP-AUTH problem with vchkpw

2011-07-01 Thread anf
Hello Rick,

Friday, July 1, 2011, 16:13:45, Rick Macdougall wrote:
RM> On 30/06/2011 8:10 PM, a...@ltmd.org wrote:
>> I tried to migrate my mail service (qmail+vpopmail+mysql) to the
>> 64-bit Gentoo platform and almost succeeded, but SMTP-AUTH problem
>> blocked me.
>>
>> Right now I have no multilib 64-bit hardened Gentoo system with
>> netqmail-1.06, vpopmail-5.4.30-r2, dovecot-2.0.13 and some other
>> stuff. Everything seems working fine, except SMTP-AUTH function.
>>
>> My mailer on this new server shows me:
>>
>> SEND  - connected to SMTP server
>> SEND  - authenticating (plain)...
>> SEND  - Server reports error. The response is: authentication failed (#5.7.1)
>> SEND  - authenticating (login)...
>> SEND  - Server reports error. The response is: authentication failed (#5.7.1)
>> SEND  - WARNING: there were no compatible authentication mechanisms detected
>>
>> Here goes my config /var/qmail/control/conf-smtpd:
>> ---
>> TCPSERVER_OPTS="${TCPSERVER_OPTS} -R"
>> QMAIL_SMTP_PRE="${QMAIL_SMTP_PRE} spamdyke -f /etc/spamdyke/spamdyke.conf"
>> QMAIL_SMTP_CHECKPASSWORD="/var/vpopmail/bin/vchkpw"
>> [[ -n "${QMAIL_SMTP_CHECKPASSWORD}" ]]&&  {
>>  [[ -z "${QMAIL_SMTP_POST}" ]]&&  QMAIL_SMTP_POST=/bin/true
>>  QMAIL_SMTP_POST="${QMAIL_SMTP_CHECKPASSWORD} ${QMAIL_SMTP_POST}"
>> }
>> ---
>>

RM> Hi,

RM> You should be able to see the auth attempt in one f your log files.  On
RM> all my servers it's in /var/log/messages.  This might help show where 
RM> the problem lies.

RM> One of my lines as an example - Jul  1 04:43:17 mail002 vpopmail[24348]:
RM> vchkpw-smtp: vpopmail user not found rlev...@aei.ca:14.208.230.43

I scanned through all my log files, but not found any entry about
with pattern vchkpw.

I have only spamdyke messages like user was not SMTP authorized.
Jul  1 00:32:49 mail spamdyke[7441]: ALLOWED from: m...@address.com to: 
m...@address.com origin_ip: 2.6.7.8 origin_rdns: 2-6-7-8.domain.com auth: 
(unknown)

Spamdyke disabling not helped me.

Server response show that it SMTP-AUTH capable:
$ telnet 1.2.3.4 25
Trying 1.2.3.4...
Connected to 1.2.3.4.
Escape character is '^]'.
220 mail.server.com ESMTP
EHLO mail.server.com
250-mail.server.com
250-STARTTLS
250-PIPELINING
250-8BITMIME
250-SIZE 0
250 AUTH LOGIN PLAIN

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?

Anf


!DSPAM:4e0dfbd932711543016584!



[vchkpw] SMTP-AUTH problem with vchkpw

2011-06-30 Thread anf
I tried to migrate my mail service (qmail+vpopmail+mysql) to the
64-bit Gentoo platform and almost succeeded, but SMTP-AUTH problem
blocked me.

Right now I have no multilib 64-bit hardened Gentoo system with
netqmail-1.06, vpopmail-5.4.30-r2, dovecot-2.0.13 and some other
stuff. Everything seems working fine, except SMTP-AUTH function.

My mailer on this new server shows me:

SEND  - connected to SMTP server
SEND  - authenticating (plain)...
SEND  - Server reports error. The response is: authentication failed (#5.7.1)
SEND  - authenticating (login)...
SEND  - Server reports error. The response is: authentication failed (#5.7.1)
SEND  - WARNING: there were no compatible authentication mechanisms detected

Here goes my config /var/qmail/control/conf-smtpd:
---
TCPSERVER_OPTS="${TCPSERVER_OPTS} -R"
QMAIL_SMTP_PRE="${QMAIL_SMTP_PRE} spamdyke -f /etc/spamdyke/spamdyke.conf"
QMAIL_SMTP_CHECKPASSWORD="/var/vpopmail/bin/vchkpw"
[[ -n "${QMAIL_SMTP_CHECKPASSWORD}" ]] && {
[[ -z "${QMAIL_SMTP_POST}" ]] && QMAIL_SMTP_POST=/bin/true
QMAIL_SMTP_POST="${QMAIL_SMTP_CHECKPASSWORD} ${QMAIL_SMTP_POST}"
}
---

mail control # ls -la /var/vpopmail/bin/vchkpw
-rws--x--x 1 root vpopmail 129128 Jul  1 02:18 /var/vpopmail/bin/vchkpw

Dovecot using vpopmail driver working fine.

userdb {
  driver = vpopmail
}

May be someone knows how can I solve that problem with SMTP-AUTH?


!DSPAM:4e0d108932711953113103!