- dovecot - dovecot.org

Re: [Dovecot] AntiSpam Plugin
by Daryl Richards 06 Aug '10

06 Aug '10

On 05/08/10 10:37 AM, Leander S. wrote: > Am 28.07.2010 21:34, schrieb Daryl Richards: >> I've also had this problem in the past. I wrote a wrapper script to >> try to log what is happening. Funny thing is, when run through this >> script it works fine. Without the script it fails. Not sure where to >> look next, I've just kept the script. >> >> #!/usr/local/bin/bash >> >> ( >> id -a >> echo $@ >> /usr/local/bin/sa-learn $@ >> rc=$? >> echo "exit code $rc" >> exit $rc >> ) > /tmp/antispam.out.$$ 2> /tmp/antispam.err.$$ >> >> On 7/28/2010 3:12 PM, Leander S. wrote: >>> >>> >>> >>> >>> >>> On 07/28/2010 07:24 PM Leander S. wrote: >>> >>>> > … >>>> > Jul 28 18:51:40 server imap: antispam: running mailtrain backend >>>> program >>>> > /usr/local/bin/sa-learn >>>> > Jul 28 18:51:40 server imap: antispam: running mailtrain backend >>>> program >>>> > /usr/local/bin/sa-learn >>>> > Jul 28 18:51:41 server imap: antispam: run program failed with exit >>>> code 9 >>>> > > > > "run program failed with exit code 9" --> unfortunately is >>>> nothing >>>> > mentioned in the dovecot antspam man. >>>> > Antispam >>>> manual:http://johannes.sipsolutions.net/files/antispam.html#lbAL >>>> > > > > > > Could anybody give me a hint where to look up this exit >>>> code? Or is >>>> > there a general meaning for exit codes? >>>> > i.e.: 0 means normal ; 5 internal error ; and 9 maybe means syntax >>>> issue >>>> > ... or whatever ?! >>> /usr/local/bin/sa-learn returned exit code 9. So, check the fine >>> spamassassin documentation. >>> >>> ^^ I did - there is nothing mentioned about exit codes at all - except >>> in the spamc manual. But the spamc manual doesn't represent exit code 9. >>> >>> Do you guys maybe have any idea what this could mean? How does your >>> config for antispam looks like - but I doubt there could be anything >>> wrong in mine. >>> >>> ... very weired ... >>> >>> >>> >>> Regards, >>> Leander >>> >>> >>> >>> >>> >>> Regards, >>> Pascal >>> -- The trapper recommends today: f007ba11.1020919(a)localdomain.org >>> >>> > Thanks for the script hint - exactly the same on my side - I also use a > script now - but mine is more simple than yours: > > server [~]# cat /script.sh > #!/usr/local/bin/bash > > /usr/local/bin/sa-learn $1 $2 $3 $4 &> /DoveDamnAntispam.log > exit 0 ; > server [~]# > > > > > Antispam part of dovecot.conf: > > ### Dovecot AntiSpam ### > # mail signature (used with any backend requiring a signature) > #antispam_signature = X-Spam-Status > #antispam_signature_missing = move > > antispam_mail_sendmail = /script.sh > #antispam_mail_sendmail = /usr/local/bin/sa-learn > antispam_mail_sendmail_args = --username=%u;--debug;all > antispam_mail_spam = --spam > antispam_mail_notspam = --ham > antispam_mail_tmpdir = /tmp > antispam_spam = Spam > antispam_unsure = Virus > antispam_trash = Trash > > > Works fine for me now - but it's really weired ... > > Anyway - lots of thx, hey! ;) > > regards I added the extra debugging to show exactly what was happening - what user was calling sa-learn, what the exit code was, etc... But, as I said, it didn't help as it runs perfectly through that script! -- Daryl Richards Isle Technical Services Inc.

1 0

[Dovecot] Cyrus to Dovecot migration (OS X Server): Backup + restore messages, live "standby server" and delayed expunge and…
by Thomas von Eyben 05 Aug '10

05 Aug '10

Hi List, I am very close to migrating from Cyrus to Dovecot (to be more precise from Mac OS X Server 10.5.8 to 10.6.4). The latter is reporting the dovecotd version to be 1.1.20apple0.5. All I have read about dovecot is extremely positive so I am exited to make the switch. BACKUP: BUT I would like to be sure that I can make a sound backup strategy. For Cyrus i used topicdesk's mailbfr (a script that stops the mailservice and then rsync's the mailstore to a backup location incrementing daily and restarting a complete backup weekly). This script is not yet ready for Dovecot, but from what I have read it should be as easy as "just" backing up the mail-data (/var/spool/imap/dovecot/mail in OS X), eg. with rsync. Our current setup is requiring ca. 11 hours for a full (200+ GB) backup (weekly) this is not good for uptime… RESTORE: Restore should be the same (well reverse) "just" restoring the files and making sure the get the correct permissions. What I am not sure about is the (cyrus specific) need for reconstructing the database, as I have read (on this list) it seems that dovecot is designed better and will "automatically" recognised the restored messages without the need to reconstruct any databases or stopping+restarting the service. Is this really true ,-)? NB.: For restores I plan to always restore to a specific subfolder for the user (eg RESTORED MAIL) as opposed to placing the mails within the folder hierachy LIVE BACKUP SERVER I have been told, that dovecot provides clever mechanisms for making it possible to synchronise the data to a "hot-spare" server. Both for being able to provide access to the data during breakdown or planned maintenance, but perhaps also to make backups easier (perhaps not needed?) DELAYED DELETION OF MESSAGES I believe that the feature is called "delayed expunge", a way of not deleting the messages until after an additional delay from the time the user deletes the message. Is this possible in dovecot? DOCUMENTATION Where would the best FAQ/KB for getting to know dovecot better be, perhaps there have even been written good books (I know old fashioned, but I really like the physical hands on a real book provides ;-) It's a lot of questions and I hope for good pointers to where I can find more documentation and good feedback from the list. BR Thomas von Eyben

3 2

[Dovecot] v2.0.rc4 released
by Timo Sirainen 05 Aug '10

05 Aug '10

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz.sig I'm planning to release rc5 maybe this Friday or weekend, and if there are no serious bugs just change the version number to v2.0.0 a day or two later. Largest changes since rc3: + director: Added director_doveadm_port for accepting doveadm TCP connections. + doveadm: Added client/server architecture support for running mail commands. Enable this by setting doveadm_worker_count to non-zero. + mail-log: Added support for mailbox_create event. + imap_capability = +XFOO BAR can be used to add capabilities instead of replacing the whole capability string. + virtual storage: Added support for IDLE notifications. - doveadm mailbox status: Fixed listing non-ASCII mailbox names. - doveadm fetch: Fixed output when fetching message header or body - doveadm director map/add/remove: Fixed handling IP address as parameter. - dsync: A few more fixes

3 10

[Dovecot] "listen=*, ::" broken?
by Peer Heinlein 05 Aug '10

05 Aug '10

Hi, the default: listen = *, :: should work and should open port 143 on IPv4 and IPv6. In my setup it looks broken: root@mail-archiv:/etc/dovecot# doveconf | grep ^listen listen = *, :: root@mail-archiv:/etc/dovecot# /etc/init.d/dovecot restart Restarting mail server: dovecotError: service(imap-login): listen(::, 143) failed: Address already in use Fatal: Failed to start listeners root@mail-archiv:/etc/dovecot# But it's working with "listen = *": root@mail-archiv:/etc/dovecot# doveconf | grep ^listen listen = * root@mail-archiv:/etc/dovecot# /etc/init.d/dovecot restart Restarting mail server: dovecot. root@mail-archiv:/etc/dovecot# Peer Heinlein -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030-405051-42 Fax: 030-405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

5 6

[Dovecot] 2.0...
by Ralf Hildebrandt 05 Aug '10

05 Aug '10

Hi I'm running 1.2.13 with sieve & managesieve; no problems whatsoever, but the patching & compilation process is a PITA. So I thought, why not try out 2.0rc4 for a change. But: I don't find sieve & managesieve mentioned there - what do I need to enable those? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

3 6

[Dovecot] IMAP IDLE, Virtual mailboxes
by Patrick Nagel 05 Aug '10

05 Aug '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, K-9 Mail (on Android) has been mentioned on this list multiple times recently, I think it's definitely an IMAP client "on the rise". :) It supports IMAP IDLE, and so brings "push mail" to Android mobile phone users. To bring this into the context of this mailing list: I guess a lot of people on this list are making use of server-side filtering (using sieve), so that mails from certain persons or mailing lists end up in the right mailboxes, right on delivery. Now, this is all great, but there are issues when server-side filtering and IMAP IDLE come together: Only one mailbox can be "watched" with one IMAP IDLE connection. So, people who have set up elaborate server-side filtering with say, 50 different sieve "fileinto" calls, will constantly have a *lot* of IMAP IDLE connections open, if they really want to get informed of any mail arriving in any of their mailboxes. Keeping those 50 IMAP connections open wouldn't cost much bandwidth, and who cares about the Internet router's connection tables getting unnecessarily big, anyway? But then there is the "problem" of a mobile phone being carried around constantly, switching physical connections (from WLAN access point 1 to WLAN access point 2 to 3G to 2G to no connection at all and back), every time needing to terminate* those 50 IMAP connections, and then establish 50 new ones (with SSL handshake overhead and all). So, all in all, not an optimal solution. *) (which does not always happen the way it should, see http://code.google.com/p/k9mail/issues/detail?id=1255) I see two ways to improve the situation (one of them quite dovecot-centric): 1) A new extension of the IMAP protocol: IMAP MULTI-IDLE, which somehow allows a client to get notified of changes to more than one mailbox within one IMAP connection. This conflicts with the basic IMAP design though, AFAIK, and is thus not likely to be feasible. 2) Enhancing dovecot's Virtual plugin, so virtual mailboxes do not only get updated on select and expunge, but also when anything changes that affects the set of messages shown in the virtual mailbox. I guess that would have an impact on performance, and thus should be optional. Let me explain the second one: With the help of the Virtual plugin, it is possible to pull all those 50 mailboxes that receive incoming mail together again, just like the INBOX of the pre-server-side-filtering times - the user could configure a virtual mailbox to show all unread mails from those 50 mailboxes. Now the mobile IMAP IDLE users could just watch that one virtual mailbox, needing only one IMAP IDLE connection. After having read the mail (directly in the virtual mailbox), it would disappear, but of course still be in the "real" mailbox, determined by the sieve filter on delivery. Patrick. - -- STAR Software (Shanghai) Co., Ltd. http://www.star-group.net/ Phone: +86 (21) 3462 7688 x 826 Fax: +86 (21) 3462 7779 PGP key E883A005 https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAku+ydsACgkQ7yMg/OiDoAXV9ACdF+BEstnjfUeJlR/JQKFf6N7n yxYAnAnuD2popWYLfZNCCtlpkAP4SQww =L33A -----END PGP SIGNATURE-----

7 19

[Dovecot] sender address of sieve vacation script
by Wolfgang Burger 05 Aug '10

05 Aug '10

Hi, not entirerly sure wether this is the right place to ask. Sorry if not. I´m running dovecot on a Mac OS X Server (10.6.4). Everything works fine. When I try to enable a vacation message, I get the following error in the log: delays=0/0.01/0.09/0.1, dsn=5.0.0, status=bounced (host XXX[x.x.x.x] said: 553 Mail to <name(a)domain.tld> not allowed; missing domain name in MAIL FROM (in reply to RCPT TO command)) Where host is the mail relay. The logs on the mail relay show matching entries. Sending mails is generally working. I´ve sniffed the network traffic and the FROM Field in the SMTP transfer contains only the following text: <> I´ve allready set the value of myorigin in /private/etc/postfix/ main.cf but to no avail. Can somebody tell me where I can set the sender address of the vacation mail? Or is there something else wrong? Thank you very much. Best regards Wolfgang

3 2

[Dovecot] mobile phone access to dovecot
by casanova99 05 Aug '10

05 Aug '10

I didn't find anything interesting in the search, so I just wanted to see what other people have done (or thought about doing). I'd like to be able to access my dovecot server via IMAP, from the Internet, using the integrated e-mail client from a smart phone. I'm very concerned about security and don't feel comfortable just poking holes into the firewall for direct access from the Internet. Is there a better way to do this? Thanks. -- View this message in context: http://old.nabble.com/mobile-phone-access-to-dovecot-tp29342338p29342338.ht… Sent from the Dovecot mailing list archive at Nabble.com.

3 3

[Dovecot] IMAP access to dovecot list archives?
by Charles Marcus 05 Aug '10

05 Aug '10

Hi Timo, Before I go file a bug for Thunderbird, can you confirm that IMAP access to the dovecot mail list archives should still be working? TB is getting stuck in the account creation screen, and this may be confirmation of a bug they are having trouble isolating in the New Account Wizard. Thanks, -- Best regards, Charles

3 11

[Dovecot] LMTP: Rejecting unknown users
by Peer Heinlein 04 Aug '10

04 Aug '10

Hi! I'm using static results in LDAP-lookups: uris = ldap://127.0.0.1 dn = xxxxxxxxxxxxx dnpass = xxxxxxxxxxxx tls = no ldap_version = 3 base = xxxxxxxxxxxxxxxxx user_attrs = =home=/mail/%d/%n,=uid=10000,=gid=10000,jpberlinMailQuota=quota_rule=*:storage=%$B user_filter = (email=%u) pass_attrs = userPassword=password pass_filter = (email=%u) default_pass_scheme = PLAIN Unfortunately, LMTP accepts mail for *all* users, even for those users, that doesn't exist in LDAP at all: 010-08-04 12:27:58 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth 2010-08-04 12:27:58 auth: Debug: auth client connected (pid=10049) 2010-08-04 12:27:58 lmtp(10054): Debug: none: root=, index=, control=, inbox= 2010-08-04 12:27:58 auth: Debug: master in: USER 1 tessdfdfgdsft(a)example.org service=lmtp lip=(null) r ip=(null) 2010-08-04 12:27:58 auth: Debug: ldap(tessdfdfgdsft(a)example.org,0.0.0.0): user search: base=xxxxxxxxxxxxxxxxxxx 2010-08-04 12:27:58 auth: Debug: ldap(tessdfdfgdsft(a)example.org,0.0.0.0): no fields returned by the server 2010-08-04 12:27:58 auth: Debug: master out: USER 1 tessdfdfgdsft(a)example.org home=/mail/example.org/tessdfdfgd sft uid=10000 gid=10000 2010-08-04 12:27:58 lmtp(10054): Debug: auth input: tessdfdfgdsft(a)example.org home=/mail/example.org/tessdfdfgdsft uid=10000 gid= 10000 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: Effective uid=10000, gid=10000, home=/mail/example.org/tessdfd fgdsft 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no , list=yes, subscriptions=yes 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: maildir++: root=/mail/example.org/tessdfdfgdsft/Maildir, index =, control=, inbox=/mail/example.org/tessdfdfgdsft/Maildir 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: Namespace : type=shared, prefix=shared/%u/, sep=/, inbox=no, h idden=no, list=children, subscriptions=no 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: shared: root=/var/run/dovecot, index=, control=, inbox= Looks like the "allow_all_users"-Problem from the static database. :-) How can I tell LMTP do reject Mails to users, that doesn't exist in the database/LDAP? It's much better to do this in Dovecot/LMTP then in Postfix-Relay (which can then use LMTP for dynamic address verification). Peer -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030-405051-42 Fax: 030-405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

4 7