- dovecot - dovecot.org

[Dovecot] A few easy pam and virtual domains questions
by Mauricio Tavares 29 May '09

29 May '09

I am using dovecot with postfix, which was setup to do virtual domains. Dovecot is setup to authenticate against pam (I know, I know) and knows to look for email in /var/spool/vmail/: virtual_mailbox_base = /var/spool/vmail I also have virtual_mailbox_maps defined as virtual_mailbox_maps = hash:/etc/postfix/vmaps.txt where I currently only have one account, % cat /etc/postfix/vmaps.txt raub(a)domain.com domain.com/raub/ % Inside raub we have the usual 3 directories, new,cur, and tmp. When I try to login through imap as raub@domain.com@mail.domain.com (i.e. since we are doing the virtual domain thingie, the username has to indicate the domain it belongs to), it will not take it. But, if I login as raub(a)mail.domain.com, it has no problems authenticating. However, it now expects to retrieve email from /var/spool/vmail/raub instead of /var/spool/vmail/domain.com/raub. Why would it be doing that? Could it be that pam reports raub to be a local account and as a result simply ignoring vmaps.txt? I asked dovecot to log everything it could. When I checked the log file, the following line screamed at me: dovecot: May 27 14:40:28 Info: IMAP(raub): maildir++: root=/var/spool/vmail//raub, index=, control=, inbox=/var/spool/vmail//raub Note the "//" in root and inbox declarations; between those slashes I would expect to be domain.com. Compounding the problem, and perhaps a clue of how pam is telling what these accounts are, postfix is completely ignoring /var/spool/vmail, placing the emails in /home/raub/Maildir (account is actually being nfs-automounted and user authenticated through ldap through pam). Once again I am guessing it too is being told raub is a local user; am I correct?

2 2

[Dovecot] What does "a" flag in Maildir format mean?
by Max Ivanov 29 May '09

29 May '09

Here is sample filename from Maildir: 1243423383.M745917P32169.termserv1,W=1295:2,Sa 1) why there is no S=<size> field? It definetely differs from 1295.I've not quota plugin, could it be the reason of this? 2) what does "a" flag mean? I not found any description of this neither in Maildir spec nor on the Dovecot wiki.

3 2

[Dovecot] syslog
by Mohsen Pahlevanzadeh 28 May '09

28 May '09

Dear all, How i use syslog for dovecot? Yours, Mohsen

2 1

[Dovecot] Testing 1.2
by Marc Perkel 28 May '09

28 May '09

Just installed it. Upgraded from 1.1.15. So far so good.

2 1

[Dovecot] test of mailing list
by Carlos Xavier 27 May '09

27 May '09

Im sendding messages to the list and they do not show up. its just a test, please ignore Regards, Carlos Xavier.

5 4

[Dovecot] RFC 3501 section 7
by Scott Haneda 27 May '09

27 May '09

Hello, been lurking a while, about to move over to Dovecot soon. I have a nice test machine up and running. My previous email server when talking IMAP to Apple Mail, will eventually go "deaf" and new messages will not make it to the Inbox of Apple Mail Client. A restart of the desktop application is required. I am told that the reason for this is that my current email server adheres to RFC 3501, specifically section 7, the second paragraph of which says: The client MUST be prepared to accept any response at all times. Apparently, Apple Mail is not adhering to that, and my email server is sending out that type of response. However, I look at this list, for which I am not entirely sure how accurate the actual test is: http://www.imapwiki.org/ImapTest/ServerStatus It lists Dovecot as one of only two that are fully compliant IMAP servers. Congrats on that. My questions are: Does Dovecot in fact support correctly the above mentioned RFC and subsection? I assume so. That being the case, I have not had issues in my testing of Dovecot, nor heard reports of Apple Mail and IMAP having any significant problems. How, if that is the case, can Apple Mail and Dovecot work well with each other, and my current email server is not able to? My primary reason for moving to Dovecot is to not be burdened by this issue, as well as have what I consider to be a more advanced storage mechanism for the actual messages. What I would like to avoid, is spending a lot of time migrating thousands of users to a new system, to only have them burdened by the same inability to have email come to them without an application relaunch. Thank you for any insight on this. * I have filed a bug report with Apple, which was accepted. Their system does not allow me to see the status on the report once it has been closed. -- Scott * If you contact me off list replace talklists@ with scott@ *

2 1

[Dovecot] Dovecot and Phpgroupware compatibility
by Carlos Xavier 27 May '09

27 May '09

Hi, I am resending this email, since the fist one didn't hit the list. Recently we moved our server from mbox format to Maildir format and started using Dovecot. Almost all the users are very happy with this, since the speed had increased very much. I used mb2md to do the conversion and on this task all the mailboxes that had "." (dot) on their names were converted to "_". But there is one issue with this, we also use the webmail that comes with Phpgroupware, and it uses some mailbox that have fixed named like INBOX.Sent, INBOX.Draft and so on. When their names were changed the sent messages didn't get saved anymore, so I had to move them back to the old names. After that the sent messages returned to be saved again, but another trouble showed up. As they start with .INBOX and have "." on the names, Dovecot shown them as a subdirectory of the INBOX and we got some people upset with this. I need help on configuring Dovecot to not show them this way, because if you reed the .INBOX.Sent either on the webmail or by Outlook, the field displayed is the sender, witch is not desired. When I did the conversion, to keep the compatibility with the old server (quota, avoid I/O bottleneck, etc), I set two Maildirs, one at /var/spool/mail/$USER, to be the INBOX and another at the user home. We are using Dovecot version 1.1.13, and below is the relevant configuration on use. namespace public { prefix = "#mbox/" separator = / inbox = yes list = no location= maildir:/var/spool/mail/%u/:CONTROL=~/control:INDEX=~/control } namespace private { separator = / prefix = location= maildir:~/Maildir/:CONTROL=~/control:INDEX=~/control inbox = no } Best Regards, Carlos Xavier.

2 1

[Dovecot] setgid error
by Roy Sigurd Karlsbakk 27 May '09

27 May '09

Hi all Trying to setup dovecot with mysql and postfix, I have configured it as given below. thecot user has the dovecot group as primary, and is also a member of mail and dovecot-users. Still, it can't setgid to dovecot-users. I tried changing the shell for the dovecot user to something useful and chmod'ing a file to dovecot-users, and it work well. Still, no mail comes through and dovecot gives me this error deliver(roy(a)somedomain.com): 2009-05-23 15:02:52 Fatal: setgid(115) failed with euid=115, gid=114, egid=114: Operation not permitted Any ideas? roy # Dovecot config # 1.0.15: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login verbose_proctitle: yes mail_privileged_group: mail mail_location: maildir:/var/spool/dovecot/%d/%n auth default: default_realm: eventchief.com verbose: yes debug: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 432 user: dovecot group: mail -- Roy Sigurd Karlsbakk (+47) 97542685 / 98013356 roy(a)karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.

2 6

Re: [Dovecot] Capability problems dovecot 2.0
by reg9009 27 May '09

27 May '09

answered the wrong address... Timo Sirainen schrieb: > On May 27, 2009, at 2:35 AM, reg9009 wrote: > >> what if TB just needs the "IMAP4rev1" capability before logging in? > > That's a completely different issue. Meaning that v2.0 is buggy here > currently and returning an empty string, because I haven't yet decided > how to fix it. That explains all :) I'll try imap_capability manual override for now. Btw., when I telnet to the server, I get * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. What's this capability string? Couldn't we use this one, at least until a user is logging in? > >> Where is the setting "imap_capability" used? I could try and see how TB >> is behaving, in parallel to Outlook, OE, etc. > > What do you mean by used? You should be able to just set in dovecot.conf: > > imap_capability = imap4rev1 and other stuff > > I didn't know if that shoul be used in some section or directly in dovecot.conf. Thx. Regards, Sebastian

1 0

[Dovecot] [bug] dovecot 1.1.15: segfault after message move
by Juergen Daubert 27 May '09

27 May '09

Hello, found the following in my error log: May 20 13:27:48 ser dovecot: imap-login: Login: user=<juergen>, method=PLAIN, rip=192.168.0.17, lip=192.168.0.90, TLS May 20 13:28:10 ser dovecot: Panic: IMAP(juergen): file imap-sync.c: line 439 (cmd_sync_delayed): assertion failed: (client->mailbox != NULL) May 20 13:28:10 ser dovecot: IMAP(juergen): Raw backtrace: imap [0x80cc01e] -> imap [0x80cc08a] -> imap [0x80cba78] -> imap [0x806642f] -> imap [0x80602c1] May 20 13:28:10 ser dovecot: child 23536 (imap) killed with signal 6 (core dumps disabled) it's almost always reproducible using the Heirloom mailx [1] mail client, with mutt I get a 'connection closed' message but no segfault: - login to the dovecot server via imap/imaps - move a message from INBOX to a another large mbox-file - quit Seems to be a new issue introduced with 1.1.15 because I don't see that with 1.1.14 or older versions. Greetings Juergen [1] http://heirloom.sourceforge.net/mailx.html #:> dovecot -n # 1.1.15: /etc/dovecot.conf # OS: Linux 2.6.27.23 i686 base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/certs/dovecot.crt ssl_key_file: /etc/ssl/keys/dovecot.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_process_per_connection: no login_processes_count: 1 first_valid_gid: 100 mail_location: mbox:~/Mail:INBOX=/var/spool/mail/%u mbox_min_index_size: 100 mbox_very_dirty_syncs: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 auth default: passdb: driver: shadow userdb: driver: passwd -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux

6 16