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
