- dovecot - dovecot.org

Re: [Dovecot] LDA vs. LMTP
by Joseph Tam 28 Jul '13

28 Jul '13

"Martin Burgraf" <martin.bg(a)web.de> writes: > According to http://wiki2.dovecot.org/LDA the recommended way is to use > LMTP, since it's supposed to have a better performance. The performance gains comes mostly from avoiding the overhead of invoking an executable and spawning a new process for each delivery. If your mail system isn't stressed, I don't think it matters much. > On the other hand, http://wiki2.dovecot.org/LMTP says, that LMTP is a > backgound process, while LDA is only called when needed. I've also > read, that LDA only uses the users privileges, which both means, that > LDA should be better. I don't know why you would consider a background process inferior to a run-on-demand executable. > I've also noticed, that LMTP adds an additional Recieved:-Header to the mail. > Are there any other differences? >From a past discussion on this topic, I think Timo stated that if you use SIS (single-instance storage or de-duping), it's more efficient using LMTP since it knows all message bodies to multiple recipients will be identical. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Case-insensitive "detail" mailboxes?
by /dev/rob0 27 Jul '13

27 Jul '13

We're using sieve with LMTP. We want to have lda_mailbox_autocreate and lmtp_save_to_detail_mailbox. Is there a way to make the "detail" case-insensitive? If so I have not found it yet. I suppose we could lowercase the input string for the SQL userdb query, but that's not what is wanted. The idea being that if a user makes a mailbox called "Test" is that user+test(a)example.com and user+TEST(a)example.com should both go to that "Test" mailbox. If it was lowercased, a mailbox called "Test" would be ignored and "test" used. With autocreate, this could be a problem if mail is delivered to autocreated case-sensitive mailboxes that the user won't see. Hmmm, maybe a global sieve script? -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:

4 5

[Dovecot] dbus support in dovecot?
by Gene Heskett 27 Jul '13

27 Jul '13

Greetings; I am trying to transition from ubu10.04.4 LTS to ubu12.04.2 LTS, but in the changeover I want to setup dovecot as a local only imap server so that I can read & respond to email from any of the other 4 or so machines on my local net. To that end, and given that I have a well working setup right now, using fetchmail driving mailfilter as a pre-check, procmail as the MTA delivering to /var/spool/mail/me, with clamav and spamd in the mix to intercept and send to /dev/null the worst of the spam, or to a quarantine file if clamav triggers. The current transfer mechanism is driven by a script that uses inotifywait to detect newly delivered mail in that directory, and which then sends kmail a dbus message to go get the mail. Since I want to insert dovecot into this chain, does dovecot have a dbus port, and if so, what is the format of the command it expects? Thanks all. Cheers, Gene -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) A pen in the hand of this president is far more dangerous than 200 million guns in the hands of law-abiding citizens.

4 10

[Dovecot] Namespace, Sieve and upgrading to dovecot 2.0 -- no folder "INBOX/"
by Ben 27 Jul '13

27 Jul '13

I just upgraded from debian squeeze->wheezy. This meant upgrading from dovecot 1.2 to 2.1.7 and upgrading to Pigdeonhole sieve. I have dovecot configured to use sieve and virtual users (I'll post config below) Now any message that come in get filtered by sieve, but any messages that don't hit any filters gives the error (in the sieve log): msgid=<XXXX(a)XXX.com>: failed to store into mailbox 'INBOX/': Invalid mailbox name As far as I can tell, Pidgeonhole has hard-coded to the behavior of 'keep' (that is unfiltered emails) to be: fileinto "INBOX/" However, in my setup "INBOX/" is not a valid folder. "INBOX" is. Is there a way to get pidgeonhole sieve to treat 'keep' as fileinto "INBOX"? Or do I need to reconfigure my dovecot namespaces? I tried playing with them, but everything works right now (sharing, etc) and when I changed my prefix on the inbox, etc, it did weird things (INBOX.INBOX.FOLDER) instead of (INBOX.Folder). Suggestions? Here is, I believe the relevant config info: dovecot.conf: namespace { inbox = yes location = prefix = separator = / type = private } namespace { list = children location = maildir:/Mail/Users/%%n/:INDEX=/Mail/Users/%u/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } Thanks, Ben

2 1

[Dovecot] Fw: POP3 issues
by Thomas I Higgins 26 Jul '13

26 Jul '13

Sorry - forgot to mention it is on Dovecot version 1.0.7 and RHEL 5.6 Tom >I have been trying off and on for the better part of a year to get a dovecot server migrated from one machine to another. It is currently working on CENTOS and we are trying to get it on Redhat. Currently I have everything migrated and >working in IMAP, but we have one client device that requires POP3 (doesn't support IMAP). To this end, we have set up everything to work in POP3 as far as I can tell. > >In the dovecot.conf file, we show: > >protocols = imap imaps pop3 pop3s >protocol pop3 { > pop3_uidl_format = %08Xu%08Xv >} > >The services running include: > >dovecot-auth >imap-login >imap-login >imap-login >pop3-login >pop3-login >pop3-login > >Everything else looks good including the logs which seem to show proper connectivity - messages are being received, accounts are connecting and disconnecting, etc. but the pop connections are not (apparently) passing messages >found in that box. They are still just sitting there, not being read, picked up, or otherwise delivered by dovecot. Any ideas on what else I can check or change to get this to pick up? > >Thanks, >Tom Higgins

2 3

[Dovecot] Duplicate Mails downloding issue
by Kavish Karkera 26 Jul '13

26 Jul '13

Hi All, We are repeatedly getting the below warning / errors on our pop server. Please help us out buy knowing what could be the issue. ------------------------------------------------------------------------------------------------------------------------------------------------------- Jul 23 15:34:51 popserver dovecot: pop3(14949_kavish): Warning: Locking transaction log file /indexes//mail/v3store/example.com/14949_kavish/.INBOX/dovecot.index.log took 133 seconds Jul 23 15:34:51 popserver dovecot: pop3(kavish(a)example.com): Error: Broken file /indexes//mail/v3store/example.com/14949_kavish/.INBOX/dovecot-uidlist line 180: UIDs not ordered (10156 >= 10156) Jul 23 15:35:01 popserver dovecot: pop3(kavish(a)example.com): Error: utime(/indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock) failed: No such file or directory Jul 23 15:35:11 popserver dovecot: pop3(kavish(a)example.com): Error: utime(/indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock) failed: No such file or directory Jul 23 15:35:21 popserver dovecot: pop3(kavish(a)example.com): Warning: Our dotlock file /indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock was deleted (kept it 30 secs) --------------------------------------------------------------------------------------------------------------------------------------------------------- Regards, Kavish Karkera

3 9

[Dovecot] dovecot-lda not logging if dovecot runs under daemontools
by Roberto Puzzanghera 26 Jul '13

26 Jul '13

Hello all, I have dovecot running under daemontools and I can't see dovecot-lda in action when I read the logs. I've set the logs to /dev/stderr because daemontools redirects /dev/stderr to /var/log/dovecot/current. The dovecot server works fine and I know that dovecot-lda is actually doing the delivery, because the sieve facility is working as well. I can get lda log working -but only on syslog- if I override the log_path in this way: protocol lda { mail_plugins = $mail_plugins sieve log_path = } I'm calling dovecot-lda in the usual qmail way. This is my .qmail-default: |/var/qmail/bin/preline -f /usr/libexec/dovecot/deliver -d $EXT@$USER As running dovecot under daemontools seems to be a common practice among qmail users, could any of you give me an hint on how dovecot should be configured to achieve the purpose? Thanks in advance. My doveconf follows Roberto Puzzanghera # dovecof -n # 2.2.4: /etc/dovecot/dovecot/dovecot.conf # OS: Linux 3.2.29-smp i686 Slackware 14.0 auth_default_realm = mydomain.net auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes default_login_user = vpopmail disable_plaintext_auth = no first_valid_gid = 89 first_valid_uid = 89 last_valid_gid = 89 last_valid_uid = 89 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /dev/stderr mail_access_groups = 89 mail_debug = yes mail_gid = 89 mail_location = maildir:%h/Maildir mail_plugins = " quota mail_log notify" mail_privileged_group = 89 mail_uid = 89 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 ihave spamtest spamtestplus namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } plugin { autocreate = Sent autocreate2 = Drafts autocreate3 = Junk autocreate4 = Trash autosubscribe = Sent autosubscribe2 = Drafts autosubscribe3 = Junk autosubscribe4 = Trash mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = maildir:User quota sieve = ~/sieve/dovecot.sieve sieve_before = /etc/dovecot/sieve/ sieve_dir = ~/sieve sieve_extensions = +spamtest +spamtestplus +relational +comparator-i;ascii-numeric } postmaster_address = postmaster@%d protocols = imap pop3 sieve sendmail_path = /var/qmail/bin/sendmail service auth-worker { user = $default_internal_user } service auth { unix_listener auth-userdb { group = vchkpw mode = 0600 user = vpopmail } user = $default_internal_user } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 vsz_limit = 64 M } ssl_cert = </etc/dovecot/ssl/certs/dovecot.pem ssl_key = </etc/dovecot/ssl/private/dovecot.pem userdb { args = /etc/dovecot/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } verbose_ssl = yes protocol lda { mail_plugins = " quota mail_log notify sieve" } protocol imap { mail_plugins = " quota mail_log notify imap_quota" } protocol pop3 { mail_plugins = " quota mail_log notify" }

2 1

[Dovecot] Managing IMAP IDLE/Push with Sieve – possible?
by FF 25 Jul '13

25 Jul '13

Hello, I've been using Dovecot with Sieve for a long time already, and I'm very happy with it. Push is working fine too. I was wondering, however, whether it would be possible to define a Sieve rule (perhaps using some plug-in), such that an IMAP push message gets sent out only for specific senders etc.? Have you come across anything like that? Thanks a lot, F.F.

3 4

[Dovecot] POP3 issues
by Thomas I Higgins 24 Jul '13

24 Jul '13

I have been trying off and on for the better part of a year to get a dovecot server migrated from one machine to another. It is currently working on CENTOS and we are trying to get it on Redhat. Currently I have everything migrated and working in IMAP, but we have one client device that requires POP3 (doesn't support IMAP). To this end, we have set up everything to work in POP3 as far as I can tell. In the dovecot.conf file, we show: protocols = imap imaps pop3 pop3s protocol pop3 { pop3_uidl_format = %08Xu%08Xv } The services running include: dovecot-auth imap-login imap-login imap-login pop3-login pop3-login pop3-login Everything else looks good including the logs which seem to show proper connectivity - messages are being received, accounts are connecting and disconnecting, etc. but the pop connections are not (apparently) passing messages found in that box. They are still just sitting there, not being read, picked up, or otherwise delivered by dovecot. Any ideas on what else I can check or change to get this to pick up? Thanks, Tom Higgins

1 0

Re: [Dovecot] Sieve info
by Reindl Harald 24 Jul '13

24 Jul '13

Am 24.07.2013 14:29, schrieb Noel Butler: > dnsbl - yes, his IP range is now listed in two lists. > > insisted to one dnsbl that they should list the dovecot mailing list > server IP's not his, why? because the list server directly sent his > abuse, not his mail server direct to, not only mine, but others :) you do not understand the problem i never said you should blacklist any mailing-list-server i only said that it is pretty dumb to block a /24 network on a DNSBL because one user from one of the IP's is disliked by you with this brain-dead logic you would need to block also all google-ranges if you dislike a single person with a gmail-address but for *that* you are too faint-hearted serious people can decide by theirself what the want or want not to read and do not need to misuse their position of controlling a RBL > Ahhh if only he was not dev nulled, I would likely have another abusive > email from him jumping up and down claiming yet again he is the innocent > victim, yes, we are all wrong.... the problem is that you can not read anything i write directly because your /dev/nulling, so in the worst case you see only stripped answers of some nitpickers and

1 0