- dovecot - dovecot.org

Keywords & sync
by Ralf Hildebrandt 10 Oct '14

10 Oct '14

We're using keywords within Thunderbird, and we're syncing those using IMAP. When using more than 5 keywords, we're envcountering problems - they're only partially being synced (between two clients, but not all clients). Any idea why this could be happening? The introduction of tagging in Thunderbird is described here: <https://bugzilla.mozilla.org/show_bug.cgi?id=114656> -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

6 5

Send an alert on master user login
by Andre Rodier 09 Oct '14

09 Oct '14

Hello, I want to know if there is an option in Dovecot to send an alert, or run a script when someone is using the master user facility. I can do something myself with fail2ban, but maybe there is an option in Dovecot? Thanks. André.

2 4

Sieve filter extracting wrong header value on certain mail messages
by gowen (dovecot) 09 Oct '14

09 Oct '14

# 2.2.12: /etc/dovecot/dovecot.conf # OS: Linux 3.15.4-x86_64-linode45 x86_64 openSUSE 12.3 (x86_64) Short version: 1) I filter out spam by using a dovecot sieve filter to act based on a header inserted by bogofilter 2) In some cases, sieve fails to correctly file based on this header 3) Testing with sieve-test indicates that it's testing the wrong header 4) Suggestions? Am I doing something wrong? Is there a problem with these headers that bends test-sieve out of shape? 5) Test files from below are also available via http://www.swynwyr.com/sieve-test/ Any help is appreciated!!! Long version with full details: Here is the simple sieve filter I'm using to test, and two different variants of an email which triggers this problem. I basically deleted things one by one from an original email (1) to get minimal testcases that triggered (2) or did not trigger (3) the problem. The filter: === begin test.sieve === require ["fileinto", "body", "regex"]; if header :contains "X-Bogosity" "Spam," { fileinto "SPAM.SPAM"; stop; } elsif header :contains "X-Bogosity" "Unsure," { fileinto "SPAM.UNSURE"; stop; } keep; stop; === end test.sieve === Here is an example email that will cause this filter to not function as expected: === begin message.2 === Return-Path: <alora(a)promosforusio.org> Subject: =?utf-8?B?QUhTIEtpdGNoZW4gTWFrZW92ZXIgR2l2ZWF3YXkg?= Subject: ÎHS KitÑhen ÎakÐµovÐµr GivÐµaway Subject: =?ISO-8859-1?Q?AHS Kitchen Makeover Giveaway =A0=A0=A0?= Subject: Subject: AHS Kitchen Makeover Giveaway X-Bogosity: Spam, tests=bogofilter, spamicity=1.000000, version=1.2.3 Home Warranty Summer Giveaway === end message.2 === If I run test-sieve on this, we can clearly see in the trace log that when it's supposed to test for header "X-Bogosity" it in fact looks at one of the multiple "Subject" headers. Note that the result is storing in INBOX rather than SPAM.SPAM, and that the "matching value" for "X-Bogosity headers" is actually the contents of the final "Subject" header in the test on line 3. In the second test, on line 6, it uses a different and correct value for the same header! But too late to help as the first test was the one it should have had a match on. === begin session === $ sieve-test -t trace2.log -Tlevel=matching test.sieve message.2 Performed actions: * store message in folder: INBOX Implicit keep: (none) sieve-test(gowen): Info: final result: success $ cat trace2.log ## Started executing script 'test' 3: header test 3: starting `:contains' match with `i;ascii-casemap' comparator: 3: extracting `X-Bogosity' headers from message 3: matching value `AHS Kitchen Makeover Giveaway' 3: with key `Spam,' => 0 3: finishing match with result: not matched 3: jump if result is false 3: jumping to line 6 6: header test 6: starting `:contains' match with `i;ascii-casemap' comparator: 6: extracting `X-Bogosity' headers from message 6: matching value `Spam, tests=bogofilter, spamicity=1.000000, version=1.2.3' 6: with key `Unsure,' => 0 6: finishing match with result: not matched 6: jump if result is false 6: jumping to line 11 11: keep action; store message in default mailbox 12: stop command; end all script execution ## Finished executing script 'test' $ === end session === Now lets remove the "Return-Path" from that message. (Of the original 26 headers, all but the 7 shown in message.2 could be removed and still have this message break the filter). This alters thing enough that sieve starts working as expected (in fact, removing any one of the 6 non-X-Bogosity headers will cause this to start working). === begin message.3 === Subject: =?utf-8?B?QUhTIEtpdGNoZW4gTWFrZW92ZXIgR2l2ZWF3YXkg?= Subject: ÎHS KitÑhen ÎakÐµovÐµr GivÐµaway Subject: =?ISO-8859-1?Q?AHS Kitchen Makeover Giveaway =A0=A0=A0?= Subject: Subject: AHS Kitchen Makeover Giveaway X-Bogosity: Spam, tests=bogofilter, spamicity=1.000000, version=1.2.3 Home Warranty Summer Giveaway === end message.3 === Now when we run test-sieve it works as expected, filing into SPAM.SPAM and showing the correct matching value for line 3: === begin session === $ sieve-test -t trace3.log -Tlevel=matching test.sieve message.3 Performed actions: * store message in folder: SPAM.SPAM Implicit keep: (none) sieve-test(gowen): Info: final result: success $ cat trace3.log ## Started executing script 'test' 3: header test 3: starting `:contains' match with `i;ascii-casemap' comparator: 3: extracting `X-Bogosity' headers from message 3: matching value `Spam, tests=bogofilter, spamicity=1.000000, version=1.2.3' 3: with key `Spam,' => 1 3: finishing match with result: matched 3: jump if result is false 3: not jumping 4: fileinto action 4: store message in mailbox `SPAM.SPAM' 5: stop command; end all script execution ## Finished executing script 'test' $ === end session ===

3 3

mailbox in different filesystem
by Héctor Moreno Blanco 08 Oct '14

08 Oct '14

Hello everyone, We have Dovecot 2.1.6 with Maildir. We would like to perform some kind of mail archiving with a mailbox in a different storage, for example a mailbox called ARCHIVED, with different disks (slower...). Is possible to locate this mailbox in other storage (SAS, Fiber...) and how can we do it? Thank you very much in advanced. Kind regards. Héctor Moreno P Please consider the environment before printing this e-mail. ______________________ This message including any attachments may contain confidential information, according to our Information Security Management System, and intended solely for a specific individual to whom they are addressed. Any unauthorised copy, disclosure or distribution of this message is strictly forbidden. If you have received this transmission in error, please notify the sender immediately and delete it. ______________________ Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener informacion clasificada por su emisor como confidencial en el marco de su Sistema de Gestion de Seguridad de la Informacion siendo para uso exclusivo del destinatario, quedando prohibida su divulgacion copia o distribucion a terceros sin la autorizacion expresa del remitente. Si Vd. ha recibido este mensaje erroneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboracion. ______________________

2 2

Re: Help with shared folder
by Eduardo Ramos 07 Oct '14

07 Oct '14

Sorry Gianluca, I know IMP/Horde just by name. Some googling show me that the option: $servers['advanced'] = array(...,'acl' => true,...) could help you, but you can get some issues: https://sys4.de/en/blog/2013/11/06/imap-acl-dovecot-horde-5-imp-6-warning/ On 10/07/2014 09:30 AM, Gianluca Calloni wrote: > HI Eduardo. > > > > Thank you for your replay.. > > > > You know if there is a plug-in also for Horde webmail GUI? > > > > Unfortunately we use outlook and it seems there is not addon for this.

2 1

Re: Help with shared folder
by Gianluca Calloni 07 Oct '14

07 Oct '14

HI Eduardo. Thank you for your replay.. You know if there is a plug-in also for Horde webmail GUI? Unfortunately we use outlook and it seems there is not addon for this.

1 0

dovecot 2.1 new imap folder permissions
by Stefanos Gerangelos 07 Oct '14

07 Oct '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I hope this is the appropriate place to ask. I am migrating an old mail (postfix/dovecot) server to a new one. Everything works much as expected. I have a small obstacle though. I use mbox format and the setup is pretty much simple. Suppose a user's home directory is the following: # ls -ld /home/foo drwxr-xr-x 3 foo users 4096 Oct 4 13:28 foo and the respective /var/mail: # ls -ld /var/mail/foo - -rw------- 1 foo mail 0 Oct 4 23:45 /var/mail/foo In the old server when the user tried to create a new test imap folder (from an imap client), then the newly created file would be: # ls -l /home/foo/ - -rw------- 1 foo users 0 Oct 2 02:08 test This is the desired behavior. In the new dovecot 2.1 server the following file permissions will apply: # ls -l /home/foo/ - -rw-r--r-- 1 foo users 0 Oct 2 02:08 test I finally noticed that if I chmod the /home/foo to 711, then the new file will have the desired (600) permissions. So, I can make a umask for the new users (login.defs), but that doesn't sound a pretty solution. Do you have anything else to suggest? If you need any .conf file, let me know. Thanks in advance! - --Stefanos -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJUM9k6AAoJEDvFaozEhZub3rwIAKglt/6iAU61rCfWJf6yfMZY HNp3rXz4WDbxhOT+eeuoHNN4QLQFTVmjYoqGpqJEazntdMKJqJ1At3osGtzUMYDe iMuhsbcP+tpMAkeFcYB69cW+HvcmWsPafRJoCgziHapT2VxluWH0rfZIDGmvBI5e kQ31ef9IHZjiBwyKf37e8QraU85HDXgF6AhcJ5I7PlDcJDW/jFGFKOUwDoKJ2BU9 JMUBWDALUZ9Uosd+8P8b11TcjjGdakKBPozvu8aAOKd9jz3G9bvatdHnZkD/OJFl pIrnrQuaBA1bW4UP8nTTSyQVuvLKYpMLbN+NTym8SaEU3BwjirWbRDozHLugXio= =lpy7 -----END PGP SIGNATURE-----

1 0

Re: Help with shared folder
by Eduardo Ramos 07 Oct '14

07 Oct '14

Hi Gianluca, I have roundcubemail as webmail. It has a plugin called 'acl', that allows users create acls easly. My users use to use thunderbird too, and the solution is that add-on: https://addons.mozilla.org/en-US/thunderbird/addon/imap-acl-extension/ On 10/06/2014 09:49 AM, Gianluca Calloni wrote: > Hi dovecot guru.. > > > > I need some help configuring shared folder in my server.. > > This is the situation: > > DOVECOT 2.0.19 > > with POSTFIX - CLAMAV - AMAVISD - SPAMASSASSIN > > > > This is the production server and sharing folder between user work.. > > But i need some explanation.. > > > > 1) It's possible to share only a subfolder (E.G. => .INBOX.ESTERO) without > share the main folder .INBOX? > > 2) Which is the best way (or best practice) to manage the dovecot-acl and > dovecot-acl-list file?? Actually, i modifiy the dovecot-acl by hand (vi > editor). but every time i modify it i need to restart the dovecot server to > apply the configuration. And i need to reset the /var/run/dovecot/dict owner > and group cause with dovecot restart the file go back in root:root owner - > group > > > > > > Thank's in advance. > > > > Gianluca

1 0

Dovecot writing to mailbox user@domain
by John Oliver 06 Oct '14

06 Oct '14

centOS 6.5, dovecot-2.0.9-7.el6_5.1.x86_64 This is frustrating, because I had it working before... I could deliver an email to a user user@domain, then connect to dovecot IMAP and see the mail, no problem! Then I was told we had to use cyrus, and I was dealing with it for a few weeks. Now we're back to dovecot, and the last backup I had of that config has postfix delivering mail to /var/vmail/username as I want and expect, but dovecot looks for and creates /var/vmail/user@domain which I DON'T want [joliver@test ~]$ dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.el6.x86_64 x86_64 CentOS release 6.5 (Final) ext4 auth_username_format = %Lu mail_access_groups = mail mail_location = maildir:/var/vmail/%u/Maildir mail_privileged_group = mail mbox_write_locks = fcntl passdb { driver = pam } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocols = imap ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } userdb { args = uid=504 gid=505 home=/var/vmail/%u driver = static } [joliver@test ~]$ cat /etc/dovecot/dovecot-ldap.conf.ext hosts = localhost auth_bind = no ldap_version = 3 debug_level = 0 default_pass_scheme = SSHA base = ou=Users,dc=test,dc=com scope = subtree pass_filter = (&(objectClass=user)(uid=%u)) pass_attrs = mail=user,userPassword=password -- *********************************************************************** * John Oliver http://www.john-oliver.net/ * * * ***********************************************************************

2 1

How best to confirm that dovecot LDA logging is working correctly?
by Ben Johnson 06 Oct '14

06 Oct '14

Hello! I've posted to the list several times about a strange issue I'm having with dovecot LDA. When dovecot-lda is called in the context of a pipe script that is executed as the "vmail" user via the Dovecot Antispam plugin, dovecot-lda exits prematurely with status code 134. The dovecot deliver manual at http://wiki2.dovecot.org/LDA#logging states very clearly, "If dovecot-lda fails to write to log files it exits with temporary failure." That's a curious note, because I believe that a "temporary failure" exit code may be what I'm dealing with here. When I drag an email from Inbox to SPAM to trigger Antispam, I see only this (and no further output beyond the last line) in syslog, which is the configured logging destination for LDA: imap: antispam: mailbox_is_unsure(Junk): 0 imap: antispam: mailbox_is_trash(INBOX): 0 imap: antispam: mailbox_is_trash(Junk): 0 imap: antispam: mail copy: from trash: 0, to trash: 0 imap: antispam: mailbox_is_spam(INBOX): 0 imap: antispam: mailbox_is_spam(Junk): 1 imap: antispam: mailbox_is_unsure(INBOX): 0 imap: antispam: mail copy: src spam: 0, dst spam: 1, src unsure: 0 imap: antispam: running mailtrain backend program /bin/bash imap: antispam: running mailtrain backend program /bin/bash imap: antispam: running mailtrain backend program parameter 1 /usr/local/bin/sa-learn-pipe.sh imap: antispam: running mailtrain backend program parameter 2 --spam By contrast, if I "su" to the "vmail" user and call the LDA executable with the same arguments that my pipe script does, I see all of the expected output in syslog, AND the message is delivered successfully: /usr/lib/dovecot/deliver -d "sa-training(a)localhost.com" -m "Training.SPAM" -p "/tmp/sendmail-msg-25169.txt" lda: Debug: Loading modules from directory: /usr/lib/dovecot/modules lda: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so lda: Debug: Module loaded: /usr/lib/dovecot/modules/lib90_sieve_plugin.so lda: Debug: auth input: sa-training(a)localhost.com home=/var/vmail/localhost.com/sa-training mail=maildir:/var/vmail/localhost.com/sa-training/Maildir uid=5000 gid=5000 quota_rule=*:storage=0B sieve=/var/vmail/localhost.com/sa-training/.sieve lda: Debug: Added userdb setting: mail=maildir:/var/vmail/localhost.com/sa-training/Maildir lda: Debug: Added userdb setting: plugin/quota_rule=*:storage=0B lda: Debug: Added userdb setting: plugin/sieve=/var/vmail/localhost.com/sa-training/.sieve lda(sa-training(a)localhost.com): Debug: Effective uid=5000, gid=5000, home=/var/vmail/localhost.com/sa-training lda(sa-training(a)localhost.com): Debug: Quota root: name=user backend=dict args=:file:/var/vmail/localhost.com/sa-training/.quotausage lda(sa-training(a)localhost.com): Debug: Quota rule: root=user mailbox=* bytes=0 messages=0 lda(sa-training(a)localhost.com): Debug: Quota rule: root=user mailbox=Trash bytes=+104857600 messages=0 lda(sa-training(a)localhost.com): Debug: Quota rule: root=user mailbox=Junk ignored lda(sa-training(a)localhost.com): Debug: Quota rule: root=user mailbox=INBOX bytes=+104857600 messages=0 lda(sa-training(a)localhost.com): Debug: Quota warning: bytes=0 (100%) messages=0 reverse=no command=quota-reached 100 sa-training(a)localhost.com localhost.com lda(sa-training(a)localhost.com): Debug: Quota warning: bytes=0 (95%) messages=0 reverse=no command=quota-warning 95 sa-training(a)localhost.com localhost.com lda(sa-training(a)localhost.com): Debug: Quota warning: bytes=0 (80%) messages=0 reverse=no command=quota-warning 80 sa-training(a)localhost.com localhost.com lda(sa-training(a)localhost.com): Debug: Quota warning: bytes=0 (100%) messages=0 reverse=yes command=quota-below below sa-training(a)localhost.com localhost.com lda(sa-training(a)localhost.com): Debug: Quota grace: root=user bytes=0 (10%) lda(sa-training(a)localhost.com): Debug: dict quota: user=sa-training(a)localhost.com, uri=file:/var/vmail/localhost.com/sa-training/.quotausage, noenforcing=0 lda(sa-training(a)localhost.com): Debug: maildir++: root=/var/vmail/localhost.com/sa-training/Maildir, index=, indexpvt=, control=, inbox=/var/vmail/localhost.com/sa-training/Maildir, alt= lda(sa-training(a)localhost.com): Debug: Quota root: name=user backend=dict args=:file:/var/vmail//raw mail user/.quotausage lda(sa-training(a)localhost.com): Debug: Quota warning: bytes=0 (100%) messages=0 reverse=no command=quota-reached 100 raw mail user lda(sa-training(a)localhost.com): Debug: Quota warning: bytes=0 (95%) messages=0 reverse=no command=quota-warning 95 raw mail user lda(sa-training(a)localhost.com): Debug: Quota warning: bytes=0 (80%) messages=0 reverse=no command=quota-warning 80 raw mail user lda(sa-training(a)localhost.com): Debug: Quota warning: bytes=0 (100%) messages=0 reverse=yes command=quota-below below raw mail user lda(sa-training(a)localhost.com): Debug: Quota grace: root=user bytes=0 (10%) lda(sa-training(a)localhost.com): Debug: dict quota: user=raw mail user, uri=file:/var/vmail//raw mail user/.quotausage, noenforcing=0 lda(sa-training(a)localhost.com): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= lda(sa-training(a)localhost.com): Debug: Destination address: sa-training(a)localhost.com (source: user@hostname) lda(sa-training(a)localhost.com): Debug: sieve: Pigeonhole version 0.4.2 initializing lda(sa-training(a)localhost.com): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. lda(sa-training(a)localhost.com): Debug: sieve: using the following location for user's Sieve script: /var/vmail/localhost.com/sa-training/.sieve;name=main script lda(sa-training(a)localhost.com): Debug: sieve: loading script /var/vmail/localhost.com/sa-training/.sieve;name=main script lda(sa-training(a)localhost.com): Debug: sieve: script binary /var/vmail/localhost.com/sa-training/.sieve.svbin successfully loaded lda(sa-training(a)localhost.com): Debug: sieve: binary save: not saving binary /var/vmail/localhost.com/sa-training/.sieve.svbin, because it is already stored lda(sa-training(a)localhost.com): Debug: sieve: executing script from /var/vmail/localhost.com/sa-training/.sieve.svbin lda(sa-training(a)localhost.com): sieve: msgid=<20141003110532.045EE6060D(a)localhost.com>: stored mail into mailbox 'Training.SPAM' I'm trying to make sense of this behavior; the implication seems to be that dovecot-lda is crashes immediately, before it can log anything, when it's triggered via Antispam. Is there some way to determine what's happening? I've posted coredump and trace information previously, and nobody replied. Thanks for any help! -Ben

1 0