Re: testing sieve/pigeonhole, auth errors

Tue, 16 Jan 2024 18:55:16 -0800 

On 1/16/2024 12:23:22, John Fawcett wrote:


On 15/01/2024 21:13, Joe Acquisto wrote:

A small SOHO system, of installed perhaps a year.  Seems to be working 
and

wished to add pigeonhole/sieve.

Per Pigeonhole/sieve troubleshooting in the docs, set on mail_debug = 
yes and
this is what I see, upon launching Thunderbird as the client.  Thought 
that
"unknown user" and "permission denied" deserved attention before any 
other

steps.
Just the dialog for one user is pasted below.
pid 475 is dovecot,vmail for dovecot imapd
This is what I see for /proc/self/io
blah # ll /proc/self/io
-r-------- 1 root root 0 Jan 15 15:10 /proc/self/io
Jan 15 14:53:35 auth-worker(22903): Info: conn unix:auth-worker
(pid=22897,uid=475): auth-worker<1>: pam
(m...@here.com,192.168.11.166,<RbZgXgEPUKbAqAum>): unknown user
Jan 15 14:53:35 auth-worker(22901): Info: conn unix:auth-worker
(pid=22897,uid=475): auth-worker<4>: passwd
(m...@here.com,192.168.11.166,<RbZgXgEPUKbAqAum>): unknown user

Jan 15 14:53:35 imap-login: Info: Login: user=<m...@here.com>, 
method=PLAIN,
rip=192.168.11.166, lip=192.168.0.225, mpid=22907, 
session=<RbZgXgEPUKbAqAum>
Jan 15 14:53:35 imap(m...@here.com)<22907><RbZgXgEPUKbAqAum>: Debug: 
Effective

uid=100, gid=1000, home=/home/vmail/m...@here.com

Jan 15 14:53:35 imap(m...@here.com)<22907><RbZgXgEPUKbAqAum>: Debug: 
open(/proc/

self/io) failed: Permission denied

Jan 15 14:53:35 imap(m...@here.com)<22907><RbZgXgEPUKbAqAum>: Debug: 
Namespace

inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes,
subscriptions=yes location=maildir:~/
Maildir

Jan 15 14:53:35 imap(m...@here.com)<22907><RbZgXgEPUKbAqAum>: Debug: 
maildir++:
root=/home/vmail/m...@here.com/Maildir, index=, indexpvt=, control=, 
inbox=/home/

vmail/joea@j4com
puters.com/Maildir, alt=
Jan 15 14:53:35 auth-worker(22904): Info: conn unix:auth-worker
(pid=22897,uid=475): auth-worker<1>: pam
(m...@here.com,192.168.11.166,<d7VgXgEPTqbAqAum>): unknown user
Jan 15 14:53:35 auth-worker(22901): Info: conn unix:auth-worker
(pid=22897,uid=475): auth-worker<5>: passwd
(m...@here.com,192.168.11.166,<d7VgXgEPTqbAqAum>): unknown user

Jan 15 14:53:35 imap-login: Info: Login: user=<m...@here.com>, 
method=PLAIN,
rip=192.168.11.166, lip=192.168.0.225, mpid=22908, 
session=<d7VgXgEPTqbAqAum>
Jan 15 14:53:35 imap(m...@here.com)<22908><d7VgXgEPTqbAqAum>: Debug: 
Effective

uid=100, gid=1000, home=/home/vmail/m...@here.com

Jan 15 14:53:35 imap(m...@here.com)<22908><d7VgXgEPTqbAqAum>: Debug: 
open(/proc/

self/io) failed: Permission denied

Jan 15 14:53:35 imap(m...@here.com)<22908><d7VgXgEPTqbAqAum>: Debug: 
Namespace

inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes,
subscriptions=yes location=maildir:~/
Maildir

Jan 15 14:53:35 imap(m...@here.com)<22908><d7VgXgEPTqbAqAum>: Debug: 
maildir++:
root=/home/vmail/m...@here.com/Maildir, index=, indexpvt=, control=, 
inbox=/home/

vmail/joea@j4com
puters.com/Maildir, alt=

Jan 15 14:53:36 imap(j...@acquisto-us.com)<22906><fwJdXgEPQKbAqAum>: 
Debug:

Mailbox INBOX: Mailbox opened

Jan 15 14:53:36 imap(m...@here.com)<22907><RbZgXgEPUKbAqAum>: Debug: 
Mailbox

INBOX: Mailbox opened

Jan 15 14:53:37 imap(j...@acquisto-us.com)<22906><fwJdXgEPQKbAqAum>: 
Debug:

Mailbox INBOX: UID 13710: Opened mail because: prefetch



Hi Joe


it looks like two different issues. The unknown user issue doesn't seem 
related to you having activated debugging, as far as I can see. Also you 
should check if that username is expected to exist or not. If the 
username does not exist, then the message is correct and you should 
investigate your client sending that request.



The permission denied is a consequence of imap running as dovecot user 
without access to that file which requires root user permission. I would 
not change the user though. Ideally a fix should be done to avoid this 
message, but I believe it is harmless, particuarly if you don't have any 
other issues.



I don't normally run debug mode, but when I have done so, I have seen 
that too.


best regards

John



Hi,  John, thanks for the reply.


I should have specified the unknown user is seen even without debug mode 
enabled.  One of the reasons I turned it on.  The other of course was to 
follow the trouble shooting steps for pigeonhole/sieve.   I am having a 
time trying to get the going.  Brain is not accepting new input as 
readily as in earlier days.



The unknown user does not seem to be affecting functioning for those 
users.  Using Thunderbird as a client seems to work just fine, other 
imap tests using those user credentials seem to work as well.  I've no 
clue at the moment.



It's a small system.  I have a few different PCs an laptop, and often 
check email from any of them.   Also use Android devices to access via 
RoundCube.



Roundcube seems not to know from Thunderbird Filters and having multiple 
PC's with TB makes filter management an issue.  Hence Pigeonhole/sieve.


_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org






















					Reply via email to