- dovecot - dovecot.org

Re: Can't Empty Inbox that is Over quota
by Jason Hirsh 06 Jun '24

06 Jun '24

> On Jun 6, 2024, at 11:00 AM, Jason Hirsh <kasdivi(a)mac.com> wrote: > > > >> On Jun 6, 2024, at 3:10 AM, Aki Tuomi <aki.tuomi(a)open-xchange.com> wrote: >> >>> >>> On 06/06/2024 04:11 EEST Jason Hirsh via dovecot <dovecot(a)dovecot.org> wrote: >>> >>> >>>> Begin forwarded message: >>>> >>>> From: Jason Hirsh <kasdivi(a)mac.com> >>>> Subject: Can't Empty Inbox that is Over quota >>>> Date: June 3, 2024 at 8:15:53 PM EDT >>>> To: dovecot(a)dovecot.org >>>> >>>> I have been trying to update my Postix/Dovecot/MySQL?Postfixadmin installation >>>> >>>> >>>> I am currently on Dovecot. 2.3.2.1 >>>> >>>> I used the guide set forth in Purplehat.org <http://purplehat.org/> which is what got me in trouble as I am in between with setup. (He went off to Maria-db and NGINX I stayed with Apache and MySQL >>>> >>>> >>>> What has happened is may Dovecot Mailboxes are super super saturated. adI inadvertently allowed email from an alarm >>>> >>>> Quota name Type Value Limit % >>>> User quota STORAGE 239754 5120 4682 >>>> User quota MESSAGE 882 - >>>> >>>> >>>> I tried to empty with the command >>>> >>>> sudo doveadm expunge -A mailbox INBOX ALL >>>> >>>> >>>> I get this error >>>> >>>> Error: auth-master: userdb list: User listing returned failure >>>> doveadm: Error: Failed to iterate through some users. >>>> >>> >>> >>> Is there anyway I can remove Dovecot from my server and reinstalll it? It is so messed up I don’t care about losing data >>> >>> >>> >> >> um.. you have multiple issues. >> >> First of all, try >> > > > >> sudo doveadm expunge -u targetuser mailbox INBOX ALL >> > > > Ok I tried that ,,say its ran but postfixadmn shows the mailbox WAY quote and new message to tha user are being rejected > > "Your message to <jason(a)kasdivi.com <mailto:jason@kasdivi.com>> was automatically rejected: > Storage quota for this account has been exceeded, please try again later.Reporting-MTA: dns; triggerfish.theoceanwindow.com <http://triggerfish.theoceanwindow.com/> > Final-Recipient: rfc822; jason(a)kasdivi.com <mailto:jason@kasdivi.com> > Action: failed > Status: 5.2.2” > > So on to > > >> rf /path/to/user/home > > > It all went away. By mail doesn’t not work. Postfixadmin still shows sett is over limited. I try deleting and get a > > Problems running mailbox postdeletion script! > The mailbox postdeletion script failed, check the error log for details! > > >> -A means all users, and it only works if your userdb iteration works. >> >> If you truly do not care about user data and want just get rid of it, >> you can just rm -rf /path/to/user/home >> >> Aki

1 0

Re: Log detective help
by Michael Slusarz 06 Jun '24

06 Jun '24

> On 06/05/2024 1:22 PM MDT GDS via dovecot <dovecot(a)dovecot.org> wrote: > > Hello all, I am seeing hundreds of lines like the one below in my mail.log from this specific IP address, which belongs to Google. Is there a way to determine why this "deferred (delivery temporarily suspended)" is happening? > > Jun 5 19:09:32 arthemis postfix/error[86771]: 5D9D148296D: to=<root(a)localhost.com>, orig_to=<root@localhost>, relay=none, delay=4099, delays=4099/0.02/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to localhost.com[74.125.224.72]:25: Connection timed out) "localhost.com" - you almost certainly are intending to connect to localhost (i.e. the local loopback address, 127.0.0.1) rather than the remote domain localhost.com. So it looks like a configuration error. michael

2 1

Fwd: EXPUNGED Folder Always Visible
by Pete Long 06 Jun '24

06 Jun '24

Sorry, forgot to change the To: field :/ Pete. > Begin forwarded message: > > From: Pete Long <pete(a)valar.uk.net> > Subject: Re: EXPUNGED Folder Always Visible > Date: 6 June 2024 at 09:43:50 BST > To: Robert L Mathews <lists(a)tigertech.com> > > > >> On 5 Jun 2024, at 19:18, Robert L Mathews via dovecot <dovecot(a)dovecot.org> wrote: >> >> On Jun 5, 2024, at 12:21 AM, Pete Long via dovecot <dovecot(a)dovecot.org> wrote: >> >>> After a restart of Dovecot, I see this in the logs: >>> >>> Jun 05 08:12:07 imap(pete)<19761><KPYfSB8aj4dWH1ne>: Error: Mailbox Deleted Messages: Lazy-expunge transaction failed: Mailbox Deleted Messages: UID=1 >>> 67: lazy_expunge: Couldn't open expunge mailbox: Failed to open mailbox .EXPUNGED: Invalid mailbox name: Begins with hierarchy separator >> >> Hmmm, I'm not sure about that -- in my setup I have something different, with no actual mailbox for it: >> >> namespace { >> hidden = yes >> inbox = no >> list = no >> location = maildir:~/expunged >> prefix = .EXPUNGED/ >> separator = . >> type = private >> } >> plugin { >> lazy_expunge = .EXPUNGED/ >> lazy_expunge_only_last_instance = yes >> ... >> >> Perhaps someone else who has a similar setup to you with it as a mailbox can offer more advice, sorry! >> > > Not to worry Robert, you've given me some useful information. > > I have a workaround now which 'works for me' (TM). The gist is to copy an acl file to the .EXPUNGED mailbox when it is created, which is usually when a mail is sent, moved or deleted. I am not using global acls so note the commented line in the next paragraph. > > In /etc/dovecot/conf.d/50-expunge.conf: > > namespace inbox { > mailbox EXPUNGED { > autoexpunge = 7days > autoexpunge_max_mails = 100000 > } > } > > > mail_plugins = $mail_plugins lazy_expunge acl > plugin { > # Move messages to an .EXPUNGED mailbox > lazy_expunge = EXPUNGED > > # Define ACL so that user cannot list the .EXPUNGED mailbox > #acl = vfile:/etc/dovecot/global-acls/expunged-acl > > # Expunged messages most likely don't want to be included in quota: > quota_rule = EXPUNGED:ignore > } > > > Once the ~/Maildir/.EXPUNGED directory is created, I copy this 'dovecot-acl' file in to that .EXPUNGED directory: > > owner wstipeka > > Note that there is no l,r or x. https://doc.dovecot.org/configuration_manual/acl/#acl > > > The end result is that the .EXPUNGED mailbox contains deleted and moved mail items but the user cannot see this mailbox and cannot delete it anyway. > > If necessary I can fire up Mutt and traverse to the relevant users .EXPUNGED folder to rescue deleted items. If they also happen to have FTP and/or SSH access, I can make the dovecot-acl immutable if necessary. > > Thanks again Robert for giving me some more options. > > > All the best, > > Pete. >

1 0

Can't Empty Inbox that is Over quota
by Jason Hirsh 06 Jun '24

06 Jun '24

I have been trying to update my Postix/Dovecot/MySQL?Postfixadmin installation I am currently on Dovecot. 2.3.2.1 I used the guide set forth in Purplehat.org <http://purplehat.org/> which is what got me in trouble as I am in between with setup. (He went off to Maria-db and NGINX I stayed with Apache and MySQL What has happened is may Dovecot Mailboxes are super super saturated. adI inadvertently allowed email from an alarm Quota name Type Value Limit % User quota STORAGE 239754 5120 4682 User quota MESSAGE 882 - I tried to empty with the command sudo doveadm expunge -A mailbox INBOX ALL I get this error Error: auth-master: userdb list: User listing returned failure doveadm: Error: Failed to iterate through some users. My dovecot configurations is # 2.3.21 (47349e2482): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21 (f6cd4b8e) # OS: FreeBSD 13.2-RELEASE-p4 amd64 ufs # Hostname: triggerfish.theoceanwindow.com dict { quota = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_gid = 110 first_valid_uid = 110 hostname = triggerfish.theoceanwindow.com last_valid_gid = 110 last_valid_uid = 110 lmtp_rcpt_check_quota = yes mail_location = maildir:/usr/local/virtual/%d/%n mail_plugins = quota managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { expire = Trash imapsieve_mailbox1_before = file:/usr/local/virtual/sieve/rspamd/rspamd-learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/usr/local/virtual/sieve/rspamd/rspamd-learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * imapsieve_mailbox3_before = file:/usr/local/virtual/sieve/global/read.sieve imapsieve_mailbox3_causes = COPY imapsieve_mailbox3_name = Trash mail_home = /usr/local/virtual/%d/%n mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = dict:User quota::proxy::quota quota_exceeded_message = Storage quota for this account has been exceeded, please try again later. quota_grace = 10%% quota_max_mail_size = 100M quota_rule = *:storage=1G quota_rule2 = Trash:storage=+30%% quota_rule3 = Sent:storage=+30%% quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning4 = -storage=100%% quota-warning -100 %u sieve = /usr/local/virtual/%d/%n/.dovecot.sieve sieve_before = /usr/local/virtual/sieve/global/default.sieve sieve_dir = /usr/local/virtual/%d/%n/sieve sieve_global = /usr/local/virtual/sieve/global/ sieve_global_dir = /usr/local/virtual/sieve/global/ sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/local/virtual/sieve/rspamd sieve_plugins = sieve_imapsieve sieve_extprograms } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh postmaster_address = admin(a)theoceanwindow.com protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = mail mode = 0666 user = postfix } unix_listener auth-userdb { group = mail mode = 0666 user = vmail } } service dict { unix_listener dict { group = vscan mode = 0660 user = vscan } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service quota-warning { executable = script /usr/local/virtual/bin/quota-warning.sh unix_listener quota-warning { user = vscan } user = dovecot } ssl_ca = </usr/local/etc/ssl/openssl/theoceanwindow.com/ca_bundle.crt ssl_cert = </usr/local/etc/ssl/openssl/theoceanwindow.com/certificate.crt ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota quota sieve zlib } protocol imap { mail_plugins = quota quota imap_quota zlib } protocol pop3 { mail_plugins = quota } jason@triggerfish:/usr/local/etc/apache24/extra: Sorry about the colors. I am at whit ends with the system and dont have the energy to take on apple mail formating I imagine I have messed up a Mysql query? Thanks for bearing with me

2 2

Log detective help
by GDS 06 Jun '24

06 Jun '24

Hello all, I am seeing hundreds of lines like the one below in my mail.log from this specific IP address, which belongs to Google. Is there a way to determine why this "deferred (delivery temporarily suspended)" is happening? Jun 5 19:09:32 arthemis postfix/error[86771]: 5D9D148296D: to=<root(a)localhost.com>, orig_to=<root@localhost>, relay=none, delay=4099, delays=4099/0.02/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to localhost.com[74.125.224.72]:25: Connection timed out) Thank you,Greg

2 1

EXPUNGED Folder Always Visible
by Pete Long 05 Jun '24

05 Jun '24

Hi all, I'm having a bit of a time trying to get the EXPUNGED mailbox to not display when any mail is moved or deleted. Here's what I'm running: Operating System = Debian 11.9 Dovecot = 2.3.13 MUA = Mac OS X Mail 16.0 $3774.600.62$ Here is the information I think is relevant: # cat /etc/dovecot/conf.d/50-expunge.conf namespace INBOX { mailbox EXPUNGED { autoexpunge = 7days autoexpunge_max_mails = 10000 } } mail_plugins = $mail_plugins lazy_expunge acl plugin { lazy_expunge = EXPUNGED quota_rule = EXPUNGED:ignore } # cat /etc/dovecot/conf.d/90-acl.conf [...] plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 } [...] # cat /etc/dovecot/global-acls/expunged.acl EXPUNGED user=masteruser lr I have also tried setting 'expunged.acl' to the following, with no ACL flags: EXPUNGED owner This version doesn't seem to do anything different but that's probably down to me. No matter what I do with this current configuration, I cannot get the EXPUNGED folder to stop showing after any deletion or move. This point aside, Dovecot's doing almost exactly what I want: all mail moved or deleted ends up in EXPUNGED; I just don't want to see it, nor anyone else with an account on my server ;) Thanks for your time and any information you can provide. Pete.

2 3

Debug: open(/proc/self/io) failed: Permission denied
by se＠maildaddy.eu 01 Jun '24

01 Jun '24

Tried all kinds of user setup, and read what I found on different foras, but still get: "Debug: open(/proc/self/io) failed: Permission denied" Is anyone able to spot the misconfig? Thanks in advance! This is my dovecot -n: # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.70-050470-generic x86_64 Ubuntu 20.04.6 LTS # Hostname: host auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_username_format = %Ln mail_location = maildir:~/Maildir mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Drafts { auto = create special_use = \Drafts } mailbox Junk { auto = create special_use = \Junk } mailbox Sent { auto = create special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = create special_use = \Trash } prefix = } passdb { driver = pam } protocols = imap pop3 lmtp imap lmtp pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/letsencrypt/live/mail.spijoing.com/fullchain.pem ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { driver = passwd }

2 2

problem setting sieve_vacation_send_from_recipient = yes
by schuerbel＠vodafonemail.de 01 Jun '24

01 Jun '24

Hello, dovecot sieve sends vacation replies with an empty FROM: field by default. Sadly my provider rejects such emails. I tried to change this behavior by adding sieve_vacation_send_from_recipient = yes to the plugin section in dovecot.conf. But still vacation replies are send with empty FROM: fields. Is there any further setting i have to change ? My Version is dovecot 2.3.16 (7e2e900c1a) on Ubuntu 22.04 . Here is my setting from dovecot -n : log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:~/Maildir mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_vacation_send_from_recipient = yes } protocols = imap sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } user = root } ssl_cert = </etc/ssl/localcerts/servercert_pub.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_key = # hidden, use -P to show it userdb { driver = passwd } userdb { driver = passwd } verbose_ssl = yes protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = torben(a)garfield.no-work.to quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } regards TS

1 0

sasl database
by Jeff P 01 Jun '24

01 Jun '24

Hello, Is there a guide for using a customized SASL database for dovecot? for example, SQLite. Thanks in advance.

3 2

Pigenohole bad commands limits and proposed minor patch
by John Fawcett 01 Jun '24

01 Jun '24

Hi I was looking into Pigeonhole behaviour in the case of managesieve receiving invalid input either before or after login. I can see that there are hard coded limits after 3 sequential bad commands prior to authentication and 20 after authentication. I was wondering if there is a reason for those values. Sieve is a protocol that is used with software and except for the limited use case of testing it is not used by people typing manually. I don't know of a lot of sieve clients. Unfortunately the one I used in Thunderbird is no longer maintained, so I only have roundcube. But do legitimate sieve clients in general make a lot of mistakes? An additional doubt about errors that I am seeing is that differently to imap and pop3 there doen't appear to be a dedicated ssl port. I only have starttls configured. I do see what look like people trying to connect with ssl directly on port 4190, which with my configuration is never going to be valid. I am attaching a very simple proposed patch to make the error limits configurable via the following settings in conf.d/20-managesieve.conf with defaults as per the existing hard coded ones: managesieve_max_command_errors = 20 managesieve_login_max_command_errors = 3 I have similar doubts about imap error limits but I'll start with sieve ones. John

1 0