- dovecot - dovecot.org

[Dovecot] dovecot-lda - sieve notify support
by Sebastjan Trepca 01 Nov '05

01 Nov '05

Hi, does current implementation of dovecot-lda supports sieve script like this: require ["notify"]; if header :contains "from" "boss(a)example.org" { notify :high "This is probably very important"; } And if it does, what happens in this case ? Is there any configuration for other notification methods? I didn't notice anything in configuration file. Thanks, Sebastjan

1 0

[Dovecot] Usernames and Passwords for Virtual Users Request
by Matt 01 Nov '05

01 Nov '05

A feature I think would be nice. When a single IP hosts email for multiple domains the solution is usually to use the complete email address as the username. I have users that have migrated from Cobalt RAQ's which do not work like that. If a user trys to authenticate with just there username such as "joeb" instead of joeb(a)dirt.com I would like Dovecot to check all the domains it hosts and if it only finds one with the username "joeb" assume thats the one. If multiple domains have the username "joeb" refuse to authenticate without the "@domain" part. Perhaps this is not possible. Sure would be handy though. Oh, it would also be nice to automatically lowercase all usernames before authentication. Matt

4 4

[Dovecot] popa3d migration problem
by Janusz Batko 01 Nov '05

01 Nov '05

Hello, I tried to migrate from popa3d to dovecot but I couldn't manage with 'pop3_reuse_xuidl = yes' option. First of all it turned out that the feature is not supported in dovecot for Fedora Core 4 (dovecot-0.99.14-4.fc4). So I downloaded latest stable release of Dovecot but it didn't have this option included too. Then I compiled the newest alpha version (dovecot 1.0.alpha4) and I tried to login with 'pop3_reuse_xuidl = yes' option enabled and I've got in my logfile the following output: Nov 1 00:58:33 sneogg dovecot: pop3-login: Login: user=<test2>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Nov 1 00:58:33 sneogg dovecot: pop3(test2): Set pop3_uidl_format setting in config file Nov 1 00:58:33 sneogg dovecot: child 32067 (pop3) returned error 89 And my session was disconnected immediately each time after sucessful authentication.. I tried to set up pop3_uidl_format to MD5 (%m) but it didn't work... Let me ask if there is a possibility to migrate from popa3d to dovecot (by using a proper patch maybe?)? I'd thankful for any response... Janusz

3 3

[Dovecot] errors after 1.0a3 -> 1.0a4
by Jakob Hirsch 31 Oct '05

31 Oct '05

Hi, somebody else seeing these? Oct 21 09:14:06 ymmv dovecot: imap-login: Login: user=<xxxx>, method=CRAM-MD5, rip=84.162.151.124, lip=85.214.25.134, TLS Oct 21 09:14:07 ymmv dovecot: imap-login: epoll_ctl(): No such file or directory Oct 21 09:14:07 ymmv dovecot: child 11419 (login) returned error 89 mailbox access fails after that. Had this already yesterday, then downgraded to alpha3 and it worked again, upgraded again and it kept working. Strange thing is, access through squirrelmail works perfect, but using Thunderbird gives these errors. I'm using maildir with epoll and inotify, if that matters.

3 7

[Dovecot] login_user & first_valid_uid
by Alexander Shikoff 30 Oct '05

30 Oct '05

Hi all, I have next settings in .conf file ... # # Login user for SQL-based virtual users # login_user = dovecot first_valid_uid = 100 first_valid_gid = 100 ... System user dovecot has UID/GID = 101/101. But every time when user logins I see in log file Oct 29 15:51:25 orion dovecot: Logins with login process UID 101 (user elnino) not permitted (see login_user in config file). Oct 29 15:51:25 orion dovecot: auth(default): Growing pool 'plain_auth_request' with: 1024 Why dovecot generate these warnings and how I can get rid of them? Thanks in advance, Alexander -- Kind Regards, Alexander Shikoff minotaur(a)crete.org.ua

4 8

[Dovecot] [info] Spamcop listing
by /dev/rob0 30 Oct '05

30 Oct '05

Smtp1.song.fi and smtp2.song.fi, our list servers, seem to have gotten listed in the bl.spamcop.net RBL. Spamcop listings are temporary and will time out, and because of occasional major false positives (or perhaps collateral damage?) like this I don't use it to reject mail. Anyone who IS using Spamcop to reject mail has missed much of today's list traffic. -- mail to this address is discarded unless "/dev/rob0" or "not-spam" is in Subject: header

8 13

[Dovecot] Dovecot Alpha 4
by Marcus Don 30 Oct '05

30 Oct '05

Hi We've been using Dovecot as our primary IMAP and POP3 server for around 70,000 users for a couple of months now. On the whole, we've been very pleased with the performance of Dovecot - and are extremely grateful to the developers! However, we have had a few issues, some of which we have yet to resolve. We chose Dovecot because it was the only IMAP/POP3 server we could find that supported direct mysql authentication and both mboxes and maildirs. With exim as our main SMTP server, we were able to convert the inboxes and imap folders for all 70,000 users from mboxes to maildirs without any downtime whatsoever! For those who are interested, we have a cluster of 5 web/imap servers (running our own webmail software) and a further 5 pop servers all placed behind 2 Zeus load balancers and running RHEL 4 (actually CentOS 4.1). Storage is provided by an EMC Clariion device, which is mounted via NFS onto all servers in the cluster over gigabit ethernet. 1. index files The main problem has always been the index files becoming corrupted. This seems to have improved with the Alpha 4 release, but still happens for several users each day. Perhaps it would be possible for Dovecot to just delete index files and re-create them when they are corrupted, rather than just erroring? Also, how do you turn off index files altogether? Even when mail_never_cache_fields is set for all available fields, they still get created. Another issue relating to the index files is that, if a user is deleted and then another user created with the same name, dovecot doesn't have permissions to re-write the index files, because it has a different uid. So, whenever a user is deleted, we have to delete the index files from every machine in the cluster. We could store index files on the NFS device, but this would affect performance (and might cause locking problems). A better solution would be to make the uid one of the variables available in default_mail_env. By naming index files by uid rather than username, this wouldn't be an issue. 2. initgroups() We use an nss-mysql to store all non-administrative system users in a mysql database. We often encounter problems with applications that use the initgroups() function, since this returns all users and groups - which in our case returns masses of data from mysql. When using mysql (or ldap etc) for authentication, it would be useful if there were an option to prevent additional system lookups. At present, we have to comment out the following in /src/lib/restrict-access.c, or the server load goes through the roof: if (initgroups(env, gid) != 0) { i_fatal("initgroups(%s, %s) failed: %m", env, dec2str(gid)); } 3. base_dir permissions bug Since the alpha 4 release, it seems that the permissions dovecot automatically sets for the base_dir are not sufficient to allow the authentication user to access sockets, unless this user belongs to the same group as the login user - which is contrary to the instructions in the documentation. I'm pretty sure this is a bug, but perhaps someone could confirm. 4. authentication caching Also since the alpha 4 release, we have found that, once the authentication cache is full, all subsequent login attempts for users that haven't been cached return "password mismatch". I though this might be a conflict with nscd, but it happens whether nscd is running or not. So, for the time being, we have had to disable the authentication cache. I'd be very keen to hear from anyone who has any feedback on any of the points above. Thanks Marcus -- Marcus Don Applications Development Manager Namesco Limited Main Line: +44 (0)870 120 8888 Main Fax: +44 (0)870 120 8008 Tech Support: +44 (0)870 162 4950 Email: mdon(a)names.co.uk Website: http://www.names.co.uk Address: Acton House, Perdiswell Park, Worcester, WR3 7GD This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. ------------------------------------------------------------------------ --------------------------------------- | Free Dial-up - no need to register! | --------------------------------------- Namesco Limited provides Free dialup access to anyone that wishes to use it. You do not even have to be a customer, there is no need to register and is especially handy if you are unable to connect with your current provider. Simply use the following details: Dialup Number: 0844 535 2100* Username: namesco Password: easydialup * Local call rate charges apply, 33% Cheaper than BT's 0845 local call rate. If you need any help in configuring the Free Dial-up service on your computer, please do not hesitate to call us on 0870 162 4950.

4 4

[Dovecot] Dovecot RPMs for Redhat Enterprise 3 repository?
by Erick Perez 30 Oct '05

30 Oct '05

Where can I find RPMs for RHEL 3? -- ------------------------------------------- Erick Perez Linux User 376588 http://counter.li.org/ (Get counted!!!) Panama, Republic of Panama

3 3

[Dovecot] Dovecot reports zero messages erroneously
by Chris Spiegel 29 Oct '05

29 Oct '05

On October 11, Mark Farmer reported a problem about not being able to see new mails. I'm running into the same issue. Even though cur/ and new/ contain messages, Dovecot reports that there aren't any. This problem seemed to start happening in alpha3 (and persists in alpha4). When I revert back to alpha2, the messages show up again. It looks like a problem with the dovecot.index* files. When I delete them, alpha4 can serve up the mails just fine, and will in fact keep working for a little while. Eventually (within a few hours, although I'm not sure what causes it), dovecot thinks things are empty again. Like Mark, I'm using Postfix.. I'm not sure if that has anything to do with the problem but I thought it'd be worth pointing out. If there are any specific things you'd like me to do to try to pin down this problem, let me know. Chris

2 4

[Dovecot] Some errors with 1.0.alpha4
by Nicolas STRANSKY 29 Oct '05

29 Oct '05

Hi, I'm getting three types of errors with latest Dovecot compiled for x86_64 GNU/Linux Debian. Oct 29 12:47:57 rouge imap-login: unable to dlopen /usr/lib/sasl2/libntlm.so.2: /usr/lib/sasl2/libntlm.so.2: failed to map segment from shared object: Cannot allocate memory Oct 29 12:47:57 rouge pop3-login: unable to dlopen /usr/lib/sasl2/libntlm.so.2: /usr/lib/sasl2/libntlm.so.2: failed to map segment from shared object: Cannot allocate memory I have no idea why there is this error, but it comes each time a user logs in, with no other severe effect. Oct 29 01:28:54 rouge dovecot: imap(glondu): pool_system_malloc(): Out of memory Oct 29 01:28:54 rouge dovecot: child 5642 (imap) returned error 83 (Out of memory) Oct 29 01:38:10 rouge dovecot: imap(glondu): pool_system_malloc(): Out of memory Oct 29 01:38:10 rouge dovecot: child 5639 (imap) returned error 83 (Out of memory) Oct 29 01:49:22 rouge dovecot: imap(glondu): pool_system_malloc(): Out of memory Oct 29 01:49:22 rouge dovecot: child 8839 (imap) returned error 83 (Out of memory) The mailbox for this user is not bigger that 10MB and dovecot mail_process_size is set to default setting so I don't see why there could be a "Out of memory" error. Oct 28 18:00:45 rouge dovecot: imap(vidal): Lost transaction log file /var/dovecot-indexes/vidal/.INBOX/dovecot.index.log seq 1 Oct 28 18:00:45 rouge dovecot: imap(vidal): Lost transaction log file /var/dovecot-indexes/vidal/.INBOX/dovecot.index.log seq 1 Oct 28 18:00:56 rouge dovecot: imap(vidal): Lost transaction log file /var/dovecot-indexes/vidal/.INBOX/dovecot.index.log seq 1 Oct 28 18:00:56 rouge dovecot: imap(vidal): Lost transaction log file /var/dovecot-indexes/vidal/.INBOX/dovecot.index.log seq 1 This error caused the user's mailbox to be unreadable, and erasing the indexes resolved the problem, but I would have expected Dovecot to have done it itself if the indexes were corrupted ? Hope this feedback helps, -- Nico

1 0