Hi List, last time i did a lot of packaging and installing different versions of dovecot 1.0.x (rc not included ;) )and all was fine. Now a have a little problem. In this case it was an update from 1.0.13 to 1.1.1 Sometime it happens that 1 user out of x (more than 100) got this standardmessage for ~1 or ~2 thousend times in his mailbox (mbox) for example:>From MAILER_DAEMON Mon Sep 18 16:16:14 2006Date: Mon, 18 Sep 2006 16:16:14 +0200 From: Mail System Internal Data <MAILER-DAEMON at myhostname> Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA Message-ID: 1158588974 at myhostname X-IMAP: 1158588973 0000001177 Status: RO This text is part of the internal format of your mail folder, and is not a real message. It is created automatically by the mail system software. If deleted, important folder data will be lost, and it will be re-created with the data reset to initial values. I can follow this in maillog: Jul 1 16:01:04 myhostname dovecot: POP3(username): Disconnected: Logged out top=0/0, retr=1177/21638, del=1177/1177, size=454 The Mails came from nowhere from one moment to other. But it seems that it was not first pop-login after dovecot update. Update time was 14:57 Uhr. Pop-Login which "created" this mails was 3rd after update. It is not a big problem, seems to happens one only time but i want to know the backgrounds. Do you need further data? My 1.1.1 /etc/dovecot.conf looks like this: protocols = imap imaps pop3 pop3s ssl_disable = no ssl_cert_file = "/etc/*.hostname.com.crt" ssl_key_file = "/etc/*.hostname.com.key" ssl_ca_file = "/etc/*.hostname.com.bundle.crt" disable_plaintext_auth = no syslog_facility = mail login_user = dovecot login_process_per_connection = no login_processes_count = 1 login_greeting = hostname.com mailserver ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c login_log_format = %$: %s max_mail_processes = 100 verbose_proctitle = yes auth_verbose = yes mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u #default_mail_env = mbox:~/mail:INBOX=/var/spool/mail/%u mail_cache_min_mail_count = 30 mmap_disable=no mail_debug=no lock_method = flock mbox_read_locks = dotlock mbox_write_locks = dotlock fcntl mbox_dirty_syncs = yes mbox_very_dirty_syncs = yes mbox_lazy_writes = no ## ## IMAP specific settings ## protocol imap { login_executable = /usr/libexec/dovecot/imap-login imap_client_workarounds = outlook-idle netscape-eoh tb-extra-mailbox-sep delay-newmail mail_plugins = mail_log } ## ## POP3 specific settings ## protocol pop3 { ssl_disable = no login_executable = /usr/libexec/dovecot/pop3-login mail_executable = /usr/libexec/dovecot/pop3 pop3_no_flag_updates = no pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = oe-ns-eoh outlook-no-nuls } ## ## Authentication processes auth default { mechanisms = plain passdb shadow { } userdb passwd { } user = root } ## ## Plugins ## plugin { } Thanks Andre
On Jul 1, 2008, at 11:52 PM, Andre H?bner wrote:> Hi List, > > last time i did a lot of packaging and installing different versions > of dovecot 1.0.x (rc not included ;) )and all was fine. > Now a have a little problem. In this case it was an update from > 1.0.13 to 1.1.1 > Sometime it happens that 1 user out of x (more than 100) got this > standardmessage for ~1 or ~2 thousend times in his mailbox (mbox) > > for example: > >> From MAILER_DAEMON Mon Sep 18 16:16:14 2006 > Date: Mon, 18 Sep 2006 16:16:14 +0200 > From: Mail System Internal Data <MAILER-DAEMON at myhostname> > Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA > Message-ID: 1158588974 at myhostname > X-IMAP: 1158588973 0000001177 > Status: RO > > This text is part of the internal format of your mail folder, and is > not > a real message. It is created automatically by the mail system > software. > If deleted, important folder data will be lost, and it will be re- > created > with the data reset to initial values.These are created by the University of Washington's implementation of an IMAP server. Notice the date is nearly 2 years ago. At some point, it seems your site was running imap-uw. -- Fred> > > I can follow this in maillog: > Jul 1 16:01:04 myhostname dovecot: POP3(username): Disconnected: > Logged out top=0/0, retr=1177/21638, del=1177/1177, size=454 > > The Mails came from nowhere from one moment to other. But it seems > that it was not first pop-login after dovecot update. > Update time was 14:57 Uhr. Pop-Login which "created" this mails was > 3rd after update. > It is not a big problem, seems to happens one only time but i want > to know the backgrounds. > Do you need further data? My 1.1.1 /etc/dovecot.conf looks like this: > > protocols = imap imaps pop3 pop3s > ssl_disable = no > ssl_cert_file = "/etc/*.hostname.com.crt" > ssl_key_file = "/etc/*.hostname.com.key" > ssl_ca_file = "/etc/*.hostname.com.bundle.crt" > disable_plaintext_auth = no > syslog_facility = mail > login_user = dovecot > login_process_per_connection = no > login_processes_count = 1 > login_greeting = hostname.com mailserver ready. > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c > login_log_format = %$: %s > max_mail_processes = 100 > verbose_proctitle = yes > auth_verbose = yes > mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u > #default_mail_env = mbox:~/mail:INBOX=/var/spool/mail/%u > mail_cache_min_mail_count = 30 > mmap_disable=no > mail_debug=no > lock_method = flock > mbox_read_locks = dotlock > mbox_write_locks = dotlock fcntl > mbox_dirty_syncs = yes > mbox_very_dirty_syncs = yes > mbox_lazy_writes = no > > > ## > ## IMAP specific settings > ## > > protocol imap { > login_executable = /usr/libexec/dovecot/imap-login > imap_client_workarounds = outlook-idle netscape-eoh tb-extra-mailbox- > sep delay-newmail > mail_plugins = mail_log > } > > > ## > ## POP3 specific settings > ## > > protocol pop3 { > ssl_disable = no > login_executable = /usr/libexec/dovecot/pop3-login > mail_executable = /usr/libexec/dovecot/pop3 > pop3_no_flag_updates = no > pop3_uidl_format = %08Xu%08Xv > pop3_client_workarounds = oe-ns-eoh outlook-no-nuls > } > > > ## > ## Authentication processes > auth default { > mechanisms = plain > > passdb shadow { > } > > userdb passwd { > } > > user = root > } > > > ## > ## Plugins > ## > > plugin { > } > > > Thanks > Andre
Hi,> These are created by the University of Washington's implementation of > an IMAP server. Notice the date is nearly 2 years ago. At some point, > it seems your site was running imap-uw. > > -- > Frednope, i dont think so. i created completly new mailbox and mailed to it from extern. after deleting this mail using pop3-client same text was left in mbox but with current date. it must be dovecot related. we use dovecot from 1.0rc7 to 1.0.15 and never a case like this occured. also this machine had a lot of updates. now, by updating from 1.0.x (most 13) to 1.1.1 some users have this problem of retrieving ~1000 - ~2000 Mails with this internal message. The messages are from one to other moment in mbox, there is no delivering by postfix etc. this is completely new to me. Hmm.... If users asking i say it is a one time incident, but i do not really know... Thanks Andre
Hi,> It's not UW-IMAP (the server). It's PINE or Alpine (the client). Those are > usually found in on-disk mbox files that have been created by PINE/Alpine. > The message is ignored by PINE/Alpine (obviously), but when you switch to > a different mailer, it doesn't know to ignore it (and shouldn't be > expected to). AFAIK, the only solution is to delete the messages.i do not think it is client related. (never heared of this clients) Seems to be a normal dovecot internal message (timo?) But dovecot should not deliver this message as real mail, regardless of which client is used. Furthermore we face this issue only by updating to 1.1.1, all earlier versions did not show this behavior. Andre
Andreas Ntaflos
2008-Jul-04 11:06 UTC
[Dovecot] litte problems upgrade from 1.0.x to 1.1.1
On Wednesday 02 July 2008 08:52:41 Andre H?bner wrote:> Sometime it happens that 1 user out of x (more than 100) got this > standardmessage for ~1 or ~2 thousend times in his mailbox (mbox) > > for example: > >From MAILER_DAEMON Mon Sep 18 16:16:14 2006 > > Date: Mon, 18 Sep 2006 16:16:14 +0200 > From: Mail System Internal Data <MAILER-DAEMON at myhostname> > Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA > Message-ID: 1158588974 at myhostname > X-IMAP: 1158588973 0000001177 > Status: RO > > This text is part of the internal format of your mail folder, and is not > a real message. It is created automatically by the mail system software. > If deleted, important folder data will be lost, and it will be re-created > with the data reset to initial values.I've seen messages such as these when using (older versions of) Horde IMP on a Cyrus server in conjunction with Thunderbird and POP3. Not sure how exactly they are created, but I think it had to do with logging in via the IMP web interface, then using Thunderbird, and after that logging in via web interface again. Dovecot does not use mail messages to store folder meta-data as far as I know so I highly doubt this message was created by Dovecot (does Dovecot even send out messages except when going over quota?). Also notice the date of 2006-09-18, which is almost two years in the past. The message was probably created by some client and was somehow (willingly) ignored or flagged as deleted. Could be that upgrading Dovecot to 1.1 made the message visible again for whatever reason. Anyway, this is most certainly not a Dovecot-internal message. Andreas -- Andreas Ntaflos Vienna, Austria GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2476 bytes Desc: not available URL: <http://dovecot.org/pipermail/dovecot/attachments/20080704/f028f9d9/attachment-0002.bin>
Hi,> Dovecot does not use mail messages to store folder meta-data as far as I > know > so I highly doubt this message was created by Dovecot (does Dovecot even > send > out messages except when going over quota?). Also notice the date of > 2006-09-18, which is almost two years in the past. The message was > probably > created by some client and was somehow (willingly) ignored or flagged as > deleted. Could be that upgrading Dovecot to 1.1 made the message visible > again for whatever reason. > and > Anyway, this is most certainly not a Dovecot-internal message. >this case is really suspicious to me. don't hang on the old date 2006-09-18. I can recreate it with dovecot 1.1.1 running on my machine. I create completly new mbox, write to it and when i view mbox in console i see just this mail. After deleting (pop3) this mail with our webmailer or OutLook Express etc. I see this internal message with current date. I do not belive in Clients that put internal mesages by pop3-protocol, but what should it be else? pop/imapserver is dovecot 1.1.1 And why this case just happens by updateing from 1.0.x to 1.1.1 and not during further updates from 1.0.x to 1.0.x+1 ? If you say this is not dovecot related i have to accept this but i am a little bit doubtful... Unfortunately i have now a more annoying error in imap processing. Sometimes it happens that dovecot seems to be out of sync. My Log says: Jul 7 11:22:44 servername dovecot: IMAP(loginname): Next message unexpectedly lost from 156756352 Jul 7 11:22:44 servername dovecot: child 21652 (imap) killed with signal 11 Jul 4 13:41:09 servername dovecot: imap-login: Login: user=<loginname>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jul 4 13:41:10 servername dovecot: IMAP(loginname): Next message unexpectedly lost from 156715931 Jul 4 13:41:10 servername dovecot: IMAP(loginname): Disconnected: Logged out bytes=459/3359 Jul 4 13:41:32 servername dovecot: imap-login: Login: user=<loginname>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jul 4 13:41:32 servername dovecot: IMAP(loginname): Next message unexpectedly lost from 156715931 Jul 4 13:41:32 servername dovecot: IMAP(loginname): Next message unexpectedly lost from 156715931 Jul 4 13:41:32 servername dovecot: Panic: IMAP(loginname): file message-parser.c: line 770 (message_parser_parse_next_block): assertion failed: (ctx->input->eof || ctx->input->closed || ctx->input->stream_errno != 0 || ctx->broken) Jul 4 13:41:32 dd10636 dovecot: IMAP(loginname): Raw backtrace: imap [0x80c2cf0] -> imap [0x80c2d4a] -> imap [0x80c265c] -> imap(message_parser_parse_body+0) [0x80bbfa0] -> imap(index_mail_cache_parse_continue+0x22) [0x8087172] -> imap(mbox_save_continue+0x9c) [0x807054c] -> imap(mail_storage_copy+0xe4) [0x8091684 ] -> /usr/lib/dovecot/imap/lib20_mail_log_plugin.so [0xb7f5ed1a] -> imap(cmd_copy+0x1d2) [0x805a1c2] -> imap [0x805edfc] -> imap [0x805eea5] -> imap [0x805f65 5] -> imap(client_input+0x5e) [0x805f86e] -> imap(io_loop_handler_run+0x100) [0x80ca590] -> imap(io_loop_run+0x28) [0x80c9738] -> imap(main+0x46b) [0x806736b] -> /lib/libc.so.6(__libc_start_main+0xdc) [0xb7e4887c] -> imap [0x8059211] Jul 4 13:41:32 dd10636 dovecot: child 10768 (imap) killed with signal 6 Hmm, if we got more errors with 1.1.1 on our servers we have to downgrade to 1.0.15 and stop installing new version and wait for 1.1.x alltogether we have ~2000 servers, but most of them are running still 1.0.x This is my configure-line, dovecot is packaged by my self ./configure \ --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var \ --mandir=/usr/share/man \ --with-ssl=openssl \ --with-storages=mbox,maildir,raw \ --with-pam \ --with-passwd This is my dovecot.conf ## Dovecot configuration file #protocols = imap imaps pop3 pop3s protocols = imap imaps pop3 pop3s ssl_disable = no ssl_cert_file = "/path/*.domainname.crt" ssl_key_file = "/path/*.domainname.com.key" ssl_ca_file = "/path/*.domainname.com.bundle.crt" disable_plaintext_auth = no syslog_facility = mail login_user = dovecot login_process_per_connection = no login_processes_count = 1 login_greeting = domainname.com mailserver ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c login_log_format = %$: %s max_mail_processes = 100 verbose_proctitle = yes auth_verbose = yes mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u #default_mail_env = mbox:~/mail:INBOX=/var/spool/mail/%u mail_cache_min_mail_count = 30 mmap_disable=no mail_debug=no lock_method = flock mbox_read_locks = dotlock mbox_write_locks = dotlock fcntl mbox_dirty_syncs = yes mbox_very_dirty_syncs = yes mbox_lazy_writes = no ## ## IMAP specific settings ## protocol imap { login_executable = /usr/libexec/dovecot/imap-login imap_client_workarounds = outlook-idle netscape-eoh tb-extra-mailbox-sep delay-newmail mail_plugins = mail_log } ## ## POP3 specific settings ## protocol pop3 { ssl_disable = no login_executable = /usr/libexec/dovecot/pop3-login mail_executable = /usr/libexec/dovecot/pop3 pop3_no_flag_updates = no pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = oe-ns-eoh outlook-no-nuls } System is suse 10.1 Thank you Andre