- dovecot - dovecot.org

Re: [Dovecot] Deleting messages with Mac Mail via IMAP
by Tim Schneider 03 Sep '13

03 Sep '13

The right wording (expunge) provided me with some clues. Anyway, Mac Mail does not have such a flag. It seems to be deliberately designed to do the expunge on quitting the application. Expunge can also be triggered by using cmd+shift+k with no marked messages to empty all trashes. Using this command, one can also mark a message and expunge it directly, bypassing the trash. I don't want to exclude the possiblity that this has got something to do with the IDLE system, and could be resolved by, for example, providing the right IMAP capabilities flags upon com init. Interestingly, iOS mail does delete the message in the inbox directly when moving it to trash. Thanks anyway to the contributors of this thread, I think I will have to accept this behavior, since Apple does usually not care about customer requests to resolve bugs. Mostly they declare them to be intended stupidity, even when they sell items that behave just the opposite way. Anyway, Zarafa mail server has a flag imap_expunge_on_delete. Perhaps this would be a useful feature for Dovecot to protect admins from angry customers who use well-designed Apple products. On 2013-09-03, at 20:16 , lists-dovecot <replies-lists-a1z2-dovecot(a)listmail.innovate.net> wrote: > > > ------------ Original Message ------------ >> Date: Tuesday, September 03, 2013 07:11:40 PM +0200 >> From: Tim Schneider <tim.schneider(a)portabile.net> >> To: dovecot(a)dovecot.org >> Subject: [Dovecot] Deleting messages with Mac Mail via IMAP >> >> Hello mailing list subscribers! >> >> When I delete a message in Mac Mail 6.5 (OS X 10.8.4), >> with the option to move messages to the trash set in Mac Mail >> account preferences, the message is copied to the trash, and >> markes as trashed in the cur/inbox directory on the server (STa >> flag in the file name). >> >> My horde webmail then displays this messages correctly as trashed >> in the inbox. However, I want the message to be gone from the >> inbox. >> >> Quitting Mac Mail deletes it in the inbox reliably. >> >> Is there any IMAP setting for dovecot to get move, and not copy >> and mark as trashed behavior? >>

1 0

[Dovecot] Deleting messages with Mac Mail via IMAP
by Tim Schneider 03 Sep '13

03 Sep '13

Hello mailing list subscribers! When I delete a message in Mac Mail 6.5 (OS X 10.8.4), with the option to move messages to the trash set in Mac Mail account preferences, the message is copied to the trash, and markes as trashed in the cur/inbox directory on the server (STa flag in the file name). My horde webmail then displays this messages correctly as trashed in the inbox. However, I want the message to be gone from the inbox. Quitting Mac Mail deletes it in the inbox reliably. Is there any IMAP setting for dovecot to get move, and not copy and mark as trashed behavior? Here are my dovecot settings: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.1 ext4 auth_mechanisms = plain login mail_location = maildir:/var/mail/vhosts/%d/%n mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = admin(a)xxx.xxx protocols = imap pop3 lmtp sieve service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 995 ssl = yes } } ssl = required ssl_cert = </etc/ssl/certs/mailportabile.pem ssl_key = </etc/ssl/private/mailportabile.key submission_host = localhost userdb { args = uid=vmail gid=vmail home=/var/mail/vhosts/%d/%n driver = static } protocol lda { mail_plugins = " sieve" }

3 2

Re: [Dovecot] Logging passwords on auth failure/dealing with botnets
by Joseph Tam 03 Sep '13

03 Sep '13

Michael Smith writes: > We're already running fail2ban, but it doesn't seem that effective > against botnets, when they only do one attempt per IP. Yeah, distributed BFDs are tough to block unless you can characterize the clients well. > That leaves us back to getting dovecot to log the tried password for > unknown users. Another tactic might be to hook in a authentication script: http://wiki2.dovecot.org/AuthDatabase/CheckPassword You can run this as an external plugin and won't have to muck into the dovecot innards. From here, you can log attempts, keep track of bad IPs, or take action if you spot a username/password combination that merits instant blacklisting. Joseph Tam <jtam.home(a)gmail.com>

5 10

[Dovecot] sync re-copies emails assigning new UIDs
by Anand Kumria 03 Sep '13

03 Sep '13

Hi, I have been (attempting) to transition a company from in-house dovecot 1.x to a hosted dovecot 2.2 setup. I am running the doveadm sync command, and for the four mailboxes have been blocked -- sync'ing seem to be copying the same mails, over and over (note, initially I was using doveadm backup but my reading has indicated that 'doveadm sync' is better) Example: # date && doveadm -v -o imapc_user=kaye(a)example.com -o imapc_password=*pass* -o imapc_host=imap.example.com -o imapc_port=993 -o imapc_ssl=imaps -o imap c_ssl_dir=/etc/ssl -o imapc_feature=rfc822.size -o imapc_ssl_verify=no sync -1 -R -u kaye(a)example.com imapc: Sat Aug 3 09:05:37 UTC 2013 [...] dsync(kaye(a)example.com): Info: copy from INBOX: box=INBOX, uid=5306, msgid=<FB3A2E1C62B148F8B057476BDCBB4A9B@THENORMANS>, size=13544 dsync(kaye(a)example.com): Info: copy from INBOX: box=INBOX, uid=5307, msgid=<006b01ce8dad$b8864930$2992db90$(a)com.au>, size=10163563 [...] dsync(kaye(a)example.com): Info: copy from INBOX: box=INBOX, uid=5311, msgid=< cm.083930.bijjdjk.jdkimlhij.r(a)createsend5.com>, size=46658 [...] # date && doveadm -v -o imapc_user=kaye(a)example.com -o imapc_password=*pass* -o imapc_host=imap.example.com -o imapc_port=993 -o imapc_ssl=imaps -o imapc_ssl_dir=/etc/ssl -o imapc_feature=rfc822.size -o imapc_ssl_verify=no sync -1 -R -u kaye(a)example.com imapc: Sat Aug 3 10:01:48 UTC 2013 [...] dsync(kaye(a)kamdha.com): Info: copy from INBOX: box=INBOX, uid=5324, msgid=<FB3A2E1C62B148F8B057476BDCBB4A9B@THENORMANS>, size=13544 dsync(kaye(a)kamdha.com): Info: copy from INBOX: box=INBOX, uid=5325, msgid=<006b01ce8dad$b8864930$2992db90$(a)com.au>, size=10163563 [...] dsync(kaye(a)kamdha.com): Info: copy from INBOX: box=INBOX, uid=5329, msgid=< cm.083930.bijjdjk.jdkimlhij.r(a)createsend5.com>, size=46658 [...] The exact same number of emails (some in the INBOX, some in the Sent folder) are transferred each time. In this case, I've firewalled the origin - so their entire mail system is stopped whilst I do the transfer just in case modifications of IMAP flags or additional delivieres might have been the problem. I am using Dovecot v2.2.4; is this normal expected behaviour? If so, what is the best way to ensure that a migration is done without data loss. If this isn't expected, has anyone else seen this kind of error before? Thanks, Anand

1 1

[Dovecot] setup of dovecot as proxy to dbmail
by Regan Yelcich 03 Sep '13

03 Sep '13

Can anyone point me in the direction of a detailed how-to for setting up a postfix and dovecot (proxy) node with dbmail? In particular I'm looking for a how-to which shows dovecot authenticating against the dbmail database directly. The only example I've found is this one which requires a duplication of the user database. http://content.fens.org/index.php?q=admin-howto/mail/dovecot2dbmail-proxy Thanks.

2 1

[Dovecot] Auth error in log
by Per-Henrik Lundblom 02 Sep '13

02 Sep '13

Hi, I have a setup with Dovecot handling a few virtual domains delivering mails to both local Unix account mailboxes and seperate mailboxes for virtual users defined in a MySQL database. A quick overview of the configuration shows two passdb definitions: auth default { mechanisms = plain login passdb pam { args = dovecot } passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb passwd { args = mail=maildir:~/Maildir blocking=yes } userdb static { args = uid=vmail gid=mail home=/var/spool/vmail/%d/%n allow_all_users=yes } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail group = mail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } !include_try /etc/dovecot/auth.d/*.auth } When a virtual user defined in the MySQL database tries to log in using IMAP or SMTP I always get auth failures logged in the system logs. Entries are like this: Aug 21 06:25:36 roadrunner dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=luser(a)mydomain.com rhost=85.224.xx.xx I assume these failures comes form the fact that PAM doesn't recognize the virtual users and Dovecot continues to the SQL passdb entry. As a result I get a _lot_ of auth failures in the logs. I have tried to come up with a way where the auth failures from PAM arent't logged if the the SQL authenication is successful. Is this possible or are there any other recommended ways to handle this? /PH -- Per-Henrik Lundblom email: ph(a)whatever.nu phone: +46 733 207126 webpage: www.whatever.nu

2 3

[Dovecot] local AND virtual mail locations ?
by Pierre-Philipp Braun 02 Sep '13

02 Sep '13

Hi, I would like to use Dovecot not only for virtual mboxes, but also for local users. In other words, I would like to use different "mail_location"s depending on "passdb" "passwd-file" versus "passwd". I need that as the smtp daemon I am using (david parsons' postoffice smtp server) serves both but is only able to process messages through procmail on local users. Here are the two mail_locations I would like to use: mail_location: mbox:~/mail/:INBOX=/var/mail/%u mail_location: mbox:/var/spool/virtual/%d/%n.imap:INBOX=/var/spool/virtual/%d/%n depending on those passdb stanzas, respectively: passdb passwd-file { args = username_format=%n /etc/virtual/%d/passwd } passdb passwd { } Any help would be appreciated. Here's my Dovecot version and current working configuration for virtual users only: # dovecot -n dovecot -n # 1.2.17: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.3-RELEASE amd64 ufs protocols: imap ssl: no disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_uid: 6 first_valid_gid: 6 mail_location: mbox:/var/spool/virtual/%d/%n.imap:INBOX=/var/spool/virtual/%d/%n imap_client_workarounds: tb-extra-mailbox-sep auth default: user: mail passdb: driver: passwd-file args: username_format=%n /etc/virtual/%d/passwd userdb: driver: static args: uid=6 gid=6 I find that first_valid_uid and first_valid_gid don't look pretty but it seems mandatory for the standard 'mail' user and group ownerships to work on the virtual mbox files and folders. I created the user while the group already existed. If you have any advices on that too, I would be pleased. Thanks Pierre-Philipp

3 7

[Dovecot] Getting back into Dovecot 2.2.5
by Kai Hendry 02 Sep '13

02 Sep '13

Hi there, I'm prompted to get into running my own mail server again with Gmail going bad. However I found /usr/share/doc/dovecot/example-config/conf.d/ a little scary, since I like to have my configs as minimalistic as possible, e.g. http://dabase.com/blog/Minimal_squid3_proxy_configuration/ So far I have: https://github.com/Webconverger/sg.webconverger.com/blob/master/dovecot/dov… I was kinda hoping for a Maildir, but this doesn't work: mail_location = maildir:~/Maildir:LAYOUT=fs:INBOX=/var/mail/%u I do realise /var/mail/%u is a mbox, but I was wondering if there could be some clever conversion. I was surprised something like INBOX=/var/mail/%u wasn't the default btw. Also surprised dovecot seems to choke on single line syntax like `passdb { driver = pam }` :-) Next thing I'm confused about is the `namespace inbox {` stuff. Is it really needed? I was expecting Dovecot to create the folders once I defined them, but mutt couldn't see them until I created them myself. The mail server is just for myself and a few colleagues. We will probably use mutt as our MUA and Apple Mail on IOS when we are out & about. I next plan to integrate dspam, and work out how to sort mails into folders like I previously effectively had with Gmail's labels. I was confused to which mechanism I should be using to sort mail into folders with rules. Sieve? Back to Procmail? Pigeonhole? I'm looking to avoid complexity here. On the topic of search, can I get away with not running a Solr server? Since I shudder at the thought of running Tomcat. http://wiki2.dovecot.org/Plugins/FTS Kiitos paljon for any pointers!

3 4

[Dovecot] Auto-blocking faulty login attempts
by Jos Chrispijn 01 Sep '13

01 Sep '13

Dear group, How can I block login attempts to dovecot after trying 5 times in error? -- Best regards, Jos Chrispijn --- Artificial intelligence is no match for natural stupidity

3 2

[Dovecot] Dovecot and Postfix Authentication
by Christopher Trom 31 Aug '13

31 Aug '13

I am a student and am trying to get a mail server setup for a project. I have all of the Postfix configuration taken care of, but I am confused by the way that authentication works with Dovecot in the mix. As a user of the system, am I supposed to authenticate myself to Postfix, Dovecot, both individually, or both together? My Postfix users are stored in a PostgreSQL database, should Dovecot also be connected to this db? Some basic pointers on how this setup ought to look is all that I'm hoping for. Thank you, Christopher

2 1