[Dovecot] global vs user script
What is the order of execution if both user and global sieve script exists? Thanks.
Re: [Dovecot] Return error instead of dying on time back skip?
Hello Amon, Amon Ott, 02.05.2007 (d.m.y): All our systems run ntpd, but they might be offline for a while before they get contact to a time server, e.g. because of DSL problems. Define one of your internal systems as master time server that connects to other NTP servers outside your networks and make your other systems synchronize their system time with this machine. Gruss/Regards, Christian Schmidt -- Writing is easy; all you do is sit staring at the blank sheet of paper until drops of blood form on your forehead. -- Gene Fowler
Re: [Dovecot] INBOX inaccessible
Ooooh ! Thanks, I have 250 users reading and sending emails on this server Sophie Charles Marcus a écrit : Anyway, a better idea is upgrading to 1.0; dovecot 0.99 is really old and no longer supported. :-\ I use the version including in my SL 4.4 distribution I hope there's some RPM somewhere for the 1.0 WARNING! Be sure to read the update notes - the config file format has changed between 0.99 and 1.0.0... http://wiki.dovecot.org/UpgradingDovecot Fax: [+33](0)4.99.61.99.99
Re: [Dovecot] Return error instead of dying on time back skip?
On Friday 04 May 2007 10:07, Christian Schmidt wrote: Hello Amon, Amon Ott, 02.05.2007 (d.m.y): All our systems run ntpd, but they might be offline for a while before they get contact to a time server, e.g. because of DSL problems. Define one of your internal systems as master time server that connects to other NTP servers outside your networks and make your other systems synchronize their system time with this machine. Thanks for the tip, but these are customer systems. Most of them only buy one server system from us and have Windows clients behind. So there is no other system available, which could be master. Instead, our server is supposed to be time master. :) From customer point of view, the mail server does not work without reason. An error message would help to understand the problem and the proposed behaviour would keep dovecot running. Now some of them just reboot the system (Windows users...), this is not the desired solution. Amon Ott -- Amon Ott - m-privacy GmbH Am Köllnischen Park 1, 10179 Berlin Tel: +49 30 24342334 Fax: +49 30 24342336 Web: http://www.m-privacy.de Handelsregister: Amtsgericht Charlottenburg HRB 84946 Geschäftsführer: Dipl.-Kfm. Holger Maczkowsky, Roman Maczkowsky GnuPG-Key-ID: EA898571
Re: [Dovecot] Sieve not recognizing keywords
Alexander Hoogerhuis wrote: I am doing all of this on Gentoo, so I decided to just redo the ebuild so that I got the dovecot 1.0.0 ebuild, but with the sieve plugin 1.0.1. Aparently I get the same error and now am at a loss here. Any pointers? Well immediate idea would be to work out exactly which require is failing. Try each option on its own in the require to work it out. Regards James Turnbull -- James Turnbull [EMAIL PROTECTED] --- Author of Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) Hardening Linux (http://www.amazon.com/gp/product/159059/) --- PGP Key (http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x0C42DF40)
Re: [Dovecot] Sieve not recognizing keywords
James Turnbull wrote: Alexander Hoogerhuis wrote: I am doing all of this on Gentoo, so I decided to just redo the ebuild so that I got the dovecot 1.0.0 ebuild, but with the sieve plugin 1.0.1. Aparently I get the same error and now am at a loss here. Any pointers? Well immediate idea would be to work out exactly which require is failing. Try each option on its own in the require to work it out. Bitten by the Gentoo. Aparently I stuffed it when rearranging the files and ebuilds. Recompiled correctly, all works. :) Regards James Turnbull mvh, A
[Dovecot] Help with LDAP authentication - user / user+domain
Hello Folks, I've my dovecot working well and authenticating in my ldap servers. But I'd like configure my users to authenticate in two ways. One is just submitting the username and the other one is providing [EMAIL PROTECTED] . I'm moving from a cyrus-imap solution to dovecot and I've implemented it with VD domains. But nowadays I still have one domain at my servers. So to no cause to much impact to users, I'd like to provide this two ways of authentication. Here follows my dovecot-ldap.conf: hosts = localhost dn = uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot dnpass = XX auth_bind = no ldap_version = 3 base = dc=domain,dc=com deref = never scope = subtree user_attrs = mail,homeDirectoryquota=quota=maildir:storage user_filter = ((objectClass=VirtualMailAccount)(mail=%u)(accountActive=TRUE)(delete=F ALSE)) pass_attrs = mail,userPassword pass_filter = ((objectClass=VirtualMailAccount)(mail=%u)(accountActive=TRUE)(delete=F ALSE)) default_pass_scheme = SSHA user_global_uid = 100 user_global_gid = 101 My logs: Apr 30 13:47:58 server dovecot: auth(default_with_listener): client in: AUTH 1 PLAIN service=POP3lip=xxx.xxx.xx.xx rip=xxx.xx.xxx.xxx resp=AGpveWNlLm1hcmlhbm8AbWFrdHVi Apr 30 13:47:58 server dovecot: auth(default_with_listener): ldap(user.test,xxx.xx.xxx.xxx): pass search: base=dc=domain,dc=com scope=subtree filter=((objectClass=VirtualMailAccount)(mail=user.test)(accountActive= TRUE)(delete=FALSE)) fields=mail,userPassword Apr 30 13:47:58 server dovecot: auth(default_with_listener): ldap(user.test,xxx.xx.xxx.xxx): unknown user Apr 30 13:47:59 server dovecot: auth(default_with_listener): client out: FAIL1 user=user.test Apr 30 13:48:05 server dovecot: pop3-login: Aborted login: user=user.test, method=PLAIN, rip=xxx.xx.xxx.xxx, lip=xxx.xxx.xx.xx If I provide [EMAIL PROTECTED] works fine. Any guesses or ideas? PS: I've suppressed some information, like IPs, server names e IPs Best Regards, Venilton C. Junior HP Certified Professional Sercompe Computadores Ltda. Office: +55 47 3431-9700 Fax: +55 47 3431-9747 Mobile: +55 47 9653-5872 www.sercompe.com.br http://www.sercompe.com.br/
Re: [Dovecot] Help with LDAP authentication - user / user+domain
Friday 04 of May 2007 15:34:51 Venilton Junior napisał(a): Hello Folks, I've my dovecot working well and authenticating in my ldap servers. But I'd like configure my users to authenticate in two ways. One is just submitting the username and the other one is providing [EMAIL PROTECTED] . I'm moving from a cyrus-imap solution to dovecot and I've implemented it with VD domains. But nowadays I still have one domain at my servers. So to no cause to much impact to users, I'd like to provide this two ways of authentication. Here follows my dovecot-ldap.conf: hosts = localhost dn = uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot dnpass = XX auth_bind = no ldap_version = 3 base = dc=domain,dc=com deref = never scope = subtree user_attrs = mail,homeDirectoryquota=quota=maildir:storage user_filter = ((objectClass=VirtualMailAccount)(mail=%u)(accountActive=TRUE)(delete=F ALSE)) pass_attrs = mail,userPassword pass_filter = ((objectClass=VirtualMailAccount)(mail=%u)(accountActive=TRUE)(delete=F ALSE)) default_pass_scheme = SSHA user_global_uid = 100 user_global_gid = 101 My logs: Apr 30 13:47:58 server dovecot: auth(default_with_listener): client in: AUTH 1 PLAIN service=POP3lip=xxx.xxx.xx.xx rip=xxx.xx.xxx.xxx resp=AGpveWNlLm1hcmlhbm8AbWFrdHVi Apr 30 13:47:58 server dovecot: auth(default_with_listener): ldap(user.test,xxx.xx.xxx.xxx): pass search: base=dc=domain,dc=com scope=subtree filter=((objectClass=VirtualMailAccount)(mail=user.test)(accountActive= TRUE)(delete=FALSE)) fields=mail,userPassword Apr 30 13:47:58 server dovecot: auth(default_with_listener): ldap(user.test,xxx.xx.xxx.xxx): unknown user Apr 30 13:47:59 server dovecot: auth(default_with_listener): client out: FAIL1 user=user.test Apr 30 13:48:05 server dovecot: pop3-login: Aborted login: user=user.test, method=PLAIN, rip=xxx.xx.xxx.xxx, lip=xxx.xxx.xx.xx If I provide [EMAIL PROTECTED] works fine. Try with auth_default_realm = domain.com in dovecot.conf -- Łukasz Mierzwa
Re: [Dovecot] Help with LDAP authentication - user / user+domain
Tnx, it's working fine! :) This option in my dovecot.conf worked for me!! Regards, Venilton C. Junior HP Certified Professional Sercompe Computadores Ltda. Office: +55 47 3431-9700 Fax: +55 47 3431-9747 Mobile: +55 47 9653-5872 www.sercompe.com.br -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lukasz Mierzwa Sent: sexta-feira, 4 de maio de 2007 10:47 To: dovecot@dovecot.org; Venilton Junior Subject: Re: [Dovecot] Help with LDAP authentication - user / user+domain Friday 04 of May 2007 15:34:51 Venilton Junior napisał(a): Hello Folks, I've my dovecot working well and authenticating in my ldap servers. But I'd like configure my users to authenticate in two ways. One is just submitting the username and the other one is providing [EMAIL PROTECTED] . I'm moving from a cyrus-imap solution to dovecot and I've implemented it with VD domains. But nowadays I still have one domain at my servers. So to no cause to much impact to users, I'd like to provide this two ways of authentication. Here follows my dovecot-ldap.conf: hosts = localhost dn = uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot dnpass = XX auth_bind = no ldap_version = 3 base = dc=domain,dc=com deref = never scope = subtree user_attrs = mail,homeDirectoryquota=quota=maildir:storage user_filter = ((objectClass=VirtualMailAccount)(mail=%u)(accountActive=TRUE)(delete=F ALSE)) pass_attrs = mail,userPassword pass_filter = ((objectClass=VirtualMailAccount)(mail=%u)(accountActive=TRUE)(delete=F ALSE)) default_pass_scheme = SSHA user_global_uid = 100 user_global_gid = 101 My logs: Apr 30 13:47:58 server dovecot: auth(default_with_listener): client in: AUTH 1 PLAIN service=POP3lip=xxx.xxx.xx.xx rip=xxx.xx.xxx.xxx resp=AGpveWNlLm1hcmlhbm8AbWFrdHVi Apr 30 13:47:58 server dovecot: auth(default_with_listener): ldap(user.test,xxx.xx.xxx.xxx): pass search: base=dc=domain,dc=com scope=subtree filter=((objectClass=VirtualMailAccount)(mail=user.test)(accountActive= TRUE)(delete=FALSE)) fields=mail,userPassword Apr 30 13:47:58 server dovecot: auth(default_with_listener): ldap(user.test,xxx.xx.xxx.xxx): unknown user Apr 30 13:47:59 server dovecot: auth(default_with_listener): client out: FAIL1 user=user.test Apr 30 13:48:05 server dovecot: pop3-login: Aborted login: user=user.test, method=PLAIN, rip=xxx.xx.xxx.xxx, lip=xxx.xxx.xx.xx If I provide [EMAIL PROTECTED] works fine. Try with auth_default_realm = domain.com in dovecot.conf -- Łukasz Mierzwa
[Dovecot] Moving new email from the mail spool to the inbox
We are considering switching from the Washington UW IMAP server to Dovecot for performance reasons, but we make use of the feature in the UW server that automatically moves new email from the mail spool to the IMAP INBOX. Has anyone implemented this in Dovecot, or considered implementing it ? We have a large number of users, so cannot easily change the way that we deliver email. -- Adrian Barker, Information Systems University College London, Gower Street, London WC1E 6BT External phone: +44 20 7679 5140, Fax (+44) 20 7388 5406 Email: [EMAIL PROTECTED]
Re: [Dovecot] Moving new email from the mail spool to the inbox
Hi Adrian, I'm thinking this is more of an issue with your MTA, as usually that's responsible for delivering into the mailbox's Inbox. You might want to look at Dovecot's LDA, deliver (http://wiki.dovecot.org/LDA). Deliver takes an e-mail piped from your MTA, with appropriate options on the command-line, and delivers it into the relevant mailbox correctly. Regards, Andy. Adrian Barker wrote: We are considering switching from the Washington UW IMAP server to Dovecot for performance reasons, but we make use of the feature in the UW server that automatically moves new email from the mail spool to the IMAP INBOX. Has anyone implemented this in Dovecot, or considered implementing it ? We have a large number of users, so cannot easily change the way that we deliver email.
[Dovecot] Subfolders with IMAP
Hello, How can I configure dovecot in order to allow subfolders on IMAP directories ? I dont find in the dovecot.conf file Thanks Sophie
Re: [Dovecot] Moving new email from the mail spool to the inbox
Thanks for replying. We cannot easily change the way we deliver email, as we have over 30,000 users, who use a mixture of imap, pop and Unix email clients, so we have to continue to deliver email to a central mail spool. The MTA that we run is Exim, which has the flexibility to deliver into the 'Inbox', but we need to remain compatible with non-IMAP mailers. Adrian Barker, University College London. Andy Shellam wrote: Hi Adrian, I'm thinking this is more of an issue with your MTA, as usually that's responsible for delivering into the mailbox's Inbox. You might want to look at Dovecot's LDA, deliver (http://wiki.dovecot.org/LDA). Deliver takes an e-mail piped from your MTA, with appropriate options on the command-line, and delivers it into the relevant mailbox correctly. Regards, Andy. Adrian Barker wrote: We are considering switching from the Washington UW IMAP server to Dovecot for performance reasons, but we make use of the feature in the UW server that automatically moves new email from the mail spool to the IMAP INBOX. Has anyone implemented this in Dovecot, or considered implementing it ? We have a large number of users, so cannot easily change the way that we deliver email. -- Adrian Barker, Information Systems University College London, Gower Street, London WC1E 6BT External phone: +44 20 7679 5140, Fax (+44) 20 7388 5406 Internal phone: x 25140 Email: [EMAIL PROTECTED]
[Dovecot] sporadic slow/non response, problems copying to sent folder
After experiencing these symptoms through many of the release candidates, we've been at v1.0.0 now for a few weeks, and they're still there. Perhaps a config issue with my setup (mbox locks?). It's really too disrupting to continue using this way. I've included symptoms, client info, mta info, log entries and config file. What other information can I provide? Please advise. Thanks, Danno symptoms: 1. Coming back to the idle client, and clicking on a newly arrived message, often a long delay (seems like minutes, sometimes) will occur before the message loads from the server. 2. Sending messages, as often as not, the client will stall, sometimes indefinitely, on copying message to sent folder. client: * usually not more than 2-3 clients running at any time. * Thunderbird 1.5.0.10 (on XP) * Thunderbird 1.5.0.5 (on FreeBSD 5.5) mta: * Sendmail 8.13.6/8.13.6 * $sudo sendmail -bt -d0.10 /dev/null | grep HASFLOCK OS Defines: BSD4_4_SOCKADDR HASFCHOWN HASFCHMOD HASFLOCK === log entries May 3 21:27:09 tejas dovecot: imap-login: Login: user=annie, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 21:28:00 tejas dovecot: IMAP(annie): Disconnected May 3 21:28:01 tejas dovecot: imap-login: Login: user=annie, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 21:32:08 tejas dovecot: IMAP(annie): Disconnected for inactivity May 3 21:37:01 tejas dovecot: IMAP(annie): Disconnected May 3 21:37:02 tejas dovecot: imap-login: Login: user=annie, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 21:37:55 tejas dovecot: IMAP(annie): Disconnected in IDLE May 3 21:38:18 tejas dovecot: IMAP(annie): Disconnected in IDLE May 3 21:56:02 tejas dovecot: imap-login: Login: user=danno, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 21:56:17 tejas dovecot: IMAP(annie): Disconnected for inactivity May 3 21:58:32 tejas dovecot: IMAP(danno): Disconnected May 3 22:02:31 tejas dovecot: imap-login: Login: user=danno, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 22:03:14 tejas dovecot: imap-login: Login: user=danno, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 22:14:10 tejas dovecot: IMAP(annie): Disconnected May 3 22:14:38 tejas dovecot: IMAP(danno): Disconnected in IDLE May 3 22:16:24 tejas dovecot: imap-login: Login: user=danno, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 22:16:33 tejas dovecot: imap-login: Login: user=annie, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 22:16:44 tejas dovecot: imap-login: Login: user=annie, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 22:18:36 tejas dovecot: imap-login: Login: user=annie, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 22:19:16 tejas dovecot: IMAP(danno): Disconnected May 3 22:19:17 tejas dovecot: imap-login: Login: user=danno, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS = config $grep -E -v '^ *(#|$)' dovecot.conf protocols = imaps login_process_size = 64 default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u mail_extra_groups = mail verbose_proctitle = yes first_valid_uid = 100 first_valid_gid = 0 mbox_read_locks = flock mbox_write_locks = flock protocol imap { imap_client_workarounds = delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep } protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { postmaster_address = [EMAIL PROTECTED] sendmail_path = /usr/sbin/sendmail } auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root } dict { } plugin { }
Re: [Dovecot] Moving new email from the mail spool to the inbox
Adrian Barker wrote: Thanks for replying. We cannot easily change the way we deliver email, as we have over 30,000 users, who use a mixture of imap, pop and Unix email clients, so we have to continue to deliver email to a central mail spool. The MTA that we run is Exim, which has the flexibility to deliver into the 'Inbox', but we need to remain compatible with non-IMAP mailers. Take a look at the convert_mail plugin option. The example is: convert_mail = mbox:/home/%u:INBOX=/var/spool/mail/%u but something similar might help. There's some discussion in the mail archives. -- Jonathan
Re: [Dovecot] Moving new email from the mail spool to the inbox
Adrian Barker wrote: We are considering switching from the Washington UW IMAP server to Dovecot for performance reasons, but we make use of the feature in the UW server that automatically moves new email from the mail spool to the IMAP INBOX. Has anyone implemented this in Dovecot, or considered implementing it ? We have a large number of users, so cannot easily change the way that we deliver email. Andy Shellam wrote I'm thinking this is more of an issue with your MTA, as usually that's responsible for delivering into the mailbox's Inbox. You might want to look at Dovecot's LDA, deliver (http://wiki.dovecot.org/LDA). Deliver takes an e-mail piped from your MTA, with appropriate options on the command-line, and delivers it into the relevant mailbox correctly. Adrian Barker wrote: Thanks for replying. We cannot easily change the way we deliver email, as we have over 30,000 users, who use a mixture of imap, pop and Unix email clients, so we have to continue to deliver email to a central mail spool. The MTA that we run is Exim, which has the flexibility to deliver into the 'Inbox', but we need to remain compatible with non-IMAP mailers. This is not clear at all, why does the number of users effect the delivery method? What mailbox format are you using? -- Kenny Dail [EMAIL PROTECTED]
Re: [Dovecot] Moving new email from the mail spool to the inbox
I guess you're delivering mail to /var/mail/username, and UW-IMAP snarfs (to use the UW term :)) the messages to ~/mbox (if it exists) whenever the user opens INBOX in IMAP. If so, I guess the problem is the Unix file-system clients which expect to see mail in /var/mail/username? Dovecot can do both IMAP and POP very well, (and you can specify the mail location for each user independently if you have to). You could configure Exim to deliver directly to the user's ~/mbox if, say, /var/mail/username is empty and ~/mbox exists, and assume that file-system clients will never have a ~/mbox or let /var/mail/username be empty. A bit yucky though! It might also be possible to write a Dovecot plugin to emulate the UW-IMAP snarf behaviour, but as far as I know, nobody has. We never used the snarf behaviour ourselves (except accidentally, when the new version of UW-IMAP I'd compiled had it built in by default, unnoticed by me, and a few ancient users had ~/mbox files ...) I have to say that our UW-IMAP - Dovecot transition was painless (transparent!) and that the performance gains were huge (otherwise we'd still be pruning user's INBOXes into folders for them every few months). Best Wishes, Chris Adrian Barker wrote: Thanks for replying. We cannot easily change the way we deliver email, as we have over 30,000 users, who use a mixture of imap, pop and Unix email clients, so we have to continue to deliver email to a central mail spool. The MTA that we run is Exim, which has the flexibility to deliver into the 'Inbox', but we need to remain compatible with non-IMAP mailers. Adrian Barker, University College London. Andy Shellam wrote: Hi Adrian, I'm thinking this is more of an issue with your MTA, as usually that's responsible for delivering into the mailbox's Inbox. You might want to look at Dovecot's LDA, deliver (http://wiki.dovecot.org/LDA). Deliver takes an e-mail piped from your MTA, with appropriate options on the command-line, and delivers it into the relevant mailbox correctly. Regards, Andy. Adrian Barker wrote: We are considering switching from the Washington UW IMAP server to Dovecot for performance reasons, but we make use of the feature in the UW server that automatically moves new email from the mail spool to the IMAP INBOX. Has anyone implemented this in Dovecot, or considered implementing it ? We have a large number of users, so cannot easily change the way that we deliver email. -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, [EMAIL PROTECTED] IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
[Dovecot] read only bug?
Hello All, I have been still struggling with the read only maildir and I think I found something: dovecot wants to rename a file but I/it have/has no rights to do that: dovecot: 2007-05-04 21:30:14 Error: IMAP(bela): rename(/home/store/oldmails/.personal/cur/1154939281.5.pc1.S=1879:2,S, /home/store/oldmails/.personal/new/1178307014.P8610Q0M347618.pc1) failed: Permission denied Why dovecot wants to rename it? It is really a read only directory. Regards, A. __ 2600 állásból Te is találsz megfelelőt! Mérnöki, értékesítői, asszisztensi, pénzügyi és IT állások a Jobline.hu-n! http://www.jobline.hu
[Dovecot] Converting Courier mailboxes to Dovecot
Hi, I have around 100 mailboxes (maildirs) to convert from Courier IMAP (4.1.3) to Dovecot. (From a recent backup) I've tested a few mailboxes on Dovecot 1.0.0, and while the client doesn't notice any difference (at least in Thunderbird) I'm hoping to get rid of the old Courier folders and convert any useful information they may have into Dovecot. I've tried Timo's migration script (http://www.dovecot.org/tools/courier-dovecot-migrate.pl) but it fails at line 230 with a no file/directory error. At that line, it appears to be finding Courier's keywords folder (courierimapkeywords), and looking for a file called :list. However in my mailboxes, there's no file by that name, only what looks like a set of standard IMAP filenames, most of which are empty files. If I can't salvage anything useful, is there any adverse effects to me deleting all the courier* files/folders from each mailbox and subfolders so when the client connects back when Dovecot's running, it creates it's own UIDs and keywords etc? Thanks Andy.
Re: [Dovecot] read only bug?
Hello, Thanks for your reply. I have some read only maildirs outside my home. Actually those files and directories does not belong to me, I am only a member of the group which can read those files and change to those directories. This is a bit overworried security: not to loose any data by accident deletion. I was happy to be able to use those read-only maildirs in mutt, therefore I tried to make it work under dovecot. I did not want all my emails in one folder, it would be too big, that is why I sorted them into very-old folder and not-so-old-and-recent folder. Hence the very-old folder does not change (except once a year or so). And I was happy when I saw that dovecot supports read-only maildirs. (And for some reasons, dovecot wants to rename the mail from cur to new!) So my questions is: Can I disable this renaming feature somehow? ACLs are great, but this option would be only the next, if this filesystem-permission approach fails to work. Regards, A. __ 2600 állásból Te is találsz megfelelőt! Mérnöki, értékesítői, asszisztensi, pénzügyi és IT állások a Jobline.hu-n! http://www.jobline.hu
Re: [Dovecot] sporadic slow/non response, problems copying to sent folder
On Fri, 04 May 2007 09:23:02 -0700 Danno Coppock [EMAIL PROTECTED] wrote: After experiencing these symptoms through many of the release candidates, we've been at v1.0.0 now for a few weeks, and they're still there. Perhaps a config issue with my setup (mbox locks?). It's really too disrupting to continue using this way. I've included symptoms, client info, mta info, log entries and config file. What other information can I provide? Please advise. Thanks, Danno symptoms: 1. Coming back to the idle client, and clicking on a newly arrived message, often a long delay (seems like minutes, sometimes) will occur before the message loads from the server. 2. Sending messages, as often as not, the client will stall, sometimes indefinitely, on copying message to sent folder. Does this happen when using a client which is on the same LAN as the server? This kind of behavior looks like a network issue. -- Marshal Newrock Ideal Solution, LLC - http://www.idealso.com
Re: [Dovecot] Converting Courier mailboxes to Dovecot
On 5/4/07, Andy Shellam [EMAIL PROTECTED] wrote: If I can't salvage anything useful, is there any adverse effects to me deleting all the courier* files/folders from each mailbox and subfolders so when the client connects back when Dovecot's running, it creates it's own UIDs and keywords etc? I rsync'ed from one mailserver to another and excluded the courier related files. Then I crawled each user's imap folders on both systems with a perlscript and wrote out the results to two files. As you suggest various logs/indexes were created by dovecot and all my accounts were the same. Baring a few deliveries. You will loose folder subscription information remember and I know nothing about shared folder stuff. Btw, the difference between courier and dovecot is insane the dovecot machine I am using is not a 3rd of the courier machine and the speed is quite impressive. I hope to see an additional advantage to using dovcot's lda deliver to prep these indexes as well. -- Gabriel Millerd