- dovecot - dovecot.org

[Dovecot] Imap Quota Exceeded - But Still Receiving Emails?
by Palatine Web Support 25 Jan '12

25 Jan '12

Hello I am trying to setup dovecot maildir quota, but even though it seems to be working fine, I am still receiving emails into my inbox even though I have exceeded my quota. Here is my dovecot config: plugin { quota = maildir:User Quota quota_rule2 = Trash:storage=+100M } And my SQL config file for Dovecot (dovecot-sql.conf): user_query = SELECT '/var/vmail/%d/%n' as home, 'maildir:/var/vmail/%d/%n' as mail, 150 AS uid, 8 AS gid, CONCAT('*:storage=', quota) AS quota_rule FROM mailbox WHERE username = '%u' AND active = '1' CONCAT('*:storage=', quota) AS quota_rule quota_rule = *:storage=3M So it picks up my set quota of 3MB but dovecot is not rejecting emails if I am over my quota. Can anyone help? Thanks. Carl

2 1

Re: [Dovecot] change smtp port
by Noel 24 Jan '12

24 Jan '12

On 1/23/2012 8:38 AM, Amira Othman wrote: > And there is no way to receive incoming emails not on port 25 ? > You can't randomly change the port you receive mail on because external MTAs have no way to find what port you're using. They will *always* use port 25 and nothing else. If your problem is that your Internet Service Provider is blocking port 25, you can contact them. Some ISPs will unblock port 25 on request, or might even have an online form you can fill out. If you can't get help from the ISP, you need a remailer service -- some outside proxy that accepts the mail for you and forwards connections to some different port on your computer. I don't know of any free services that do this; dyndns and others offer this for a fee, sometimes combined with spam/virus filtering. -- Noel Jones

4 6

Re: [Dovecot] change smtp port
by Charles Marcus 24 Jan '12

24 Jan '12

On 2012-01-24 7:51 AM, Amira Othman <a.othman(a)cairosource.com> wrote: > Thanks for reply > > The problem that ISP for some reason port 25 is not stable and refuse > connection for several times so I tried to change port to 587 instead > of 25 to keep sending emails. And I though that I can stop using port > 25 as it's not always working from ISP As I said, you obviously do not understand how smtp works. This is made obvious by your questions, and failure to understand that port 25 is *the* port for receiving email on the public internet. Period. If your main problem with port 25 is *sending* (relaying outbound) mails, then you will need to take this up with your ISP. If they are unable or unwilling to address the problem, one option would be to setup your system to relay through some other smtp relay service on the internet using port 587 as you apparently read somwehere, but you don't do this by changing the main smtpd daemon to port 587, because as you discovered, you won't be able to receive *any* emails like this. That said, I fail to see any relevance to dovecot in this thread... -- Best regards, Charles

1 0

[Dovecot] Trying to get metadata plugin working
by Thomas Koch 24 Jan '12

24 Jan '12

Hi, I'm working on a Kolab related project and wanted to use dovecot on my dev machine. However I'm stuck with the metadata-plugin. I "solved" the permissions problems but now I get dict: Error: file dict commit: file_dotlock_open(~/Maildir/shared-metadata) failed: No such file or directory Before that, I had dict { metadata = file:/var/lib/dovecot/shared-metadata but got problems since my normal user had no permission to access /var/lib/dovecot. I compiled the plugin from the most recent commit. My dovecot runs in a chroot. I can login with KMail and can create Groupware (annotated) folders, but the metadata file dict won't get created and I also can't set/get metadata via telnet. doveconf -N # 2.0.15: /etc/dovecot/dovecot.conf # OS: Linux 3.1.0-1-amd64 x86_64 Debian 6.0.3 auth_mechanisms = plain dict { metadata = file:~/Maildir/shared-metadata } mail_access_groups = dovecot mail_location = maildir:~/Maildir mail_plugins = " metadata" passdb { driver = pam } plugin { metadata_dict = proxy::metadata } protocols = " imap" service dict { unix_listener dict { group = dovecot mode = 0666 } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol imap { mail_plugins = " metadata imap_metadata imap_annotatemore" } Best regards, Thomas Koch, http://www.koch.ro

4 5

[Dovecot] Capabilities of imapc
by René Neumann 24 Jan '12

24 Jan '12

Hi *, I can't find any decent information about the capabilities of imapc in the planned future dovecot releases. As I think about using imapc, I'll just give the two use-cases I see for me. Will this be possible with imapc? 1) One (or more) folders in a mailbox which are proxied? 2) Proxy a whole mailbox _and use the folders in it as shared folders_. That means account X on Server 1 (the dovecot box) is proxied via imapc to Server 2 (some other server). The folders of this account on Server 1 are then shared with account Y. When account Y uses these folders they are always up-to-date (so no action of account X is required). The second use-case is just some (ugly) workaround in case the first one is not possible. Thanks, René

2 2

[Dovecot] dbox + SIS + zlib fixed
by Timo Sirainen 24 Jan '12

24 Jan '12

I think a few people have complained about this combination being somewhat broken, resulting in bogus "cached message size wrong" errors sometimes. This fixes it: http://hg.dovecot.org/dovecot-2.0/rev/9b2931607063

1 0

[Dovecot] make imap search less verbose
by Jan-Frode Myklebust 24 Jan '12

24 Jan '12

We have an imap-client (SOGo) that doesn't handle this status output while searching: * OK Searched 76% of the mailbox, ETA 0:50 Is there any way to disable this output on the dovecot-side? -jf

2 3

[Dovecot] Director questions
by Mark Moseley 23 Jan '12

23 Jan '12

In playing with dovecot director, a couple of things came up, one related to the other: 1) Is there an effective maximum of directors that shouldn't be exceeded? That is, even if technically possible, that I shouldn't go over? Since we're 100% NFS, we've scaled servers horizontally quite a bit. At this point, we've got servers operating as MTAs, servers doing IMAP/POP directly, and servers separately doing IMAP/POP as webmail backends. Works just dandy for our existing setup. But to director-ize all of them, I'm looking at a director ring of maybe 75-85 servers, which is a bit unnerving, since I don't know if the ring will be able to keep up. Is there a scale where it'll bog down? 2) If it is too big, is there any way, that I might be missing, to use remote directors? It looks as if directors have to live locally on the same box as the proxy. For my MTAs, where they're not customer-facing, I'm much less worried about the latency it'd introduce. Likewise with my webmail servers, the extra latency would probably be trivial compared to the rest of the request--but then again, might not. But for direct IMAP, the latency likely be more noticeable. So ideally I'd be able to make my IMAP servers (well, the frontside of the proxy, that is) be the director pool, while leaving my MTAs to talk to the director remotely, and possibly my webmail servers remote too. Is that a remote possibility?

2 2

[Dovecot] LMTP ignoring tcpwrappers
by Harm Weites 23 Jan '12

23 Jan '12

Hello, we want to use dovecot LMTP for efficient mail delivery from our MX servers (running postfix 2.8) to our storage servers (dovecot 2.0.17). However, the one problem we see is the lack of access control when using LMTP. It apears that every client in our network who has access to the storage machines can drop a message in a Maildir of any user on that storage server. To prevent this behaviour it would be nice to use libwrap, just as it can be used for POP3/IMAP protocols. This, however, seems to be impossible using the configuration as mentioned on the dovecot wiki: login_access_sockets = tcpwrap service tcpwrap { unix_listener login/tcpwrap { group = $default_login_user mode = 0600 user = $default_login_user } } This seems to imply it only works for a login, and LMTP does not use that. The above works perfectly when trying to block access to IMAP or POP3 in /etc/hosts.deny, though a setting for LMTP is simply ignored. Is there a configuration setting needed for this to work for LMTP, or is it simply not possible (yet) and does libwrap support for LMTP requires a patch? Any help is appreciated. Regards, Harm

2 2

[Dovecot] Quota is not working (Debian Squeeze - Dovecot 1.2)
by RaSca 23 Jan '12

23 Jan '12

Hi all, I'm trying to make quota work in Squeeze (Dovecot 1.2.15-7). The quota module is correctly loaded and, when receiving a message, from the log I see these messages: Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): Loading modules from directory: /usr/lib/dovecot/modules/lda Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): Module loaded: /usr/lib/dovecot/modules/lda/lib10_quota_plugin.so Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): Module loaded: /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): auth input: uid=5000 Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): auth input: gid=5000 Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): auth input: home=/mail/mailboxes/<mydomain>/testquota Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): Quota root: name=/mail/mailboxes/<mydomain>/testquota backend=maildir args= Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): maildir: data=/mail/mailboxes/<mydomain>/testquota@<mydomain> Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): maildir++: root=/mail/mailboxes/<mydomain>/testquota@<mydomain>, index=, control=, inbox=/mail/mailboxes/<mydomain>/testquota@<mydomain> Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): sieve: user's script path /mail/mailboxes/<mydomain>/testquota/.dovecot.sieve doesn't exist (using global script path in stead) Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): sieve: using sieve path for user's script: /mail/sieve/globalsieverc Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): sieve: opening script /mail/sieve/globalsieverc Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): sieve: executing compiled script /mail/sieve/globalsieverc Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): Namespace : Using permissions from /mail/mailboxes/<mydomain>/testquota@<mydomain>: mode=0700 gid=-1 Jan 16 11:20:05 mail-1 dovecot: deliver(testquota@<mydomain>): sieve: msgid=<4F13F996.4000501(a)seat.it>: stored mail into mailbox 'INBOX' Now, since I've got a message like this: Quota root: name=/mail/mailboxes/<mydomain>/testquota@<mydomain> backend=maildir args= it seems that something is checked, but even if this directory is over quota, nothing happens. This is my dovecot conf: protocols = imap pop3 disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/mail/mailboxes/%d/%n@%d mail_privileged_group = mail mail_debug = yes mail_nfs_storage = yes mmap_disable=yes fsync_disable=no mail_nfs_index = yes protocol imap { mail_plugins = quota imap_quota } protocol pop3 { pop3_uidl_format = %08Xu%08Xv mail_plugins = quota } protocol managesieve { } protocol lda { auth_socket_path = /var/run/dovecot/auth-master postmaster_address = postmaster@<mydomain> mail_plugins = sieve quota quota_full_tempfail = no log_path = } auth default { mechanisms = plain passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb passwd { } userdb static { args = uid=5000 gid=5000 home=/mail/mailboxes/%d/%n@%d allow_all_users=yes } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } plugin { quota = maildir:/mail/mailboxes/%d/%n@%d sieve_global_path = /mail/sieve/globalsieverc } The db connection works, this is /etc/dovecot/dovecot-sql.conf: driver = mysql connect = host=<myserver> dbname=mail user=<myuser> password=<mypassword> default_pass_scheme = CRYPT password_query = SELECT username, password FROM mailbox WHERE username='%u' user_query = SELECT username AS user, maildir AS home, CONCAT('*:storage=', quota , 'B') AS quota_rule FROM mailbox WHERE username = '%u' AND active = '1' and for the user testquota the user_query results in this: +-------------------+----------------------------+--------------------+ | user | home | quota_rule | +-------------------+----------------------------+--------------------+ | testquota@<mydom> | <mydom>/testquota@<mydom>/ | *:storage=1024000B | +-------------------+----------------------------+--------------------+ everything else is ok, for example I'm using sieve for the spam filter, and the SPAM is correctly put in the .SPAM dir. I turned on debug on dovecot, but I can't see if the query in some way fails. Can you please help me to understand what am I doing wrong? -- RaSca Mia Mamma Usa Linux: Niente è impossibile da capire, se lo spieghi bene! rasca(a)miamammausalinux.org http://www.miamammausalinux.org

3 4