- dovecot - dovecot.org

[Dovecot] Squirrelmail + Dovecot + Maildir
by Vicki Stanfield 21 Dec '07

21 Dec '07

I have been struggling with getting my Fedora 7 box set up to use dovecot with Squirrelmail and Maildir. It works correctly with the exception of writing outgoing mail to the right folder (.Sent) or drafts (.Drafts). If I send a mail with Mutt, it writes the mail to the right place, so it has to be squirrelmail config or dovecot config. I want to use .Sent for sent-mail (~user/Maildir/.Sent) and .Drafts for drafts (~user/Maildir/.Drafts). Here is what I see in /etc/squirrelmail/config.php $optional_delimiter = '.'; [snip] $default_folder_prefix = ''; $trash_folder = 'Trash'; $sent_folder = 'Sent'; $draft_folder = 'Drafts'; $default_move_to_trash = true; $default_move_to_sent = true; $default_save_as_draft = true; The error in the browser is: * ERROR : Bad or malformed request.* Server responded: {830} BAD Error in IMAP command : Unknown command. and in the logs I see this: Dec 18 09:41:56 opus postfix/smtpd[12747]: connect from localhost[127.0.0.1] Dec 18 09:41:56 opus postfix/smtpd[12747]: 4CB7329B00B2: client=localhost[127.0.0.1] Dec 18 09:41:56 opus postfix/cleanup[12750]: 4CB7329B00B2: message-id=<51150.127.0.1.1.1197988916.squirrel(a)127.0.1.1> Dec 18 09:41:56 opus postfix/qmgr[2650]: 4CB7329B00B2: from=<vic(a)thepenguin.net>, size=1015, nrcpt=1 (queue active) Dec 18 09:41:56 opus postfix/smtpd[12747]: disconnect from localhost[127.0.0.1] Dec 18 09:41:56 opus dovecot: imap-login: Login: user=<vic>, method=PLAIN, rip=::ffff:127.0.1.1, lip=::ffff:127.0.1.1, secured Dec 18 09:41:56 opus dovecot: IMAP(vic): Disconnected: Too many invalid IMAP commands. Dec 18 09:41:59 opus postfix/smtp[12751]: 4CB7329B00B2: to=<vstanfield(a)other.com>, relay=platinum.fusionalliance.com[168.215.73.114]:25, delay=3.6, delays=0.08/0.01/2.6/0.89, dsn=2.0.0, status=sent (250 Requested mail action okay, completed) Dec 18 09:41:59 opus postfix/qmgr[2650]: 4CB7329B00B2: removed As you can surmise from the logs, the mail does get sent. Anybody see my mistake? CaptainVic

5 5

[Dovecot] 1.1.beta11 crashes
by Brian Taber 21 Dec '07

21 Dec '07

I am running 1.1.beta11 because I was having locking and coruption issues with indexes and mailbox on the latest release version. Some of my previous corrupted indexes caused an issue with 1.1.beta11: Dec 20 21:25:40 ra dovecot: IMAP(bodil(a)mydomain.com): Raw backtrace: imap [0x47ef81] -> imap [0x47eca6] -> imap [0x42c3bc] -> imap [0x42f201] -> imap [0x42f324] -> imap [0x41d585] -> imap(imap_fetch+0x147) [0x41cb17] -> imap(cmd_fetch+0x1bc) [0x41686c] -> imap(cmd_uid+0x52) [0x419c42] -> imap [0x41a508] -> imap [0x41a5aa] -> imap(client_input+0x72) [0x41ab72] -> imap(io_loop_handler_run+0x106) [0x485746] -> imap(io_loop_run+0x1d) [0x484dbd] -> imap(main+0x401) [0x421f51] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x30af61d8a4] -> imap [0x414fa9] Dec 20 21:25:40 ra dovecot: child 4353 (imap) killed with signal 6 Dec 20 21:28:24 ra dovecot: IMAP(bodil(a)mydomain.com): file maildir-uidlist.c: line 840 (maildir_uidlist_set_ext_real): assertion failed: (rec != NULL) Dec 20 21:28:24 ra dovecot: IMAP(bodil(a)mydomain.com): Raw backtrace: imap [0x47ef81] -> imap [0x47eca6] -> imap [0x42c3bc] -> imap [0x42f201] -> imap [0x42f324] -> imap [0x41d585] -> imap(imap_fetch+0x147) [0x41cb17] -> imap(cmd_fetch+0x1bc) [0x41686c] -> imap(cmd_uid+0x52) [0x419c42] -> imap [0x41a508] -> imap [0x41a5aa] -> imap(client_input+0x72) [0x41ab72] -> imap(io_loop_handler_run+0x106) [0x485746] -> imap(io_loop_run+0x1d) [0x484dbd] -> imap(main+0x401) [0x421f51] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x30af61d8a4] -> imap [0x414fa9] Dec 20 21:28:24 ra dovecot: child 4385 (imap) killed with signal 6 Dec 20 21:30:08 ra dovecot: IMAP(bodil(a)mydomain.com): file maildir-uidlist.c: line 840 (maildir_uidlist_set_ext_real): assertion failed: (rec != NULL) Dec 20 21:30:08 ra dovecot: IMAP(bodil(a)mydomain.com): Raw backtrace: imap [0x47ef81] -> imap [0x47eca6] -> imap [0x42c3bc] -> imap [0x42f201] -> imap [0x42f324] -> imap [0x41d585] -> imap(imap_fetch+0x147) [0x41cb17] -> imap(cmd_fetch+0x1bc) [0x41686c] -> imap(cmd_uid+0x52) [0x419c42] -> imap [0x41a508] -> imap [0x41a5aa] -> imap(client_input+0x72) [0x41ab72] -> imap(io_loop_handler_run+0x106) [0x485746] -> imap(io_loop_run+0x1d) [0x484dbd] -> imap(main+0x401) [0x421f51] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x30af61d8a4] -> imap [0x414fa9] Dec 20 21:30:08 ra dovecot: child 4397 (imap) killed with signal 6 I removed the index files for that mainbox and that error went away, but it caused another error: Dec 20 21:45:29 ra dovecot: IMAP(bodil(a)mydomain.com): file_dotlock_open() failed with file /mailindex/mydomain.com/bodil/.INBOX/dovecot.index.log: No such file or directory I had to recreate the .INBOX folder manually and all was great. The funny thing is it had already created all the other folders in the mailbox....

2 1

[Dovecot] Recent message flag unavailable ?
by Nicolas KOWALSKI 21 Dec '07

21 Dec '07

Hello, When a message is copied or newly-delivered to a folder, it does not have the "recent" flag set. Is there something in the configuration to activate it ? Thanks. # dovecot -n # 1.0.9: /usr/local/etc/dovecot.conf protocols: imap login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_location: mbox:~/mail:INBOX=~/mail/INBOX:INDEX=/var/cache/dovecot mbox_write_locks: fcntl auth default: passdb: driver: pam userdb: driver: passwd The MUA which shows it is Alpine 0.999999. -- Nicolas

2 2

[Dovecot] namespace problem / 1.1beta11
by ja nein 21 Dec '07

21 Dec '07

Hi all, actually I got a problem with the namespaces in dovecot 1.1 beta11. It occured after purging index files and resynch via imapsync. Dovecot complains about "Unknown namespace", though it worked with versions before. I cannot comfirm for 1.1beta10, but I surely know 1.1beta9 worked with these settings. Example: From Folder [INBOX/Trash] To Folder [___________] To Folder ___________ does not exist Creating folder [___________] Couldn't create [___________]266 NO Unknown namespace. Used imapsync command: /home/imapsync/imapsync --host1 ip.of.host.1 --user1 user1 --password1 password --host2 127.0.0.1 --user2 user2 --password2 password --authmech2 LOGIN --regextrans2 s/\./_/g --delete2 --sep1 . --sep2 . --justfolders Another run with different namespace settings shows up the folders in Thunderbird as INBOX^2002, INBOX^Trash ans so on... My goal is to keep all client settings when migrating a bigger installation of cyrus to dovecot. For know all folders in Cyrus appear as subfolders of INBOX, which I had achieved with dovecot < 1.1beta11. Any ideas? Btw., as we work in a load balanced environment, LMTP delivery would be a great feature for upcoming releases, as it would enable people to use multiple frontends of SMTP servers without the need of connecting them to a somewhat shared file system. Forwarding all mail to a SMTP server on the machine running dovecot and doing delivery there isn't the favoured option (at least for us). And a huge thx to Timo on working that hard on such a great working product! Regrads, Sebastian Dovecot conf putput: # 1.1.beta11: /etc/dovecot/dovecot.conf base_dir: /home/dovecot/ syslog_facility: local3 protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /home/dovecot/var/run/login login_executable(default): /opt/dovecot-1.1-beta11/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot-1.1-beta11/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot-1.1-beta11/libexec/dovecot/pop3-login verbose_proctitle: yes mail_location: maildir:/home/dovecot/mail/%d/%u:INDEX=/home/dovecot/index/%d/%u mail_executable(default): /opt/dovecot-1.1-beta11/libexec/dovecot/imap mail_executable(imap): /opt/dovecot-1.1-beta11/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot-1.1-beta11/libexec/dovecot/pop3 mail_plugins(default): fts fts_squat mail_plugins(imap): fts fts_squat mail_plugins(pop3): mail_plugin_dir(default): /opt/dovecot-1.1-beta11/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot-1.1-beta11/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot-1.1-beta11/lib/dovecot/pop3 namespace: type: private separator: / prefix: INBOX/ inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login digest-md5 cram-md5 verbose: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /home/dovecot/var/run/dovecot/auth-client master: path: /home/dovecot/var/run/dovecot/auth-master user: vuser plugin: fts: squat __________________________________ Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern. www.yahoo.de/clever

2 1

[Dovecot] Dovecot truncating messages and/or attachments
by fp＠kraptastic.com 21 Dec '07

21 Dec '07

Hello, I am having problems with Dovecot not sending clients emails bigger then 8-12k (it varies) or attachments bigger then 8-12k. I am also getting 'Corrupted transaction log file' errors ' unexpected end of file while reading header' I have deleted the dovecot.index.log, dovecot.index.cache, and dovecot.index several dozen times. I started off using Centos 5, with their package of dovecot 1.05, after seeing that there were problems in the package in the http://wiki.dovecot.org/WhyDoesItNotWork, I went with a source install of dovecot 1.09. Here is my cfg info: # dovecot -n # 1.0.9: /etc/dovecot.conf protocols: pop3 pop3s imap imaps ssl_cert_file: /etc/dovecert.pem ssl_key_file: /etc/dovekey.pem disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_process_size: 128 first_valid_uid: 106 last_valid_uid: 106 mail_extra_groups: mail mail_location: maildir:/var/spool/postfix/virtual/%d/%u mail_debug: yes maildir_copy_with_hardlinks: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle pop3_uidl_format: %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login user: vmail passdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: prefetch socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: vmail master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: vmail (the login process is 128 because i was experimenting with various numbers (32,64,80,etc) The /var/log/maillog has hundreds of these: Dec 11 16:27:42 le1 dovecot: POP3(xxx@xxx): Corrupted transaction log file /var/spool/postfix/virtual/xxx.com/xxx(a)xxx/dovecot.index.log: unexpected end of file while reading header I turned made it so the mail stays on the server, so i can see that the mail stored there by postfix is the correct size. When email clients download mail through pop3 or pop3s it only downloads 4,8, or 12 k worth of the email (whether it has attachments or not). Here is an example transaction: Dec 11 17:18:31 le1 dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=142.179.211.193 rip=24.71.237.54 resp= Dec 11 17:18:31 le1 dovecot: auth(default): client out: CONT 1 Dec 11 17:18:31 le1 dovecot: auth(default): client in: CONT 1 AHNoYXduQGxhbmdmb3JkZWxlY3RyaWMuY2EAdW5mdW5m Dec 11 17:18:31 le1 dovecot: auth(default): cache(shawn(a)xxx.com,24.71.237.54): hit Dec 11 17:18:31 le1 dovecot: auth(default): client out: OK 1 user=shawn(a)xxx.com Dec 11 17:18:31 le1 dovecot: auth(default): master in: REQUEST 92 8447 1 Dec 11 17:18:31 le1 dovecot: pop3-login: Login: user=<shawn(a)xxx.com>, method=PLAIN, rip=24.71.237.54, lip=142.179.211.193 Dec 11 17:18:31 le1 dovecot: auth(default): master out: USER 92 shawn(a)xxx.com maildir=xxx.com/shawn@xxx.com/ uid=106 gid=106 Dec 11 17:18:31 le1 dovecot: POP3(shawn(a)xxx.com): Effective uid=106, gid=106 Dec 11 17:18:31 le1 dovecot: POP3(shawn(a)xxx.com): maildir: data=/var/spool/postfix/virtual/xxx.com/shawn@xxx.com Dec 11 17:18:31 le1 dovecot: POP3(shawn(a)xxx.com): maildir: root=/var/spool/postfix/virtual/xxx.com/shawn@xxx.com, index=/var/spool/postfix/virtual/xxx.com/shawn@xxx.com, control=, inbox= Dec 11 17:18:31 le1 dovecot: auth(default): new auth connection: pid=8487 Dec 11 17:18:31 le1 dovecot: POP3(shawn(a)xxx.com): Disconnected: Logged out top=0/0, retr=1/4215, del=0/1, size=70206 To be clear, if i telnet to 110, and manually do a retr on the message it only sends 4,8,or 12k worth of the message. So it does not appear to be a permission problem, it is reading and writing to the directory properly. The system is x86_64 centos 5, not using the standard dovecot nor postfix rpms that come with the distro. postfix from what I can tell, is working fine, but dovecot isn't. I'm going to try installing cyrus to make sure it's not postfix, but I'd really like to avoid cyrus if possible. Thanks in advance for any help.

2 1

[Dovecot] about quota_warning behavior
by naoki 21 Dec '07

21 Dec '07

Hi, We've been using v1.0.5 +quota_warning patch, however quota_warning does't seem to be working properly. For example, in order to enable 80% over for quota warning, and we configured like following: ----------------------------------------------------------------------- plugin { quota_warning = storage=80%% /usr/local/path/to/plugin } ----------------------------------------------------------------------- But it does not work. However we set quota_warning value to 20%, it seems to be working. ----------------------------------------------------------------------- plugin { quota_warning =storage=20%% /usr/local/path/to/plugin } ----------------------------------------------------------------------- If this is the case, do we always have to set quota value to what we have after subtracting the required quota warning value from 100. for example, if we want quota warning value to be 70%, we actually have to write 30% in configuration?? Will there be another patch to fix this? Thanks -- Naoki Takazawa Marino Ltd., Yokohama, JAPAN

2 1

Re: [Dovecot] 1.1.Beta9 deliver problem: Unknown mail storage driver raw
by ja nein 21 Dec '07

21 Dec '07

Hi Velko, I recently hit the same problem. You have to add raw storage driver to your compile options, meaning "--with-storages=maildir,mbox,dbox,raw,cydir", that will do the trick. Maybe it would be good to update the description of available storage drivers in configure script. Regards, Sebastian ----- Ursprüngliche Mail ---- Von: Velko Ivanov <dachev(a)nove.bg> An: dovecot(a)dovecot.org Gesendet: Samstag, den 1. Dezember 2007, 14:19:18 Uhr Betreff: [Dovecot] 1.1.Beta9 deliver problem: Unknown mail storage driver raw Hello, I'm new to dovecot, trying to configure a Postfix/Dovecot system. Got everything in place - smtp with dovecot SASL and imap working fine, maildir is created, thunderbird logs in successfuly .. but the Dovecot LDA gives me this error on delivery: "Couldn't create internal raw storage: Unknown mail storage driver raw". I tried searching the configuration manual, reference, google and this list's archives, but found no clue. Checked the source, but it will take me some time to figure out what is a storage driver and where is the "raw" one hiding, so if somebody could help, please .. I did it with userdb static initially - uid=dovecot_mail, gid=dovecot_mail, home=/usr/local/storage/mail/%d/%n but after reading, that some passdbs don't work with deliver&static, I moved everything to the db (found out that prefetch isn't working with deliver btw - moans about userdb_ entries not present, while the imap finds them and works happily). It didn't help. # 1.1.beta9: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot listen: mail.srv.ivanov-nest.com ssl_cert_file: /usr/local/etc/dovecot.crt ssl_key_file: /usr/local/etc/dovecot.key login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_location: dbox:~/Maildir dotlock_use_excl: yes maildir_copy_preserve_filename: yes namespace: type: private inbox: yes hidden: yes list: yes subscriptions: yes auth default: mechanisms: plain login user: dovecot_db passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: dovecot_mail group: wheel Heute schon einen Blick in die Zukunft von E-Mails wagen? www.yahoo.de/mail

5 7

[Dovecot] 1.1 beta 11 - no quota warnings
by adam_jh＠hotmail.com 21 Dec '07

21 Dec '07

Having tried and failed to get 1.0.8 with quota-rewrite to send warnings, I removed the 1.0.8 and installed the latest 1.1 - however I still can't get the warnings! Can someone advise what might be wrong - it must be my configuration?? To compile 1.1 I used ./configure --with-deliver --with-mysql. I've chopped and changed my conf till I'm blue in the face. My dovecot-mysql.conf file does not override the quota, I've enabled the debug and verbose = yes - but they don't mention any quota warnings, just normal delivered logs. What else can I do? The process I use is to add up the maildirsize totals, set a storage figure in the conf which makes the maildirsize just less than 95%, then restart dovecot, send an email - and nothing - no warning is triggered! Any help appreciated - I've spent so long on this now. adam # 1.1.beta11: /usr/local/etc/dovecot.conf protocols: imap imaps pop3 pop3s ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot-login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: maildir:/var/vmail/%d/%n mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: user: nobody verbose: yes debug: yes passdb: driver: sql args: /usr/local/etc/dovecot-mysql.conf userdb: driver: sql args: /usr/local/etc/dovecot-mysql.conf socket: type: listen client: path: /var/spool/postfix/private/auth user: postfix group: mail master: path: /var/run/dovecot/auth-master user: vmail group: mail plugin: quota: maildir quota_rule: *:storage=220000b quota_warning: storage=95%% /usr/local/bin/quota-warning 90

3 4

[Dovecot] imap+unix users and pop3+virtual users
by Wendell Turner 21 Dec '07

21 Dec '07

This should be simple, but I'm missing something. My virtual users cannot access their mail. I would like Unix users to get their mail via imap which is deposited in /var/spool/mail/username. (This works.) I would like virtual users to get their mail via pop3 which is deposited in /var/spool/mail/vhosts/example.com/auser/mail/inbox (postfix does in fact put the mail there). Those users can get authenticated via file /var/dovecot/passwd, but cannot retrieve their mail. The log message is shown below. The file/directory is there, but doesn't dovecot see it? Thanks, Wendell -------------------- Info: POP3(auser(a)example.com): mbox: data=/var/spool/mail/vhosts/example.com/auser/mail/:INBOX=/var/mail/auser@e… Info: POP3(auser(a)example.com): mbox: root=/var/spool/mail/vhosts/example.com/auser/mail, index=/var/spool/mail/vhosts/example.com/auser/mail, inbox=/var/mail/auser(a)example.com Info: POP3(auser(a)example.com): Mailbox init failed top=0/0, retr=0/0, del=0/0, size=0 -------------------- /usr/sbin/dovecot -n # 1.0.7: /etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log protocols: pop3 imap imaps pop3s ssl_cert_file: /etc/CA/cert.pem ssl_key_file: /etc/CA/key.pem login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: mbox:~/mail/:INBOX=/var/mail/%u mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd userdb: driver: static args: uid=vmail gid=vmail home=/var/spool/mail/vhosts/%d/%n

4 9

[Dovecot] upgrade to 1.1 and mail location
by lenny＠edpausa.com 21 Dec '07

21 Dec '07

I recently upgraded from 1.0.8 to 1.1-11 the only thing that was changed in the config file was the new syntax for mail location. default_mail_env = mbox:~/:INBOX=~/mbox to mail_location = mbox:~/:INBOX=~/mbox now some imap clients, like squirrellmail and pine have difficulties writting to Sent, Draft and sent-mail folders. In all cases the folders are visible and are present in .subsriptions file( although not seen as subscribed in squirrelmail), but the clients complain that folders already exist when trying to write to them after sending. has anyone run into this ? any suggestions ? thanks a lot.

2 1