- dovecot - dovecot.org

[Dovecot] more info (more dsync problems)
by Jeff Gustafson 10 Jul '12

10 Jul '12

Rerunning the dsync command right after the timeout (see previous message) gave me these errors: dsync-local(vmail): Error: remote: dsync-remote(vmail): Error: Corrupted dbox file /home/.incoming_mail_migrations/users/user%domain.com/mdbox/s torage/m.60 (around offset=807789): msg header has bad magic value dsync-local(vmail): Error: remote: dsync-remote(vmail): Error: Corrupted dbox file /home/.incoming_mail_migrations/users/user%domain.com/mdbox/s torage/m.60 (around offset=807789): msg header has bad magic value dsync-local(vmail): Error: remote: dsync-remote(vmail): Warning: mdbox /home/.incoming_mail_migrations/users/user% domain.com/mdbox/storage: Inconsistency in map index (2,75904 != 2,82524) dsync-remote(vmail): Warning: mdbox /home/.incoming_mail_migrations/users/user% domain.com/mdbox/storage: rebuilding indexes dsync-local(vmail): Error: remote: dsync-remote(vmail): Error: Corrupted dbox file /home/.incoming_mail_migrations/users/user% domain.com/mdbox/storage/m.60 (around offset=807789): msg header has bad magic value dsync-local(vmail): Error: remote: dsync-remote(vmail): Warning: dbox: Copy of the broken file saved to /home/.incoming_mail_migrations/users/user% domain.com/mdbox/storage/m.60.broken dsync-local(vmail): Error: remote: dsync-remote(vmail): Error: Corrupted dbox file /home/.incoming_mail_migrations/users/user% domain.com/mdbox/storage/m.60 (around offset=807789): EOF reading msg header (got 0/30 bytes) dsync-local(vmail): Error: remote: dsync-remote(vmail): Warning: mdbox /home/.incoming_mail_migrations/users/user% domain.com/mdbox/storage: rebuilding indexes dsync-local(vmail): Error: remote: dsync-remote(vmail): Error: mdbox /home/.incoming_mail_migrations/users/user% domain.com/mdbox/storage: Duplicate GUID 1341304555.M433317P26661.n13,S=142447,W=144391 in m.62:790375 and m.60:790375

1 0

[Dovecot] more dsync problems: Error: proxy client timed out
by Jeff Gustafson 10 Jul '12

10 Jul '12

Hi all, I'm using dsync for backups. I recently upgraded to 2.1.7 due to issues with dsync mirror/backups. 2.1.7 fixed the issue with the guid conflict, but now I'm seeing this error on a couple of mailboxes: Error: proxy client timed out (waiting for output stream to flush, 0 bytes left) If there are 0 bytes left, why is it trying to flush? I'm using this command to backup the mailbox: dsync -vo mail_home=/home/users/user%domain.com backup ssh vmail(a)10.1.2.2 dsync -o mail_home=/home/.incoming_mail_migrations/users/user%adomain.com Any ideas? ...Jeff

1 0

Re: [Dovecot] Howto add another disk storage
by Stan Hoeppner 10 Jul '12

10 Jul '12

On 7/8/2012 5:16 PM, Matthias-Christian Ott wrote: > On 2012-07-08 23:29, Stan Hoeppner wrote: >> On 7/8/2012 8:27 AM, Patrick Domack wrote: >>> >>> Quoting Wojciech Puchar <wojtek(a)wojtek.tensor.gdynia.pl>: >>> >>>>> I think there are optimal situations where any configuration looks >>>>> good . . How often can a real-world disk actually deliver the 6Gbs >>>>> when only a minority of disk reads are long sequential runs on the >>>>> platters? >>>> none of hard drives can saturate 1.5Gb/s >>> >>> There are many disks out that do 150-200MB/sec, easily exceeding 1.5gb/s >>> speeds. >> >> There are a few SAS drives that can saturate a 150MB/s link, such as the >> Seagate Cheetah 15k.7, which can sustain 204MB/s streaming read on the >> outer tracks. >> >> But, again, streaming rate is irrelevant to mail storage. What matters >> is random seek latency. And the faster the spindle, the lower the >> latency. Thus 15k Seagate SAS drives are excellent candidates for mail >> store duty, as are any 10k or 15k drives. > > This is simply not true. SATA SSDs (~0,66 €/GB) are as expensive as the > 15k Seagate SAS HDDs (0,63 €/GB), but definitely faster. First, this sub discussion in this thread has been dealing strictly with mechanical storage, and that was intentional. Now you've injected solid state storage, and in the process you first disagreed with my statement, then agreed with it. Apparently you didn't realize you did so. Would you please clarify what I stated that is "simply not true"? You comment WRT SSD doesn't prove anything I said to be untrue. Quite the contrary, you reinforced my statements. -- Stan

11 25

[Dovecot] recover .sieve plaintext from .sievec binary file
by Florin Andrei 09 Jul '12

09 Jul '12

Hi, I upgraded a server from an old Linux distribution to a much newer one. In the process, Dovecot got upgraded from v1 to v2. By mistake, I deleted the .sieve plaintext file with all the Sieve filters, but I still do have the .sievec compiled binary. Is there any way to dump the binary file back into plaintext format? Keep in mind, I'm running v2 now, and the binary was made on a v1 Dovecot server. Thanks. -- Florin Andrei http://florin.myip.org/

3 4

[Dovecot] configuring imap_stats
by Reinhard Vicinus 09 Jul '12

09 Jul '12

Hi, i'm trying to configure imap_stats like it's documented in the wiki: http://wiki2.dovecot.org/Statistics. But as soon as i activate the imap_stats plugin i get the following error message trying to login via imap: dovecot: imap: Error: Can't load plugin imap_stats_plugin: Plugin stats must be loaded also (you must set: mail_plugins=$mail_plugins stats) But the stats plugin is configured as you can see in the attached configurations. Also i can get statistics without the imap_stats enabled, but as far as i know only of the pop3 users. Kind regards Reinhard

2 1

[Dovecot] mailboxes missing after upgrade from 2.1.4 to 2.1.7
by Micah Anderson 09 Jul '12

09 Jul '12

Hi all, I mentioned this on the #dovecot irc channel, but I thought I would post here so I can provide more details. The basic problem is that when I upgraded from 2.1.4 to 2.1.7, some users no longer are able to see their folders in pine/alpine. The folders are actually there, and are subscribed (according to doveadm) and its possible to do operations on those folders, if you know the name (for example, opening the folder works fine if you know the name). When I downgrade to 2.1.4 again, the folders appear again, so its clearly something that changed between the two versions. I looked through the changelog, and found a few possibile culprits, I think pine/alpine use imapc, so that could be related: . imapc: Use imapc_list_prefix also for listing subscriptions . Fixed looking up parent mailbox name with different namespace vs. layout separators. . imapc: Don't list mailboxes that don't match list patterns. . layout=fs: Fixed listing mailboxes with prefix=INBOX/ . LIST with mailbox {} settings incorrectly set subscribed-flags. Here is my dovecot -n output: # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.5 auth_default_realm = example.net auth_verbose = yes default_process_limit = 256 default_vsz_limit = 512 M dict { expire = mysql:/etc/dovecot/dovecot-dict-sql.conf quota = mysql:/etc/dovecot/dovecot-dict-sql.conf } disable_plaintext_auth = no first_valid_gid = 8 first_valid_uid = 8 last_valid_gid = 8 last_valid_uid = 8 listen = * login_greeting = howdy, ready. mail_location = mdbox:~/mdbox:INDEX=/srv/dovecot_indexes/%d/%1n/%n mail_plugins = expire quota zlib stats maildir_very_dirty_syncs = yes namespace { inbox = yes location = prefix = separator = . } namespace { alias_for = hidden = yes inbox = no list = no location = prefix = INBOX. separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { antispam_allow_append_to_spam = yes antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /usr/local/bin/train_spam antispam_pipe_program_args = -d;10.0.1.109 antispam_pipe_program_notspam_arg = ham antispam_pipe_program_spam_arg = spam antispam_pipe_tmpdir = /var/tmp antispam_signature = X-Spam-Flag antispam_signature_missing = error antispam_spam_pattern_ignorecase = SPAM antispam_trash_pattern = trash;Trash;Deleted * expire = Trash expire2 = Trash/* expire3 = Spam expire_dict = proxy::expire quota = dict:Your mail quota::proxy::quota quota_rule = *:bytes=100663296 quota_rule2 = Trash:bytes=+20%% quota_rule3 = Spam:bytes=+10%% quota_rule4 = INBOX.Trash:bytes=+20%% quota_rule5 = INBOX.Spam:bytes=+10%% quota_rule6 = INBOX.restored_from_backups:bytes=+500%% sieve = ~/.dovecot.sieve sieve_after = /var/lib/dovecot/sieve/after.sieve sieve_before = /var/lib/dovecot/sieve/default.sieve sieve_dir = ~/sieve stats_refresh = 30 secs stats_track_cmds = yes zlib_save = gz zlib_save_level = 6 } postmaster_address = postmaster(a)example.net protocols = " imap pop3" service anvil { unix_listener anvil { group = dovecot mode = 0660 user = root } } service auth { unix_listener auth-userdb { group = mail mode = 0600 user = mail } } service dict { unix_listener dict { group = mail mode = 0600 user = mail } } service imap-login { process_min_avail = 10 service_count = 0 vsz_limit = 512 M } service imap-postlogin { executable = script-login /usr/local/sbin/postlogin_imap } service imap { executable = imap imap-postlogin process_limit = 2048 } service pop3-login { process_min_avail = 10 service_count = 0 vsz_limit = 512 M } service pop3-postlogin { executable = script-login /usr/local/sbin/postlogin_pop } service pop3 { executable = pop3 pop3-postlogin } service stats { fifo_listener stats-mail { mode = 0600 user = mail } } ssl_cert = </etc/certs/wildcard/cert.pem ssl_cipher_list = HIGH:-ADH:-aNULL ssl_key = </etc/certs/wildcard/key.pem userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol lda { mail_plugins = expire quota zlib stats sieve plugin { quota_exceeded_message = Sorry, your message cannot be delivered to that person because their mailbox is full. If you can contact them another way, you may wish to tell them of this problem. quota_rule7 = INBOX:bytes=+10%% } } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_max_userip_connections = 20 mail_plugins = expire quota zlib stats imap_quota imap_zlib antispam imap_stats plugin { quota_exceeded_message = You are over quota. To avoid losing mail, immediately empty your Trash and Sent folders and delete emails with large attachments. Visit https://help.example.net/quota for more help. } } protocol pop3 { mail_plugins = expire quota zlib stats pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %g } As requested by tss in #dovecot, I attempted to add 'rawlog' to: service imap-postlogin { executable = script-login /usr/local/sbin/postlogin_imap } to get: service imap-postlogin { executable = script-login rawlogin /usr/local/sbin/postlogin_imap } but with that, it doesn't even open the INBOX folder, and there is nothing in the user's rawlog folder, I get this error: dovecot: imap-postlogin: Error: Fatal: This process must not be run as root it didn't open even the INBOX imap folder I went over the http://wiki2.dovecot.org/Debugging/Rawlog and made sure everything was correct there, but it still didn't work right. Any ideas or suggestions of things to try would be greatly appreciated! thanks, micah --

1 1

[Dovecot] Howto add another disk storage
by Adrian Minta 08 Jul '12

08 Jul '12

Hi all What is the best strategy to add another storage to an existing virtual mail system ? Move some domains to the new storage and create symlinks ? Switch to dovecot hashing ? But in this case what is the easy-east way to migrate ? Thanks for any suggestions or tips !

15 50

Re: [Dovecot] Dovecot 2.1.8 crashes when doing POP3 UIDL on empty INBOX
by Joseph Tam 08 Jul '12

08 Jul '12

Timo Sirainen <tss(a)iki.fi> writes: >> #0 i_panic (format=0xff2302f8 "Trying to allocate %u bytes") at failures.c:259 >> #1 0xff2068a4 in pool_alloconly_malloc (pool=0x60330, size=0) at mempool-alloconly.c:259 >> #2 0x00018248 in client_uidls_save (client=0x54d28) at pop3-commands.c:761 >> #3 0x00018444 in cmd_uidl_init (client=0x54d28, seq=0) at pop3-commands.c:793 >> #4 0x000185a8 in cmd_uidl (client=0x54d28, args=0x19eb8 "") at pop3-commands.c:824 >> #5 0x00018a24 in client_command_execute (client=0x54d28, name=0x2b550 "UIDL", args=0x19eb8 "") >> at pop3-commands.c:889 > > Fixed: http://hg.dovecot.org/dovecot-2.1/rev/ea18b2ddb67b > > Date: Sat, 7 Jul 2012 05:52:03 +0300 2 hours after I reported it; do you ever sleep?! Thanks. Joseph Tam <jtam.home(a)gmail.com>

4 3

[Dovecot] + sub addressing setup
by Voytek Eymont 07 Jul '12

07 Jul '12

I have Dovecot/Postfix/MySQL/PostfixAdmin, I'd like to setup + sub addressing (for +spam and possibly user-defined +folders) I have setup a user+spam folder path in PostfixAdmin as so; vvv+spam@tld path:tld/vvv@tld/.spam/ that requires me to put a 'duplicate' user with the + and +path for each user, the folks on PostfixAdmin suggested that Dovecot might have a better way of handling this, how do I accomplish this in Dovecot ? thanks for any suggestions or tips -- Voytek

2 6

[Dovecot] Dovecot 2.1.8 crashes when doing POP3 UIDL on empty INBOX
by Joseph Tam 06 Jul '12

06 Jul '12

I noticed a bunch of crashes when Gmail users tried to slurp up their (empty) mailboxes. The problem is not noticed by clients though, but it crashes the pop3 process. POP3 session S: +OK Ready. C: USER user S: +OK C: PASS password S: +OK Logged in. C: UIDL ... server crash and disconnects ... Resulting log Jul 06 16:58:05 pop3(user): Panic: Trying to allocate 0 bytes Jul 06 16:58:05 pop3(user): Error: Raw backtrace: 0xff1e6454 -> 0xff1e4f78 -> 0xff20689c -> 0x18240 -> 0x1843c - > 0x185a0 -> 0x18a1c -> 0x1576c -> 0x159cc -> 0xff1fee6c -> 0xff200e24 -> 0xff1fef60 -> 0xff1d8010 -> 0x13584 - > 0x1285c Jul 06 16:58:14 pop3(user): Fatal: master: service(pop3): child 24972 killed with signal 6 (core dumps disabled) GDB traceback: #0 i_panic (format=0xff2302f8 "Trying to allocate %u bytes") at failures.c:259 #1 0xff2068a4 in pool_alloconly_malloc (pool=0x60330, size=0) at mempool-alloconly.c:259 #2 0x00018248 in client_uidls_save (client=0x54d28) at pop3-commands.c:761 #3 0x00018444 in cmd_uidl_init (client=0x54d28, seq=0) at pop3-commands.c:793 #4 0x000185a8 in cmd_uidl (client=0x54d28, args=0x19eb8 "") at pop3-commands.c:824 #5 0x00018a24 in client_command_execute (client=0x54d28, name=0x2b550 "UIDL", args=0x19eb8 "") at pop3-commands.c:889 #6 0x00015774 in client_handle_input (client=0x54d28) at pop3-client.c:629 #7 0x000159d4 in client_input (client=0x54d28) at pop3-client.c:682 #8 0xff1fee74 in io_loop_call_io (io=0x37298) at ioloop.c:379 #9 0xff200e2c in io_loop_handler_run (ioloop=0x34138) at ioloop-poll.c:211 #10 0xff1fef68 in io_loop_run (ioloop=0x34138) at ioloop.c:398 #11 0xff1d8018 in master_service_run (service=0x33c88, callback=0x13120 <client_connected>) at master-service.c:543 #12 0x0001358c in main (argc=1, argv=0xffbffe0c) at main.c:268 Some non-trivial changes in pop3-commands.c were done between 2.1.3 and 2.1.8 (expecially pop3_uidl_duplicates changes in 2.1.7). I guess this bug has crept in there. Joseph Tam <jtam.home(a)gmail.com>

2 1