- dovecot - dovecot.org

[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 29 Oct '05

29 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

[Dovecot] Basic Configuration
by Ashvin Meetoo 29 Oct '05

29 Oct '05

Hi, Been setting up a backup mail server just in case... using FC4... basic configuration... postfix/dovecot... imap pop3... When I send an external email, example(a)gmail.com, everything works well. When I send an internal email, i.e. to another user, user receives a blank email? Everytime he clicks on get mail a new empty email is added... checked /<user>/Mailbox/new folder email is there and header is ok. What can be the matter? Did this thousand times before and even reinstalled FC4... same problem. Also, I have tried: echo test | mail root but mail gives me : No mail for root Help please. __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

1 0

[Dovecot] dovecot-lda cvs
by Rene Luria 28 Oct '05

28 Oct '05

I am using dovecot-lda from cvs (checked out on september the 21st) and dovecot 1.0alpha2 (not yet upgraded ok). I have a strange feeling about "redirect" feature. Let's see two sieve scripts examples: # ex1 require ["fileinto", "vacation"]; if header :is ["blabla"] "blabla" { fileinto "blabla"; } redirect "user(a)domain.com"; keep; # ex2 require ["fileinto", "vacation"]; redirect "user(a)domain.com"; keep; In both cases, I redirect mail to an external address, keeping a copy. (this would emulate redirect :copy "user(a)domain.com"; which is still not implemented). In first example I run a test on headers, but not on the second. The effect is that in the second example, the forwarded mail is "complete" (exactly the original one with routing header modified), but in the first one, the forwared mail is completely messed up: no Subject header, and so on. This could be because as tests are run on the incoming mail, the working in memory of the mail is changed, and then, forwarded. So when no tests are run, the mail remains intact. How can I deal with this ? Is there some nice hotfix that would prevent a few (like 100'000) users to kill me ? Best regards. -- Rene Luria

3 5

[Dovecot] 1.0alpha3: fcntl() complaints?
by Jeff A. Earickson 28 Oct '05

28 Oct '05

Hi, Since installing 1.0alpha3 this morning, I've seen this syslog complaint a few times. Anything to worry about? A "server too busy" issue? imap(user): fcntl() failed with mbox file /var/mail/user: Resource temporarily unavailable Jeff Earickson Colby College

2 4

[Dovecot] DoveCot 1.0a3 hangs at login
by Justin Finkelstein 28 Oct '05

28 Oct '05

I've just upgraded to 1.0a3 via a freebsd port, and I've begun to notice odd behaviour from Dovecot. After converting my config file settings over to the new format, everything runs fine for an hour or so, then dovecot stops responding: oot@toejamfootball# telnet localhost 143 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. 1 login justin(a)redwiredesign.com password [dovecot then just stops doing anything] * BYE Disconnected for inactivity. Connection closed by foreign host. in the logs, it says: Oct 13 09:43:22 toejamfootball dovecot: imap-login: Disconnected: Inactivity: method=PLAIN, rip=192.168.2.11, lip=192.168.2.43 Oct 13 09:43:22 toejamfootball dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=192.168.2.43 rip=192.168.2.11 resp=AGp1c3RpbkByZWR3aXJlZGVzaWduLmNvLnVrAHBhc3N3b3Jk Oct 13 09:43:22 toejamfootball dovecot: auth-worker(default): sql(x,192.168.2.11): query: SELECT username AS user, MD5(clear) AS password FROM users LEFT JOIN domains ON domains.domain_id = users.domain_id WHERE domain="x" AND username="x" AND users.enabled = 1 AND domains.enabled = 1 Oct 13 09:43:22 toejamfootball dovecot: auth(default): pam(justin(a)x,192.168.2.11): pam_authenticate() failed: authentication error Any clues? I don't use pam for auth anyway, so I just ignore that. When I restart the server and login again it's fine. j.

2 1

[Dovecot] 1.0.alpha3 plaintext authentication problem
by Sergey Redin 28 Oct '05

28 Oct '05

Hello everyone, Since the upgrade to 1.0.alpha3 I experience a strange problem with plaintext authentication. I successfully login first few (2-5) times after the dovecot restart, and then on a reason I cannot login any more (both via POP3 and IMAP). I tried to find out what could be the reason for this but I failed. Nothing is changed inside the user's home directory or /var/run/dovecot, but I cannot login any more. I guess there is something wrong inside dovecot-auth od dovecot process itself. I just start to receive "01 NO Authentication failed." or "-ERR Authentication failed." from dovecot and "Authenticate PLAIN failed: Unsupported authentication mechanism.: method=PLAIN" in my logs, even though I used the same PLAIN two minutes ago without a problem. Here is my dovecot.conf: nevoservice# egrep -v '^[ ]*(\#.*)?$' /usr/local/etc/dovecot.conf protocols = imap pop3 ssl_disable = no ssl_cert_file = /etc/mail/certs/server.crt ssl_key_file = /etc/mail/certs/server.key disable_plaintext_auth = no log_path = /var/log/dovecot/log info_log_path = /var/log/dovecot/info login_user = dovecot login_processes_count = 1 verbose_proctitle = no first_valid_gid = 0 mail_extra_groups = mail mail_debug=yes default_mail_env = mbox:/var/mail/%u maildir_copy_with_hardlinks = yes 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 } auth_verbose = yes auth_debug = yes auth default { mechanisms = plain passdb passwd-file { args = /usr/local/etc/dovecot.passwd } userdb passwd-file { args = /usr/local/etc/dovecot.passwd } user = root } Here are two lines in dovecot.passwd which define the user that I use: wail:password-hash:1050:1032:Administrator wail.spb.ru:/home/wail.spb.ru:::/var/mail/wail wail@nevoservice.ispvds.com:password-hash:1050:1032:Administrator wail.spb.ru:/home/wail.spb.ru:::/var/mail/wail A few lines from my /var/log/dovecot/info file: dovecot: Oct 10 02:03:11 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=82.146.50.34 rip=82.146.63.23 resp=AHdhaWwAVGxNSFRuUlI2 dovecot: Oct 10 02:03:11 Info: auth(default): client out: OK 1 user=wail dovecot: Oct 10 02:03:11 Info: auth(default): master in: REQUEST 3 53919 1 dovecot: Oct 10 02:03:11 Info: auth(default): master out: USER 3 wail uid=1050 gid=1032 home=/home/wail.spb.ru mail=/var/mail/wail dovecot: Oct 10 02:03:11 Info: pop3(wail): Effective uid=1050, gid=1032 dovecot: Oct 10 02:03:11 Info: pop3(wail): maildir autodetect: stat(/var/mail/wail/cur) failed: Not a directory dovecot: Oct 10 02:03:11 Info: pop3(wail): mbox autodetect: data=/var/mail/wail dovecot: Oct 10 02:03:11 Info: pop3(wail): mbox autodetect: INBOX file: yes (/var/mail/wail) dovecot: Oct 10 02:03:11 Info: pop3(wail): mbox: data=/var/mail/wail dovecot: Oct 10 02:03:11 Info: pop3(wail): mbox: root exists (/home/wail.spb.ru/mail) dovecot: Oct 10 02:03:11 Info: pop3(wail): mbox: root=/home/wail.spb.ru/mail, index=/home/wail.spb.ru/mail, inbox=/var/mail/wail dovecot: Oct 10 02:03:11 Info: pop3-login: Login: user=<wail>, method=PLAIN, rip=82.146.63.23, lip=82.146.50.34 dovecot: Oct 10 02:03:13 Info: pop3(wail): Logout. top=0/0, retr=0/ del=0/3, size=5372 dovecot: Oct 10 02:03:20 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=82.146.50.34 rip=82.146.63.23 resp=AHdhaWwAVGxNSFRuUlI2 dovecot: Oct 10 02:03:20 Info: auth(default): client out: OK 1 user=wail dovecot: Oct 10 02:03:20 Info: auth(default): master in: REQUEST 4 53918 1 dovecot: Oct 10 02:03:20 Info: auth(default): master out: USER 4 wail uid=1050 gid=1032 home=/home/wail.spb.ru mail=/var/mail/wail dovecot: Oct 10 02:03:20 Info: pop3(wail): Effective uid=1050, gid=1032 dovecot: Oct 10 02:03:20 Info: pop3(wail): maildir autodetect: stat(/var/mail/wail/cur) failed: Not a directory dovecot: Oct 10 02:03:20 Info: pop3(wail): mbox autodetect: data=/var/mail/wail dovecot: Oct 10 02:03:20 Info: pop3(wail): mbox autodetect: INBOX file: yes (/var/mail/wail) dovecot: Oct 10 02:03:20 Info: pop3(wail): mbox: data=/var/mail/wail dovecot: Oct 10 02:03:20 Info: pop3(wail): mbox: root exists (/home/wail.spb.ru/mail) dovecot: Oct 10 02:03:20 Info: pop3(wail): mbox: root=/home/wail.spb.ru/mail, index=/home/wail.spb.ru/mail, inbox=/var/mail/wail dovecot: Oct 10 02:03:20 Info: pop3-login: Login: user=<wail>, method=PLAIN, rip=82.146.63.23, lip=82.146.50.34 dovecot: Oct 10 02:03:21 Info: pop3(wail): Logout. top=0/0, retr=0/ del=0/3, size=5372 dovecot: Oct 10 02:03:28 Info: pop3-login: Authenticate PLAIN failed: Unsupported authentication mechanism.: method=PLAIN, rip=82.146.63.23, lip=82.146.50.34 dovecot: Oct 10 02:03:30 Info: pop3-login: Aborted login: method=PLAIN, rip=82.146.63.23, lip=82.146.50.34 We see here two successfull logins with PLAIN and then suddenly PLAIN becomes unsupported. I run dovecot 1.0.alpha3 on FreeBSD 4.11, it was installed from ports and then I edited dovecot.conf (and created dovecot.passwd). Any help would be really appreciated. Sergey Redin.

2 1

Re: [Dovecot] Dovecot Alpha 4
by Tomi Hakala 28 Oct '05

28 Oct '05

Marcus Don wrote: > How confident are you of the CVS? Any idea when the next (perhaps beta?) > release will be? I run CVS code most of the time, but only with handful of users and with them it has been working OK. I wouldn't use CVS code in production without thorough stress testing in a lab first. >>Have you thought of clustered file system to go with your Dovecot >>hosts and CLARiiON device? > I'm not sure why this would benefit us at the moment. Before we switched to > maildirs, the bottleneck we were experiencing at busy times was the ethernet > speed, not the storage device speed. > Is there another reason you suggested this? No, I'm just not very fond of NFS myself but it seems that for you it is doing job pretty well. Your CLARiiON is a normal SAN device and you have some singe host providing NFS? It didn't quite open to me how your mail spool is set up, is it some meta LUN distributed over two disk arrays or do you just have one huge LUN and mirror it between two arrays? -- Tomi Hakala

1 0

[Dovecot] problem with thunderbird
by Alfonso Sparano 28 Oct '05

28 Oct '05

Hi all, I've a problem with thunderbird 1.0.6/7/1.5 and dovecot pop3 I've tried dovecot alpha 3 and 1.0 stable but neither one is capable of downloading mails. Nothing is written into the log. I've tried also to delete dovecot.index* and dovecot-uidlist into the Maildir directory. The cur directory contains more than 8100 messages (single files) Anyone has founded this problem? Alfonso

3 3

[Dovecot] Corrupted index cache file [...] invalid record size
by Lorens 28 Oct '05

28 Oct '05

I get this error every single time some of my users log in: Error: POP3(${user}): Corrupted index cache file /${userdir}/dovecot.index.cache: invalid record size The named file seems to be deleted as soon as corruption is found. This only affects some users. I thought the affected users had in common that they are using POP3 in "leave-messages-on-server" mode, and that their mailboxes are big ( > 100 MB). However I've found a few counterexamples, few and far between (not every login) but still. Google's no help, for once :-) Could this be a locking problem, a bug with big Maildirs (counterexamples being few), or what? I know some of my users have had problems logging several IMAP clients into the smae account at the same time, wouldn't put it past some of those with problems to be trying the same with POP. I know that a detected cache corruption is merely that, but I find the error message annoying :-) Configuration: v1.0-stable (0.99.20050712-2 from debian unstable) Maildir only Default locking (nothing mentioned in conf file) Access over NFS mmap_disable = yes (wiki says to disable mmap to use indexes on NFS). Thanks for any pointers.

2 1

[Dovecot] 1.0alpha3: assert and core
by Jeff A. Earickson 28 Oct '05

28 Oct '05

Hi, An assert and core with 1.0alpha3 on Solaris 9, mbox format, imap only, compiled with gcc 4.0.1. The syslog message was: imap(user): file message-body-search.c: line 393 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos) gdb core dump analysis is attached. Jeff Earickson Colby College

2 1

[Dovecot] hangup with corrupted indexes
by Sergey Redin 28 Oct '05

28 Oct '05

Hello everyone, I remember that Timo wrote in this maillist that if index files are corrupted, dovecot should be OK and just recreate it. So I report here a bug: I have corrupted indexes which make pop3 and imap processes to hangup right after the first list command. The process does not respond and eats 90% of CPU. Just unpack http://redin.info/dovecot-corrupted-index.tgz (10 Kb) into a user's IMAP root (I have mbox storage, but the same thing for maildir with this indexes), do the chown, and try to check the email. I know that the problem can be fixed by removing the index files or using INDEX=MEMORY, but it is claimed that dovecot is failsafe and can deal with any kind of corrupted index files. This is the only reason why I report it here. I have 1.0.alpha4 on FreeBSD 4.11 (installed from ports). Best regards, Sergey Redin.

2 1

[Dovecot] Dovecot problems on Debian
by Jaldhar H. Vyas 28 Oct '05

28 Oct '05

If you have been bitten by bug #334180 and dovecot 1.0alpha3-2.0.1 rest assured the problem is being worked on. In the meantime you should downgrade to -2 which can be found at: http://snapshot.debian.net/archive/2005/10/08/debian/pool/main/d/dovecot/ -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

1 0

[Dovecot] Weirdness with authentication/1.0a4.
by Ashley Penney 28 Oct '05

28 Oct '05

Hi, FreeBSD has recently upgraded their port from 0.99 to 1.0a4, and this has caused me an absolute nightmare of a situation. In a nutshell I replaced my conf with the -example, and modified almost nothing. I made some SSL certs and put them in place, left it with imap/pop/pam etc. Whenever users tried to connect to the remote address, cara.untaken.net, I would get: Oct 27 18:31:14 cara dovecot: Dovecot v1.0.alpha4 starting up Oct 27 18:31:33 cara dovecot: imap-login: Login failed: Plaintext authentication disabled: rip=217.206.62.50, lip=217.206.62.50 Oct 27 18:31:33 cara dovecot: imap-login: Disconnected: rip=217.206.62.50, lip=2 17.206.62.50 However, plaintext authenication was most definitely not disabled. Using www.untaken.net/mail/ which is hosted on the same box as dovecot I could get this plaintext failure constantly using cara.untaken.net, but switching to 'localhost' instead would work fine, despite being the same physical machine. I'm baffled at what could cause this, I put my currently conf over at www.untaken.net/dovecot/ just for reference, I've modified various bits now from the default in a desperate attempt to get it working. Has anyone else seen anything like it? -- <EisernLint> i am considering taking pilates classes.

2 1

[Dovecot] Authentication using native MySQL PASSWORD() function
by Tom Sommer 28 Oct '05

28 Oct '05

Hi, I have a little problem, I need to adapt a setup that currently uses the native MySQL PASSWORD() function to encrypt passwords for e-mail accounts. I plan on using Dovecot with SQL to authenticate on my server, is there a password scheme that fits this authentication method? Any help is appreciated -- Tom Sommer

3 11

[Dovecot] Strange Disconnect Problem
by Marc Perkel 27 Oct '05

27 Oct '05

It's only happening with one user but for some reason I can't get this person logged in. And I'm using his ID on my computer and my ID works. Using two different IMAP clients. What would be causeing the "disconnected" to happen? dovecot: Oct 17 10:56:43 Info: imap-login: Login: user=<lowsley(a)cbsyellowpgs.com>, method=PLAIN, rip=65.37.192.182, lip=69.50.231.10 dovecot: Oct 17 10:56:47 Info: imap-login: Disconnected: user=<john(a)sembrot.com>, method=PLAIN, rip=204.95.16.61, lip=69.50.231.10

2 1

[Dovecot] Shared Folder usage alpha3
by Ralf Zerres 27 Oct '05

27 Oct '05

Dear List, this is my first mail to this list. I'v tried to carefully review all given information towards the Shared Folder subject I could find in the archive / mailing list / wiki. And so far I'm also aware that Timo hasn't put it on the active tasklist for the 1.0 release. Citing the track http://dovecot.org/pipermail/dovecot/2003-October/002493.html I was wandering, wether any further attempt has been made, to use the given functionality for real work. To be more precise, wether anybody has done - delivery of mailboxes to a shared maildir - offering these maildirs through a given namespace Before bothering here without any local experience, I'v set up a dov-server (1.0alpha3) on a debian sid. As an MTA postfix is doing the job. Within postfix I did set up a virtual domain and the needed maps (mailbox, alias). I'm able to deliver successful with the standard postfix functionality to the given filesystem structure (fs=ext3). If it is on any help, I can post the relevant config files. As good practice, all mail is delivered to given mailbox-owner with 0600 permission for the new subdir. Hence, can't be seen by any shared-maildir user (unless owner uid matches:) >From here on I'v tried to switch from debians default postfix delivery-strategy (mailbox_command = procmail -a "$EXTENSION") to given dovcot deliver process (mailbox_command = /usr/lib/dovecot/deliver). The primary aim is to define a strategy to deliver with 0660 rights which will enable group read-write access to the given Mailstore. I have adopted the dovecot.conf enableing a listening socket ... default_mail_env = maildir:/home/%u/Maildir: \ INDEX=/home/%u/MaildirIndex namespace private { separator = / prefix = inbox = yes } namespace public { # the prefix needs to be postponed with the separator prefix = Public/ # the location path given as [<mailbox-type>:]<path>/mailbox location = maildir:/home/SharedMaildirs separator = / inbox = no hidden = no } auth default { ... # using deliver through a socket socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 } } } and configured the subsequent dovecot-deliver.conf ... auth_socket_path = /var/run/dovecot/auth-master mail = maildir:%h/Maildir/ umask = 0007 auth_verbose = yes use_syslog = yes just to see, whether a manual call /usr/lib/dovecot/dovecot-deliver -d <user> <testmail would do the trick. Well, I got the delivered mail, but files are not installed with the etimated previledges. Can someone can point me to the clou? Greetings Ralf PS: I also read about posix-acl's support. But my test's didn't allow a successful read ....

2 1

[Dovecot] Alpha4 pre-release, please upgrade
by Timo Sirainen 27 Oct '05

27 Oct '05

Please try if http://dovecot.org/nightly/dovecot-latest.tar.gz (or the CVS directly) works with you. I made a lot of changes to dovecot-auth, so I wouldn't want to make alpha4 release without some more testing in different environments. I'll release alpha4 in a few days, but it'll be basically same as this unless more bugs get fixed. Some of the changes include: - IMAP: We might have sent extra EXPUNGE messages when output buffer got full. This could have caused various sorts of very bad behavior. This is the main reason why everyone should upgrade as soon as possible. - POP3: We sent duplicate replies for LIST command when output buffer got full. Probably caused Thunderbird's duplicate deletion bugs? (Although I thought someone checked that Dovecot's reply was correct when the bug occurred?) - pop3_uidl_format setting is now required to be explicitly set in configuration file for pop3 to work at all. I want to get rid of the old default setting which breaks Outlooks, and simply changing the default would break existing setups. - Multiple passdbs and userdbs of same type can now be added with different parameters. Some people asked about this earlier. - Authentication cache works now with other than SQL and LDAP passdbs. Some passdbs such as PAM require some additional settings to work. See example config file. - Some other fixes to authentication cache related to failure handling and non-plaintext authentication. - deny passdb wasn't working for non-plaintext authentication.

8 21

[Dovecot] auth
by Riccardo Bini 27 Oct '05

27 Oct '05

It's possible to have an auth order so if the first is true skip the other ones? Bye Rick

2 1

[Dovecot] pop3 behaviour
by Krzysztof Janiszewski - IT Partner 27 Oct '05

27 Oct '05

Hi! I'v installed dovecot over um-pop3 today. Dovecot has only pop3 enabled. imap will be enabled later. But there is one issue - on some accounts, after receiving mail to Outlook Express, mail is not deleted from /var/mail/username mbox file, and on most it is deleted. Why it works in that way? Best regards Krzysztof

2 1