- dovecot - dovecot.org

[Dovecot] Changed URL of the Sieve Mercurial repository.
by Stephan Bosch 19 Jul '09

19 Jul '09

Hi, I've changed the name of the Sieve Mercurial repository form dovecot-libsieve to dovecot-1.2-sieve, to signify the Dovecot version it applies to. The URL thus looks as follows: http://hg.rename-it.nl/dovecot-1.2-sieve Note that there are already dovecot-2.0-sieve and dovecot-2.0-managesieve repositories, but these are still somewhat broken in multiple ways and I wouldn't call these ready for testing yet. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

[Dovecot] dsync - one or two ways?
by Timo Sirainen 18 Jul '09

18 Jul '09

dsync in Dovecot v2.0 tree is a new utility for syncing a mailbox in two locations. Some things it can be used for: - Initially transfer a mailbox to another server via SSH - A faster sync done to an existing mailbox, sending only changes - A superfast sync based on modification sequences. - Source and destination mailboxes can use different formats (convert-tool will be history) dsync can handle all kinds of conflicts in mailboxes, handle mailbox deletions, renames, etc. So it's safe to sync even if both source and destination mailboxes have had all kinds of changes. Now, the question is: Does anyone want dsync to only sync changes from source to destination, instead of doing a full two-way sync? I think in typical cases where you'd think you would want only one-way sync are also the cases where there's no changes coming the other way in any case.

7 23

[Dovecot] SMTP Auth Issue for non /etc/passwd accounts
by Mark R. Baith 17 Jul '09

17 Jul '09

Folks - With Dovecot 1.0.7, we're seemingly unable to authenticate users for out-going SMTP access who are not residing directly within the main system passwd/shadow files. (I.e. the users seeded within our non-system "dovecot" userdbs & passwd files have no "smtp-auth" joy! (Ye olde "Relaying denied. Proper authentication required") I've mucked around with this from several different angles and clearly saslauthd is the sticking point in terms of "locking-in" on the /etc system files ONLY for smtp-auth. Our defined dovecot user/passwd files are entirely ignored. Can anyone provide a direction regarding the appropriate smtp-auth in-road? Thanks, -M Regards, M

3 5

[Dovecot] Question regarding layout.
by Johan Hendriks 17 Jul '09

17 Jul '09

Hello all. I have a question regarding my mail flow. We have some users who are in a mail group (alias), and these alias receives a lot of attached documents. So i have the document in all the mailboxes of the alias. If the attached document is 2MB and that is not rare, i have 10 times 2 MB on my mail server. Is there a way to tackle this. Maybe by making the alias a mailbox itself and give other users acces or are there other options. Also i have very lame and lazy users. They refuse to clean thrash cans (i asked about that earlier,and got that tackled through the expire plugin.),also the do not remove old mail not even reading it. So is there also a option to remove mail that is not been opened, and is older than xx days or weeks. Thanks -- _______________________ *Johan Hendriks* *Schavemaker Transport* Tel: +31 (0)251 229098 Fax: +31 (0)251 212016 email: j.hendriks(a)schavemaker.com <mailto:j.hendriks@schavemaker.com> web: http://www.schavemaker.com _______________________

2 2

[Dovecot] exim4 dovecot sasl problem
by Tristan Rex Santiago 17 Jul '09

17 Jul '09

hi! i'm trying to do smtp authentication using dovecot and exim4 by following this guide http://wiki.dovecot.org/HowTo/EximAndDovecotSASL. for the exim4 part, i got an authenticator dovecot: cannot find authenticator driver "dovecot" error after i entered the codes in /etc/exim4/exim4.conf.template and reloaded exim4 with the update-exim4.conf command. i'm running debian lenny. here's the authentication section of exim4.conf.template: begin authenticators cram_md5: driver = cram_md5 public_name = CRAM-MD5 client_name = ${extract{1}{:}{${lookup{$ host}nwildlsearch{CONFDIR/passwd.client}{$value}fail}}} client_secret = ${extract{2}{:}{${lookup{$host}nwildlsearch{CONFDIR/passwd.client}{$value}fail}}} PASSWDLINE=${sg{\ ${lookup{$host}nwildlsearch{CONFDIR/passwd.client}{$value}fail}\ }\ {\\N[\\^]\\N}\ {^^}\ } plain: driver = plaintext public_name = PLAIN .ifndef AUTH_CLIENT_ALLOW_NOTLS_PASSWORDS client_send = "<; ${if !eq{$tls_cipher}{}\ {^${extract{1}{:}{PASSWDLINE}}\ ^${sg{PASSWDLINE}{\\N([^:]+:)(.*)\\N}{\\$2}}\ }fail}" .else client_send = "<; ^${extract{1}{:}{PASSWDLINE}}\ ^${sg{PASSWDLINE}{\\N([^:]+:)(.*)\\N}{\\$2}}" .endif login: driver = plaintext public_name = LOGIN .ifndef AUTH_CLIENT_ALLOW_NOTLS_PASSWORDS # Return empty string if not non-TLS AND looking up $host in passwd-file # yields a non-empty string; fail otherwise. client_send = "<; ${if and{\ {!eq{$tls_cipher}{}}\ {!eq{PASSWDLINE}{}}\ }\ {}fail}\ ; ${extract{1}{::}{PASSWDLINE}}\ ; ${sg{PASSWDLINE}{\\N([^:]+:)(.*)\\N}{\\$2}}" .else # Return empty string if looking up $host in passwd-file yields a # non-empty string; fail otherwise. client_send = "<; ${if !eq{PASSWDLINE}{}\ {}fail}\ ; ${extract{1}{::}{PASSWDLINE}}\ ; ${sg{PASSWDLINE}{\\N([^:]+:)(.*)\\N}{\\$2}}" .endif dovecot_login: driver = dovecot public_name = LOGIN server_socket = /var/run/dovecot/auth-client server_set_id = $auth1 dovecot_plain: driver = dovecot public_name = PLAIN server_socket = /var/run/dovecot/auth-client server_set_id = $auth1 How can I fight insomnia? Discover how on Yahoo! Answers. http://ph.answers.yahoo.com

2 1

[Dovecot] user unknown with deliver
by Nikolay Shopik 16 Jul '09

16 Jul '09

I'm getting user unknown when trying to deliver to Sent folder messages. My master.cf part is: copy2sent unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -d ${sasl_username} -m Sent But it still won't work. I'm running 1.0.15 pluto postfix/pipe[30934]: 7470890C4DA: to=<bcc(a)bcc.example.com>, relay=copy2sent, delay=0.03, delays=0.02/0/0/0.01, dsn=5.1.1, status=bounced (user unknown)

3 10

[Dovecot] Can Dovecot Proxy GMail?
by Paul Carter-Brown 16 Jul '09

16 Jul '09

Hi, We are using gmail (google apps) across our company with most users using outlook (windoze) or evolution (linux) and imap/pop based on user preference. We are having issues in that our internet links are fairly slow and when users download mails they get frustrated with the time it takes and often get timeouts and issues where outlook fails to fetch a mail yet gmail thinks it was retrieved - users then complain of "missing" emails. Is there a way that we could use dovecot (or similar?) to act as an imap "proxy" and users connect to dovecot while dovecot connects to gmail? Thanks Paul

3 2

[Dovecot] sieve / managesieve: unknown Sieve capability 'imapflags'
by Ralf Hildebrandt 16 Jul '09

16 Jul '09

$HOME/.dovecot.sieve.log reports: main_script: line 8: error: require command: unknown Sieve capability 'imapflags'. main_script: line 8: error: require command: unknown Sieve capability 'notify'. main_script: error: validation failed. I'm using sieve (not cmusieve) and managesieve with dovecot-1.2. SquirrelMail 1.4 is using the avelsieve plugin to created/edit the sieve rules. What am I doing wrong here? -- 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

4 7

[Dovecot] Expire plugin - where to start?
by Frank Leonhardt 15 Jul '09

15 Jul '09

I'm running Dovecot 1.1.3 on FreeBSD 7.0 with procmail 3.22 sorting the output of Spamassassin. Just for me and a few friends. I didn't like the ageing 'standard' IMAP implementation so I thought I'd give Dovecot a try and it's really impressive. However, I'm a complete newbie to its inner workings. Spamassassin is able to find plenty to chew on so the "Probable spam" mbox (note) fills up fast. I obviously want to zap the old stuff in there automatically. It seems to me that the expire plugin is the thing I need BUT reading the documentation: http://wiki.dovecot.org/Plugins/Expire Leaves me to scared to try anything. It's all working and I don't want to break it or delete anyone's mail. The problem that the wiki isn't accurate to the version I'm running. For example /usr/libexec/dovecot/expire-tool.sh doesn't exist. Okay, this isn't Linux, and there's something likely where I'd expect it on BSD (/usr/local/...) - but it's a binary, not a shell script. It may be a direct replacement AFAIK, but it may not. I've been reading the old mailing list about problems with 1.2 and this reinforces the feeling that the wiki is out-of-sync. Am I being paranoid? Possibly, but I don't want to be posting a "Help! I've wrecked my config and deleted all my friend's mail" type message. (Okay, I'd take a backup first). So could some kind person point me at the latest documentation? Thanks, Frank.

2 2

[Dovecot] multiple authentication mechanisms/passwords for same account
by Tapani Tarvainen 15 Jul '09

15 Jul '09

This may be trivial but reading the documentation I can't find a clear answer: If multiple authentication mechanisms (or multiple databases for one) are defined, does it allow one user account to have several (at least two) alternative passwords (so that any of them would work)? Or does it first map an account to a fixed authentication mechanism/password and if it fails, others won't be tried? -- Tapani Tarvainen

2 3