- dovecot - dovecot.org

[Dovecot] filtering problem using sieve
by ajmcello ajmcello 30 Aug '06

30 Aug '06

For some reason, I cannot filter messages that have uppercase or possibly mixed casing in them. I have tried several tests by connecting to port 25 and sending messages. The ones that fail are from MAILER-DAEMON(a)mydomain.net. Here are the rules I have tried: require ["fileinto", "reject", "vacation"]; if header :contains ["To", "Cc", "Bcc", "Reply-To", "In-Reply-To"] " mailer-daemon(a)mydomain.net" { fileinto "mailer-daemon"; stop; } if header :contains ["To", "Cc", "Bcc", "Reply-To", "In-Reply-To"] " MAILER-DAEMON(a)mydomain.net" { fileinto "mailer-daemon"; stop; } if header :contains ["To", "Cc", "Bcc", "Reply-To", "In-Reply-To"] " MAILER-DAEMON(a)mail.mydomain.net" { fileinto "mailer-daemon"; stop; } if header :contains ["To", "Cc", "Bcc", "Reply-To", "In-Reply-To"] " mailer-daemon(a)mail.mydomain.net" { fileinto "mailer-daemon"; stop; } They all fail to deliver to my mail folder "mailer-daemon" and go to my inbox instead. Anybody have any ideas what I am doing wrong? Also, how can I add a wildcard so that I do not have to specify subdomains? Thank you!

3 2

[Dovecot] Dovecot public folders ACL
by typus vulgaris 29 Aug '06

29 Aug '06

Hi, all! I'm new to dovecot but trying to setup read-only public folders for different user groups. My goal is to create several public folder such as sales, operation etc with per user index. But I have some problem which I can't resolve with Google and Dovecot.Org. Now users can see and subscribe to test folder "share", but I can't block ability to delete messages via ACL. Here is file system permissions: public/.share ]> ls -la total 12 drwxrwx--- 5 share mail 512 17 авг 12:17 . drwxrwx--- 6 root mail 512 17 авг 11:04 .. drwxrwx--- 2 share mail 512 17 авг 11:18 cur -rwxrwx--- 1 root mail 21 17 авг 10:36 dovecot-acl -rwxrwx--- 1 root mail 0 16 авг 17:56 dovecot-shared drwxrwx--- 2 share mail 512 17 авг 11:17 new drwxrwx--- 2 share mail 512 17 авг 11:17 tmp my dovecot-acl file: public/.share ]> cat dovecot-acl owner lr user=typ lr But user typ can delete messages. But ACL seems working because if I remove letter 'l' from typ's setting he cannot see the folder. Here is my config: ----------8<------------ protocols = imap ssl_disable = yes disable_plaintext_auth = no shutdown_clients = yes log_path = /var/log/dovecot/sys.log info_log_path = /var/log/dovecot/info.log login_process_size = 64 verbose_proctitle = yes first_valid_gid = 0 mail_extra_groups = mail default_mail_env = mbox:/var/mail/%u:INDEX=/home/user/%u:INBOX=/var/mail/%u namespace private { separator = / prefix = location = maildir:/home/user/%u/.maildir inbox = yes } namespace public { separator = / prefix = Public/ location = maildir:/home/user/public:CONTROL=/home/user/%u/public/control:INDEX=/home/user/%u/public/index hidden = no inbox = no } mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl mbox_lock_timeout = 300 mbox_very_dirty_syncs = yes umask = 0007 protocol imap { listen = 192.168.101.1:143 mail_plugins = acl imap_client_workarounds = delay-newmail outlook-idle } protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root } plugin { } -----------------8<-------------- -- typus vulgaris

4 4

[Dovecot] 0.99.11 (CentOS4 or RHEL4) to 1.0.rc7 upgrade folder issue
by Stephen Warren 29 Aug '06

29 Aug '06

[Sending this again from the email account that I actually have subscribed to the list - hopefully won't be a dup...] We have been running dovecot-0.99.11-2.EL4.rpm on CentOS4 (since that's the latest that ships with RHEL/CentOS) for a while. Aalso in parallel, we have been running various 1.0 betas and RCs on a different port for a different set of more test-tolerant users. This weekend, I upgraded to 1.0.rc7, and made all users use this. I found a small issue. All our users have a large set of folders in their Maildir. For the users who got upgraded from 0.99.11 to 1.0.rc7 (well, the one user who accessed their mail so far since the upgrade...) their folders weren't showing up in Thunderbird any more. Deleting all the dovecot-* files in the Maildir didn't help. In the end, the user re-subscribed to all the folders and then they showed up. (FYI, this is a right-click operation on the account in the Thunderbird tree view, subscribe menu option, then re-check all the folder names). Is there anything that can be implemented in 1.0.rc7 so that users don't have to manually re-subscribe to everything, so the upgrade process in this situation is a little more transparent? Is this simply a matter of the different Dovecot versions naming the folders with different UUIDs (or whatever the IMAP protocol uses), or something else?

3 2

[Dovecot] auth mechanisem and postfixadmin
by xrado 29 Aug '06

29 Aug '06

Aug 29 20:58:01 example dovecot: auth(default): client in: AUTH^I2^IPLAIN^Iservice=IMAP^Isecured^Ilip=127.0.0.1^Irip=127.0.0.1^Iresp=AHJhZG9AZXhhbXBsZS5jb20AcmFkbw== Aug 29 20:58:01 example dovecot: auth-worker(default): sql(rado(a)example.com,127.0.0.1): query: SELECT password FROM mailbox WHERE username = 'rado(a)example.com' Aug 29 20:58:01 example dovecot: auth-worker(default): sql(rado(a)example.com,127.0.0.1): Password mismatch Aug 29 20:58:01 example dovecot: auth-worker(default): sql(rado(a)example.com,127.0.0.1): PLAIN(rado) != '$1$997b1881$fpU1U5wRtWfVZQqbat0km/' Aug 29 20:58:03 example dovecot: auth(default): client out: FAIL^I2^Iuser=rado(a)example.com Aug 29 20:58:08 example dovecot: imap-login: Aborted login: user=<rado(a)example.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured which mechanisem do i have to use, database uses md5crypt-ed passwords rado.

1 0

[Dovecot] Problem using Apple Mail with Dovecot (fwd)
by Jason Fesler 29 Aug '06

29 Aug '06

---------- Forwarded message ---------- From: Bruce Arthur <barthur(a)apple.com> To: dovecot(a)dovecot.org Cc: Bruce Arthur <barthur(a)apple.com> Date: Tue, 29 Aug 2006 09:04:35 -0700 Subject: Problem using Apple Mail with Dovecot Server Configuration: dovecot-1.0.rc6 Built with: ./configure --prefix=/usr/local OS: FreeBSD 4.10-STABLE i386 running on ufs Client configuration Mac OS X 10.4.7, using Apple Mail client. Issue: Apple Mail is able to connect to the server, but it is not seeing the available folder correctly. I did a little debugging and it looks like dovecot is failing to provide the separator in response to the LIST command. I did not spend anytime trying to figure out how other mail clients are getting this (my tcpdump is a little rusty these days). Here is what I see Mail sending to the server, and it's responses. 1 LOGIN applecot ******** 1 OK Logged in. 2 CAPABILITY * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS 2 OK Capability completed. 3 LIST "" "" 3 OK List completed. The "LIST" command should be sending back the mailbox separator. The IMAP spec seems pretty clear about this (but reading RFC's is always a bit of a challenge). From the RFC: http://www.ietf.org/rfc/rfc2060.txt 6.3..8. LIST Command Arguments: reference name mailbox name with possible wildcards Responses: untagged responses: LIST Result: OK - list completed NO - list failure: can't list that reference or name BAD - command unknown or arguments invalid An empty ("" string) reference name argument indicates that the mailbox name is interpreted as by SELECT. The returned mailbox names MUST match the supplied mailbox name pattern. A non-empty reference name argument is the name of a mailbox or a level of mailbox hierarchy, and indicates a context in which the mailbox name is interpreted in an implementation-defined manner. An empty ("" string) mailbox name argument is a special request to return the hierarchy delimiter and the root name of the name given in the reference. The value returned as the root MAY be null if the reference is non-rooted or is null. In all cases, the hierarchy delimiter is returned. This permits a client to get the hierarchy delimiter even when no mailboxes by that name currently exist. Example: C: A101 LIST "" "" S: * LIST (\Noselect) "/" "" S: A101 OK LIST Completed C: A102 LIST #news.comp.mail.misc "" S: * LIST (\Noselect) "." #news. S: A102 OK LIST Completed C: A103 LIST /usr/staff/jones "" S: * LIST (\Noselect) "/" / S: A103 OK LIST Completed C: A202 LIST ~/Mail/ % S: * LIST (\Noselect) "/" ~/Mail/foo S: * LIST () "/" ~/Mail/meetings S: A202 OK LIST completed -- Bruce

1 0

Re: [Dovecot] Problem using Apple Mail with Dovecot
by Jason Fesler 29 Aug '06

29 Aug '06

> Server Configuration: > dovecot-1.0.rc6 > Built with: ./configure --prefix=/usr/local > OS: FreeBSD 4.10-STABLE i386 running on ufs Thanks, Bruce. Timo et all; Bruce specifically has been looking at my instance of dovecot after a friend of his reported problems with Mail.app and my server. More information: Stock dovecot namespaces work; This name space does not: namespace private { separator = . prefix = INBOX. inbox = yes hidden = no } namespace private { separator = / inbox = no hidden = yes prefix = "#mail/" location = mbox:/home/%u/mail } > > Client configuration > Mac OS X 10.4.7, using Apple Mail client. > > Issue: > Apple Mail is able to connect to the server, but it is not seeing the > available folder correctly. > > I did a little debugging and it looks like dovecot is failing to provide the > separator in response to the LIST command. I did not spend anytime trying to > figure out how other mail clients are getting this (my tcpdump is a little > rusty these days). Here is what I see Mail sending to the server, and it's > responses. > > 1 LOGIN applecot ******** > 1 OK Logged in. > 2 CAPABILITY > * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT > LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS > 2 OK Capability completed. > 3 LIST "" "" > 3 OK List completed. > > The "LIST" command should be sending back the mailbox separator. The IMAP > spec seems pretty clear about this (but reading RFC's is always a bit of a > challenge). > > From the RFC: http://www.ietf.org/rfc/rfc2060.txt > 6.3..8. LIST Command > > Arguments: reference name > mailbox name with possible wildcards > > Responses: untagged responses: LIST > > Result: OK - list completed > NO - list failure: can't list that reference or name > BAD - command unknown or arguments invalid > ? > An empty ("" string) reference name argument indicates that the > mailbox name is interpreted as by SELECT. The returned mailbox > names MUST match the supplied mailbox name pattern. A non-empty > reference name argument is the name of a mailbox or a level of > mailbox hierarchy, and indicates a context in which the mailbox > name is interpreted in an implementation-defined manner. > > An empty ("" string) mailbox name argument is a special request to > return the hierarchy delimiter and the root name of the name given > in the reference. The value returned as the root MAY be null if > the reference is non-rooted or is null. In all cases, the > hierarchy delimiter is returned. This permits a client to get the > hierarchy delimiter even when no mailboxes by that name currently > exist. > ? > > Example: C: A101 LIST "" "" > S: * LIST (\Noselect) "/" "" > S: A101 OK LIST Completed > C: A102 LIST #news.comp.mail.misc "" > S: * LIST (\Noselect) "." #news. > S: A102 OK LIST Completed > C: A103 LIST /usr/staff/jones "" > S: * LIST (\Noselect) "/" / > S: A103 OK LIST Completed > C: A202 LIST ~/Mail/ % > S: * LIST (\Noselect) "/" ~/Mail/foo > S: * LIST () "/" ~/Mail/meetings > S: A202 OK LIST completed > > -- Bruce > >

1 0

Re: [Dovecot] IMAP Query
by Magnus Holmgren 29 Aug '06

29 Aug '06

On Tuesday 29 August 2006 15:41, Chris Kenward took the opportunity to say: > Hi Magnus > > > Just a couple of general netiquette issues: When bringing up > > a new topic you shouldn't use the Reply command, and you > > should also use a more descriptive subject, such as "Mail > > deleted from IMAP server doesn't disappear". > > Sorry about that - will try and behave a little better in future. In the future, please send follow-ups to the mailing list. The support you get from mailing lists is of a collaborative nature and you can't normally assume that because someone replies to your questions, he or she is prepared to give you personal assistance. Also, the other list subscribers may be interested in the answers. > > What mail user agent are you using? Do the messages *appear* > > in the Trash folder? Messages, when deleted, are normally > > only marked as such and not really removed until they are expunged. > > I'm using Outlook 2003. I've set up this particular account in Outlook as > an IMAP account and the folders all appear as they should down the left > hand side. > > 1. Mail arrives and I get the "beep" to let me know. > 2. I go and look at the Inbox, which has the new message in bold. > 3. I read the message and then highlight and delete it, using either > the DEL key on the keyboard or else the X in Outlook. > 4. The message header is scored through with a line, denoting that it > has been deleted but that's it. The message neither moves from the > Inbox to Trash nor does it disappear. So I end up with a load of > 'deleted' messages in the Inbox. > > Trust that's enough detail. I would have imagined that there would be some > sort of "refresh" every so many seconds or something which would purge > 'deleted' messages. This is a client issue. Some clients let you choose between deleting messages by moving them to the Trash folder or just by marking them as deleted (which is, arguably, The IMAP Way). I don't use Outlook 2003 myself but from what I find by googling it seems that there is no such option in Outlook. However, you can choose whether deleted messages are hidden or shown. http://email.about.com/cs/outlooktips/qt/et060204.htm -- Magnus Holmgren holmgren(a)lysator.liu.se (No Cc of list mail needed, thanks)

3 3

[Dovecot] dovecot SASL as auth backend to exim?
by OpenMacNews 29 Aug '06

29 Aug '06

hi, i'm running dovecot branch_10 cvs on OSX 10.4.7 w/ exim 4.63. i'd like to use Dovecot's SASL as an auth backend to exim, instead of Cyrus-SASL. @ dovecot's sasl page: http://wiki.dovecot.org/Sasl i know there's a patch against exim 4.43: http://www.exim.org/eximwiki/AuthenticatedSmtpUsingDovecot that, purportedly, enables EXIM to use dovecot's SASL as an auth backend. questions: (1) with 'recent' updates to both dovecot/exim, is that patch still required? (2) if so, is that patch still viable/safe against 4.63? (3) can anyone provide a _specific_ example of the exim config(s) (Makefile, Router, Transport) they're using to 'make it work'? i've asked this question @ exim list, but, other than a 'why would you bother?' and a 'good luck with your efforts', no "joy" so far ... thanks, richard -- /"\ \ / ASCII Ribbon Campaign X against HTML email, vCards / \ & micro$oft attachments [GPG] OpenMacNews at gmail dot com fingerprint: 50C9 1C46 2F8F DE42 2EDB D460 95F7 DDBD 3671 08C6

2 1

[Dovecot] Auto-blacklisting hosts after too many failed logins
by Amon Ott 29 Aug '06

29 Aug '06

Hi folks, first of all thanks for Dovecot, I appreciate it a lot. On one of our servers, we experience regular tries to brute force logins, probably based on harvested mail addresses. Now I wonder if dovecot has or could in future have some mechanism to blacklist remote IP addresses after a configurable number of failures to login to any account. Blacklisted IPs could simply be disconnected without giving them a chance to do anything. After e.g. one day or one hour of no further connection, the blacklist entry could be dropped. As a bonus, it would be great to have a way to close the POP3/IMAP firewall ports to these IPs to avoid dovecot seeing the connection at all. A kind of blacklist status file on disk would be enough, from which some cron job could fill a firewall chain. If necessary, I would try to add this functionality myself. Amon. -- http://www.rsbac.org - GnuPG: 2048g/5DEAAA30 2002-10-22

5 4

[Dovecot] 1.0rc7 working well
by Bruce Lane 29 Aug '06

29 Aug '06

Fellow dove-users, Just a note to say that Dovecot 1.0rc7 is working very well indeed, supplying SPOP3, regular POP3, and TLS/SASL services on FreeBSD 6.1 Production, in conjunction with Postfix 2.3.2. I have authentication methods PAM and passwd in use. Keep the peace(es). -=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner & Head Hardware Heavy, Blue Feather Technologies -- http://www.bluefeathertech.com kyrrin (at) bluefeathertech do/t c=o=m "If Salvador Dali had owned a computer, would it have been equipped with surreal ports?"

2 1