- dovecot - dovecot.org

[Dovecot] Dovecot version mismatch - after restart
by edeis 07 May '10

07 May '10

Getting the followng error when managesieve is enabled. Any other post I've read says this problem is because the service hasn't restarted after upgrade. I've restarted dovecot & postfix many times, reboot machine too. Still get the error. Racking my brains on this!! May 7 13:21:19 drizzle dovecot: dovecot: Created login processes successfully, unstalling May 7 13:21:20 drizzle dovecot: managesieve-login: Fatal: Dovecot version mismatch: Master is v1.2.11, login is v1.2.10 (if you don't care, set version_ignore=yes) May 7 13:21:20 drizzle dovecot: dovecot: Temporary failure in creating login processes, slowing down for now May 7 13:21:20 drizzle dovecot: managesieve-login: Fatal: Dovecot version mismatch: Master is v1.2.11, login is v1.2.10 (if you don't care, set version_ignore=yes) Running CentOS5.4. Installed Packages from atrpms dovecot.x86_64 1:1.2.11-3_108.el5 installed dovecot-managesieve.x86_64 0.11.11-0_4.el5 installed dovecot-sieve.x86_64 1:0.1.15-4.el5 installed Here's my dovecot settings: [root@drizzle /]# dovecot -n # 1.2.11: /etc/dovecot.conf # OS: Linux 2.6.18-164.15.1.el5.028stab068.9 x86_64 CentOS release 5.4 (Final) protocols: imap imaps pop3 pop3s managesieve ssl_cert_file: /etc/ssl/certs/mydomain.com.crt ssl_key_file: /etc/ssl/certs/mydomain.com.key 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_executable(managesieve): /usr/libexec/dovecot/managesieve-login mail_privileged_group: mail mail_location: maildir:%h 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_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 mail_plugin_dir(managesieve): /usr/lib64/dovecot/managesieve namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes lda: postmaster_address: me(a)mydomain.com auth default: mechanisms: plain login passdb: driver: checkpassword args: /var/www/ispcp/engine/ispcp-dovecot-mngr userdb: driver: sql args: /etc/dovecot/dovecot-sql-domain.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql-aliasdomain.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql-subdomain.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: mail plugin: sieve: /etc/dovecot/sieve/dovecot.sieve [root@drizzle /]# -- View this message in context: http://old.nabble.com/Dovecot-version-mismatch---after-restart-tp28491245p2… Sent from the Dovecot mailing list archive at Nabble.com.

1 0

[Dovecot] Requiring STARTTLS only on some networks
by Thomas Hummel 07 May '10

07 May '10

Hello Timo, is there a way, either in 1.2.x or in 2.x to activate disable_plaintext_auth=yes only for some address or network ? The idea would be to enable clients from the internal networks to keep making clear text connections while forbidding it to the rest of the world. Thanks. -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

3 6

[Dovecot] Tracing sieve execution
by Jerry 07 May '10

07 May '10

I have just recently begun learning how to use sieve. For the most part, it works fine. The problem is that I have created some rather complicated rules. Occasionally, an e-mail will get sorted incorrectly and I am not able to easily determine what rule caused it to occur. Is there any way or utility that I could use to actually see what rule or line in the sieve file caused the action? -- Jerry Dovecot.user(a)seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ I hate it when my foot falls asleep during the day cause that means it's going to be up all night. Steven Wright

2 1

[Dovecot] dovecotpw documentation
by Phil Howard 07 May '10

07 May '10

Where can I find documentation on how to use the "dovecotpw" program that I was referred to? No man page. No wiki. Very little from "dovecotpw -h". What I need to do is generate the "passwd-file" contents with an MD5 scheme (the one equivalent to /etc/shadow is preferred).

1 0

[Dovecot] Iphone and Dovecot - 2-way sync
by Lucio Godoy 07 May '10

07 May '10

Hi All; Does the Iphone and Dovecot works well? Do you get full IMAP sync with IPHONE <=> DOVECOT <=> Outlook, pls? thanks Lucio =========================================================== The Home CCTV Security System made easy! http://www.kaduco.com/our-list-products-services/cctv-security-camera-syste… _________________________________________________________________ http://clk.atdmt.com/UKM/go/197222280/direct/01/ We want to hear all your funny, exciting and crazy Hotmail stories. Tell us now

5 9

[Dovecot] ACLs and public folders
by hyperbatus＠gmx.de 07 May '10

07 May '10

Dear list, I am using dovecot 1.0.15 on Debian Lenny. I have a public folder, I use ACL / vfile (without public ACL), and I use maildir / vmail. Now I have two questions: 1) http://wiki.dovecot.org/ACL states: "Mailboxes in public namespaces don't have owners, so by default no-one can access them." The same document, when explaining the meaning of the k flag in the ACLs, states: "Mailboxes can be created (or renamed) under this mailbox (there is no recursion, so creating a mailbox under this mailbox's child uses only the child's ACLs)" I have placed an ACL (dovecot-ACL) at the root of the public namespace (all rights to anyone). The public namespace was appearing correctly in my IMAP client. Then I have copied a large folder with hundreds of nested subfolders (nesting level > 3) from another account to the root of the public namespace. According to the documentation mentioned above, this should not have been possible (if I got the docs right): The first nesting level of folder should have been created, but not the messages in them and for sure not the deeper nested folders. There is no dovecot-acl within a single of the first level folders (I have verified this), so no one should have access to them. Nevertheless, in addition to the succesful copy, I can see every folder and every message in my IMAP client, I can delete and so on. Could some please explain if I got the docs wrong? 2) If there really is no ACL recursion, how are we supposed to copy large folder structures (perhaps thousands of folders, nested to 5 levels deep) to a public namespace? Do we need to create all folders by hand, then place the dovecot-acl in each folder, and then copy the messages to each folder by hand? Do we need to switch to global ACLs so that we can establish a master user for doing the act of filling the public space? Or is there a dovecot module which, immediately after creating a folder, looks into the parent folder of the new folder and copies the dovecot-acl from the parent folder to the new folder? Currently, I am very happy that dovecot didn't what it should do according to my understanding of the documentation (since I really needed to copy this folder structure to the public namespace), but on the other hand, I am a bit puzzled now not knowing if the documentation is wrong, my understanding of it is wrong or the source code is wrong :-) Thanks you very much for any help, Peter Here is the output of dovecot -n: # 1.0.15: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps listen: 192.168.20.23 ssl_cert_file: /etc/dovecot/imap-ssl.home.omeganet.de.crt ssl_key_file: /etc/dovecot/imap-ssl.home.omeganet.de.key ssl_parameters_regenerate: 24 ssl_cipher_list: ALL:!LOW login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_processes_count: 1 login_max_processes_count: 32 max_mail_processes: 32 mail_privileged_group: mail mail_location: maildir:~/Maildir mail_cache_fields: mail_never_cache_fields: mail_plugins: acl namespace: type: private inbox: yes namespace: type: public prefix: Archive. location: maildir:/home/vmail/archive:INDEX=~/Maildir/archive auth default: cache_size: 1 cache_ttl: 600 worker_max_count: 4 passdb: driver: passwd-file args: /etc/dovecot/passdb userdb: driver: static args: uid=vmail gid=vmail home=/home/vmail/%u socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: root plugin: acl: vfile -- GMX DSL: Internet, Telefon und Entertainment für nur 19,99 EUR/mtl.! http://portal.gmx.net/de/go/dsl02

2 2

[Dovecot] during change sql password on squirrelmail
by Yavuz Maşlak 07 May '10

07 May '10

Hello I use squirrelmail1.4.20, compatible2, change_sql plugin, dovecot, postfix, mysql,virtualuser. I can change my email password successfully on squirrelmail. When I change my password the squirrelmail throw me a page which contains an error as followings; "This page request could not be verified and appears to have expired." how can I correct this issue?

2 1

[Dovecot] log_path and info_log_path - ownership of parent directory
by Phil Howard 07 May '10

07 May '10

The Ubuntu package didn't create the directory for these. What ownership/permissions are needed for it? Does it need to be owned by the dovecot user?

2 1

[Dovecot] disable plaintext auth ... only for some addresses
by Phil Howard 06 May '10

06 May '10

I'd like to disable plaintext authentication (e.g. only allow authentication that does STARTTLS or connects on SSL/TLS only ports) only for certain (most) IP addresses. I want to exempt a few addresses (users coming over known VPNs). Fortunately, all this is coming in over a firewall (Sonicwall) in which I can NAT traffic by IP address to go to specific port numbers. So, if I can establish a different disable_plaintext_auth policy by port number (for extra port numbers I'll choose later), that would let me accomplish this. If I cannot do this, then my only alternative is making the SSL/TLS only ports the only ones open to the internet, and use the non-SSL/TLS ports only for the VPNs (with disable_plaintext_auth = no). But I read somewhere that this is discouraged. What say ye?

1 0

[Dovecot] adding users to passwd-file
by Phil Howard 06 May '10

06 May '10

Is there a tool equivalent to the system "passwd" command (or maybe "adduser" or "useradd") that can support a passwd-file by setting a password, encrypting it with the salted MD5 scheme? The system "passwd" command doesn't have an option to "do it to this alternate file instead of /etc/shadow".

4 5