- dovecot - dovecot.org

[Dovecot] Dovecot strong or not for a big Webmail architecture
by John fistack 03 Aug '07

03 Aug '07

Hello, Do you think Dovecot could handle millions of active users in a big architecture ? This cluster could be for example (each server is a bi quad Xeon 2.66 Ghz) : - 40 Dovecot servers - 4 LVS - 20 Apache+PHP - 2 Openldap - 20 Postfix + ClamAV + SpamAssassin - 1 NFS Netapps For millions of user it could be multiple different clusters of 40 Dovecot servers with 1 Netapp for each cluster. I want to work in NFS. I've experimented problem with Cyrus and NFS on Netapp. I want to use maildir, I can manage limitations of inodes with Netapp. I know webmail.us use Dovecot, what is the most big dovecot architecture known ? Do you think Dovecot can handle 1 million of active users in a good architecture ? Do you think it's a good solution to use one synchronised local Openldap on each server Dovecot ? Do you think It's possible to use Postgresql or MySQL instead of Openldap ? Are cyrus or courrier-imap better solutions ? Someone say "Zimbra is highly scalable and fast", I think Zimbra could be to heavy in this architecture, is Dovecot scalable ? Thank you for your ideas. Regards. John Fistack _____________________________________________________________________________ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail

3 2

[Dovecot] dovecot 1.0.2, sieve 1.0.2 and regex
by Alexander Hoogerhuis 03 Aug '07

03 Aug '07

I've just ported a largeish procmail script across to sieve and want to get to use wildcards in filing mail and can't seem to get regex to work. The script starts nicely with: > require ["fileinto","regex","envelope","vacation","regex"]; and a bit down these few lines comes into play: > elsif header :regex "From" "logwatch.*stuff.com" { > fileinto "INBOX.Admin/Logwatch Stuff"; > } and regex just never seem to catch. I have 50ish machines in the stuff.com domain, and writing an induvidual section like this works: > elsif header :contains "From" "logwatch(a)a.stuff.com" { > fileinto "INBOX.Adin/Logwatch Stuff"; > } > elsif header :contains "From" "logwatch(a)b.stuff.com" { > fileinto "INBOX.Adin/Logwatch Stuff"; > } etc. But this shouldn't be neccesary? mvh, A

1 1

[Dovecot] how to "authenticate plain" ???
by Steffen Brunk 02 Aug '07

02 Aug '07

Hello list, my name is Steven and of course: I got a problem... we are using dovecot 0.99 because it´s the actual stable version for RedHat 4 Enterprise. I am trying to authenticate using "PLAIN" but I don´t know how. that´s what I am doing: telnet conny.MYDOMAIN.de 143 Trying IP.AD.RE.SS... Connected to conny.MYDOMAIN.de. Escape character is '^]'. * OK dovecot ready. a1 authenticate plain + a1 NO Authentication failed. what do I have to send after receiving the "+"-symbol? dovecot is waiting for something base64-encoded and I tried to give him by typing my username and pass and encrypted it here : http://www.php-einfach.de/base64_generator.php But I don´t know the correct syntax and it drives me crazy.... thanks for ANY help Steve .

3 2

[Dovecot] Editing sieve files
by jalal 02 Aug '07

02 Aug '07

Hi all I've got a standard dovecot setup: home is /var/spool/vmail/domain/user/ uid: vmail gid: vmail Sieve file is: /var/spool/vmail/domain/user/.dovecot.sieve if i want to change the dovecot-sieve file to modify the rules (or even let my users do it at some point) then it has to been done by root. Is there a way to setup the sieve plugin so a user can create his own rules? sort of like ~/.procmailrc TIA jalal

2 2

[Dovecot] v1.0.3 released
by Timo Sirainen 02 Aug '07

02 Aug '07

http://dovecot.org/releases/1.0/dovecot-1.0.3.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.3.tar.gz.sig - deliver: v1.0.2's bounce fix caused message to be always saved to INBOX even if Sieve script had discard, reject or redirect commands. - LDAP: auth_bind=yes and empty auth_bind_userdn leaked memory - ACL plugin: If user was given i (insert) right for a mailbox, but not all s/t/w (seen, deleted, other flags) rights, COPY and APPEND commands weren't supposed to allow saving those flags. This is technically a security fix, but it's unlikely this caused problems for anyone. - ACL plugin: i (insert) right didn't work unless user was also given l (lookup) right. - Solaris: Fixed filesystem quota for autofs mounts.

7 10

[Dovecot] migrating users
by Pete McEvoy 02 Aug '07

02 Aug '07

Hi. I've been migrating users from mbox to maildir on a new server running dovecot 1.0 - is there any method I can employ to prevent my pop3 users having to redownload mails after I move them? Thanks -- Pete

1 1

[Dovecot] Shared mailboxes v1.0.3
by Bruce Bodger 02 Aug '07

02 Aug '07

On Jul 28, 2007, at 3:47 PM, Sergey A. Kobzar wrote: > > BTW /home/mail/public/ is not a mailbox and must not contain cur new > and tmp folders. As Timo said this bug was fixed in 1.1. > Just for the record, and I realize it's not scheduled to be fixed until v1.1, this is still "broken" in v 1.0.3. Dovecot still creates cur, tmp, and new in /home/mail/public (or applicable, as configured). Doesn't hurt anything but just wanted to make the point. > http://wiki.dovecot.org/SharedMailboxes B. Bodger

1 0

Re: [Dovecot] Missing MIME-Version header in e-mails.
by Bill Boebel 02 Aug '07

02 Aug '07

On Wed, August 1, 2007 8:36 pm, Tan Shao Yi <tansy(a)pacific.net.sg> said: > Will it be possible to make this available in the 1.0 branch? UW-IMAP > seems to continue to process e-mails without the MIME-Version, so long as > it has the Content-Type or -Encoding header. It's an easy patch if you want to apply it to your installation. Probably something like this, although I haven't tried it... src/lib-mail/message-parser.c @225: - if (!hdr->eoh && strcasecmp(hdr->name, "Mime-Version") == 0) { + //if (!hdr->eoh && strcasecmp(hdr->name, "Mime-Version") == 0) { /* it's MIME. Content-* headers are valid */ part->flags |= MESSAGE_PART_FLAG_IS_MIME; - }

1 0

[Dovecot] mbox inbox default
by bhayden＠umn.edu 01 Aug '07

01 Aug '07

HI Timo & all. We're an mbox environment, inboxes in /var/mail/$USER (I'll include dovecot -n output at the bottom of this mail). mail_location is set accordingly for deliver. I'd assumed that if the /var/mail/$USER file doesn't exist, dovecot would create it, but we've discovered from experience (and I verified it in mbox-storage.c) that if access(path, R_OK|W_OK) fails--as it does if the file doesn't exist--that dovecot defaults then to delivering in root_dir/inbox. I'm curious why this is. It seems like if the configured INBOX file doesn't exist, dovecot should create it if possible; it's a different case than if, say, the user doesn't have write access to that directory, in which case it of course would be appropriate to fall back to some other location rather than rejecting mail. Is there something I'm missing that makes my idea wrong? Thanks, -Brian Hayden OIT Internet Services University of MN # ./dovecot -n # /etc/opt/dovecot/dovecot.conf syslog_facility: local6 protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/opt/openssl/certs/dovecot.pem ssl_key_file: /etc/opt/openssl/private/dovecot.pem shutdown_clients: no login_dir: /var/opt/dovecot/run/dovecot/login login_executable(default): /opt/dovecot/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot/libexec/dovecot/pop3-login login_log_format_elements: user=<%u> pid=<%p> method=%m rip=%r lip=%l %c login_processes_count: 32 login_max_processes_count: 6000 max_mail_processes: 8192 first_valid_uid: 100 mail_location: mbox:~:INBOX=/var/mail/%u:INDEX=/var/mail/.dovecot-index/%1u/%u/ mail_debug: yes mbox_lazy_writes: no mail_executable(default): /opt/dovecot/libexec/dovecot/mail_path.sh mail_executable(imap): /opt/dovecot/libexec/dovecot/mail_path.sh mail_executable(pop3): /opt/dovecot/libexec/dovecot/pop3 mail_plugins(default): acl mail_plugins(imap): acl mail_plugins(pop3): mail_plugin_dir(default): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot/lib/dovecot/pop3 mail_log_prefix: [%p] %Us(%u): mail_log_max_lines_per_sec: 0 imap_client_workarounds(default): delay-newmail outlook-idle tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv namespace: type: private separator: / location: mbox:~:INBOX=/var/mail/%u:INDEX=/var/mail/.dovecot-index/%1u/%u/ inbox: yes namespace: type: private separator: / prefix: mail/ location: mbox:~/mail/:INDEX=/var/mail/.dovecot-index/%1u/%u/ hidden: yes namespace: type: private separator: / prefix: ~/mail/ location: mbox:~/mail/:INDEX=/var/mail/.dovecot-index/%1u/%u/ hidden: yes namespace: type: private separator: / prefix: ~%u/mail/ location: mbox:~/mail/:INDEX=/var/mail/.dovecot-index/%1u/%u/ hidden: yes namespace: type: private separator: / prefix: Shared/ location: maildir:~/Maildir/Shared/:INDEX=/var/mail/.dovecot-index/%1u/%u/shared:CONTROL=/var/mail/.dovecot-index/%1u/%u/shared-control auth default: username_format: %Lu passdb: driver: pam args: session=yes * userdb: driver: passwd plugin: acl: vfile:

2 2

[Dovecot] High cpu usage OpenSolaris
by Gary Gendel 01 Aug '07

01 Aug '07

All, Nevermind... I discovered the problem. It was in the Solaris Sun Studio 12 compiler. I created a debug version to begin testing, but that version worked without sucking up the cpu. So it looks like the optimizer messed up. If I used the -fast optimization, it sucks up cpu, but with -xO5 all is well. Gary --------------------------------------------------------------------- Hi, I've built 64-bit dovecot 1.0.2 on Opensolaris to replace version 1.0.0rc10. It functions fine, but when I connect, it eats up all available cpu. My guess is that the poll thread is running continuously. Any ideas on what I should do to verify this or does anyone know of a fix? Thanks, Gary

4 4