May 2010 - dovecot - dovecot.org

[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

[Dovecot] dovecot and pigeonhole
by Vasiliy G Tolstov 06 May '10

06 May '10

Hello. Today i'm compile dovecot and pigeonhole from hg repo. After start dovecot i get errors in log like this: May 6 12:04:15 selfip dovecot: imap: Error: dlopen(/usr/lib/dovecot/lib90_sieve_plugin.so) failed: /usr/lib/dovecot/libdovecot-sieve.so.0: undefined symbol: mail_deliver_get_log_var_expand_table Google sasys, that this functions added in dovecto 2010-04-26, why a get this error when load sieve plugin? Thnak You. -- Vasiliy G Tolstov <v.tolstov(a)selfip.ru> Selfip.Ru

2 2

[Dovecot] !include
by Andre Hübner 06 May '10

06 May '10

dovecot 1.2.11 Hello, i do some tests with: !include /etc/dovecot/conf.d/*.conf dovecot fails to start if /etc/dovecot/conf.d/ is empty. Is this a expected behaviour? !include_try works without error but seems to me to be more usual when explicit, complete filename is given. is a little bit strange in contrast to behaviour of other servertypes which support a include-directive. Thanks, Andre

1 0

Re: [Dovecot] Dovecot Won't start on SLITAZ Linux
by Ludovic LEMARINEL 06 May '10

06 May '10

2010/5/6 Ludovic LEMARINEL <l.lemarinel(a)gmail.com> > 2010/5/6 Tom Hendrikx <tom(a)whyscream.net> > > On 06/05/10 13:40, Ludovic LEMARINEL wrote: >> > 2010/5/6 Charles Marcus <CMarcus(a)media-brokers.com> >> > >> >> On 2010-05-06 4:51 AM, Ludovic LEMARINEL wrote: >> >>> I've just compiled dovecot under Slitaz, but I can't get it to >> >>> run... >> >>> >> >>> It always die with this message in log : >> >>> >> >>> 2010-05-06 12:35:12 dovecot: Info: Dovecot v1.2.11 starting up >> >>> 2010-05-06 12:35:12 dovecot: Fatal: setrlimit(RLIMIT_DATA, 256): >> >>> Operation not permitted >> >> >> >> Google is your friend. Simply highlighting the above error: >> >> >> >> Fatal: setrlimit(RLIMIT_DATA, 256): Operation not permitted >> >> >> >> Provides the answer: >> >> >> >> http://tinyurl.com/25rmjod >> >> >> >> > >> > Thanks for your answer, but no, this page does not provide the answer. >> > The error message this guy gets is not the same as me >> >> Your original post says it does. If you receive another error message, >> please add it to your problem report. Also, please try to start dovecot >> from the commandline (as suggested in the url from Charles), and tell us >> about its behaviour, output and logging. >> >> > , and I don't have any >> > "/etc/security/limits.conf" file, so I can't change this setting . >> >> Dovecot tells you only what setting to to adjust. Where you put your >> settings is largely dependant on your OS or distro implementation. >> >> >> Ow, and please do not top-post. >> >> Regards, >> Tom >> > > > I've tried to run dovecot from the command line : it says what was the last > error (see my first post), and then nothing more. > When I do "ps", I can't see any process running, and the log says dovecot > finished... > > No more message than this :( > I'm going to try with 2.0 beta, and if no luck, I'll try to go down to 1.1. > Some news from my problem : I've tried 2.0 beta, 1.1, and both didn't worked. I went down to v1.0.15, and it works... Still haven't found what's wrong with newer versions...

1 0