- dovecot - dovecot.org

Re: [Dovecot] dovecot user
by Stan Hoeppner 27 Mar '10

27 Mar '10

Timo Sirainen put forth on 3/27/2010 2:18 AM: > On Sat, 2010-03-27 at 02:10 -0500, Stan Hoeppner wrote: >>> Maybe the native english speakers (and I'd think only a subset of them too). I had never heard of dovetail. >> >> I'm guessing that's because you're not a woodworker, or know any. ;) It's a >> great hobby if you ever found the spare time. > > Sure. But we're talking about UNIX admin kind people here. Somehow I > doubt they spent much attention to woodworking classes at school (we > actually had such classes, and I might know the Finnish word for > dovetail if someone told me it, but I doubt it's common knowledge in > either language). Probably depends on what city/state/province/country as well. I'm in the midwest USA, and alot of people in general, sysadmins or not, are DIY type folks. You grow up on a farm or in a small town and learn a whole lot of non computer stuff (including basic woodworking) before going to college and then to the big city for the sysadmin job. Then you visit mom/dad on the weekends, and they have you rebuilt the kitchen and bathroom. Then you decide to rebuild your own kitchen and bathroom. And then your neighbors find out you know how to do that kind of work and ... you lose a few more weekends. :( >>> I want something that's at least potentially understandable to people who understand english (and not just native speakers). I wouldn't know why some process is owned by user "dovel". That might not even make me realize it's a Dovecot process. >> >> How about "pigeon"? Dovecots house two kinds of birds, doves, and, far more >> often, pigeons. So, pigeon should be the new user name. No one knows what >> the heck a "dovecot" is until they look it up anyway (at least non Scots), >> so using "pigeon" is in keeping with naming your server Dovecot. There. >> Now that that's settled... > > But Dovecot is the name of the software, and admins know that, even if > they have no clue what it means. dove* as the username makes them think > of Dovecot regardless. You think anyone is going to add the user "pigeon" to any groups? I'm thinking that, as with "dovenull", that most would avoid touching "pigeon" at all costs. Then again, some may think their system was hacked, and want to remove the user "pigeon" lol. If your main goal is getting people to leave that user alone, I think pigeon would definitely fit the bill. And it adds a bit of humor to the mix since pigeons tend to crap all over everything. ;) >> dovecot dove-main >> dovecot-auth dove-auth >> imap-login dove-imaplgn >> pop3-login dove-poplgn >> imap dove-imap >> pop3 dove-pop3 >> >> Just a thought. But a nice thought at that. :) > > But you're talking about process names, right? That's already changed in > v2.0. You have one "dovecot" process and everything else is "dovecot/*". > For example: > > root 1840 0.0 0.0 43140 1328 pts/0 S+ 05:02 0:00 /usr/local/sbin/dovecot -F > dovecot 1841 0.0 0.0 30568 976 pts/0 S+ 05:02 0:00 dovecot/anvil > root 1842 0.0 0.0 30676 1120 pts/0 S+ 05:02 0:00 dovecot/log > root 2500 0.0 0.1 38524 2760 pts/0 S+ 08:59 0:00 dovecot/lmtp > root 2501 0.0 0.2 37684 4372 pts/0 S+ 08:59 0:00 dovecot/config > dovecot 2502 0.0 0.1 68500 3112 pts/0 S+ 08:59 0:00 dovecot/auth Ahh, sw333t! I haven't played with 2.0 yet so I hadn't seen this yet. That's precisely the kinda thing I had in mind. See? Great minds think alike. (most of the time anyway) ;) -- Stan

1 0

[Dovecot] dovecot user
by Stan Hoeppner 27 Mar '10

27 Mar '10

Sorry, meant this to go to the list. Timo Sirainen put forth on 3/27/2010 12:08 AM: > On 27.3.2010, at 6.49, Stan Hoeppner wrote: > >>> Tail just doesn't make much sense to me. Also it's not completely free >>> of pornographic associations either. :) >> >> No, no, totally free of pornographic connotation. Dovetail is a type of >> woodworking joint. That's what the vast majority of people on planet earth >> will associate "dovetail" with anyway. > > Maybe the native english speakers (and I'd think only a subset of them too). I had never heard of dovetail. I'm guessing that's because you're not a woodworker, or know any. ;) It's a great hobby if you ever found the spare time. >>> So my last idea: doveless. "It's less of a dovecot process." To me it >>> seems closer to perfect as anything I've seen so far. >> >> Or how about just "dovel", a crafty word smithing merge of dovecot+shovel? >> Although I'm unsure of any parallels between the work done by this thing and >> that performed by a shovel. ;) Still, it's catchy. > > I want something that's at least potentially understandable to people who understand english (and not just native speakers). I wouldn't know why some process is owned by user "dovel". That might not even make me realize it's a Dovecot process. How about "pigeon"? Dovecots house two kinds of birds, doves, and, far more often, pigeons. So, pigeon should be the new user name. No one knows what the heck a "dovecot" is until they look it up anyway (at least non Scots), so using "pigeon" is in keeping with naming your server Dovecot. There. Now that that's settled... Kinda related to the current subject, naming things, I personally believe renaming all of the processes with a "dove-" or similar at the start of the process name would be nice. I wish Wietse would do so with Postfix as well, although I've not mentioned it (yet). Something like this: dovecot dove-main dovecot-auth dove-auth imap-login dove-imaplgn pop3-login dove-poplgn imap dove-imap pop3 dove-pop3 Just a thought. But a nice thought at that. :) -- Stan

1 0

[Dovecot] corrupted mbox
by Jernej Porenta 27 Mar '10

27 Mar '10

Heya, we have two IMAP (UW-imap and dovecot) servers accessing the same mbox files for our users (don't ask why) and sometimes the UW-imap corrupts the mbox file. The mbox looks just like normal mbox except it does not have the proper 'From ' beginning of the file (usually there are some random tidbits in the begining of the file, which can be easily stripped to recover the working mbox). The problem is that if we use dovecot for POP3 server, the dovecot logs the mbox corruption just fine: POP3(username): Couldn't init INBOX: Mailbox isn't a valid mbox file But if we use IMAP for the same mailbox, dovecot opens the file and does not report any corruption, the user on the other hand sees just empty mailbox. So I was wondering if there are any possibilities to report mbox corruption with IMAP as well? thanks in advance, regards, Jernej

2 4

[Dovecot] shared mailboxes, mkdir_parents problem
by Leo Unglaub 27 Mar '10

27 Mar '10

Hi Friends, i have a little problem with my Dovecot installation. The normal installation works very well and now i have to configurate dovecot that all member from a domain can access all mailboxes from this domain. I configurate the shared namespace and set the IMAP ACL Flag but i can't abonement the other mailboxes. I get a error in the logs: > 2010-03-18 10:03:04 IMAP(unglaub): Info: maildir: > data=/var/mails/e-c-o.at/kirchmeir:INDEX=/var/mails/e-c-o.at/shared/mitarbeiter/kirchmeir > > 2010-03-18 10:03:04 IMAP(unglaub): Info: maildir++: > root=/var/mails/e-c-o.at/kirchmeir, > index=/var/mails/e-c-o.at/shared/mitarbeiter/kirchmeir, control=, > inbox=/var/mails/e-c-o.at/kirchmeir > 2010-03-18 10:03:04 IMAP(unglaub): Info: acl: initializing backend > with data: vfile:/etc/dovecot-acl > 2010-03-18 10:03:04 IMAP(unglaub): Info: acl: acl username = unglaub > 2010-03-18 10:03:04 IMAP(unglaub): Info: acl: owner = 0 > 2010-03-18 10:03:04 IMAP(unglaub): Info: acl vfile: Global ACL > directory: /etc/dovecot-acl > 2010-03-18 10:03:04 IMAP(unglaub): Info: acl vfile: file > /etc/dovecot-acl//.DEFAULT not found > 2010-03-18 10:03:04 IMAP(unglaub): Info: Namespace > shared/mitarbeiter/kirchmeir/: Permission lookup failed from > /var/mails/e-c-o.at/kirchmeir > 2010-03-18 10:03:04 IMAP(unglaub): Info: Namespace > shared/mitarbeiter/kirchmeir/: Using permissions from > /var/mails/e-c-o.at/kirchmeir: mode=0700 gid=-1 > 2010-03-18 10:03:04 IMAP(unglaub): Error: > mkdir_parents(/var/mails/e-c-o.at/kirchmeir) failed: Permission denied In this case the User unglaub(a)e-c-o.at try to access the mailbox kirchmeir(a)e-c-o.at. My config looks like this: > mail:~# dovecot -n > # 1.2.11: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.30-bpo.1-amd64 x86_64 Debian 5.0.4 ext3 > log_path: /var/log/dovecot/dovecot.log > log_timestamp: %Y-%m-%d %H:%M:%S > disable_plaintext_auth: no > login_dir: /var/run/dovecot/login > login_executable: /usr/lib/dovecot/imap-login > mail_privileged_group: mail > mail_uid: 501 > mail_gid: 501 > mail_location: maildir:/var/mail/%d/%n > mail_debug: yes > maildir_copy_preserve_filename: yes > mbox_write_locks: fcntl dotlock > mail_plugins: acl imap_acl > namespace: > type: private > separator: / > inbox: yes > list: yes > subscriptions: yes > namespace: > type: shared > separator: / > prefix: shared/mitarbeiter/%%n/ > location: maildir:/var/mails/e-c-o.at/%%n:INDEX=/tmp/%%n > list: children > lda: > postmaster_address: postmaster(a)e-c-o.at > mail_plugins: acl > auth_socket_path: /var/run/dovecot/auth-master > log_path: /var/log/dovecot/dovecot-deliver-errors.log > info_log_path: /var/log/dovecot/dovecot-deliver.log > auth default: > default_realm: e-c-o.at > passdb: > driver: ldap > args: /etc/dovecot/dovecot-ldap.conf > userdb: > driver: ldap > args: /etc/dovecot/dovecot-ldap.conf > socket: > type: listen > client: > path: /var/spool/postfix/private/auth > mode: 432 > user: postfix > group: postfix > master: > path: /var/run/dovecot/auth-master > mode: 384 > user: dovecot-data > group: dovecot-data > plugin: > acl: vfile:/etc/dovecot-acl > acl_shared_dict: file:/var/mail/%d/shared-mailboxes.db Do you have any idea why my setup isn't working correct? My users are stored in a LDAP (openLDAP) Server and the login works very well. For completion i post the LDAP-File to. > mail:~# grep -v '^ *$#.*$\?$' /etc/dovecot/dovecot-ldap.conf > hosts = 192.168.1.230 > dn = cn=ldapadmin,dc=e-c-o,dc=net > dnpass = xxxxxxxx > ldap_version = 3 > base = ou=smbUser,ou=dc,ou=at,dc=e-c-o,dc=net > scope = subtree > user_filter = (&(objectClass=posixAccount)(uid=%n)) > user_attrs = mail=mail > pass_filter = (&(objectClass=posixAccount)(uid=%n)) > pass_attrs = uid=user,userPassword=password,\ > homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid > default_pass_scheme = CRYPT Thank you very much. Greetings from Austria Leo

4 3

[Dovecot] mail_save_crlf Semantics
by Sabahattin Gucukoglu 27 Mar '10

27 Mar '10

Hi, It's not clear from the configuration when CR/LF conversion happens with mail_save_crlf set. Does this only happen with appends, or do all mails handled by Dovecot always get converted when opened? Cheers, Sabahattin

2 1

[Dovecot] 2.0.beta4 compile errors
by Steven King 27 Mar '10

27 Mar '10

I am unable to get 2.0.beta4 to compile. I get the following errors: /usr/lib64/gcc/x86_64-slackware-linux/4.3.3/../../../../lib64/libwrap.a(hosts_access.o): In function `host_match': hosts_access.c:(.text+0x625): undefined reference to `yp_get_default_domain' collect2: ld returned 1 exit status make[3]: *** [tcpwrap] Error 1 make[3]: Leaving directory `/root/dovecot/dovecot-2.0.beta4/src/util' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/dovecot/dovecot-2.0.beta4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/dovecot/dovecot-2.0.beta4' make: *** [all] Error 2 Any help would be appreciated. -- Steve King Senior Linux Engineer - Advance Internet, Inc. Cisco Certified Network Associate CompTIA Linux+ Certified Professional CompTIA A+ Certified Professional

2 1

[Dovecot] dovecot 2.0beta4 zlib
by Renaud Allard 27 Mar '10

27 Mar '10

Hello, When trying to enable the zlib and imap_zlib plugins, I get the following error: imap: dovecot/imap:/opt/dovecot/lib/dovecot/lib2 0_zlib_plugin.so: undefined symbol 'i_stream_create_bz2' I did not compile it using --with-bzlib though and bz2 libs are available on the system. Best Regards

2 1

[Dovecot] cmusieve auto-reply and quota
by Mauro Faccenda 27 Mar '10

27 Mar '10

Hi there, I'm quite new to Dovecot, but already can tell that it is a really great work, congrats to the developers! But I'm having a little problem and couldn't figure it out how to solve. First, let me talk about my setup: I'm running Debian 5 (Lenny) with it's default Dovecot (common, pop3 and imap) packages (version 1:1.0.15-2.3+lenny1), I really would like to keep it this way unless I haven't another option. All authentication is made through a MS Active Directory and messages delivered to a virtual mailbox (/var/vmail/<domain>/<mailbox>), using Postfix as SMTP, that uses procmail (just for filtering the messages, not to deliver) that calls Dovecot's deliver like this: -- :0 w | $DELIVER -d $RECIPIENT -e -- $DELIVER points to /usr/lib/dovecot/deliver and $RECIPIENT is fed by Postfix in it's master.cf All this work great. Then I needed to enable quotas it's working as well. Here is the section that show how I've set it up: -- protocol lda { mail_plugin_dir = /usr/lib/dovecot/modules/lda mail_plugins = cmusieve quota postmaster_address = postmaster(a)do.ma.in hostname = mybox.do.ma.in auth_socket_path = /var/run/dovecot/auth-master quota_full_tempfail = no } -- I also want to run some sieve scripts just to be able to do some auto-replies (i.e. Out of office), and also it works well. Here is an example of a sieve I was using in some tests: -- require ["fileinto", "vacation"]; if header :contains "X-DSPAM-Result" "Spam" { stop; } vacation :days 1 :subject "Out of office reply" :addresses ["john.doe(a)do.ma.in", "jd(a)do.ma.in"] "I'm out of office, please contact Joan Doe instead. Best regards John Doe"; -- And as I said it works. But when I send a message to this mailbox that could exceed it's quota I get this on my logs: -- Mar 25 14:02:25 mybox postfix/pickup[21407]: 68D1DA82F: uid=103 from=<> Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): msgid=<4BAB9728.6000601(a)other.do.ma.in>: sent vacation response to <faccenda(a)other.do.ma.in> Mar 25 14:02:25 mybox postfix/cleanup[22119]: 68D1DA82F: message-id=<dovecot-1269536545-332912-0(a)do.ma.in> Mar 25 14:02:25 mybox postfix/qmgr[17299]: 68D1DA82F: from=<>, size=623, nrcpt=1 (queue active) Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): msgid=<4BAB9728.6000601(a)other.do.ma.in>: save failed to INBOX: Quota exceeded Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): sieve runtime error: Keep: Generic Error Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): sieve_execute_bytecode(/var/vmail/do.ma.in/john.doe/.dovecot.sievec) failed Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): msgid=<4BAB9728.6000601(a)do.ma.in>: Rejected: Quota exceeded Mar 25 14:02:25 mybox postfix/pipe[22086]: 7C666A825: to=<john.doe(a)do.ma.in>, relay=procmail, delay=1.1, delays=0.39/0/0/0.68, dsn=4.3.0, status=deferred (temporary failure) -- And every time the server tries again to deliver that message it re-sends the auto-reply. Is it an undesirable behavior, isn't it? Does anyone knows how to address it? Also, I thought that that configuration (using the -e parameter to deliver) and the "quota_full_tempfail = yes" would make give an permanent error, not trying to deliver that message again. What is wrong about it? Thanks in advance,

2 1

[Dovecot] A questions about consume_results (driver-pgsql.c)
by Rainer Weikusat 27 Mar '10

27 Mar '10

Code -------------- static void consume_results(struct pgsql_db *db) { do { if (!PQconsumeInput(db->pg)) break; if (PQisBusy(db->pg)) return; } while (PQgetResult(db->pg) != NULL); if (PQstatus(db->pg) == CONNECTION_BAD) io_remove_closed(&db->io); else io_remove(&db->io); db->querying = FALSE; if (db->queue != NULL && db->connected) queue_send_next(db); } --------------- This is the only part of the driver-pgsql.c code where a CONNECTION_BAD does not result in driver_pgsql_close being called. This will likely happen after the next query (from queue or a new one) failed because the connection was bad. Is there a reason for this?

2 2

[Dovecot] v2.0.beta4 released
by Timo Sirainen 27 Mar '10

27 Mar '10

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz.sig I think this release is finally feature complete. There are still some bugs left to be fixed, but it's mainly in the dsync/mdbox area. v2.0.rc1 should hopefully be out in a couple of weeks. After that v2.0.0 will be released after no serious bugs have been found for a couple of weeks. Major changes since beta3: - auth process now runs as $dovecot_internal_user ("dovecot") by default. Auth worker processes still run as root by default, so this won't break PAM etc, but it could break passwd-file configurations. - It can now read v1.2's dovecot.conf file. If you find that it won't read your config, let me know and I'll see about adding code to fix it. It'll log warnings about each obsolete setting it sees. The easiest way to get rid of the warnings is to just translate your old config to v2.0: doveconf -n -c old.conf > new.conf - auth passdb/userdb configuration in example-config is now a bit different .. hopefully less confusing to new people than the old one. - added support for auth settings (including passdb/userdb) inside protocol sections, so it'll affect only those protocols - mail_plugins can now be set more easily. you can have a single global mail_plugins and then add more plugins to it like protocol imap { mail_plugins = $mail_plugins imap_quota } - doveconf finally shows all settings, including all protocol, local and remote sections - doveadm quota get|recalc command added. This is a plugin (yeah, doveadm now supports plugins!), so you must have a global mail_plugins=quota setting for the command to show up. - doveadm kick user/network to kick out logged in users (by sending TERM signal to processes). This was written by Pascal Volk. - and of course tons and tons of fixes all around

6 11

[Dovecot] dovecot 2.0 fails self-tests
by Michal Hlavinka 26 Mar '10

26 Mar '10

Hi, is it expected that dovecot 2.0.beta4 pass all of it's self-tests or some failures are normal? I've tried make check and everything passed up to this test: ... message_date_parse(7) ................................................ : ok 0 / 8 tests failed test-message-decoder.c:67: Assert failed: message_decoder_decode_next_block(ctx, &input, &output) test-message-decoder.c:78: Assert failed: output.size == 3 test-message-decoder.c:84: Assert failed: output.size == 14 test-message-decoder.c:85: Assert failed: memcmp(output.data, " bar", 14) == 0 message decoder ...................................................... : FAILED 1 / 1 tests failed Regards, Michal Hlavinka

2 3

[Dovecot] CentOS yum update causing died unexpectedly
by dovecot＠corwyn.net 26 Mar '10

26 Mar '10

Running CentOS 5.x running a postfix/dovecot implementation. Dovecot 1.1.8. I just ran a full system update in my dev environment, and now I'm occasionally getting: Mar 26 07:15:43 example dovecot: auth(default): worker-server(test222(a)int.example.com,127.0.0.1): Aborted: Worker process died unexpectedly in /var/log/maillog. Any suggestions on where to look to figure out what's causing this? I don't see that error at all in the past 4 weeks of logs in production. Thanks Rick Rick Steeves http://www.sinister.net In reality nothing is more damaging to the adventurous spirit within a man than a secure future - Alexander Supertramp

2 1

[Dovecot] quota dict with mysql 4.0
by Andre Hübner 26 Mar '10

26 Mar '10

Hello, i use successfully mysql-quotasystem with dovecot 1.2.11 on different servers except for mysql 4.0 servers dovecot internally uses sql: "ON DUPLICATE KEY UPDATE" which was introduced in mysql 4.1 Is there a chance to make this statement mysql 4.0 compatible or should i update mysql? i want to avoid updating mysql because some old software is running which is not compatible to higher mysql versions. Thanks, Andre

5 6

[Dovecot] test
by total＠example.com 25 Mar '10

25 Mar '10

test

4 3

[Dovecot] outgoing mails
by Ing. Hugo Ruiz de Huidobro 25 Mar '10

25 Mar '10

Hello, I need to restrict outgoing email. I am using RedHat CentOS 4.7 and Dovecot 0.99.11 Today all users can send emails to Internet. But some people should only be able to send email to other user in this mail server. Just a few persons can send emails to the Internet. How can I do that? THANKS! Hugo

2 1

[Dovecot] Dovecot 2.0beta4
by Renaud Allard 25 Mar '10

25 Mar '10

Hello, It seems dovecot 2.0 beta4 still behave strangely without tcpwrap. I still get the errors: 2010-03-25_17:26:59.33848 Fatal: service(tcpwrap) access(/opt/dovecot/libexec/dovecot/tcpwrap) failed: No such file or directory 2010-03-25_17:27:00.36108 Fatal: service(tcpwrap) access(/opt/dovecot/libexec/dovecot/tcpwrap) failed: Permission denied It's easy to solve by touching and chmodding 0755 that file, but prod version shouldn't exhibit that behavior. Best Regards

2 1

[Dovecot] 1.2.11 nfs_flush_file_handle_cache_dir problems
by Ade Fewings 25 Mar '10

25 Mar '10

Hi chaps We're using the mbox_snarf plugin to snarf mail from /var/mail/%U to ~%U/Mail/inbox and using dotlocking on all accesses. This is on Solaris with NFS mounted home directories. We're getting a few (very few) of these for just a couple of users: Error: nfs_flush_file_handle_cache_dir: rmdir(/var/mail) failed: Device busy Which, having searched, I see some discussion of in the past, but not with 1.2. We're using: mail_privileged_group = mail For the /var/mail 'inboxes', which I thought would tackle this problem. Couple of questions, if you don't mind: 1. Does dovecot user need to be a member of the mail group? 2. Does this error message represent a real problem that needs solving? It's very strange how rare it is and that only a few select users have encountered. Full dovecot.conf below: > # 1.2.11: /usr/local/dovecot-1.2.11-b/etc/dovecot.conf > # OS: SunOS 5.10 sun4v > log_path: /usr/local/dovecot/var/dovecot.log > protocols: imap imaps pop3 pop3s > listen(default): *:143 *:10143 *:20143 *:30143 *:40143 *:50143 > listen(imap): *:143 *:10143 *:20143 *:30143 *:40143 *:50143 > listen(pop3): *:110 > ssl_listen(default): *:993 *:10993 > ssl_listen(imap): *:993 *:10993 > ssl_listen(pop3): *:995 > ssl: no > ssl_cipher_list: MEDIUM:!LOW > disable_plaintext_auth: no > shutdown_clients: no > login_dir: /usr/local/dovecot-1.2.11-b/var/run/dovecot/login > login_executable(default): > /usr/local/dovecot-1.2.11-b/libexec/dovecot/imap-login > login_executable(imap): > /usr/local/dovecot-1.2.11-b/libexec/dovecot/imap-login > login_executable(pop3): > /usr/local/dovecot-1.2.11-b/libexec/dovecot/pop3-login > max_mail_processes: 1024 > verbose_proctitle: yes > mail_privileged_group: mail > mail_location: mbox:~/Mail:INBOX=/var/mail/%u > mail_debug: yes > mmap_disable: yes > mail_nfs_storage: yes > mail_nfs_index: yes > lock_method: dotlock > mbox_read_locks: dotlock > mbox_write_locks: dotlock > mail_executable(default): /usr/local/dovecot-1.2.11-b/libexec/dovecot/imap > mail_executable(imap): /usr/local/dovecot-1.2.11-b/libexec/dovecot/imap > mail_executable(pop3): /usr/local/dovecot-1.2.11-b/libexec/dovecot/pop3 > mail_plugins: mbox_snarf > mail_plugin_dir(default): /usr/local/dovecot-1.2.11-b/lib/dovecot/imap > mail_plugin_dir(imap): /usr/local/dovecot-1.2.11-b/lib/dovecot/imap > mail_plugin_dir(pop3): /usr/local/dovecot-1.2.11-b/lib/dovecot/pop3 > auth default: > verbose: yes > debug: yes > passdb: > driver: pam > passdb: > driver: passwd > args: blocking=yes > userdb: > driver: passwd > args: blocking=yes > plugin: > mbox_snarf: ~/Mail/inbox Much appreciate your time, it has made an amazing difference here, I'm just seeking absolute perfection I think (well, mbox perfection anyway). ~~ Ade -- Centre for Advanced Software Technology Limited is a limited company registered in England and Wales. Postal Address: C.A.S.T. Limited, Technium CAST, Ffordd Penlan, Parc Menai, Bangor, Gwynedd. LL57 4HJ. Registered Number: 04473521. Registered Office: Finance Office, Bangor University, College Road, Bangor, Gwynedd. LL57 2DG. www.techniumcast.com

2 4

[Dovecot] Dovecot-1.2 + Sieve + Managesieve on Debian
by Proskurin Kirill 25 Mar '10

25 Mar '10

Hello! I think about migrate from FreeBSD to Linux because I need DRBD for clustering. I want to use Debian Lenny but run on some problems. I want near latest Dovecot packages. Native repos are too old. Backports seems to don`t have a Sieve&Managesieve support and we need it(am I wrong?). Stephan Bosch auto packeges is not for production. How could I solve this without make own packages? What Debian folk`s do in this situation? P.S. I don`t want to use RedHat like OS because I not familiar with it. -- Best regards, Proskurin Kirill

10 20

[Dovecot] can Dovecot do VERP?
by Rick Graves 25 Mar '10

25 Mar '10

Hey, I have several thousand email addresses, the vast majority of which are definitely no good, and I want to figure out which are good. So I will send out an email to all the email addresses. By making a list of the ones that bounced, and comparing that list with the full list, I can determine which are still good. This is for a non-profit association -- I am not in the spam business. Knowing exactly which emails bounced would be much easier if I could set up an in box implementing VERP. http://en.wikipedia.org/wiki/Variable_envelope_return_path In other words, I want an in box accepting all mail where the email addresses match a wildcard pattern like this: mail_admin_??????(a)domain.org, where ?????? are 6 digits. The digits would be a scrambled contact ID. Since they will be digits only, here is the regular expression: mail_admin_\d{6}. (We will pick a wildcard pattern that does not conflict with any existing address on the server.) Sending the outgoing emails, each with a different "From" address matching the wildcard pattern, is not a problem -- I have a working python script for this. The challenge is getting one in box to accept emails with different "From" addresses (matching the wildcard pattern). We are running IMAP server Dovecot 1.0.7. How do I set this up in the IMAP server to accept emails to addresses matching the wildcard pattern? Thanks, Rick Graves

4 4

Re: [Dovecot] quota dict with mysql 4.0
by Andre Hübner 25 Mar '10

25 Mar '10

(sorry, i only read the digest version of list and always create i new thread by "fake-Re") Hello, >> Perhaps you can implement some updating procedure that >> would only involve a percentage of your users at one time. no way, i want to fix this! but i need help because i have no idea of c-programming. i can read the code a little bit, but never lerned it. solution is to edit dovecot-1.2.11/src/lib-dict/dict-sql.c i can avoid using ON DUPLICATE KEY UPDATE by changing line 91 to: orig: dict->has_on_duplicate_key = strcmp(driver->name, "mysql") == 0; changed: dict->has_on_duplicate_key = strcmp(driver->name, "mysqlXXX") == 0; this works only 50%. if a user has no entry in quotatable, dovecot is updating his quota with 2 queries: INSERT INTO quota (bytes,username) VALUES ('2456','myuser') INSERT INTO quota (messages,username) VALUES ('2','myuser') The first query works, the second throws an error because username-field is uniqe. Duplicate entry 'myuser' for key 1 So i have to find a way to make this query in one step: INSERT INTO quota (bytes,messages, username) VALUES ('2456','2','myuser') or turn the second insert into an update update quota SET messages='2' where username='myuser' But iam afraid this is too much for my c-skills. I need help of an C-Crack or timo as developer. if timo could create a switch for mysql 4.0 would surely be the best. Thanks, Andre

1 0

Re: [Dovecot] quota dict with mysql 4.0
by Andre Hübner 25 Mar '10

25 Mar '10

Hello, >> I am somewhat surprised that the older software is not compatible with >> the newer version of MySQL. Usually, it is the other way around. Have >> you checked to see if newer versions of the incompatible software >> exist? I would be willing to wager that they have been updated to >> accommodate the newer MySQL versions. Syntax changed a litte bit and also there are some new protected words which are used by older software in sql without backticks etc. I agree updating would be the better way but we talking about a big number of servers and customers still using it. this is not changed over night.... I looked into dovecot-1.2.11/src/lib-dict/dict-sql.c, there seems to be a check for "ON DUPLICATE KEY UPDATE" on line 588. I recompiled dovecot on mysql 4.0 machine and tried again but there was no change. SQL is successful when dataset in quotatable is existing. in this case dovecot triggers an update of the data. But if no line for user is existing in quotatable and an insert is needed there is still the error: sql dict: commit failed: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'ON DUPLICATE KEY UPDATE bytes='12525'' at line why is the mysql 4.0-recompiled dovecot thinking my mysql is able to do "ON DUPLICATE KEY UPDATE"? How to avoid this? Thanks, Andre

2 1

[Dovecot] What is the difference between the plugin zlib and imap-zlib ?
by Alex Baule 24 Mar '10

24 Mar '10

What is the difference between the plugin zlib and imap-zlib ? in dovecot 1.2.X the zlib plugin works with imap....imap-zlib is a complement to zlib ?

2 1

[Dovecot] Question howto wiki.dovecot.org about quotas using dict
by Ricardo Barbosa 24 Mar '10

24 Mar '10

Hi, I am configuring a server with postfix and dovecot with virtual domains and using quota. To implement quota followed the documentation of the link http://wiki.dovecot.org/Quota/Dict, did not understand what you mean the field "where_field = path" would be the path on the filesystem of your mailbox? I would have to create the table that he says in the documentation or can I force a value with concat and using the AS (ie select '/var/vmail/domain/user' as path from table) ? Regards. __________________________________________________ Faça ligações para outros computadores com o novo Yahoo! Messenger http://br.beta.messenger.yahoo.com/

2 3

[Dovecot] Is it possible to prevent users from ever deleting anything?
by Snaky Love 24 Mar '10

24 Mar '10

Hi, dear dovecot-users, is it possible to make dovecot ignore the DELETE command for some accounts? Basically what I want to achieve is: users shall not be able to delete their emails - but they still should be able write emails. This is meant for a setup where different users are sending and receiving emails for a "support" account. I looked into IMAP virtual folders and ACL but I did not see a way of totally disabling the possibility to delete emails and share the whole account. I realize there may be race conditions with a setup like this and a web based ticket system might be a better solution, but it is only a very small team and we can always talk to each others to resolve conflicts - so using only one mail account for support seems practical and could keep the overhead small - but we do not want to delete anything from it (accidentaly). Of course, at one point in future somebody has to delete some mails from this accounts to get rid of old stuff - so I would like to implement a super-user that is able to do that kind of mailbox maintanance. How would I use ACL to setup such a scenario? Is it even possible? Or did I misunderstand IMAP shared folders completely??? Thank you very much for your attention! Have a nice day, Snaky

4 3

[Dovecot] Writing "sieve" script
by Jerry 24 Mar '10

24 Mar '10

This is probably not the best place to ask this question; however, I figured I had to start somewhere. I want to write a sieve script that can sort incoming mail into specific locations. EXAMPLE: require ["fileinto"]; if header :contains "X-Virus-Status" "Infected" {fileinto "SPAM"; stop;} elsif header :contains "X-SpamCop-Disposition" "Blocked" {fileinto "SPAM"; stop;} elsif address :contains "To" "user1(a)domain.com" {fileinto "INBOX.user1";} elsif address :contains "To" "user2(a)domain.com" {fileinto "INBOX.user2";} elsif address :contains "To" "user3(a)domain.com" {fileinto "INBOX.user3";} # The rest goes into INBOX # The default is "implicit keep", we do it here explicitly else {keep;} This works fine unless user1, user2 and or user3 are all included in the same e-mail address. It is rare; however, it does happen. In that case, a separate message for each recipient would be delivered to the first matching mailbox. The other recipients would not receive any traffic at all. I am new at writing sieve scripts, and have not come up with any way of preventing this from happening. If anyone has a suggestion, I would love to hear it. Even the examples I found by Googling were not really informative. -- Jerry Dovecot.user(a)seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ "Glory is fleeting, but obscurity is forever." - Napoleon Bonaparte

2 1