[Indimail-support] login problems

[Fabian Santiago]

testing login.

testing smtp via telnet locally, on 25, 465, and 587

receive:

454-Invalid argument (#4.3.0)
451 Requested action aborted: problem with child and I can't auth (#4.3.0)

using AUTH LOGIN with base64 encoded values derived with:

perl -MMIME::Base64 -e 'print encode_base64("username");'
perl -MMIME::Base64 -e 'print encode_base64("password");'

whats going on?

also, can i completely disallow auth on port 25 altogether while
requiring all sent mail be from authenticated users? if this isn't
enforced already by default.

- Fabian S.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Indimail-support mailing list
Indimail...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/indimail-support

[Fabian Santiago]

when i try using starttls with openssl on the cli, i receive:

139777253910432:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong
version number:s3_pkt.c:339:

- Fabian S.

[Manvendra Bhangui]

On 18 March 2017 at 09:33, Fabian Santiago <fsan...@garbage-juice.com> wrote:
> testing login.
>
> testing smtp via telnet locally, on 25, 465, and 587
>
> receive:
>
> 454-Invalid argument (#4.3.0)
> 451 Requested action aborted: problem with child and I can't auth (#4.3.0)
>
> using AUTH LOGIN with base64 encoded values derived with:
>
> perl -MMIME::Base64 -e 'print encode_base64("username");'
> perl -MMIME::Base64 -e 'print encode_base64("password");'
>
> whats going on?

1. Which version of IndiMail have you installed 1.x, 2.x or compiled
from Source?
2. This is how I would test

$ printf "\0post...@example.com\0pass" | /var/indimail/bin/base64
AHBvc3RtYXN0ZXJAZXhhbXBsZS5jb20AcGFzcw==

$ telnet 0 smtp
Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.
220 indimail.org (NO UCE) ESMTP IndiMail 1.192 Sat, 18 Mar 2017 14:00:55 +0530
auth plain AHBvc3RtYXN0ZXJAZXhhbXBsZS5jb20AcGFzcw==
235 ok, go ahead (#2.0.0)

You can also use /var/indimail/bin/swaks to test this out

>
> also, can i completely disallow auth on port 25 altogether while
> requiring all sent mail be from authenticated users? if this isn't
> enforced already by default.

You can edit /service/qmail-smtpd.25/run

edit the list line and remove AUTHMODULES so that the last line looks like this
/var/indimail/indimail/bin/qmail_smtpd $HOSTNAME /bin/false 2>&1"
I am assuming you are using indimail 1.x

Stop and restart qmail-smtpd on port 25

# /var/indimail/bin/svc -d /service/qmail-smtpd.25
# /var/indimail/bin/svc -u /service/qmail-smtpd.25

$ telnet 0 smtp
Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.
220 indimail.org (NO UCE) ESMTP IndiMail 1.192 Sat, 18 Mar 2017 14:05:48 +0530
auth plain AHBvc3RtYXN0ZXJAZXhhbXBsZS5jb20AcGFzcw==
535 authorization failed (#5.7.1)

example on using swaks
$ swaks --to testu...@example.com --from testu...@example.com
--auth PLAIN --auth-user testu...@example.com --auth-password pass
*** MX Routing not available: requires Net::DNS. Using localhost as mail server
=== Trying localhost:25...
=== Connected to localhost.
<- 220 indimail.org (NO UCE) ESMTP IndiMail 1.192 Sat, 18 Mar 2017
14:11:22 +0530
-> EHLO localhost
<- 250-indimail.org
<- 250-AUTH LOGIN PLAIN CRAM-MD5 CRAM-SHA1 CRAM-SHA256 CRAM-SHA512
CRAM-RIPEMD DIGEST-MD5
<- 250-AUTH=LOGIN PLAIN CRAM-MD5 CRAM-SHA1 CRAM-SHA256 CRAM-SHA512
CRAM-RIPEMD DIGEST-MD5
<- 250-PIPELINING
<- 250-8BITMIME
<- 250-SIZE 10000000
<- 250-ETRN
<- 250-STARTTLS
<- 250 HELP
-> AUTH PLAIN AHRlc3R1c2VyMDFAZXhhbXBsZS5jb20AcGFzcw==
<- 235 ok, go ahead (#2.0.0)
-> MAIL FROM:<testu...@example.com>
<- 250 ok
-> RCPT TO:<testu...@example.com>
<- 250 ok
-> DATA
<- 354 go ahead
-> Date: Sat, 18 Mar 2017 14:11:21 +0550
-> To: testu...@example.com
-> From: testu...@example.com
-> Subject: test Sat, 18 Mar 2017 14:11:21 +0550
-> X-Mailer: swaks v20100211.0 jetmore.org/john/code/swaks/
->
-> This is a test mailing
->
-> .
<- 250 ok 1489826482 qp 30884
-> QUIT
<- 221 indimail.org closing connection
=== Connection closed with remote host.


--
Regards Manvendra - http://www.indimail.org
GPG Pub Key
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC7CBC760014D250C

[Manvendra Bhangui]

On 18 March 2017 at 09:59, Fabian Santiago <fsan...@garbage-juice.com> wrote:
> 139777253910432:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong
> version number:s3_pkt.c:339:

Do you have /var/indimail/control/tlsserverciphers

--
Regards Manvendra - http://www.indimail.org
GPG Pub Key
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC7CBC760014D250C

[Fabian A. Santiago]

Same error, with both methods, I sent you previously.

This is indimail 1.9.x., installed from rpm repo.

I also read that by default indimail supports cram-md5. When I tried from another mail client I received the error cram-md5 not supported. Strange?

Thanks for your help.

- Fabian s.

--
Thanks.
Fabian S.

[Fabian A. Santiago]

On March 18, 2017 4:49:36 AM EDT, Manvendra Bhangui <mbha...@gmail.com> wrote:
>On 18 March 2017 at 09:59, Fabian Santiago
><fsan...@garbage-juice.com> wrote:
>> 139777253910432:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong
>> version number:s3_pkt.c:339:
>
>
>Do you have /var/indimail/control/tlsserverciphers

Yes, it appears to contain whatever your default values are.
--
Thanks.
Fabian S.

[Manvendra Bhangui]

On 18 March 2017 at 18:43, Fabian A. Santiago

CRAM-MD5 requires you to store the password un-encrypted (vpasswd -e option)

--
Regards Manvendra - http://www.indimail.org
GPG Pub Key
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC7CBC760014D250C

[Fabian A. Santiago]

Ok, understood. I didn't catch that. Or actually I did see that somewhere, I just didn't process it.

I still can't login though....? ;-)
--
Thanks.
Fabian S.

[Manvendra Bhangui]

On 18 March 2017 at 18:49, Fabian A. Santiago

<fsan...@garbage-juice.com> wrote:
>
> I still can't login though....? ;-)
> --
> Thanks.
> Fabian S.

Did you do vadddomain, vadduser?
are you able to login to IMAP or POP3?
does vuserinfo on a virtual domain user work?

[Fabian A. Santiago]

On March 18, 2017 9:24:01 AM EDT, Manvendra Bhangui <mbha...@gmail.com> wrote:
>On 18 March 2017 at 18:49, Fabian A. Santiago
><fsan...@garbage-juice.com> wrote:
>>
>> I still can't login though....? ;-)
>> --
>> Thanks.
>> Fabian S.
>
>Did you do vadddomain, vadduser?
>are you able to login to IMAP or POP3?
>does vuserinfo on a virtual domain user work?

I've tried:

Postmaster account (added via vadddomain)
A user (added via vadduser)
Neither imap nor pop3 work.
Vuserinfo appears normal, as does iwebadmin.

This is my first or default domain I'm testing with. No other domains created.

--
Thanks.
Fabian S.

[Manvendra Bhangui]

On 18 March 2017 at 19:01, Fabian A. Santiago

<fsan...@garbage-juice.com> wrote:
> On March 18, 2017 9:24:01 AM EDT, Manvendra Bhangui <mbha...@gmail.com> wrote:
>>On 18 March 2017 at 18:49, Fabian A. Santiago
>><fsan...@garbage-juice.com> wrote:
>>>
>>> I still can't login though....? ;-)
>>> --
>>> Thanks.
>>> Fabian S.
>>
>>Did you do vadddomain, vadduser?
>>are you able to login to IMAP or POP3?
>>does vuserinfo on a virtual domain user work?
>
> I've tried:
>
> Postmaster account (added via vadddomain)
> A user (added via vadduser)
> Neither imap nor pop3 work.
> Vuserinfo appears normal, as does iwebadmin.
>
> This is my first or default domain I'm testing with. No other domains created.
>
> --
> Thanks.
> Fabian S.

You need to do some troubleshooting

let us assume your domain is example.com
user is testuser01
password is xxxyyyzz

on a terminal do tail -f /var/log/indimail/imapd.143/current

on another terminal do the following

$ telnet 0 143

Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.

* OK IMAP4rev1 Server Ready.
a1 login testu...@example.com xxxyyyzz
a1 OK LOGIN Ok.


What do you see in the terminal 1 tail -f ?

--
Regards Manvendra - http://www.indimail.org
GPG Pub Key
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC7CBC760014D250C

[Fabian A. Santiago]

On March 18, 2017 11:06:06 AM EDT, Manvendra Bhangui <mbha...@gmail.com> wrote:
>On 18 March 2017 at 20:07, Fabian Santiago
><fsan...@garbage-juice.com> wrote:
>> ok, terminal 2:
>>
>> a1 NO Login failed.
>> Connection closed by foreign host.
>>
>> terminal 1:
>>
>
>> @4000000058cd453b108e460c /var/indimail/control/inquery/infifo.1: No
>> such file or directory
>
>That is not good. Are all services enabled in /service ?
>Did you remove /service/mysql.3306/down after checking MySQL service?
>
># /var/indimail/bin/svc -u /service/mysql.3306
>
>If mysql come up then remove the file /service/mysql.3306/down
>so that mysql service comes up after every reboot
>
>What is the output of
># /var/indimail/bin/svstat /service/*

Yes MySQL starts with qmail and is working.

[root@mail ~]# /var/indimail/bin/svstat /service/*
/service/fetchmail: down 38820 seconds
/service/greylist.1999: up (pid 10762) 38820 seconds
/service/indisrvr.4000: up (pid 10794) 38820 seconds
/service/inlookup.infifo: up (pid 10798) 38820 seconds
/service/mysql.3306: up (pid 10779) 38820 seconds
/service/proxy-imapd.4143: up (pid 10790) 38820 seconds
/service/proxy-imapd-ssl.9143: up (pid 10773) 38820 seconds
/service/proxy-pop3d.4110: up (pid 10787) 38820 seconds
/service/proxy-pop3d-ssl.9110: up (pid 10780) 38820 seconds
/service/pwdlookup: up (pid 10755) 38820 seconds
/service/qmail-imapd.143: up (pid 10764) 38820 seconds
/service/qmail-imapd-ssl.993: up (pid 10775) 38820 seconds
/service/qmail-pop3d.110: up (pid 10803) 38820 seconds
/service/qmail-pop3d-ssl.995: up (pid 10804) 38820 seconds
/service/qmail-poppass.106: up (pid 10761) 38820 seconds
/service/qmail-qmqpd.628: down 38820 seconds
/service/qmail-qmtpd.209: up (pid 10800) 38820 seconds
/service/qmail-send.25: up (pid 10768) 38820 seconds
/service/qmail-smtpd.25: up (pid 28260) 6360 seconds
/service/qmail-smtpd.366: up (pid 10778) 38820 seconds
/service/qmail-smtpd.465: up (pid 10812) 38820 seconds
/service/qmail-smtpd.587: up (pid 10770) 38820 seconds
/service/qmail-spamlog: up (pid 10786) 38820 seconds
/service/qscanq: up (pid 31071) 19 seconds
/service/udplogger.3000: up (pid 10757) 38820 seconds
[root@mail ~]#


My MySQL version is 5.7.17.
--
Thanks.
Fabian S.

[Manvendra Bhangui]

On 18 March 2017 at 20:45, Fabian A. Santiago

<fsan...@garbage-juice.com> wrote:
>
>
> [root@mail ~]# /var/indimail/bin/svstat /service/*

> /service/qmail-smtpd.465: up (pid 10812) 38820 seconds
> /service/qmail-smtpd.587: up (pid 10770) 38820 seconds
> /service/qmail-spamlog: up (pid 10786) 38820 seconds
> /service/qscanq: up (pid 31071) 19 seconds
> /service/udplogger.3000: up (pid 10757) 38820 seconds

any errors in /var/log/indimail/inlookup.infifo/current ?
Looks like inqery service is not working
what is the content of the file /var/indimail/etc/indimail.cnf
what is the output of the following command
# inquerytest -q 3 -i "" youruser@yourdomain

Try the following
rm /service/qmail-imapd.143/variables/QUERY_CACHE
svc -d /service/qmail-imapd.143
svc -u /service/qmail-imapd.143

Now try login to imap using telnet

[Fabian A. Santiago]

On March 18, 2017 11:59:21 AM EDT, Manvendra Bhangui <mbha...@gmail.com> wrote:
>On 18 March 2017 at 20:45, Fabian A. Santiago
><fsan...@garbage-juice.com> wrote:
>>
>>
>> [root@mail ~]# /var/indimail/bin/svstat /service/*
>> /service/qmail-smtpd.465: up (pid 10812) 38820 seconds
>> /service/qmail-smtpd.587: up (pid 10770) 38820 seconds
>> /service/qmail-spamlog: up (pid 10786) 38820 seconds
>> /service/qscanq: up (pid 31071) 19 seconds
>> /service/udplogger.3000: up (pid 10757) 38820 seconds
>
>any errors in /var/log/indimail/inlookup.infifo/current ?
>Looks like inqery service is not working
>what is the content of the file /var/indimail/etc/indimail.cnf
>what is the output of the following command
># inquerytest -q 3 -i "" youruser@yourdomain
>
>Try the following
>rm /service/qmail-imapd.143/variables/QUERY_CACHE
>svc -d /service/qmail-imapd.143
>svc -u /service/qmail-imapd.143
>
>Now try login to imap using telnet

Ok,

The log showed MySQL account login denied errors.

I did change​ the indimail password and updated the host file in the beginning.

RM'ing the cache file fixed it. Imap works now. Will I have to do similar with other services as well? Thanks.
--
Thanks.
Fabian S.

[Manvendra Bhangui]

On 18 March 2017 at 21:44, Fabian A. Santiago

<fsan...@garbage-juice.com> wrote:
> On March 18, 2017 11:59:21 AM EDT, Manvendra Bhangui <mbha...@gmail.com> wrote:
>>On 18 March 2017 at 20:45, Fabian A. Santiago
>><fsan...@garbage-juice.com> wrote:
>>>
>>>
>>> [root@mail ~]# /var/indimail/bin/svstat /service/*
>>> /service/qmail-smtpd.465: up (pid 10812) 38820 seconds
>>> /service/qmail-smtpd.587: up (pid 10770) 38820 seconds
>>> /service/qmail-spamlog: up (pid 10786) 38820 seconds
>>> /service/qscanq: up (pid 31071) 19 seconds
>>> /service/udplogger.3000: up (pid 10757) 38820 seconds
>>
>>any errors in /var/log/indimail/inlookup.infifo/current ?
>>Looks like inqery service is not working
>>what is the content of the file /var/indimail/etc/indimail.cnf
>>what is the output of the following command
>># inquerytest -q 3 -i "" youruser@yourdomain
>>
>>Try the following
>>rm /service/qmail-imapd.143/variables/QUERY_CACHE
>>svc -d /service/qmail-imapd.143
>>svc -u /service/qmail-imapd.143
>>
>>Now try login to imap using telnet
>
> Ok,
>
> The log showed MySQL account login denied errors.
>
> I did change the indimail password and updated the host file in the beginning.
>
> RM'ing the cache file fixed it. Imap works now. Will I have to do similar with other services as well? Thanks.

removing the QUERY_CACHE only bypasses inlookup and the queries
directly go to mysql. You need to fix all errors in
inlookup.infifo/current

ensure that the socket referenced in /service/mysql.3306,
/var/indimail/etc/indimail.cnf and /var/indimail/control/host.mysql
are all same

[Fabian A. Santiago]

The cnf and the host file match and the service run file simply greps the socket from the cnf.

Obviously I created domains / accounts so I know I'm talking to the db.

Where else could I look?

--
Thanks.
Fabian S.

[Manvendra Bhangui]

On 18 March 2017 at 22:03, Fabian A. Santiago

<fsan...@garbage-juice.com> wrote:
>>> RM'ing the cache file fixed it. Imap works now. Will I have to do
>>similar with other services as well? Thanks.
>>
>>removing the QUERY_CACHE only bypasses inlookup and the queries
>>directly go to mysql. You need to fix all errors in
>>inlookup.infifo/current
>>
>>ensure that the socket referenced in /service/mysql.3306,
>>/var/indimail/etc/indimail.cnf and /var/indimail/control/host.mysql
>>are all same
>
> The cnf and the host file match and the service run file simply greps the socket from the cnf.
>
> Obviously I created domains / accounts so I know I'm talking to the db.
>
> Where else could I look?
>

restart inlookup.infifo service

svc -d /service/inlookup.infifo
svc -u /service/inlookup.infifo

# inquerytest -q 3 -i "" youruser@yourdomain

If the above command works enable the query cache

# echo 1 > /service/qmail-imapd.143/variables/QUERY_CACHE
# svc -d /service/qmail-imapd.143
# svc -u /service/qmail-imapd.143

Then test if imap is working. If imap authenticaiton works, you will
find all others working too (SMTP, POP3, etc)

[Fabian A. Santiago]

Yep that did it. Working now. Thank you. What caused this issue do you believe?
--
Thanks.
Fabian S.

[Manvendra Bhangui]

On 18 March 2017 at 22:18, Fabian A. Santiago

<fsan...@garbage-juice.com> wrote:
>>restart inlookup.infifo service
>>
>>svc -d /service/inlookup.infifo
>>svc -u /service/inlookup.infifo
>>
>># inquerytest -q 3 -i "" youruser@yourdomain
>>
>>If the above command works enable the query cache
>>
>># echo 1 > /service/qmail-imapd.143/variables/QUERY_CACHE
>># svc -d /service/qmail-imapd.143
>># svc -u /service/qmail-imapd.143
>>
>>Then test if imap is working. If imap authenticaiton works, you will
>>find all others working too (SMTP, POP3, etc)
>
> Yep that did it. Working now. Thank you. What caused this issue do you believe?

pasword change. inlookup service was startup before the password
change. It was still
using the old password. WHen you restarted it, it got the new password
from /var/indimail/control/host.mysql

[Fabian A. Santiago]

On March 18, 2017 12:50:48 PM EDT, Manvendra Bhangui <mbha...@gmail.com> wrote:
>On 18 March 2017 at 22:18, Fabian A. Santiago
><fsan...@garbage-juice.com> wrote:
>>>restart inlookup.infifo service
>>>
>>>svc -d /service/inlookup.infifo
>>>svc -u /service/inlookup.infifo
>>>
>>># inquerytest -q 3 -i "" youruser@yourdomain
>>>
>>>If the above command works enable the query cache
>>>
>>># echo 1 > /service/qmail-imapd.143/variables/QUERY_CACHE
>>># svc -d /service/qmail-imapd.143
>>># svc -u /service/qmail-imapd.143
>>>
>>>Then test if imap is working. If imap authenticaiton works, you will
>>>find all others working too (SMTP, POP3, etc)
>>
>> Yep that did it. Working now. Thank you. What caused this issue do
>you believe?
>
>pasword change. inlookup service was startup before the password
>change. It was still
>using the old password. WHen you restarted it, it got the new password
>from /var/indimail/control/host.mysql

Is
Systemctl restart indimail

Not sufficient to fully restart all components?

I certainly did that after the password change and updating the host file.

?
--
Thanks.
Fabian S.

[Manvendra Bhangui]

On 18 March 2017 at 22:22, Fabian A. Santiago

<fsan...@garbage-juice.com> wrote:
> On March 18, 2017 12:50:48 PM EDT, Manvendra Bhangui <mbha...@gmail.com> wrote:
>>On 18 March 2017 at 22:18, Fabian A. Santiago
>><fsan...@garbage-juice.com> wrote:
>>>>restart inlookup.infifo service
>>>>
>>>>svc -d /service/inlookup.infifo
>>>>svc -u /service/inlookup.infifo
>>>>
>>>># inquerytest -q 3 -i "" youruser@yourdomain
>>>>
>>>>If the above command works enable the query cache
>>>>
>>>># echo 1 > /service/qmail-imapd.143/variables/QUERY_CACHE
>>>># svc -d /service/qmail-imapd.143
>>>># svc -u /service/qmail-imapd.143
>>>>
>>>>Then test if imap is working. If imap authenticaiton works, you will
>>>>find all others working too (SMTP, POP3, etc)
>>>
>>> Yep that did it. Working now. Thank you. What caused this issue do
>>you believe?
>>
>>pasword change. inlookup service was startup before the password
>>change. It was still
>>using the old password. WHen you restarted it, it got the new password
>>from /var/indimail/control/host.mysql
>
> Is
> Systemctl restart indimail
>
> Not sufficient to fully restart all components?
>
> I certainly did that after the password change and updating the host file.
>

systemctl restart indimail or service indimail restart or
/etc/init.d/indimail restart are all sufficient.
mysql password requires just inlookup and indisrvr service to be
restarted. You don't have to restart indimail just for that

The mysql password is picked up from host.mysql. So obviously inlookup
had the wrong password.

[Fabian A. Santiago]

I rebooted my server today for an unrelated reason and once again, I couldn't log into email. I had to manually restart inlookup again. Why doesn't this recover from a reboot? Same thing must have happened to me in yesterday's go around.
--
Thanks.
Fabian S.

[Manvendra Bhangui]

On 19 March 2017 at 23:08, Fabian A. Santiago

Not sure what is happening without seeing the inlookup logs
you can delete the following files and restart the the following
service so that they don't use inlookup

/service/qmail-imapd.143/variables/QUERY_CACHE
/service/qmail-smtpd.25/variables/QUERY_CACHE
/service/qmail-imapd-ssl.993/variables/QUERY_CACHE
/service/qmail-smtpd.366/variables/QUERY_CACHE
/service/qmail-pop3d.110/variables/QUERY_CACHE
/service/qmail-smtpd.465/variables/QUERY_CACHE
/service/qmail-pop3d-ssl.995/variables/QUERY_CACHE
/service/qmail-smtpd.587/variables/QUERY_CACHE

--
Regards Manvendra - http://www.indimail.org
GPG Pub Key
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC7CBC760014D250C

[Fabian A. Santiago]

I've sent you the log privately.
--
Thanks.
Fabian S.