- dovecot - dovecot.org

[Dovecot] building a simple antispam plugin
by Alexander Prinsier 21 Apr '08

21 Apr '08

Hello, I'm trying to build another antispam plugin, but some things are a bit unclear. In backend_handle_mail I put store the signature returned from signature_extract into my antispam_transaction_context. In backend_commit it appears that the signature is empty. (It wasn't in backend_handle_mail). Somehow between backend_handle_mail en backend_commit it has been cleared... When I use i_strdup it appears to work. Anyone can tell me where this clearing happens? Is i_strdup the right way to do it then? Thanks, Alexander

3 4

[Dovecot] How to deal with mail to unknown virtual recipients?
by Andreas Ntaflos 19 Apr '08

19 Apr '08

Hello list, I am not quite sure whether this is a questions for Dovecot or Postfix. I have set up, virtual hosting for one domain (for test purposes) using a passwd-file as passdb and a static userdb (see dovecot -n at the end) along with Postfix in a manner described in [1], i.e. a non-Postfix mail store. Other than that I also do hosting for the canonical domain which is for users with a regular Unix account on the system (looked up via PAM) The virtual domain shall be "example.org", with two users "alice(a)example.org" and "bob(a)example.org". But today I received spam mail (which was correctly identified as such by amavisd-new) for "info(a)example.org" and "sales(a)example.org", two recipient addresses that do not exist. According to [1] "it's left up to the non-Postfix delivery agent to reject non-existent recipients from local submission or from local alias expansion." How to deal with such a situation? The sender address was clearly forged so returning a failed delivery message is pointless. The messages are now hanging around in the queue with a status of "deferred: temporary failure". The logs show: dovecot: auth(default): passwd(info(a)exmaple.org): unknown user dovecot: auth(default): passwd-file(info(a)mexample.org): unknown user dovecot: auth(default): static(info(a)example.org): passdb doesn't support lookups, can't verify user's existence postfix/pipe[25328]: C7EA18BC0B5: to=<info(a)exmaple.org>, relay=dovecot, delay=1.4, delays=0.07/0.02/0/1.3, dsn=4.3.0, status=deferred (temporary failure) The dovecot relay is defined in /etc/postfix/master.cf: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} The question, once again, is: what to do in such a situation? A catch-all address could be set up, but to what end? It would just catch a lot of spam over time. What is the correct way to deal with this? More importantly: is there even anything Dovecot could (or should) do? Thanks in advance, Andreas [1] http://www.postfix.org/VIRTUAL_README.html#in_virtual_other # 1.0.10: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): *:2000 ssl_cert_file: /path/to/ssl_cert ssl_key_file: /path/to/private_key login_dir: /var/run/dovecot//login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login mail_extra_groups: mail mail_location: maildir:~/Maildir maildir_copy_with_hardlinks: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): outlook-idle delay-newmail tb-extra-mailbox-sep imap_client_workarounds(imap): outlook-idle delay-newmail tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle imap_client_workarounds(managesieve): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_uidl_format(managesieve): sieve_storage(default): sieve_storage(imap): sieve_storage(pop3): sieve_storage(managesieve): ~/sieve sieve(default): sieve(imap): sieve(pop3): sieve(managesieve): ~/.dovecot.sieve namespace: type: public separator: / prefix: Public/ location: maildir:/var/mail/public:CONTROL=~/Maildir/control/public:INDEX=~/Maildir/index/public namespace: type: private separator: / inbox: yes auth default: mechanisms: plain login verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd passdb: driver: pam userdb: driver: passwd userdb: driver: static args: uid=vmail gid=vmail home=/home/vmail/%d/%u socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: vmail -- Andreas "daff" Ntaflos Vienna, Austria GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4

5 6

[Dovecot] Delete antispam emails
by David Reid 19 Apr '08

19 Apr '08

I'm using dovecot with the antispam plugin to allow for training, but how do I delete emails once they've been trained? If I delete them from the folder using an email client they get retrained as valid emails when they're moved to the trash folder! D'oh. I'm looking, ideally, for a solution that doesn't need a script to be run per user as I have a number of users using this feature. Also, the cleanspam script doesn't seem to be able to find the folder I'm using ('SpamTrain') so what format should I use? Thanks. david

3 11

[Dovecot] Cannot connect to dovecot imap server -- nothing in log
by David Benfell 18 Apr '08

18 Apr '08

Hello all, I'm trying to connect to a dovecot server I've just installed, using evolution. And I'm not having any success: starshine# tail -f /var/log/dovecot.log dovecot: 2008-04-16 20:11:37 Info: Dovecot v1.0.10 starting up dovecot: 2008-04-17 16:40:30 Warning: Killed with signal 15 dovecot: 2008-04-17 16:40:30 Info: Dovecot v1.0.10 starting up starshine# man dovecot starshine# dovecot -n # 1.0.10: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: none login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mail_location: maildir:~/Maildir:INBOX=~/failed-to-sort-Maildir:INDEX=% h/imap-folders namespace: type: private separator: / prefix: folders/ location: ~/imap-folders inbox: yes auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: pam userdb: driver: passwd starshine# All evolution tells me is that an error occurred. I have no idea what the problem is here. The server is on mail.parts-unknown.org if you wish to try to connect to it. And yes, it is actually running: starshine# ps aux | grep dovecot root 3072 0.0 0.0 2072 580 ? Ss 16:40 0:00 /usr/sbin/dovecot root 3073 0.0 0.1 9000 2148 ? S 16:40 0:00 dovecot-auth root 3559 0.0 0.0 3004 748 pts/0 R+ 16:48 0:00 grep dovecot starshine# I installed it from the Ubuntu package (hardy heron) and it is: starshine# dovecot --version 1.0.10 starshine# I'm simply mystified. What now? -- David Benfell benfell(a)parts-unknown.org Skype: greybeard95a

2 4

[Dovecot] CRAM-MD5 HMAC-MD5 password algorithm for PHP
by Hajo Noerenberg 18 Apr '08

18 Apr '08

Hi, based on the recent discussion by Bill Cole and Douglas Willcocks I've quickly put together a PHP script which generates MD5 'contexts' for Dovecot's password files: http://www.noerenberg.de/hajo/pub/dovecot_hmacmd5.php.txt The script has not been tested extensively, so use it on your own risk :) Most of the code has been shamelessly stolen from various sources. You'll find the names in the header of the script. Hajo

1 0

[Dovecot] Message UID Question
by Joe Allesi -X (joallesi - Coyote Creek Consulting at Cisco) 18 Apr '08

18 Apr '08

I have referred to the wiki and the RFC, but I still can't find the exact answer I'm looking for. From what I know, Dovecot uses the IMAP standard of 32 bit integers to uniquely identify messages. After a message is deleted from the mbox, can this UID ever be reissued to a new message or is that UID retired? What about after the 2 billion limit is reached? Thanks!

2 1

[Dovecot] Please help: LDAP configuration _almost_ works.
by Jack McKinney 18 Apr '08

18 Apr '08

Red Hat Linux release 7.2 (Enigma) OpenLDAP 2.3.38 Dovecot 1.0.12 SHORT VERSION ----- ------- Here is my dovecot-ldap.conf: hosts = ldap.lrtz dn = cn=varmail,ou=users,dc=lorentz,dc=com dnpass = ********* ldap_version = 3 auth_bind = yes pass_filter = (&(objectClass=inetOrgPerson)(mail=%Lu)) base = ou=users, dc=%Dd scope = onelevel I have tested using the above information with ldapsearch, and it works fine. However, when dovecot tries to authenticate the user, the LDAP server receives the query and responds to it (according to the LDAP log file), but dovecot just hangs there. 180 seconds later, it drops the IMAP client. E.g.: The dovecot log shows: Apr 3 08:13:21 fourier dovecot: auth(default): new auth connection: pid=15774 Apr 3 08:13:30 fourier dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=IMAP^Isecured^Ilip=x.x.x.x^Irip=y.y.y.y^Iresp=<hidden> Apr 3 08:13:30 fourier dovecot: auth(default): ldap(jackmc(a)lorentz.com,y.y.y.y): bind search: base=ou=users, dc=lorentz,dc=com filter=(&(objectClass=inetOrgPerson)(mail=jackmc(a)lorentz.com)) Apr 3 08:16:30 fourier dovecot: imap-login: Disconnected: Inactivity: method=PLAIN, rip=y.y.y.y, lip=x.x.x.x, TLS The OpenLDAP log shows that the query is received and that it returns a match: Apr 3 08:13:30 fourier slapd[14039]: conn=7 op=3 SRCH base="ou=users,dc=lorentz,dc=com" scope=1 deref=0 filter="(&(objectClass=inetOrgPerson)(mail=jackmc(a)lorentz.com))" Apr 3 08:13:30 fourier slapd[14039]: conn=7 op=3 SRCH attr=uid Apr 3 08:13:30 fourier slapd[14039]: conn=7 op=3 SEARCH RESULT tag=101 err=0 nentries=1 text= LONG VERSION ---- ------- My users login using their email address as username. Each domain has their own LDAP subtree. Each user has an entry in the ou=users subtree of the domain subtree, and has a mail: field (inetOrgPerson) listing their email address/login name. I am trying to use auth_bind: when I login with jackmc(a)lorentz.com, dovecot should search for mail=jackmc(a)lorentz.com in the onelevel below ou=users,dc=lorentz,dc=com and find me as "cn=Jack McKinney,ou=users,dc=lorentz,dc=com". I have created an entry in LDAP (varmail) that should be able to do this query. Indeed, from the command line, it works: ldapsearch -h ldap.lrtz -b 'ou=users, dc=lorentz, dc=com' -D 'cn=varmail,ou=users,dc=lorentz,dc=com' -x -W -s onelevel '(&(objectClass=inetOrgPerson)(mail=jackmc(a)lorentz.com))' Enter LDAP Password: # extended LDIF # # LDAPv3 # base <ou=users, dc=lorentz, dc=com> with scope oneLevel # filter: (&(objectClass=inetOrgPerson)(mail=jackmc(a)lorentz.com)) # requesting: ALL # # Jack McKinney, users, lorentz.com dn: cn=Jack McKinney,ou=users,dc=lorentz,dc=com objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetOrgPerson cn: Jack McKinney givenName: Jack McKinney sn: McKinney mail: jackmc(a)lorentz.com # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 It appears that dovecot performs the above query successfully, but then never uses the password and retrieved DN to attempt to bind and authenticate the user. Instead, it just times out. (See log files above in the SHORT VERSION). I tried to add pass_attrs, in case there was a bug in dovecot where it ignores the reply if there are no pass_attrs (even though none are needed), but it still fails the same way. Timo Sirainen suggested that I add a debug line to src/auth/db-ldap.c ldap_input() around line 372: msgid = ldap_msgid(res); // added line: i_info("LDAP: Received reply %d", msgid); I did this. Now, when the server first starts up, this line is logged. However, it is not logged when it queries the LDAP server as a result of an IMAP connection needing authentication. -- Jack McKinney GPG 1024D/99C6A174 jackmc(a)lorentz.com YM:lfaatsnat2006 AIM:jackmclorentz "There is no parameter that makes it impossible for you to perform still more excellently." -Mario Cuomo, on the lack of a clock in baseball

7 25

Re: [Dovecot] Mixing LDAP and static
by k bah 18 Apr '08

18 Apr '08

That didn't work for me: user_attrs = =home=/var/dovecot-test/home/%n,uid=user (at /etc/dovecot/dovecot-ldap.conf) ( /etc/dovecot/dovecot.conf: mail_location = mbox:/var/dovecot-test/data/%n~%d:INBOX=/var/dovecot-test/%n~%d:INDEX=/var/dovecot-test-no-quotas/index/%n~%d ) neither: user_attrs = uid=user,=home=/var/dovecot-test/home/%n neither: user_attrs = =home=/var/dovecot-test/home/%n on the log it says: dovecot: auth(default): ldap(user0027(a)mydomain.tld,1xx.xxx.xxx.x): user search: base=dc=mydomain,dc=tld scope=subtree filter=(&(objectclass=inetlocalmailrecipient)(mail=user0027(a)mydomain.tld)) fields= and at dovecot start up: Starting dovecot ILoading modules from directory: /usr/lib64/dovecot/modules/imap IModule loaded: /usr/lib64/dovecot/modules/imap/lib10_quota_plugin.so IModule loaded: /usr/lib64/dovecot/modules/imap/lib11_imap_quota_plugin.so IEffective uid=65534, gid=65534, home= using dovecot-1.0.5-6 on OpenSuSE 10.3. thanks = Arthritis Specialists in Magnetism Quality hand crafted jewelry with magnets. Necklaces, bracelets, shoe insoles and more. http://a8-asy.a8ww.net/a8-ads/adftrclick?redirectid=dfcb5a2d4f25ae3051a9c94… -- Powered by Outblaze

3 2

[Dovecot] authentication troubles
by Albert Dengg 18 Apr '08

18 Apr '08

hi i have a strange problem with my dovecot installtion: i configured it to accept digest-md5 authentication only but for some reason mailclients (i tried mutt and thunderbird so far) want to log with PLAIN (which fails of course). authentication basically works, e.g. if i explicitly set set imap_authenticators="digest-md5 in .muttrc everything works... any idea what is going wrong? config attached below tia yours albert # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps pop3s ssl_listen(default): *:22993 ssl_listen(imap): *:22993 ssl_listen(pop3): *:22995 ssl_cipher_list: ALL:!LOW login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login first_valid_uid: 107 last_valid_uid: 107 mail_location: maildir:%h/Maildir mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 namespace: type: private location: maildir:%h/Maildir inbox: yes auth default: mechanisms: digest-md5 realms: mailstore.nicenamecrew.com default_realm: mailstore.nicenamecrew.com username_format: %Lu verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=vmail gid=vmail home=/var/mail/virtual/%d/%n socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 group: vmail

2 2

[Dovecot] postfix, dovecot-lda, sieve & smartsieve not working on 1.1-rc4
by kjetil＠hoiseth.no 18 Apr '08

18 Apr '08

Seems there is a bug in 1.1-rc4 in regards to sieve/managesieve, this problem goes away if I downgrade to 1.0.13. Gentoo x86_64 2.6.18-028stab053 (OpenVZ) Intel(R) Core(TM)2 Quad CPU Q6600 Maildirs are not NFS mounted The VE in question runs daemons with the following USE flags; mail-mta/postfix-2.4.6-r2 USE="dovecot-sasl ipv6 ldap mailwrapper mysql pam ssl" net-mail/dovecot-1.0.13-r1 USE="ipv6 ldap managesieve mysql pam sieve ssl" Sieve rules are setup only in Smartsieve(1.0-RC2), running in Lighttpd(1.4.18-r3). --- # 1.0.13: /etc/dovecot/dovecot.conf protocols: imaps managesieve ssl_cert_file: /etc/ssl/private/hoiseth.no.pem ssl_key_file: /etc/ssl/private/hoiseth.no.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login mail_location: maildir:~/.maildir mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(managesieve): /usr/lib64/dovecot/managesieve sieve_storage(default): sieve_storage(imap): sieve_storage(managesieve): ~/sieve sieve(default): sieve(imap): sieve(managesieve): ~/.dovecot.sieve auth default: passdb: driver: pam args: login userdb: driver: passwd --- 1.1-rc4; deliver(kjetil): Apr 04 15:17:43 Info: Loading modules from directory: /usr/lib/dovecot/lda deliver(kjetil): Apr 04 15:17:43 Info: Module loaded: /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so deliver(kjetil): Apr 04 15:17:43 Info: maildir: data=/home/kjetil/.maildir deliver(kjetil): Apr 04 15:17:43 Info: maildir++: root=/home/kjetil/.maildir, index=, control=, inbox=/home/kjetil/.maildir deliver(kjetil): Apr 04 15:17:43 Info: msgid=<567340a538d370592ec2a6da4e0fcdf2(a)langtind.no>: saved mail to INBOX 1.0.13; deliver(kjetil): Apr 04 15:33:14 Info: Loading modules from directory: /usr/lib/dovecot/lda deliver(kjetil): Apr 04 15:33:14 Info: Module loaded: /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so deliver(kjetil): Apr 04 15:33:14 Info: maildir: data=/home/kjetil/.maildir deliver(kjetil): Apr 04 15:33:14 Info: maildir: root=/home/kjetil/.maildir, index=/home/kjetil/.maildir, control=, inbox= deliver(kjetil): Apr 04 15:33:14 Info: cmusieve: Using sieve path: /home/kjetil/.dovecot.sieve deliver(kjetil): Apr 04 15:33:14 Info: cmusieve: Executing script /home/kjetil/.dovecot.sievec deliver(kjetil): Apr 04 15:33:14 Info: msgid=<4b15e68896a9ef204bf00482e948058f(a)langtind.no>: saved mail to priv I upgraded to 1.1-rc4 and indeed the problem re-occured, Id be happy to bring more info/ax to the VE if it helps nailing the issue.

2 1