[Dovecot] Index and Thunderbird

[Jon]

Hi,

Whitbox Linux 3 (RHEL)
Dovecot 1.0.rc29
Using NFS

From time to time does all mail get re-downloaded to Thunderbird. I 
would believe this has something to do with an index problem. I upgraded 
to 1.0 a few months ago but that didn't work well so I installed version 
1.0.rc29 which worked better but we still get this problem from time to 
time. DOes anyone know if it is a good idea to install 1.03 or perhaps 
1.1alpha?


dovecot: Sep 01 04:47:30 Error: IMAP(XX): 
rename(/mail2/home/XX/.Maildir/.Sent/dovecot-uidlist.lock, 
/mail2/home/XX/.Maildir/.Sent/dovecot-uidlist) failed: No such file i
dovecot: Sep 01 04:47:30 Error: IMAP(XX): 
file_dotlock_replace(/mail2/home/XX/.Maildir/.Sent/dovecot-uidlist) 
failed: No such file or directory
dovecot: Sep 01 04:47:30 Error: IMAP(XX): 
/mail2/home/XX/.Maildir/.Sent/dovecot-uidlist: next_uid was lowered 
(19065 -> 19064)
dovecot: Sep 01 04:47:30 Error: IMAP(XX): 
rename(/mail2/home/XX/.Maildir/.Sent/dovecot-uidlist.lock, 
/mail2/home/XX/.Maildir/.Sent/dovecot-uidlist) failed: No such file
dovecot: Sep 01 04:47:30 Error: IMAP(XX): 
file_dotlock_replace(/mail2/home/XX/.Maildir/.Sent/dovecot-uidlist) 
failed: No such file or directory
dovecot: Sep 01 09:11:23 Error: IMAP(XX): 
rename(/mail2/home/XX/.Maildir/dovecot-uidlist.lock, 
/mail2/home/XX/.Maildir/dovecot-uidlist) failed: No such file or 
directory
dovecot: Sep 01 09:11:23 Error: IMAP(XX): 
file_dotlock_replace(/mail2/home/XX/.Maildir/dovecot-uidlist) 
failed: No such file or directory
dovecot: Sep 01 09:11:23 Error: IMAP(XX): 
/mail2/home/XX/.Maildir/dovecot-uidlist: next_uid was lowered (18094 
-> 18093)
dovecot: Sep 01 14:32:25 Error: IMAP(XX): 
rename(/mail2/home/XX/.Maildir/dovecot-uidlist.lock, 
/mail2/home/XX/.Maildir/dovecot-uidlist) failed: No such file or 
directory
dovecot: Sep 01 14:32:25 Error: IMAP(XX): 
file_dotlock_replace(/mail2/home/XX/.Maildir/dovecot-uidlist) 
failed: No such file or directory
dovecot: Sep 01 14:32:25 Error: IMAP(XX): 
/mail2/home/XX/.Maildir/dovecot-uidlist: next_uid was lowered (18095 
-> 18094)
dovecot: Sep 01 17:13:27 Error: IMAP(XX): 
rename(/mail2/home/XX/.Maildir/dovecot-uidlist.lock, 
/mail2/home/XX/.Maildir/dovecot-uidlist) failed: No such file or 
directory
dovecot: Sep 01 17:13:27 Error: IMAP(XX): 
file_dotlock_replace(/mail2/home/XX/.Maildir/dovecot-uidlist) 
failed: No such file or directory
dovecot: Sep 01 17:13:27 Error: IMAP(XX): 
/mail2/home/XX/.Maildir/dovecot-uidlist: next_uid was lowered (18096 
-> 18095)
dovecot: Sep 01 17:31:26 Error: IMAP(XX): 
rename(/mail2/home/XX/.Maildir/dovecot-uidlist.lock, 
/mail2/home/XX/.Maildir/dovecot-uidlist) failed: No such file or 
directory
dovecot: Sep 01 17:31:26 Error: IMAP(XX): 
file_dotlock_replace(/mail2/home/XX/.Maildir/dovecot-uidlist) 
failed: No such file or directory
dovecot: Sep 01 17:31:26 Error: IMAP(XX): 
/mail2/home/XX/.Maildir/dovecot-uidlist: next_uid was lowered (18097 
-> 18096)
dovecot: Sep 01 17:38:28 Error: IMAP(XX): 
rename(/mail2/home/XX/.Maildir/dovecot-uidlist.lock, 
/mail2/home/XX/.Maildir/dovecot-uidlist) failed: No such file or 
directory
dovecot: Sep 01 17:38:28 Error: IMAP(XX): 
file_dotlock_replace(/mail2/home/XX/.Maildir/dovecot-uidlist) 
failed: No such file or directory
dovecot: Sep 01 19:05:24 Error: IMAP(XX): 
rename(/mail2/home/XX/.Maildir/dovecot-uidlist.lock, 
/mail2/home/XX/.Maildir/dovecot-uidlist) failed: No such file or 
directory
dovecot: Sep 01 19:05:24 Error: IMAP(XX): 
file_dotlock_replace(/mail2/home/XX/.Maildir/dovecot-uidlist) 
failed: No such file or directory
dovecot: Sep 02 09:53:34 Error: IMAP(XX): 
rename(/mail2/home/XX/.Maildir/dovecot-uidlist.lock, 
/mail2/home/XX/.Maildir/dovecot-uidlist) failed: No such file or 
directory
dovecot: Sep 02 09:53:34 Error: IMAP(XX): 
file_dotlock_replace(/mail2/home/XX/.Maildir/dovecot-uidlist) 
failed: No such file or directory
dovecot: Sep 02 09:53:35 Error: IMAP(XX): 
/mail2/home/XX/.Maildir/dovecot-uidlist: next_uid was lowered (33015 
-> 33014)
dovecot: Sep 02 09:54:57 Error: IMAP(XX): 
/mail2/home/XX/.Maildir/dovecot-uidlist: next_uid was lowered (33015 
-> 2)
dovecot: Sep 02 09:58:49 Error: IMAP(XX): 
rename(/mail2/home/XX/.Maildir/dovecot-uidlist.lock, 
/mail2/home/XX/.Maildir/dovecot-uidlist) failed: No such file or 
directory
dovecot: Sep 02 09:58:49 Error: IMAP(XX): 
file_dotlock_replace(/mail2/home/XX/.Maildir/dovecot-uidlist) 
failed: No such file or directory
dovecot: Sep 02 09:58:49 Error: IMAP(XX): 
/mail2/home/XX/.Maildir/dovecot-uidlist: next_uid was lowered (33017 
-> 33016)
dovecot: Sep 02 09:58:50 Error: IMAP(XX): 
rename(/mail2/home/XX/.Maildir/dovecot-uidlist.lock, 
/mail2/home/XX/.Maildir/dovecot-uidlist) failed: No such file or 
dir

[Dovecot] PAM child process timed out, killing it.

[Mart Pirita]

Tere.

Second time - does anybody have any idea what is wrong, btw I downgraded to 
1.0.2, and
getting from time to time same errors:

I'm running 1.0.3 in RedHat for some time, few days ago also upgraded
1.0.0 to 1.0.3 on Debian Sarge, 64 machine.

But now message log runs like crazy (about 10 GB since yesterday
evening) with such errors:

Aug 30 05:57:09 stan dovecot: auth(default):
pam(user1,172.18.1.25): PAM child process 1266 timed out, killing it
Aug 30 05:57:09 stan dovecot: auth(default): pam(user2,172.18.18.44):
PAM child process 15323 timed out, killing it
Aug 30 05:57:09 stan dovecot: auth(default): pam(user3,172.18.18.33):
PAM child process 29381 timed out, killing it
Aug 30 05:57:09 stan dovecot: auth(default): pam(user3,172.18.18.107):
PAM child process 15325 timed out, killing it
Aug 30 05:57:09 stan dovecot: auth(default): pam(user4,172.18.18.97):
PAM child process 1269 timed out, killing it
Aug 30 05:57:09 stan dovecot: auth(default):
pam(user5,192.168.190.53): PAM child process 15326 timed out, killing it
Aug 30 05:57:09 stan dovecot: auth(default):
pam(user6,172.18.18.33): PAM child process 29383 timed out, killing it

Whats wrong? Compiled from source, with the same options, as always?

-- 
Mart

Re: [Dovecot] PAM child process timed out, killing it.

[Marcus Rueckert]

On 2007-09-03 11:21:43 +0300, Mart Pirita wrote:
> Second time - does anybody have any idea what is wrong, btw I downgraded to 
> 1.0.2, and
> getting from time to time same errors:
> 
> I'm running 1.0.3 in RedHat for some time, few days ago also upgraded
> 1.0.0 to 1.0.3 on Debian Sarge, 64 machine.
> 
> But now message log runs like crazy (about 10 GB since yesterday
> evening) with such errors:
> 
> Aug 30 05:57:09 stan dovecot: auth(default):
> pam(user1,172.18.1.25): PAM child process 1266 timed out, killing it
> Aug 30 05:57:09 stan dovecot: auth(default): pam(user2,172.18.18.44):
> PAM child process 15323 timed out, killing it
> Aug 30 05:57:09 stan dovecot: auth(default): pam(user3,172.18.18.33):
> PAM child process 29381 timed out, killing it
> Aug 30 05:57:09 stan dovecot: auth(default): pam(user3,172.18.18.107):
> PAM child process 15325 timed out, killing it
> Aug 30 05:57:09 stan dovecot: auth(default): pam(user4,172.18.18.97):
> PAM child process 1269 timed out, killing it
> Aug 30 05:57:09 stan dovecot: auth(default):
> pam(user5,192.168.190.53): PAM child process 15326 timed out, killing it
> Aug 30 05:57:09 stan dovecot: auth(default):
> pam(user6,172.18.18.33): PAM child process 29383 timed out, killing it
> 
> Whats wrong? Compiled from source, with the same options, as always?

can you tell us more about your config? what backends are you using?

  darix

-- 
   openSUSE - SUSE Linux is my linux
   openSUSE is good for you
   www.opensuse.org

Re: [Dovecot] PAM child process timed out, killing it.

[Mart Pirita]

Tere.
> can you tell us more about your config? what backends are you using?
>
>   
Debian Sarge, 64, reiser, dovecot -a:

# 1.0.2: /etc/dovecot.conf
base_dir: /var/run/dovecot/
log_path:
info_log_path:
log_timestamp: %b %d %H:%M:%S
syslog_facility: mail
protocols: imap imaps pop3 pop3s
listen: *
ssl_listen:
ssl_disable: no
ssl_ca_file:
ssl_cert_file: /etc/ssl/certs/dovecot.pem
ssl_key_file: /etc/ssl/private/dovecot.pem
ssl_key_password:
ssl_parameters_regenerate: 168
ssl_cipher_list:
ssl_verify_client_cert: no
disable_plaintext_auth: no
verbose_ssl: no
shutdown_clients: no
nfs_check: yes
version_ignore: no
login_dir: /var/run/dovecot//login
login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login
login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login
login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login
login_user: dovecot
login_greeting: Dovecot ready.
login_log_format_elements: %u %r %m %c
login_log_format: %$: %s
login_process_per_connection: yes
login_chroot: yes
login_greeting_capability: no
login_process_size: 64
login_processes_count: 15
login_max_processes_count: 384
login_max_connections: 256
valid_chroot_dirs:
mail_chroot:
max_mail_processes: 3072
verbose_proctitle: yes
first_valid_uid: 500
last_valid_uid: 0
first_valid_gid: 1
last_valid_gid: 0
mail_extra_groups: mail
default_mail_env:
maildir:%h/Maildir:INDEX=/var/spool/dovecot/index/%u:CONTROL=/var/spool/dovecot/co
mail_location:
maildir:%h/Maildir:INDEX=/var/spool/dovecot/index/%u:CONTROL=/var/spool/dovecot/contr
mail_cache_fields: flags
mail_never_cache_fields: imap.envelope
mail_cache_min_mail_count: 0
mailbox_idle_check_interval: 30
mail_debug: no
mail_full_filesystem_access: no
mail_max_keyword_length: 50
mail_save_crlf: no
mail_read_mmaped: no
mmap_disable: no
mmap_no_write: no
dotlock_use_excl: no
fsync_disable: no
lock_method: fcntl
maildir_stat_dirs: no
maildir_copy_with_hardlinks: yes
maildir_copy_preserve_filename: no
mbox_read_locks: fcntl
mbox_write_locks: dotlock fcntl
mbox_lock_timeout: 180
mbox_dotlock_change_timeout: 180
mbox_min_index_size: 0
mbox_dirty_syncs: yes
mbox_very_dirty_syncs: no
mbox_lazy_writes: yes
dbox_rotate_size: 2048
dbox_rotate_min_size: 16
dbox_rotate_days: 1
umask: 63
mail_drop_priv_before_exec: no
mail_executable(default): /usr/local/dovecot/libexec/dovecot/imap
mail_executable(imap): /usr/local/dovecot/libexec/dovecot/imap
mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3
mail_process_size: 256
mail_plugins:
mail_plugin_dir(default): /usr/local/dovecot/modules/imap
mail_plugin_dir(imap): /usr/local/dovecot/modules/imap
mail_plugin_dir(pop3): /usr/local/dovecot/modules/pop3
mail_log_prefix: %Us(%u):
mail_log_max_lines_per_sec: 10
imap_max_line_length: 65536
imap_capability:
imap_client_workarounds(default): outlook-idle netscape-eoh
tb-extra-mailbox-sep delay-newmail
imap_client_workarounds(imap): outlook-idle netscape-eoh
tb-extra-mailbox-sep delay-newmail
imap_client_workarounds(pop3): outlook-idle
pop3_no_flag_updates: no
pop3_enable_last: no
pop3_reuse_xuidl: no
pop3_lock_session: no
pop3_uidl_format(default):
pop3_uidl_format(imap):
pop3_uidl_format(pop3): %08Xu%08Xv
pop3_client_workarounds(default):
pop3_client_workarounds(imap):
pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
pop3_logout_format(default): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s
pop3_logout_format(imap): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s
pop3_logout_format(pop3): retr=%r/%R, del=%d/%m, size=%s
auth default:
  mechanisms: plain
  realms:
  default_realm:
  cache_size: 0
  cache_ttl: 3600
  executable: /usr/local/dovecot/libexec/dovecot/dovecot-auth
  user: root
  chroot:
  username_chars:
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@
  username_translation:
  username_format:
  master_user_separator:
  anonymous_username: anonymous
  krb5_keytab:
  gssapi_hostname:
  verbose: yes
  debug: no
  debug_passwords: no
  ssl_require_client_cert: no
  ssl_username_from_cert: no
  count: 1
  worker_max_count: 90
process_size: 512
  passdb:
driver: pam
args:
deny: no
pass: no
master: no
  userdb:
driver: passwd
args:




-- 
Mart

Re: [Dovecot] imap process consuming 100% CPU (Dovecot 1.0.3)

[Robert Tomanek]

Hi,

Sunday, September 2, 2007, 22:42:37, you wrote:
>> 0x0806049d in imap_sync_more (ctx=0x80d9770) at imap-sync.c:104
>> 104 if (ctx->seq == 0) {

 A short follow-up on this, looks like an infinite loop to me, unless
 some threading magic is supposed to happen here:
> (gdb) step
> 120 if (ctx->sync_rec.seq1 > ctx->messages_count)
> (gdb)
> 104 if (ctx->seq == 0) {
> (gdb)
> 117 if (ctx->sync_rec.seq2 > ctx->messages_count) {
> (gdb)
> 120 if (ctx->sync_rec.seq1 > ctx->messages_count)
> (gdb)
> 104 if (ctx->seq == 0) {
> (gdb)
> 117 if (ctx->sync_rec.seq2 > ctx->messages_count) {
> (gdb)
> 120 if (ctx->sync_rec.seq1 > ctx->messages_count)
> (gdb) print ctx->seq
> $1 = 8317
> (gdb) print ctx->sync_rec.seq1
> $2 = 8318
> (gdb) print ctx->sync_rec.seq2
> $3 = 8320
> (gdb) print ctx->messages_count
> $4 = 8317

 The corresponding code in imap-sync.c is:
103:for (;;) {
104:if (ctx->seq == 0) {
105:/* get next one */
106:ret = mailbox_sync_next(ctx->sync_ctx,
107:&ctx->sync_rec);
108:if (ret <= 0) {
109:if (ret == 0) {
110:/* all finished ok */
111:ret = 1;
112:}
113:break;
114:}
115:}
116:
117:   if (ctx->sync_rec.seq2 > ctx->messages_count) {
118:/* don't send change notifications of messages we
119:   haven't even announced to client yet */
120:if (ctx->sync_rec.seq1 > ctx->messages_count)
121:continue;
122:ctx->sync_rec.seq2 = ctx->messages_count;
123:}
 ...
185:}

-- 
Best regards,
 Robert Tomanek   mailto:[EMAIL PROTECTED]

[Dovecot] Dovecot problem

[Raphael Bittencourt S. Costa]

Helo all,

Yesterday dovecot began droping connections and there is nothing
conclusive in the log file, just the messagens below:

Sep  2 11:43:57 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=200.152.100.77, lip=10.0.3.1
Sep  2 11:44:02 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=200.204.69.20, lip=10.0.3.1
Sep  2 11:44:19 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.20.236.248, lip=10.0.3.1
Sep  2 11:44:21 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.83.2.206, lip=10.0.3.1
Sep  2 11:44:24 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=200.158.0.143, lip=10.0.3.1
Sep  2 11:44:25 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.52.200.131, lip=10.0.3.1
Sep  2 11:44:26 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.53.20.53, lip=10.0.3.1, TLS
Sep  2 11:44:35 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.0.90.117, lip=10.0.3.1
Sep  2 11:44:41 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=189.33.173.226, lip=10.0.3.1
Sep  2 11:44:45 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.82.135.42, lip=10.0.3.1
Sep  2 11:45:03 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.19.218.250, lip=10.0.3.1
Sep  2 11:45:04 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.83.2.206, lip=10.0.3.1
Sep  2 11:45:05 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.81.250.119, lip=10.0.3.1
Sep  2 11:45:21 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=200.171.100.233, lip=10.0.3.1
Sep  2 11:45:23 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=64.233.182.131, lip=10.0.3.1
Sep  2 11:45:27 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.43.185.179, lip=10.0.3.1
Sep  2 11:45:40 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=200.161.155.35, lip=10.0.3.1
Sep  2 11:45:41 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.62.149.20, lip=10.0.3.1
Sep  2 11:45:43 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.83.43.154, lip=10.0.3.1
Sep  2 11:45:47 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=134.171.76.5, lip=10.0.3.1
Sep  2 11:45:49 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.92.248.84, lip=10.0.3.1
Sep  2 11:45:55 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.21.114.120, lip=10.0.3.1
Sep  2 11:45:57 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=200.229.107.85, lip=10.0.3.1
Sep  2 11:46:04 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=200.204.69.20, lip=10.0.3.1
Sep  2 11:46:04 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.53.83.146, lip=10.0.3.1
Sep  2 11:46:05 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=200.152.100.77, lip=10.0.3.1
Sep  2 11:46:35 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.95.95.108, lip=10.0.3.1
Sep  2 11:46:35 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.0.90.117, lip=10.0.3.1
Sep  2 11:46:35 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=200.159.87.122, lip=10.0.3.1
Sep  2 11:46:40 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=83.131.211.245, lip=10.0.3.1
Sep  2 11:46:41 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.6.61.147, lip=10.0.3.1
Sep  2 11:47:13 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.1.153.202, lip=10.0.3.1
Sep  2 11:47:38 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=189.0.252.144, lip=10.0.3.1
Sep  2 11:47:39 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.20.236.248, lip=10.0.3.1
Sep  2 11:47:47 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=134.171.76.5, lip=10.0.3.1
Sep  2 11:47:51 relay01 dovecot: pop3-login: Disconnected: Inactivity:
method=PLAIN, rip=201.12.103.67, lip=10.0.3.1


After restart, everything just back working.

Any ideia?


Raphael Costa

Re: [Dovecot] maildir rename_subfolders() and listescape interaction

[pod]

> "pod" == pod  <[EMAIL PROTECTED]> writes:

pod> I'd like to flag a problem we are observing that looks like it is
pod> caused by the listescape-plugin.c.  I realize that this plugin is
pod> not part of the standard Dovecot 1.0 distribution but I would
pod> appreciate any insights or suggestions for fixes that anyone is
pod> kind enough to offer.
[...]

Update: my original analysis of this was incorrect.  The 'internal'
functions are correctly using 'internal' names, however
maildir_mailbox_list_next() references storage->hierarchy_sep to obtain a
char with which to join together path elements.  Under listescape however
storage->hierarchy_sep == '/' so non-existent pathnames are generated.

I've come up with the following workaround but I can't help feeling it is
maybe a little fragile.

Timo: please consider applying this to


diff -r 70cc4b8884ef src/plugins/listescape/listescape-plugin.c
--- a/src/plugins/listescape/listescape-plugin.cTue Jul 31 19:42:03 
2007 +0100
+++ b/src/plugins/listescape/listescape-plugin.cFri Aug 31 19:21:05 
2007 +0100
@@ -160,10 +160,16 @@ listescape_mailbox_rename(struct mail_st
 {
struct listescape_mail_storage *mstorage =
LIST_ESCAPE_CONTEXT(storage);
+   char saved_hierarchy_sep;
+   int ret;
 
oldname = list_escape(oldname);
newname = list_escape(newname);
-   return mstorage->super.mailbox_rename(storage, oldname, newname);
+   saved_hierarchy_sep = storage->hierarchy_sep;
+   storage->hierarchy_sep = REAL_SEP;
+   ret = mstorage->super.mailbox_rename(storage, oldname, newname);
+   storage->hierarchy_sep = saved_hierarchy_sep;
+   return ret;
 }
 
 static int listescape_set_subscribed(struct mail_storage *storage,

Re: [Dovecot] Index and Thunderbird

[Charles Marcus]

From time to time does all mail get re-downloaded to Thunderbird. I 
would believe this has something to do with an index problem. I upgraded 
to 1.0 a few months ago but that didn't work well so I installed version 
1.0.rc29 which worked better but we still get this problem from time to 
time. DOes anyone know if it is a good idea to install 1.03 or perhaps 
1.1alpha?


Without dovecot -n output, it is difficult to guess... but most likely 
it is something to do with the POP3UIDL format. Have you read closely 
this page:


http://wiki.dovecot.org/POP3Server#uidl

Re: [Dovecot] IMAP: Disconnected: BUG: Unknown internal error (Dovecot 1.0.3)

[Robert Tomanek]

Hi,

Sunday, September 2, 2007, 20:24:04, you wrote:
>  I am getting the following error in the server mail logfile:
>> Sep  2 18:39:44 h648123 dovecot: IMAP()(): Disconnected: BUG:
>> Unknown internal error
>  I am running Dovecot 1.0.3 (compiled from sources) on Suse 9.3.

 I did one more thing: using gdb I attached to all 'imap' processes
 and set a breakpoint at the only place in the code where "Unknown
 internal error" appears (that is 'index_storage_get_last_error' in
 lib-storage/index/index-storage.c) in order to get backtrace for it
 (which may or may not help). See for yourselves:

> (gdb) break index-storage.c:452
> Breakpoint 1 at 0x807eec7: file index-storage.c, line 452.
> (gdb) continue
> Continuing.
> 
> Breakpoint 1, index_storage_get_last_error (storage=0x80cca90, 
> syntax_error_r=0x0, temporary_error_r=0xb8ef)
> at index-storage.c:452
> 452 *temporary_error_r = TRUE;
> (gdb) bt full
> #0  index_storage_get_last_error (storage=0x80cca90, syntax_error_r=0x0, 
> temporary_error_r=0xb8ef)
> at index-storage.c:452
> No locals.
> #1  0x08097765 in mail_storage_get_last_error (storage=0x0, 
> syntax_error_r=0xb8ee, temporary_error_r=0xb8ef)
> at mail-storage.c:345
> No locals.
> #2  0x080573b1 in cmd_fetch_finish (ctx=) at 
> cmd-fetch.c:90
> storage = (struct mail_storage *) 0x80cca90
> error = 
> syntax = false
> temporary_error = 8
> cmd = (struct client_command_context *) 0x80ccdbc
> ok_message = 0x80b395b "OK Fetch completed."
> #3  0x08057623 in cmd_fetch (cmd=0x80ccdbc) at cmd-fetch.c:173
> client = (struct client *) 0x80ccd78
> ctx = (struct imap_fetch_context *) 0x80cf010
> args = 
> search_arg = (struct mail_search_arg *) 0x80cefd8
> messageset = 
> ret = 
> #4  0x0805a0de in cmd_uid (cmd=0x80ccdbc) at cmd-uid.c:19
> cmd_name = 0x80cd078 "FETCH"
> #5  0x0805a616 in client_handle_input (cmd=0x80ccdbc) at client.c:335
> client = (struct client *) 0x80ccd78
> #6  0x0805a73a in client_handle_input (cmd=0x80ccdbc) at client.c:389
> client = (struct client *) 0x80ccd78
> #7  0x0805ac4c in _client_input (context=0x80ccd78) at client.c:432
> client = (struct client *) 0x80ccd78
> cmd = (struct client_command_context *) 0x80ccdbc
> ret = 2
> #8  0x080aa441 in io_loop_handler_run (ioloop=0x80cb9b0) at ioloop-epoll.c:203
> ctx = (struct ioloop_handler_context *) 0x80cb9d8
> list = (struct io_list *) 0x80ccf48
> io = (struct io *) 0x80ccf28
> tv = {tv_sec = 0, tv_usec = 927459}
> events_count = 4
> t_id = 2
> msecs = 
> ret = 1
> i = 0
> j = 0
> call = 
> #9  0x080a9889 in io_loop_run (ioloop=0x80cb9b0) at ioloop.c:329
> No locals.
> #10 0x08062087 in main (argc=1, argv=0xbaf4, envp=0xbafc) at 
> main.c:290
> plugin_dir = 

 Any thoughts here?

 One more piece of info that might (?) be interesting -- I have just
 run a grep on historical logs and it seems the bug never occured on
 previous versions of Dovecot I had been running in the past (first
 it was stock Suse 9.3 Dovecot 0.99.14, then a self-compiled
 1.0.rc27).

 The only difference (apart from the actual source code, of course)
 between 1.0.rc27 and the current 1.0.3 that might play any role are
 the configure flags:
 - 1.0.rc27: ./configure --with-pam
 - 1.0.3   : ./configure --with-ioloop=best --with-ldap --with-sql
 --with-mysql --with-pam
 This resulted in using epoll() for 1.0.3 and poll() for 1.0.rc27;
 both versions are using dnotify.

 BTW, 'uname -a' returns:
 Linux h648123 2.6.11.4-21.9-default #1 Fri Aug 19 11:58:59 UTC 2005 i686 
athlon i386 GNU/Linux
 
-- 
Best regards,
 Robert Tomanek   mailto:[EMAIL PROTECTED]

[Dovecot] Dovecot + Sieve

[Marcin M. Jessa]

Hi guys.

I installed dovecot 1.0.3 with sieve plugin.
It looks like sieve is loaded fine by dovecot [1].
I set up dovecot to use sieve globally:
protocol lda {
mail_plugins = cmusieve quota
sieve_global_dir = /usr/local/etc/sieve/Junk
   .
}

And created a sieve file which is supposed to move all the Spam marked by 
dspam to users's Junk folder (listed as Junk in the subscriptions file) :
require ["fileinto"];
# Move spam to Junk folder
if header :contains ["X-DSPAM-Result:"] "Spam" {
fileinto "Junk";
# Stop here so that we do not reply on spams
stop;
}

I also set up postfix to use pipe mail through dovecot:
mailbox_command = /usr/local/libexec/dovecot/deliver

The problem is dovecot seems to be ignoring my sieve rule and delivers emails 
directly to INBOX.
Any idea how to fix that?


[1]:
deliver([EMAIL PROTECTED]): Sep 03 23:02:57 Info: Loading modules from 
directory: /usr/local/lib/dovecot/lda
deliver([EMAIL PROTECTED]): Sep 03 23:02:57 Info: Module 
loaded: /usr/local/lib/dovecot/lda/lib10_quota_plugin.so
deliver([EMAIL PROTECTED]): Sep 03 23:02:57 Info: Module 
loaded: /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so


Cheers,
Marcin.
-- 
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115), 
10);'


!DSPAM:351,46dc7a4820752062134273!

Re: [Dovecot] Plugin development question

[Gary Smith]

> I think you should begin with Dovecot v1.1 code which makes it a lot
> easier. It has Cydir format that is really simple and serves as a
> pretty good example of how to implement a new backend.

I've been digging though the cydir format.  It looks fairly simple.
Basically, the short gist of it is that I will be replacing some of the
service calls (that retrieve data) with web service calls (to retrieve
data).  The data for the messages themselves (i.e. the envelope) is
stored in a database.

So looking into the cydir, I see the retrieval and storage functions.
Since this is read only, this part is pretty simple, I think.

But the Maildir list functions seem a little more complicated.  I'm
walking through them right now.  From looking into it, it seems there
are several functions that I will need to define in my own class to
handle/override the existing core functions.  Where can I get a list of
all of the virtual functions that can be derived from, without digging
through the code completely.  

Also, keeping in mind that everything is basically read only from a
client perspective, can I only implement the read functions and still
end up with a working system?

Please bear in mind that my C skills are 10 years old, so a lot of this
is a learning experience :).

BTW, you mentioned the FS backend.  I didn't see that under
lib-storage/*.  

Gary

> 
> Cydir is a mail_storage backend, but you'll probably need to also
> implement mailbox_list backend. Shouldn't be too difficult by looking
> at FS and Maildir++ backends I think.

Re: [Dovecot] Plugin development question

[Gary Smith]

> But the Maildir list functions seem a little more complicated.  I'm
> walking through them right now.  From looking into it, it seems there
> are several functions that I will need to define in my own class to
> handle/override the existing core functions.  Where can I get a list
of
> all of the virtual functions that can be derived from, without digging
> through the code completely.

Somehow I missed all of the lib-storage/list/* files.  I've seem to have
found most of what I'm looking for.  I also discovered the *_vfuncs
declarations that list everything that needs overriding.  My intent now
is to build out a shell wrapper for my plugins.

My only other question for the time being would be the minimal
implementation for functions that do nothing.  That is, all of the write
functions.  Do I need to pass down to a base class or just return a
default success value (or whatever the return type would be)?

> BTW, you mentioned the FS backend.  I didn't see that under
> lib-storage/*.
> 
> Gary