- dovecot - dovecot.org

Broken pipe with own dict server. Timing issue?
by martijn.list 08 Apr '16

08 Apr '16

Hi, I have created my own dict server (proxy:[<dict path>]:<destination dict>) to access a proprietary database. The dict server basically creates a listing socket on a separate thread and then waits for incoming requests with accept(handle, NULL, 0). When a request comes in (i.e., when accept returns the accepted socket fd), the request is handed over to a handler thread (from a thread pool). The handler thread then read from the input. The issue that I have is that if the read is done too fast after the accept, Dovecot reports a broken pipe: dovecot: auth-worker(19904): Error: write(/usr/share/test-server/tmp/test-dict) failed: Broken pipe This happens for almost all processes that try to access the dict server. However If I add some sort of delay between the accept call and read (for example a sleep), everything works. No broken pipe even after testing with a large number of parallel requests for a long time. Somehow it looks like if the first read is done too fast, it takes a long time to read the data. During this time it looks like all other Dovecot processes are no longer able to connect and report the broken pipe. With the artificial delay, everything works ok and I can see that multiple incoming request are handled by multiple threads so it looks like Dovecot uses multiple auth worker processes. If however one connection hangs on the read it looks like no Dovecot proccess is able to connect Any idea what might be causing the broken pipe in relation to timing of the read? Kind regards, Martijn

2 2

Own implementation of a dict server. Is dict lookup multi threaded or single threaded?
by martijn.list 08 Apr '16

08 Apr '16

Hi, I have created my own dict server (proxy:[<dict path>]:<destination dict>) to access a proprietary database. What happens if the dict server lookup is slow? for example because the lookup process takes some time? Does Dovecot access the dict proxy from multiple threads or is this a single threaded process? Kind regards, Martijn Brinkers

2 1

ETOOMANYREFS related errors
by Luis Ugalde 07 Apr '16

07 Apr '16

Hi, I'm starting to see, on a pretty standard Debian Jessie installation, some error messages that are apparently related to the ETOOMANYREFS errno. Firstly, the mail log shows this: dovecot: pop3-login: Error: fd_send(pop3, 18) failed: Too many references: cannot splice And then the login process fails: dovecot: pop3-login: Internal login failure (pid=34388 id=1) (internal failure, 1 successful auths): user=<username>, method=PLAIN, rip=rip, lip=lip, session=<session> Is this something that Dovecot should be able to handle, or is it strictly Debian/libc/MySillyMistake related? #uname -a Linux server 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64 GNU/Linux #dovecot --version 2.2.13 #dpkg -l | grep -E 'dovecot-core|libc6|linux-image' ii dovecot-core 1:2.2.13-12~deb8u1 amd64 ii libc6:amd64 2.19-18+deb8u3 amd64 ii libc6-i386 2.19-18+deb8u3 amd64 ii linux-image-3.16.0-4-amd64 3.16.7-ckt20-1+deb8u3 amd64 Best Regards, Luis

2 3

lmtp_rcpt_check_quota = yes silently blocks mail if quota check fails
by Tom Sommer 07 Apr '16

07 Apr '16

I have a user which has a quota-check that fails with 'Internal error', if I enable lmtp_rcpt_check_quota, the mail is silently tempfailed. Actually it looks like lmtp_rcpt_check_quota=yes suppresses normal Info/Error logging, even on Director. The MTA just gets " 451 4.3.0 <xxxx(a)xxx.xxx> Temporary internal error (in reply to end of DATA command)" from the director, but nothing is logged with lmtp_rcpt_check_quota=yes, anywhere. -- Tom

1 0

doveadm sync -1 -R
by Lukas Kolbe 07 Apr '16

07 Apr '16

Hi, I’m migrating an old Zarafa-installation to a dovecot using mdbox and sis on Debian Jessie. To copy over the emails, I use doveadm backup on the new box - or more precisely: vmail# doveadm -v -o imapc_user=$user -o imapc_password=$pass -o imapc_host=$host -o imapc_features=rfc822.size -o imapc_port=993 -o mailbox_list_index=no -o imapc_ssl_verify=no backup -R -x "Public folders*" -x "Public folders/*" -u $user imapc: For each invoke of doveadm backup -R, the local (new) mailbox gets wiped and all mails are retransferred - so far, so good. I’d like to use "doveadm sync -1“ as per the manpage to keep the downtime short, however sync doesn’t like the -R option: sync: invalid option -- 'R' doveadm sync [-u <user>|-A] [-S <socket_path>] [-1fPU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g <mailbox_guid>] [-n <namespace> | -N] [-x <exclude>] [-s <state>] -d|<dest> If I understand it correctly, without -R it would mean that doveadm sync would incorporate the changes from the local dovecot-mailbox into the remote imapc:-Mailbox, which is the opposite of what I want. Dovecot version is current head as of yesterday. Is what I’m trying to do even possible with doveadm sync? Kind regards, Lukas

2 2

[help]enotify "mail to" run fine edit via managesieve 0.4.4 complied failed
by wuwei 07 Apr '16

07 Apr '16

hi all edit via vi editor to change dovecot.sieve and enotify works fine.but when I telnet 4190 port via managesieve to edit it with the same code,the managesieve said "NO "Error in MANAGESIEVE command CHECKSCRIPT: "", find many topic in wiki and maillist but not solved. need you help!thanks!!dovecot version 2.2.15,pigonhole version 0.4.4 here are more infos below: *managesieve cmds:* "IMPLEMENTATION" "Dovecot Pigeonhole" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate vacation-seconds" "NOTIFY" "mailto" "SASL" "PLAIN LOGIN" "VERSION" "1.0" OK "Dovecot ready." listscripts NO "Error in MANAGESIEVE command received by server." AUTHENTICATE "PLAIN" "AGFuZ196aGFAdG9tLmNvbQAxMTExMTE=" OK "Logged in." listscripts "blackwhitelist" "rulefilter" ACTIVE OK "Listscripts completed." getscript "rulefilter" {471} require ["reject","fileinto","imap4flags","vacation","regex","encoded-character","include","copy","enotify","variables"]; if header :matches "Subject" "*" { set "Subject" "${1}"; } if header :matches "From" "*" { set "From" "${1}"; } if header :matches "Message-ID" "*" { set "msg_id" "${1}"; } if header :matches "To" "*" { set "To" "${1}"; } if header :matches "Date" "*" { set "Date" "${1}"; } notify "mailto:wuweiwwd@tom.com"; OK "Getscript completed." checkscript {471} require ["reject","fileinto","imap4flags","vacation","regex","encoded-character","include","copy","enotify","variables"]; if header :matches "Subject" "*" { set "Subject" "${1}"; } if header :matches "From" "*" { set "From" "${1}"; } if header :matches "Message-ID" "*" { set "msg_id" "${1}"; } if header :matches "To" "*" { set "To" "${1}"; } if header :matches "Date" "*" { set "Date" "${1}"; } notify "mailto:wuweiwwd@tom.com"; *NO "Error in MANAGESIEVE command CHECKSCRIPT: "* BYE "Disconnected for inactivity" Connection closed by foreign host. *sieve code:* require ["reject","fileinto","imap4flags","vacation","regex","encoded-character","include","copy","enotify","variables"]; if header :matches "Subject" "*" { set "Subject" "${1}"; } if header :matches "From" "*" { set "From" "${1}"; } if header :matches "Message-ID" "*" { set "msg_id" "${1}"; } if header :matches "To" "*" { set "To" "${1}"; } if header :matches "Date" "*" { set "Date" "${1}"; } notify "mailto:wuweiwwd@tom.com"; *dovecot.conf ./dovecot -n* # 2.2.15: /home/mail/dovecot/etc/dovecot/dovecot.conf doveconf: Warning: service auth { client_limit=80960 } is lower than required under max. load (300000) doveconf: Warning: service anvil { client_limit=60000 } is lower than required under max. load (240003) # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.2 auth_cache_negative_ttl = 1 days auth_cache_size = 1000 k auth_cache_ttl = 1 days auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_mechanisms = plain login debug_log_path = /home/mail/dovecot/logs/dovecot.log default_client_limit = 60000 default_internal_user = vmail default_login_user = dovecotauth default_process_limit = 60000 disable_plaintext_auth = no first_valid_gid = 1007 first_valid_uid = 1007 imapc_features = rfc822.size fetch-headers imapc_host = 172.24.173.212 imapc_password = tom123VipIMAP587 imapc_user = %u info_log_path = /home/mail/dovecot/logs/dovecot.log log_path = /home/mail/dovecot/logs/dovecot.log mail_debug = yes mail_fsync = never mail_plugins = fts fts_lucene mail_log notify quota zlib mail_prefetch_count = 20 maildir_very_dirty_syncs = yes 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 ihave duplicate vacation-seconds namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox "Junk E-mail" { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = . } passdb { args = /home/mail/dovecot/etc/dovecot/passwd.masterusers driver = passwd-file master = yes } passdb { args = /home/mail/dovecot/bin/CheckPassword driver = checkpassword } plugin { fts = lucene fts_lucene = whitespace_chars=@. mail_debug = yes mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename append mail_log_fields = uid box msgid size quota = dict:%u::redis:host=127.0.0.1:prefix=user_quota/ quota_rule2 = Trash:storage=+80%% quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = storage=70%% quota-warning 70 %u quota_warning4 = storage=60%% quota-warning 60 %u sieve = ~/sieve/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +vacation-seconds sieve_max_redirects = 10 sieve_redirect_envelope_from = orig_recipient sieve_vacation_default_period = 0 sieve_vacation_max_period = 0 sieve_vacation_min_period = 0 welcome_letter_path = /home/mail/dovecot/etc/welcome welcome_letter_url = http://202.108.252.162:8080/domainmail zlib_save = gz zlib_save_level = 6 } pop3_fast_size_lookups = yes pop3_no_flag_updates = yes postmaster_address = postmastar@%d protocols = imap pop3 sieve lmtp service auth-worker { user = dovecotauth } service auth { client_limit = 80960 unix_listener /home/mail/postfix/var/spool/postfix/private/auth-client { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 143 } service_count = 0 vsz_limit = 256 M } service imap { executable = imap postlogin process_limit = 60240 } service lmtp { inet_listener { port = 11000 } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 0 vsz_limit = 256 M } service managesieve { process_limit = 80960 } service pop { executable = imap postlogin process_limit = 60240 } service pop3-login { inet_listener pop3 { port = 110 } service_count = 0 vsz_limit = 256 M } service postlogin { executable = script-login -d rawlog -b -t } service quota-warning { executable = script /home/mail/dovecot/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl = no submission_host = 172.24.140.52:26 userdb { driver = prefetch } userdb { args = /home/mail/dovecot/etc/dovecot/dovecot-dict-auth.conf.ext driver = dict } protocol imap { imap_logout_format = bytes=%i/%o mail_plugins = fts fts_lucene mail_log notify quota zlib imap_quota imap_zlib } protocol pop3 { pop3_logout_format = bytes=%i/%o, top=%t/%p, retr=%r/%b, del=%d/%m, size=%s } protocol lmtp { mail_plugins = fts fts_lucene mail_log notify quota zlib quota sieve } protocol sieve { mail_max_userip_connections = 1000 mail_plugins = fts fts_lucene mail_log notify quota zlib quota managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 10 managesieve_max_line_length = 65536 } -- View this message in context: http://dovecot.2317879.n4.nabble.com/help-enotify-mail-to-run-fine-edit-via… Sent from the Dovecot mailing list archive at Nabble.com.

2 2

What is dovecot.socket and do i need it?
by Hamy 07 Apr '16

07 Apr '16

Helloafter rebooting the server, i keep getting these errors in mail.err : Apr 7 06:08:09 main dovecot: master: Error: systemd listens on port 143, but it's not configured in Dovecot. Closing. Apr 7 06:08:09 main dovecot: master: Error: systemd listens on port 993, but it's not configured in Dovecot. Closing. Apr 7 06:08:09 main dovecot: master: Error: systemd listens on port 993, but it's not configured in Dovecot. Closing. And then dovecot refuses any connection. the problem is solved if i do a manual restart of dovecot.service. After some search, i found 2 different solutions, one suggesting disabling dovecot.socket completely, the other one adjusting its settings: https://sowhatisthesolution.wordpress.com/2015/04/27/upgrading-dovecot-debi… I also found an old thread in the mailing list that might be relevant: http://dovecot.org/list/dovecot/2012-March/134376.html The errors indeed seem to go away if i disable dovecot.socket . I would be grateful is someone could help me understand the role of dovecot.socket , and why that error happens and what is the right way to solve it? PS: I am using Ubuntu server 15.10 and dovecot package v2.2.18 Best Regards,

1 0

RE: State for dsync not working
by Simon Pierre Desrosiers 07 Apr '16

07 Apr '16

No one will answer, so I will provide my own answer for posterity. The -s flag does not accept a file, but a string. So a correct for loop would be the following : for user in $userlist ; do state=$(cat "/Users/_dovecot/.bin/syncStates/syncstate$user" ) doveadm sync -u $user -s $state tcp:xxx.xxx.xxx.xxx > "/Users/_dovecot/.bin/syncStates/syncstate$user" done Hope it helps someone. > > ------------------------------ > > Message: 3 > Date: Fri, 25 Mar 2016 19:26:11 -0400 > From: Simon Pierre Desrosiers <simonpie(a)cs.mcgill.ca> > To: dovecot(a)dovecot.org > Subject: State for dsync not working. > Message-ID: <CAF2F45A-3F6A-4540-8C32-6551C6F27F7C(a)cs.mcgill.ca> > Content-Type: text/plain; charset=us-ascii > > Hello, > > Since replication does not seem to work on Mac OSX, I will run doveadm sync by hand every few minutes. > > In order to improve efficiency, I would like to use state. I have tried a few ways, but I always get the following error > doveadm(user): Error: Saved sync state is invalid, falling back to full sync: Invalid base64 data > KBtMOd0181bQ/wAAoQsxE90181YBAAAAAQAAAAAAAAAAAAAAAAAAABtI+mg= > > > Here is the code I use to sync : > for user in $userlist ; do > doveadm sync -u $user -s "/Users/_dovecot/.bin/syncStates/syncstate$user" tcp:xxx.xxx.xxx.xxx > "/Users/_dovecot/.bin/syncStates/syncstate$user" > done > > Any idea on how I can correct the encoding error ? > > Thank you > > ------------------------------ > > Message: 4 > Date: Sat, 26 Mar 2016 13:30:03 +1000 > From: Noel Butler <noel.butler(a)ausics.net> > To: dovecot(a)dovecot.org > Subject: Re: NetApp NFS vs. ZFS and NFS for Maildir > Message-ID: <79e7f44d74014b5c83d370d74e02205b(a)ausics.net> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > It seems its troll time again on this list, ohh maybe its Harry in > disguise... So I will play along, for today anyway :) > > > On 19/03/2016 18:11, Stephan von Krawczynski wrote: >> On Sat, 19 Mar 2016 17:37:04 +1000 >> Noel Butler <noel.butler(a)ausics.net> wrote: >> >>> On 14/03/2016 18:49, Stephan von Krawczynski wrote: >>>> >>>>> >>>>> and you've never seen these cause problems with FS? then you must be >>>>> a >>>>> newbie, in over 25 years I've seen it happen several times - yes even >>>>> after an apparent controlled shutdown. >>>> >>>> Maybe you're doing something wrong then. because in my last 21 years >>>> working >>>> exactly in this business I've not seen a single deadly fs-crash because >>>> of a >>>> power-outage. Not one. And we had of course several, all backed by UPS. >>> >>> Consider yourself lucky, Most network admins whove been around large >>> busy ISP DC's have seen this in their lifetime, to not have seen one >>> is >>> rare, go buy yourself a lotto ticket :) >>> >>>> >>>> If your servers get drowned with water during a fire your fs is >>>> probably the >>>> least of your worries. You don't really plan to re-enable servers with >>>> water- or fire-damage, do you? That's probably why there shouldn't be a >>>> fireman pouring water in the first place. >>> >>> This shows you dont understand structural engineering, the fire does >>> not >>> have to be on your floor, it can be far away as two or so levels >>> above, >>> with the high pressure water used - equating to a shitload of water, >>> there are ducts, shafts, other risers and so on that with a shit-tone >>> of >>> water can easily penetrate fireblocks of floors below - dont take my >>> work, go ask a fireman, or maybe watch the nightly news sometime >>> (building fire - many levels water affected blah blah blah)... so >>> keeping those boxes on via UPS's is asking for lots of charcoaled >>> boards >>> and fried drives. IOW, total stupidity. >>> >>> Should those machines be depowered as required by our building codes, >>> well, might take a few days of drying out but at least they will power >>> back up without error - yes, done it in risk assessments. >> > >> Obviously you must work for people that have not the slightest idea >> about >> using hardware in a correct way and don't know when the time has come >> to throw > >> it away. Man, there is no way to let a drowned box survive. It is not >> back to > > Wow, how long did you allege to have been in network/sys admin? 20 > years? Really? I think you made a typo and and it should have read 20 > minutes, ya know I have refrained from posting no here for a long time > (apart from fact I rarely read the list), and I was not going to feed > the trolls, but sometimes the smart mouthed know nothing, need to bitch > slap upside the head so thats why I am devoting about 60 seconds to you. > > Of course there is, networks dont throw away many hundreds of servers > valued $7K to $10K, nor $100K+ storage systems, or $40K routers, LB's or > switches, just because they got drenched - with power isolated. > > >> normal when it is dry. If you don't get that I am pretty happy to be no >> customer. This can only be an idea born in the sick mind of a >> controller who > > You will never be a customer _or_employee_ of mine, trust me on that > one! > >> didn't want to pay insurance in the first place. We are talking about >> serious > > Got nothing to with insurance, it might take 2 days to dry out and get > back up and running, it will take an awful lot longer to get offsite > backups and restore every last one of them. > > I hope your employer reads this list, because he/she should be seeing > alarm bells from your comments. > >> corrosion effects here let alone that you have a hard time even >> knowning when > > yep, you sure did fail basic engineering > >> your boxes are really dry. Your fireman on the other hand seem to be >> stuck in >> the 80ths. Today there are solar panels almost everywhere _which you >> cannot >> turn off_. > > Wow, you really are clutching the fantasy straws arnt you, perhaps your > country lacks modernisation, I can go to the side of my house and > isolate the panels with a flick of a switch, strangely enough and I > guess in your eyes horrifyingly called "solar isolator" that stops the > panels providing power to my electrical circuits, yes, there might be > power from panels to it, but thats not going to affect my power circuits > or equipment > > > > -- > If you have the urge to reply to all rather than reply to list, you best > first read http://members.ausics.net/qwerty/ > > > ------------------------------ > > Message: 5 > Date: Sat, 26 Mar 2016 13:34:34 +1000 > From: Noel Butler <noel.butler(a)ausics.net> > To: dovecot(a)dovecot.org > Subject: Re: Email hosting provider > Message-ID: <2b1abc9c94e3f1322753d7547cb991e4(a)ausics.net> > Content-Type: text/plain; charset=UTF-8; format=flowed > > On 21/03/2016 17:06, Andre Rodier wrote: >> Hello, >> >> Sorry if I am off topic a little. >> >> I am looking for an email host provider that supports dovecot, sieve >> and manage sieve. Ideally with the roundcube webmail and managesieve >> plugin >> >> Better if it is in Europe or switzerland. I don't mind paying a little. >> >> Thanks, >> Andr?. > > Hi Andre, > > see www.webhostingtalk.com > > There are a number of reliable and reasonable priced hosts in Germany > (best place if you value your privacy) and Netherlands. > > > -- > If you have the urge to reply to all rather than reply to list, you best > first read http://members.ausics.net/qwerty/ > > > ------------------------------ > > Message: 6 > Date: Sat, 26 Mar 2016 10:52:33 +0530 > From: Joy <pj.netfilter(a)gmail.com> > To: Joseph Tam <jtam.home(a)gmail.com> > Cc: Dovecot Mailing List <dovecot(a)dovecot.org> > Subject: Re: IMAP Idle > Message-ID: > <CALM64LbXF_Nw+7STyxHMnjLNujEcTsc5mEXMA8DXaZuNX4pvpA(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > I am ok if connection is closed automatically after 30 min if client is not > responding but connection is not being closed even after 2 days. > > > On Sat, Mar 26, 2016 at 2:52 AM, Joseph Tam <jtam.home(a)gmail.com> wrote: > >> Joy <pj.netfilter(a)gmail.com> wrote: >> >> We have implement imap idle in web mail built by us to have >>> push mail feature. IMAP idle working perfectly with browser notification >>> and we are happy with it but having one issue with users who close the >>> browser directly and never logout in that case there are number of idle >>> connection which are not in use and users are unable to login once IP wise >>> connection limit is reached. >>> >>> Dovecot is not closing connection which are not in use, is there any >>> setting available which can help me to resolve this issue. >>> >> >> I had much the same situation where a user signed up with a roaming >> wireless carrier that assigned a new IP to the client whenever it got >> passed from one access point to another. Good fun when this person >> took a bus ride through the city, leaving orphaned connections in >> its wake. >> >> The IDLE disconnection timeout is hardwired in the Dovecot code >> >> http://wiki.dovecot.org/Timeouts >> >> It's set to the RFC minimum of 30min. You'll have to recompile Dovecot >> to lower this to a non-RFC compliant value. I'm not sure how this this >> will affect clients, but 30min seems to be overly generous. >> >> Joseph Tam <jtam.home(a)gmail.com> >> > > > ------------------------------ > > Message: 7 > Date: Sat, 26 Mar 2016 08:04:33 +0100 > From: Stephan von Krawczynski <skraw(a)ithnet.com> > To: dovecot(a)dovecot.org > Subject: Re: Email hosting provider > Message-ID: <20160326080433.07fcf216.skraw(a)ithnet.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Sat, 26 Mar 2016 13:34:34 +1000 > Noel Butler <noel.butler(a)ausics.net> wrote: > >> On 21/03/2016 17:06, Andre Rodier wrote: >>> Hello, >>> >>> Sorry if I am off topic a little. >>> >>> I am looking for an email host provider that supports dovecot, sieve >>> and manage sieve. Ideally with the roundcube webmail and managesieve >>> plugin >>> >>> Better if it is in Europe or switzerland. I don't mind paying a little. >>> >>> Thanks, >>> Andr?. >> >> Hi Andre, >> >> see www.webhostingtalk.com >> >> There are a number of reliable and reasonable priced hosts in Germany >> (best place if you value your privacy) and Netherlands. > > You mean "best place if you have no idea of the german laws and whats really > going on" ... > > -- > Regards, > Stephan > > > ------------------------------ > > Message: 8 > Date: Sat, 26 Mar 2016 10:48:47 +0000 > From: michael crane <mick.crane(a)gmail.com> > To: dovecot(a)dovecot.org > Subject: mailbox prefix > Message-ID: > <CACJbxCQ5by9eXKtAMfJ7aa1C2hCkmph=LbyUqn2yv6w=0hVseQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > dovecot version 2.2.13 > > hello, > I try to make a new server just for me after having old one working for > ages with Dovecot, Fetchmail, Squirrelmail, Procmail > making new one with above plus Postfix using Maildir structure. > I am having a bit of trouble understanding exactly what the namespace and > prefix are. > Is the "private/" prefix an internal thing with Dovecot ? Or is it supposed > to be a real directory ? > I'm not quite sure how to properly address the INBOX in Procmail, > Squirrelmail, Postfix config. > > > for example am I supposed to say inbox is ".private/.INBOX" > > > > cheers > > zemlik > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > dovecot mailing list > dovecot(a)dovecot.org > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > > ------------------------------ > > End of dovecot Digest, Vol 155, Issue 45 > ****************************************

1 0

"Lost" e-mail after alternate partition offline
by Daniel van Ham Colchete 07 Apr '16

07 Apr '16

Hey guys! I've got a problem here and I wish you could help me. A drive failed here and went offline for some time. This was a alternate storage drive so it took a while (hours) for us to notice. There was a problem with DRBD also, so it didn't move to the redundancy, it just went offline. I was able to recover all the files there, but a few of my users still don't see their old e-mails, the ones that are supposed to be on the alternate storage. >From what I could troubleshoot here file are there, vmail user can access them, so it's not a permission issue, but a doveadm dump on the index file of each mail folder, won't show the e-mail at the alternate storage drive. So, they are there (at the filesystem), but they aren't (from a imap client). Is there a way to rebuild the dovecot.index file, re-adding everything back to each folder? Best, Daniel Colchete

2 1

namespace...mailbox doesn't exist
by Eric 06 Apr '16

06 Apr '16

Hello list, I have a namespace called 'projects' which when clicked in Thunderbird (nonexistent in eM Client) yields the following error: "The current operation on 'projects' did not succeed. The mail server for account user(a)domain.tld responded: mailbox doesn't exist: projects.projects (0.00 + 0.00 secs)." The namespace is configure as follows: # Shared namespace 'projects' namespace { location = maildir:/home/vpopmail/domains/domain.tld/shared/projects prefix = projects. separator = . type = public } This is the log: 1: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: Effective uid=89, gid=89, home=/home/vpopmail/domains/domain.tld/postmaster 2: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: Quota root: name=ignore=Trash backend=maildir args= 3: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: Quota rule: root=ignore=Trash mailbox=? bytes=0 messages=0 4: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: Quota grace: root=ignore=Trash bytes=0 (10%) 5: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: Namespace : type=private, prefix=, sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location= 6: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: mdbox: access(/home/vpopmail/domains/domain.tld/postmaster/mdbox, rwx): failed: No such file or directory 7: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: mdbox: couldn't find root dir 8: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: sdbox: access(/home/vpopmail/domains/domain.tld/postmaster/sdbox, rwx): failed: No such file or directory 9: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: sdbox: couldn't find root dir 10: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: maildir: root exists (/home/vpopmail/domains/domain.tld/postmaster/Maildir) 11: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: maildir++: root=/home/vpopmail/domains/domain.tld/postmaster/Maildir, index=, indexpvt=, control=, inbox=/home/vpopmail/domains/domain.tld/postmaster/Maildir, alt= 12: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: Namespace : type=public, prefix=projects., sep=., inbox=no, hidden=no, list=yes, subscriptions=yes location=maildir:/home/vpopmail/domains/domain.tld/shared/projects 13: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: maildir++: root=/home/vpopmail/domains/domain.tld/shared/projects, index=, indexpvt=, control=, inbox=, alt= This did not happen with other versions of dovecot (I think) but just started happening with the upgrade. While it is not a serious problem and I can live with it, what would be causing it in the new dovecot iteration (2.2.23) ? And, could it be that I'm missing the necessary setting to mitigate this? Please let me know if any additional information is necessary. I'm thinking that the problem lies in lines 6/7 and 8/9 where Dovecot is looking for mdbox/sdbox. Eric

3 5