- dovecot - dovecot.org

[Dovecot] SASL Dovecot, Active Directory, LDAP
by Gilles Albusac 20 Aug '09

20 Aug '09

My configuration : - a smtp server with Postfix 2.6 and Dovcot 1.1.11. - a windows 2003 server with active directory for accounts and boxes I would like to use SMTP / SASL on my postfix 2.6 to authenticate my remote laptop users (allow legitimate users to relay mail). To do that, I need to use SASL Dovecot fonctionnality and ldap request. How to configure Dovecot to enable SMTP/SASL and verify login/password who are declared on a second server in Windows 2003 (Active Directory). Regards

1 0

[Dovecot] dovecot auth is case insensitive, but fs is sensitive :)
by Benny Pedersen 20 Aug '09

20 Aug '09

others have found this problem ? this possible bug can be used by user in that way that one password login can use 2 maildirs in filesystem effitively give them all space qoutas and lost of other goodies so to speak: foo(a)example.com with a password can login with fOO(a)example.com and fOo(a)example.com add more chars to get more mailbox :/ confirms ? i found the problem when i had horde installed dovecot 1.1.7 -- xpoint

6 7

[Dovecot] script to report quota upon user's request
by Δημήτριος Καραπιπέ ρης 20 Aug '09

20 Aug '09

Hi there is there any binary/script to repot user's quota upon request? Dimitrios Karapiperis

4 3

[Dovecot] dovecot-1.2.4, sendmail,deliver,sieve
by Jonathan Siegle 20 Aug '09

20 Aug '09

I'm trying to setup deliver as an LDA for system users. I've read http://wiki.dovecot.org/LDA/Sendmail which handles virtual users. I don't see a README for what I need. I want sendmail to accept the mail and then hand off to deliver with sieve plugin. Deliver should look in the users home directory which is found in /etc/passwd for the sieve-script to see what to do with it. If the sieve-script DNE, then just deliver to INBOX(from dovecot.conf). Any help would be appreciated. Thanks, Jonathan protocols: imap disable_plaintext_auth: no login_dir: /usr/dovecot-1.2.4/var/run/dovecot/login login_executable: /usr/dovecot-1.2.4/libexec/dovecot/imap-login login_greeting: Dovecot ready. login_processes_count: 30 max_mail_processes: 4096 mail_location: mbox:%h:INBOX=/var/spool/mail/%Ju/%u mail_full_filesystem_access: yes mmap_disable: yes dotlock_use_excl: no mbox_write_locks: fcntl mbox_lazy_writes: no mail_plugins: mbox_snarf mail_plugin_dir: /usr/dovecot-1.2.4/lib/dovecot/imap/ imap_client_workarounds: tb-extra-mailbox-sep imap_id_log: * lda: postmaster_address: postmaster@localhost auth default: mechanisms: plain gssapi krb5_keytab: /etc/krb5/krb5.keytab gssapi_hostname: $ALL debug: yes worker_max_count: 2 passdb: driver: pam args: max_requests=1 userdb: driver: passwd plugin: mbox_snarf: /gpfs/inbox/%Ju/%u

2 3

[Dovecot] Oops!
by Daniel L. Miller 20 Aug '09

20 Aug '09

I was testing a new webmail client - like an idiot, against my own mailbox, instead of a test mailbox (or even a separate server) - and my Inbox got wiped. Fortunately I backup our mails nightly, so I only lost a couple from today. No idea how the wipe occured - I didn't INTENTIONALLY perform a delete + purge...but it happened. Is there a way of configuring Dovecot to ensure that any delete operation specified by a client results in a "move to Trash" as a precaution? Instead of relying on the client to perform it? -- Daniel

2 1

[Dovecot] v1.2.4 released
by Timo Sirainen 19 Aug '09

19 Aug '09

http://dovecot.org/releases/1.2/dovecot-1.2.4.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.4.tar.gz.sig I'll be on vacation for the rest of this week. I'll read my mails once in a while though. * acl: When looking up ACL defaults, use global/local default files if they exist. So it's now possible to set default ACLs by creating dovecot-acl file to the mail root directory. + imap/pop3 proxy: If proxy destination is known to be down, fail connections to it immediately. + imap/pop3 proxy: Added proxy_timeout passdb extra field to specify proxy's connect timeout. - Fixed a crash in index file handling. - Fixed a crash in saving messages where message contained a CR character that wasn't followed by LF (and the CR happened to be the last character in an internal buffer). - v1.2.3 crashed when listing shared namespace prefix. - listescape plugin: Several fixes. - autocreate plugin: Fixed autosubscribing to mailboxes in subscriptions=no namespaces.

3 2

[Dovecot] dovecot/sieve current date
by bart 19 Aug '09

19 Aug '09

Hi, Is there a way in sieve to get the current date, preferably in YYYYMMDD format? To what I've found it's hard to achieve. I have tried including a :global sieve script in which I would set the current date to a certain variable and overwrite this included script every day. But to my disappointement variables set in an included script do not exist in the original script... In fact what I want to achieve is that some actions like forwarding or vacation messages are performed from a certain date untill another date. Which would allow a user to define a timeperiod in which the autoreply or forward should be done and automatically stop without updating the sieve script again. Comparing start and stopdate is cake, but just getting today's date seems to be a hassle, any ideas? regards, bart

2 1

[Dovecot] Restoring backup?
by Bjørn T Johansen 18 Aug '09

18 Aug '09

I have understood correctly when thinking that all I need to do in order to restore mails, is to just copy the old maildir folder to the location where mail_location is pointing to and dovecot will find all the mails and display the old mails? Regards, BTJ -- ----------------------------------------------------------------------------------------------- Bjørn T Johansen btj(a)havleik.no ----------------------------------------------------------------------------------------------- Someone wrote: "I understand that if you play a Windows CD backwards you hear strange Satanic messages" To which someone replied: "It's even worse than that; play it forwards and it installs Windows" -----------------------------------------------------------------------------------------------

3 2

[Dovecot] alias does not work
by denis 18 Aug '09

18 Aug '09

Hi, Thank you to everyone who helped me get near the goal. Remains a problem is that aliases don't work. The problem is that in the configuration of alternc, the mails are seen as aliases in the form user_domain.tld. In a second time, a match is made to see if an "real" alias exists. postmap -q test(a)lists.test.net mysql:/etc/postfix/mydomain.cf test-owner_lists.collectifs.net postmap -q test-owner_lists.test.net mysql:/etc/postfix/myalias.cf "| /var/lib/mailman/mail/mailman owner test" With my configuration, this second part doesn't work. Perhaps the simplest is to ask to deliver the mail to user_domain.tld except of user(a)domain.tld in master.cf ? Thanks Denis # main.cf virtual_alias_maps = proxy:mysql:/etc/postfix/myalias.cf, hash:/etc/aliases virtual_mailbox_domains = mysql:/etc/postfix/mydomain.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/myvirtual.cf virtual_transport = dovecot dovecot_destination_recipient_limit = 1 # master.cf dovecot unix - n n - - pipe flags=DRhu user=www-data:www-data argv=/usr/lib/dovecot/deliver -d $(recipient)

1 0

[Dovecot] Gotchas in switching from one server to another without impacting users?
by Gary Chodos 18 Aug '09

18 Aug '09

We have to replace one mail store (foo.example.org) with another (bar.example.org) I rsync'd the maildirs from foo to bar today and the plan is to hold all delivery (in the SMTP server) on foo over the weekend, rsync again (this time it should be much faster since the large xfer already occurred today), then flush the SMTP queue on foo towards bar, direct all new deliveries to bar.example.org. Users currently access their IMAP mailboxes via imap.example.org. I plan to just 'flip the switch' at DNS so imap.example.org points to bar.example.org (instead of foo.example.org) so users don't have to change anything on their end and should not even notice this change. Is there anything else I should think about to mitigate users noticing a change? Does the fact that the mail filenames include 'foo.example.org' in the file name (while new deliveries to bar.example.org will include that new hostname) spell trouble later on or can I ignore it? Is there a more efficient way to achieve my goal? And finally, dovecot on foo.example.org is 1.1.7 while the new server is running 1.1.16. I don't think that should be an issue, but mentioning it just in case. Thanks! -- GC

5 5