- dovecot - dovecot.org

[Dovecot] Check if a message has attachments
by Antoine Nguyen 14 Jan '11

14 Jan '11

Hi all, my question is not specific to Dovecot but to the IMAP protocol in general. I'm working on a web based software that provides a simple webmail ( http://modoboa.org/) I'm wondering what would an efficient way to detect if a message (or a group of messages) has attachments. I know it certainly consists in checking for specific MIME constructions but how to achieve that without fetching the whole body for each message? Thanks in advance, Antoine Nguyen

2 2

[Dovecot] Running two different versions of Dovecot (was: making folders unmovable)
by David Salisbury 14 Jan '11

14 Jan '11

OK, so I decided to go ahead and just upgrade to the latest 1 series Dovecot and see if that solves my ACL/config issues I've been having. (I tried compiling 2.0.9, but it errored out and I assume that's because it's a pretty old machine/compiler.) Anyway, 1.2.16 compiled fine, and I installed it in another location from the currently running 1.1 series install. I have this new install running (IMAP) on a non-standard port while I test it out, and it starts fine and all seems well. However, I'm wondering, is it OK to run it and have it look at the same Maildir mailboxes as the currently running 1.1 series install? Does that have the potential to mess with indexes or change anything in a bad way? (FWIW, I tried it briefly, and after changing the port number in and restarting my mail client [Thunderbird], it had trouble pulling up the mailbox I was trying to access.) David

1 0

Re: [Dovecot] Time jumped forwards
by Ian B 14 Jan '11

14 Jan '11

On Fri Jan 14 07:23:32 EET 2011, Eric Shubert wrote: >See >http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType… > > >In particular, see NTP Recommendations and VMware Tools bits at the bottom. Thanks, I've read through that document a couple of times now & I'm fairly sure my system 'ticks all the boxes' yet the warning messages continues. I can see no noticeable time discrepancy when I do periodic time checks from the command line comparing against another system's clock - certainly not 2 minute error margin Could this be a time mismatch between imap client & server? Ian.

3 4

[Dovecot] email addresses as usernames with Kerberos
by Peter Mogensen 14 Jan '11

14 Jan '11

Hi, I was trying out Kerberos authentication with som sample users for Dovecot and stumbled into this problem: The user names are of the form local-part@domain, so the Kerberos principal becomes "local-part\@domain@REALM". But it seems Dovecot (1.2.9) doesn't understand that syntax. Looking at the 2.0.8 sources I guess it's not supported. But isn't this a valid Kerberos principal? Is it a bug, or a missing feature or is there a special reason for not supporting it ? kind regards, Peter

1 0

[Dovecot] Time jumped forwards
by Ian B 14 Jan '11

14 Jan '11

Running Dovecot 2.0.8 on 32bit Centos5.5. The machine is a VMWare ESX VM. I'm seeing a lot of warning messages in syslog as follows: 2011-01-14T11:45:37.315917+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:46:00.598006+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:46:25.364405+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:46:27.030658+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:46:49.712202+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:07.600748+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:23.195587+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:37.342804+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:42.671037+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:45.903081+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:48:49.001119+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:48:58.935835+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:49:15.046253+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 104 seconds 2011-01-14T11:49:16.842962+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds I've checked the clock settings in Centos and it all looks OK. NTP is running and not complaining about clock drift. Vmware recommend appending 'divider=10 clocksource=acpi_pm' kernel boot options to prevent timekeeping issues, which I've done. Has anyone else encountered this message? Is it something to be concerned about? Thanks, Ian.

2 1

Re: [Dovecot] Making shared folders "unmovable"
by Dave 13 Jan '11

13 Jan '11

Well, I just noticed this in my logs after I re-loaded the latest Dovecot config I tried: Jan 13 15:09:45 mail dovecot: SIGHUP received - reloading configuration Jan 13 15:09:45 mail dovecot: read(imap dump-capability process) failed: Interrupted system call Jan 13 15:09:45 mail dovecot: Invalid configuration, keeping old one Jan 13 15:09:45 mail dovecot: child 2085 (unknown) returned error 82 (Internal logging error) It's apparently been doing this every time I've reloaded the config, so this is probably why none of my changes with the ACLs are working. :/ Any thoughts on what could be causing this kind of error?? Does that error just basically mean something's set wrong somewhere in dovecot.conf? David

1 0

Re: [Dovecot] Best Cluster Storage
by Jonathan Tripathy 13 Jan '11

13 Jan '11

On 13/01/11 10:57, Stan Hoeppner wrote: > Jonathan Tripathy put forth on 1/13/2011 2:24 AM: > >> Ok so this is interesting. As long as I use Postfix native delivery, >> along with >> Dovecot director, NFS should work ok? > One has nothing to do with the other. Director doesn't touch smtp > (afaik), only > imap. The reason for having Postfix use its native local(8) delivery > agent for > writing into the maildir, instead of Dovecot deliver, is to avoid > Dovecot index > locking/corruption issues with a back end NFS mail store. So if you > want to do > sorting you'll have to use something other than sieve, such as > maildrop or > procmail. These don't touch Dovecot's index files, while Deliver > (LSA) does > write to them during message delivery into the maildir. Yes, I thought it had something to do with that >>> For any meaningful use of virtualized clusters with Xen, ESX, etc, a >>> prerequisite is shared storage. If you don't have it, get it. The >>> hypervisor >>> is what gives you fault tolerance. This requires shared storage. >>> If you do not >>> intend to install shared storage, and intend to use things like drbd >>> between >>> guests to get your storage redundancy, then you really need to >>> simply throw out >>> your hypervisor, in this case Xen, and do direct bare metal host >>> clustering with >>> drbd, gfs2, NFS, etc. >> Why is this the case? Apart from the fact that Virtualisation becomes >> "more >> useful" with shared storage (which I agree with), is there anything >> wrong with >> doing DR between guests? We don't have shared storage set up yet for the >> location this email system is going. We will get one in time though. > I argue that datacenter virtualization is useless without shared > storage. This > is easy to say for those of us who have done it both ways. You > haven't yet. > Your eyes will be opened after you do Xen or ESX atop a SAN. If > you're going to > do drbd replication between two guests on two physical Xen hosts then > you may as > well not use Xen at all. It's pointless. Where did I say I havn't done that yet? I have indeed worked with VM infrastructures using SAN storage, and yes, it's fantastic. Just this particular location doesn't have a SAN box installed. And we will have to agree to disagree as I personally do see the benefit of using VMs with local storage > What you need to do right now is build the justification case for > installing the > SAN storage as part of the initial build out and setup your virtual > architecture > around shared SAN storage. Don't waste your time on this other > nonsense of > replication from one guest to another, with an isolated storage pool > attached to > each physical Xen server. That's just nonsense. Do it right or don't > do it at all. > > Don't take my word for it. Hit Novell's website and VMWare's and pull > up the > recommended architecture and best practices docs. You don't need to tell me :) I already know how great it is > One last thing. I thought I read something quite some time ago about Xen > working on adding storage layer abstraction which would allow any Xen > server to > access directly connected storage on another Xen server, creating a > sort of > quasi shared SAN storage over ethernet without the cost of the FC > SAN. Did > anything ever come of that? > I haven't really been following how the 4.x branch is going as it wasn't stable enough for our needs. Random lockups would always occur. The 3.x branch is rock solid. There have been no crashes (yet!) Would DRBD + GFS2 work better than NFS? While NFS is simple, I don't mind experimenting with DRBD and GFS2 is it means fewer problems?

1 0

[Dovecot] Problem after migration dovecot 1.2 -> dovecot 2.0
by Javier de Miguel Rodríguez 13 Jan '11

13 Jan '11

I have migrated from dovecot 1.2 to dovecot 2.0. When I connect via telnet to 110 port of the dovecot server the client hangs: telnet 192.168.4.80 110 Trying 192.168.4.80... /Connected to 192.168.4.80. Escape character is '^]'./ In syslog I got the following error: /Jan 12 12:14:44 buzon dovecot: imap-login: Error: auth: connect(login) in directory / failed: Permission denied (euid=107(<unknown>) egid=110(<unknown>) missing +x perm: /, euid is not dir owner)/ My /var/run/dovecot directory listing is the following: ls -lhR /var/run/dovecot //var/run/dovecot: total 12K srw------- 1 root root 0 ene 12 11:40 anvil srw------- 1 root root 0 ene 12 11:40 anvil-auth-penalty srw------- 1 root root 0 ene 12 11:40 auth-client srw------- 1 dovecot root 0 ene 12 11:40 auth-login srw------- 1 entrega root 0 ene 12 11:40 auth-master srw------- 1 entrega root 0 ene 12 11:40 auth-userdb srw------- 1 dovecot root 0 ene 12 11:40 auth-worker srw------- 1 root root 0 ene 12 11:40 config srw------- 1 root root 0 ene 12 11:40 dict srwxrwxrwx 1 root root 0 dic 27 21:36 dict-server srw------- 1 root root 0 ene 12 11:40 director-admin srw------- 1 root root 0 ene 12 09:17 director-userdb srw-rw-rw- 1 root root 0 ene 12 11:40 dns-client srw------- 1 root root 0 ene 12 11:40 doveadm-server lrwxrwxrwx 1 root root 25 ene 12 11:40 dovecot.conf -> /etc/dovecot/dovecot.conf drwxr-xr-x 2 root root 4,0K ene 12 09:05 empty drwxr-x--- 2 root root 4,0K ene 12 11:40 login -rw------- 1 root root 6 ene 12 11:40 master.pid /var/run/dovecot/empty: total 0 /var/run/dovecot/login: total 4,0K srw-rw-rw- 1 root root 0 ene 12 11:40 dns-client srw-rw-rw- 1 root root 0 ene 12 11:40 imap srw-rw-rw- 1 root root 0 ene 12 11:40 login srw-rw-rw- 1 root root 0 ene 12 11:40 pop3 srw-rw-rw- 1 root root 0 ene 12 11:40 sieve -rw-r--r-- 2 root root 230 ene 9 20:56 ssl-parameters.dat srw-rw-rw- 1 root root 0 ene 12 11:40 ssl-params / My doveconf -n is the following: / # OS: Linux 2.6.18-194.26.1.el5 x86_64 Red Hat Enterprise Linux Server release 5.5 (Tikanga) ext3 auth_debug = yes auth_master_user_separator = * auth_mechanisms = plain login base_dir = /var/run/dovecot/ default_client_limit = 4096 default_process_limit = 2500 disable_plaintext_auth = no dotlock_use_excl = yes mail_fsync = never mail_gid = entrega mail_location = maildir:/buzones/us.es/%2.26Hn/%2.200Hn/%n:INDEX=/buzones/ramdisk/%2.26Hn/%2.200Hn/%n mail_plugins = " zlib" mail_uid = entrega managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date passdb { driver = shadow } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = /etc/usuario_maestro.txt driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { quota = maildir:Cuota de usuario quota_rule2 = Trash:storage=+10%% quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2 = storage=80%% /usr/local/bin/quota-warning.sh 80 sieve = /buzones/us.es/%2.26Hn/%2.200Hn/%n/dovecot.sieve sieve_dir = /buzones/us.es/%2.26Hn/%2.200Hn/%n/sieve/ zlib_save = gz zlib_save_level = 9 } protocols = pop3 imap sieve service auth { unix_listener auth-master { user = entrega } unix_listener auth-userdb { user = entrega } user = root } service imap-login { executable = /usr/libexec/dovecot/imap-login process_limit = 2000 } service imap { executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap process_limit = 2000 } service managesieve-login { executable = /usr/libexec/dovecot/managesieve-login inet_listener sieve { port = 2000 } process_limit = 2000 } service managesieve { executable = /usr/libexec/dovecot/managesieve process_limit = 2000 } service pop3-login { executable = /usr/libexec/dovecot/pop3-login process_limit = 2000 } service pop3 { executable = /usr/libexec/dovecot/pop3 process_limit = 2000 } ssl_ca = </etc/pki/generico/cacert.crt.pem ssl_cert = </etc/pki/generico/wildcard-us_es.crt ssl_key = </etc/pki/generico/wildcard-key.pem userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap } verbose_proctitle = yes protocol sieve { managesieve_implementation_string = dovecot managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 65536 } protocol lda { hostname = us.es info_log_path = log_path = mail_fsync = optimized mail_plugins = quota sieve zlib postmaster_address = evcorreo(a)us.es syslog_facility = mail } protocol imap { mail_plugins = quota imap_quota zlib } protocol pop3 { mail_plugins = zlib pop3_enable_last = yes pop3_uidl_format = %08Xv%08Xu } /UID & GID of my users: [root@buzon login]# id entrega uid=500(entrega) gid=500(entrega) grupos=500(entrega) [root@buzon login]# id dovecot uid=104(dovecot) gid=107(dovecot) grupos=107(dovecot) [root@buzon login]# id dovenull uid=107(dovenull) gid=110(dovenull) grupos=110(dovenull) What am I doing wrong? I have migrated a identical server from dovecot 1.2 to dovecot 2.0 without this problem. Regards Javier

2 3

[Dovecot] Denying authentication
by Romer Ventura 13 Jan '11

13 Jan '11

Hello, I've been running dovecot for over 3 years now and it works with no problems. I have it setup so that it authenticates users against Active Directory via LDAP and so far no problems. What I would like to know is if there is any way that I could deny access for users trying to access email via cellphones or email clients outside the company. I can close everything since there are a few users that need to get emails from outside the company via cell phone of email clients. I was thinking if there was a way to lets say create a group in AD named: "remote-email" that will allow connection and authentication from any network, any user not in that group will only be able to authenticate if the source is 192.168.xx.xx/24. Is this possible? Maybe not with Dovecot, but maybe someone else has any ideas..? Thanks -------- Romer Ventura

3 4

[Dovecot] Making shared folders "unmovable"
by Dave 13 Jan '11

13 Jan '11

I have set up an area of shared folders with Dovecot 1.2 that is accessed by several people (by way of one account, and everyone who logs in sees these same folders), and the only problem with this setup is that occasionally somebody moves one of the folders underneath another folder or somewhere else in the folder structure, and this sometimes disrupts some automatic procmail filters and the like. Is there a way to keep folders in a shared setup such as this "static" or "unmovable" so that the users can't disrupt the structure? Like, where the folder structure itself can't be changed, but new messages can still come in to the folders? David

5 9