RE: Unable to find mail
Rob, We need to see your conf before answering your question. Can you give us the result of the next command? # doveconf -n From: dovecot On Behalf Of Rob Campbell Sent: Saturday, November 6, 2021 12:04 PM To: dovecot@dovecot.org Subject: Unable to find mail I just installed dovecot and it seems to be working well except I can't find where my new mail is being stored. ~ In all things, Be Intentional.
RE: mail_max_userip_connections per remote IP not working
Alessio,
> remote 1.2.3.4 {
> }
This isn't supported.
You can only set the same max connection for all userips.
protocol imap {
mail_max_userip_connections = 100
}
The conf above will act :
- 1.2.3.4's max connections will be set to 100 when using imap connection.
- 1.2.3.5's max connections will be set to 100 when using imap connection.
- and so on. Every connection to imap will have max connection limit, 100.
If you want to limit max connections only for a specific ip, you might want to
do that on your firewall.
-Original Message-
From: dovecot On Behalf Of Alessio Cecchi
Sent: Wednesday, April 14, 2021 5:39 AM
To: Dovecot Mailing List
Subject: mail_max_userip_connections per remote IP not working
Hi,
I'm tryng to set a specific mail_max_userip_connections for a remote IP
(webmail IMAP software), but it seems not working:
remote 1.2.3.4 {
protocol imap {
mail_max_userip_connections = 100
}
}
and also this isn't working
remote 1.2.3.4 {
mail_max_userip_connections = 100
}
I insert it at the end of 20-imap.conf file.
Is something wrong or is not supported?
I'm running dovecot 2.3.14.
Thanks
--
Alessio Cecchi
Postmaster @http://www.qboxmail.it
https://www.linkedin.com/in/alessice
RE: Logfile flooding with lookup failure for root user using pam
Michael, Your Dovecot's LMTP is just looking up root because mails are sent to root. If you don't want root to be looked-up, then you just have to prevent being sent to root, I guess. Are the mails sent to postmaster addressed to root in the alias file? Should check the alias on the postfix side. -Original Message- From: dovecot On Behalf Of Michael Ruiz Sent: Thursday, February 4, 2021 3:09 AM To: dovecot@dovecot.org Subject: Logfile flooding with lookup failure for root user using pam Hi all, I am getting the error where root is constantly being lookedup over imap I am guessing. I am pretty sure services like fail2ban and logwatch are setup to send from another user instead of root @ localhost so I think this may be an imap issue. I tried adding root to /etc/dovecot/deny-users , but this error still persists. I know imap as root is a big security issue and is disabled, but I cannot pinpoint how or why this is happening so often. I am using PAM and passwd for authentication and authorization. How can I prevent root user from being looked up in the first place ? Regards, Michael dovecot[606167]: lmtp(606199): Error: lmtp-server: conn unix:pid=606196,uid=73 [2]: rcpt root@: Failed to lookup user root@: Invalid settings in userdb: userdb returned 0 as uid replaced my domain name with in this example.
RE: dovecot quota-warning detection mail
Morikawa-san, Okey, then your conf should be right. Did you try the conf below which was noticed by Gedalya? auth_default_realm = example.co.jp Kouga -Original Message- From: 森川 孝司 Sent: Wednesday, October 28, 2020 4:28 PM To: 林 宏河 ; dovecot@dovecot.org Subject: RE: dovecot quota-warning detection mail kouga-san After copying and pasting, something went wrong. Actually "quota_warning = storage=95%% quota-warning 95 %u" It is set in. (In fact, I usually receive a notification email.) Thank you. -Original Message- From: dovecot [mailto:dovecot-boun...@dovecot.org] On Behalf Of Koga Hayashi Sent: Wednesday, October 28, 2020 1:58 PM To: 森川 孝司 ; dovecot@dovecot.org Subject: RE: dovecot quota-warning detection mail Morikawa-san, Your conf is wrong. Should be: quota_warning = storage = 95 %% quota-warning 95 %u Your conf: quota_warning = storage = 95 %% quota-warning 95% u There's a space between % and u. First of all, try the above and let us know if it changes. Kouga
RE: dovecot quota-warning detection mail
Morikawa, What do you mean by "logged-in user"? %u stands for the username. If, for an example, user "morikawa" exists in your dovecot server (I mean as local user), your quota warning configuration should be fine. But if user "morikawa" does not exist in your server, and, dovecot can't resolve the username to the mail address, then the quota warning mail be rejected because dovecot can't find the "username" in local recipient table. A little more information about your server environment will be appreciated. Kouga -Original Message- From: dovecot On Behalf Of 森川 孝司 Sent: Wednesday, October 28, 2020 10:17 AM To: dovecot@dovecot.org Subject: dovecot quota-warning detection mail Hi, all. we use quota-warning emails to notify you of quotas. In rare cases, the email address has changed to the logged-in user. (Because the address of %u is passed as the logged-in user.) So I couldn’t send the email with “Recipient address rejected: User unknown in local recipient table”. Why does my email address change to a logged-in user? %u of "quota_warning = storage = 95 %% quota-warning 95% u" The output is the logged-in user. By Morikawa
RE: dovecot quota-warning detection mail
Morikawa-san,
Your conf is wrong.
Should be:
quota_warning = storage = 95 %% quota-warning 95 %u
Your conf:
quota_warning = storage = 95 %% quota-warning 95% u
There's a space between % and u.
First of all, try the above and let us know if it changes.
Kouga
-Original Message-
From: 森川 孝司
Sent: Wednesday, October 28, 2020 1:20 PM
To: 林 宏河 ; dovecot@dovecot.org
Subject: RE: dovecot quota-warning detection mail
Hi,Kouga-san
When quota-warning works normally
I'm sending an email to "From: to =
"
When it doesn't work
An email was sent to "From: to =
"
"Recipient address rejected: User unknown in local recipient table"
It will be.
cat /etc/dovecot/conf.d/90-quota.conf
-- plugin {
quota_warning = storage = 95 %% quota-warning 95% u
quota_warning1 = storage = 90 %% quota-warning 90% u
quota_warning2 = storage = 85 %% quota-warning 85% u
quota_warning3 = storage = 80 %% quota-warning 80% u }
service quota-warning {
executable = script /usr/local/bin/quota-warning.pl
user = dovecot
unix_listener quota-warning {
user = vmail
}
}
-- -
And it is set.
Thank you.
-Original Message-
From: Koga Hayashi [mailto:haya...@progdence.co.jp]
Sent: Wednesday, October 28, 2020 12:50 PM
To: 森川 孝司 ; dovecot@dovecot.org
Subject: RE: dovecot quota-warning detection mail
Morikawa,
What do you mean by "logged-in user"?
%u stands for the username.
If, for an example, user "morikawa" exists in your dovecot server (I mean as
local user), your quota warning configuration should be fine.
But if user "morikawa" does not exist in your server, and, dovecot can't
resolve the username to the mail address, then the quota warning mail be
rejected because dovecot can't find the "username" in local recipient table.
A little more information about your server environment will be appreciated.
Kouga
-Original Message-
From: dovecot On Behalf Of 森川 孝司
Sent: Wednesday, October 28, 2020 10:17 AM
To: dovecot@dovecot.org
Subject: dovecot quota-warning detection mail
Hi, all.
we use quota-warning emails to notify you of quotas.
In rare cases, the email address has changed to the logged-in user.
(Because the address of %u is passed as the logged-in user.)
So I couldn’t send the email with “Recipient address rejected: User unknown in
local recipient table”.
Why does my email address change to a logged-in user?
%u of "quota_warning = storage = 95 %% quota-warning 95% u"
The output is the logged-in user.
By Morikawa
