- dovecot - dovecot.org

[Dovecot] sieve :regex problem
by Václav Hůla 07 Jul '08

07 Jul '08

Hello, I have dovecot 1.1.1 with dovecot-sieve-1.1.5 and managesieve 0.10.3. Everything is working, with exeption of this filter: if header :comparator "i;ascii-casemap" :regex "X-Spam-Score" ".*\+\+\+\+" { fileinto "Spamq"; stop; } Which I think should match only messages with ++++ somewhere in their X-Spam-Score header - but matches everything (this is filter generated by ingo fom horde.org framework). Can someone please tell me where the problem really is? Ax -- Václav Hůla, správce linuxových serverů Přírodovědecká fakulta Univerzita Karlova v Praze

2 1

[Dovecot] Semi-away until Friday
by Timo Sirainen 07 Jul '08

07 Jul '08

If anyone's been wondering, I'm in India now and I'll get back to Finland on Friday. Until then I don't really have energy to reply to most mails.

1 0

[Dovecot] Dovecot failed with a correct sql user_query
by Nicola Tiling 07 Jul '08

07 Jul '08

Dovecot (1.1.1) criticises a sql user_query that's working on the sql console and thats correct. DOVECOT-LOG: "dovecot: Jul 06 22:58:29 Error: auth(default): sql(nti): User query failed: ERROR: syntax error at or near "mbox" dovecot: Jul 06 22:58:29 Error: auth(default): LINE 1: ...gid, home, (CASE WHEN smtp like '/var/pop3/ THEN 'mbox:' || ..." QUERY: user_query = SELECT '%u' AS user, uid, gid, home, (CASE WHEN home like '/var/pop3/%' THEN 'mbox:' || home || '/mail/:INDEX=' || home || '/ indexes/' WHEN home like '/var/maildir/%' THEN 'maildir:' || home || '/ mail/:INDEX=' || home || '/indexes/' END) AS mail FROM users WHERE username = '%u' AND users.enabled = '1' AND users.type='local' PGSQL-PROMPT: mail=# SELECT 'nti' AS user, uid, gid, home, (CASE WHEN home like '/ var/pop3/%' THEN 'mbox:' || home || '/mail/:INDEX=' || home || '/ indexes/' WHEN home like '/var/maildir/%' THEN 'maildir:' || home || '/ mail/:INDEX=' || home || '/indexes/' END) AS mail FROM users WHERE username = 'nti' AND users.enabled = '1' AND users.type='local'; user | uid | gid | home | mail ------+-----+-----+------------------ +---------------------------------------------------------------- nti | 99 | 99 | /var/maildir/nti | maildir:/var/maildir/nti/ mail/:INDEX=/var/maildir/nti/indexes/

2 2

[Dovecot] can't download attachment from the wiki
by Andrew Schulman 05 Jul '08

05 Jul '08

Hi. At http://wiki.dovecot.org/ManageSieve#line-229 , I want to download the patch that's supposed to fix two problems in Avelsieve. Unfortunately, when I click on the link to the patch, I always get an error message: You are not allowed to do AttachFile on this page. Annoying. I've created an account and logged in, but still no joy. Can anyone suggest how or where else I can get that patch? Thanks, Andrew.

3 5

[Dovecot] Cannot access IMAP from other computer on network
by Anthony Campbell 05 Jul '08

05 Jul '08

I am a newcomer to Dovecot so apologies if this is elementary. I want to set up dovecot to allow other computers on my home network to read emails on my desktop via IMAP. This computer is called arcadia. dovecot is running and I can access the mail on the same computer with mutt -f imap://ac@localhost. If I use the above line on a different computer in the network it says "authenticaing 'PLAIN'" and then "logging in ..", then "login failed" and cuts out. In /etc/dovecot/dovecot.conf I have set disable_plaintext_auth = no I have no idea how to proceed further. Anthony Campell

1 1

[Dovecot] newbie: problem with IMAPS + mutt + Thunderbird
by Toni Mueller 04 Jul '08

04 Jul '08

Hi, I'm a Dovecot newbie and have some problems with the configuration/the resulting interoperability. My setup looks like this: I receive my mail using qmail-ldap and sort it with a number of means into ~/Mailbox/ (= INBOX) and ~/Mail/folder/ for various values of 'folder' (generally one folder per mailing list). The sorting is done via .qmail-* files, LDAP entries, and procmail (this is a "legacy" setup that I'd rather not change too much). I usually access my mail using 'mutt' on the local machine (Debian 4.0), and everything is fine. I'd like to be able to access the same email using Thunderbird over IMAPS as well, to gain foreign character support (ie, Chinese), while continuing to use mutt as my main MUA. There are, so far, two problems with this setup: 1. I can't find the folders in ~/Mail/. As an interim solution, I symlinked them from my ~/Mailbox/ dir, but this is _dead_ugly_. 2. (MUCH more serious) As soon as I access the email using Thunderbird, Dovecot moves all new mail from somefolder/new to somefolder/cur, thereby making mutt flag all my new mail as 'O' ("old") which was flagged 'N' ("new") before. If I remember which the new mails were, I can flag them as 'N' in mutt, and they get moved to .../new again, but this isn't usually the case because my mailboxen are often large (> 10.000 messages), and it's undone as soon as I access the mailbox with Thunderbird (over IMAPS). I also have a wish list. Both Mutt and Dovecot (can) make use of index files to speed mail access. It would be great if this could be unified so that both programs use the same index files (in a consistent manner, of course). The software versions I currently use are these: Mutt: 1.5.17+2008011 Dovecot: 1.0.13-1~bpo40 Thunderbird: 1.5.0.13+1.5.0 Dovecot configuration: log_timestamp: %Y-%m-%dT%H:%M:%S protocols: imaps ssl_listen: 10.10.10.1:993 login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_processes_count: 2 login_max_processes_count: 20 max_mail_processes: 30 first_valid_uid: 2000 first_valid_gid: 2000 mail_location: maildir:~/Mail:INBOX=~/Mailbox/ mail_debug: yes auth default: verbose: yes passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf Kind regards, --Toni++

1 1

[Dovecot] litte problems upgrade from 1.0.x to 1.1.1
by Andre Hübner 04 Jul '08

04 Jul '08

Hi List, last time i did a lot of packaging and installing different versions of dovecot 1.0.x (rc not included ;) )and all was fine. Now a have a little problem. In this case it was an update from 1.0.13 to 1.1.1 Sometime it happens that 1 user out of x (more than 100) got this standardmessage for ~1 or ~2 thousend times in his mailbox (mbox) for example: >From MAILER_DAEMON Mon Sep 18 16:16:14 2006 Date: Mon, 18 Sep 2006 16:16:14 +0200 From: Mail System Internal Data <MAILER-DAEMON@myhostname> Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA Message-ID: 1158588974@myhostname X-IMAP: 1158588973 0000001177 Status: RO This text is part of the internal format of your mail folder, and is not a real message. It is created automatically by the mail system software. If deleted, important folder data will be lost, and it will be re-created with the data reset to initial values. I can follow this in maillog: Jul 1 16:01:04 myhostname dovecot: POP3(username): Disconnected: Logged out top=0/0, retr=1177/21638, del=1177/1177, size=454 The Mails came from nowhere from one moment to other. But it seems that it was not first pop-login after dovecot update. Update time was 14:57 Uhr. Pop-Login which "created" this mails was 3rd after update. It is not a big problem, seems to happens one only time but i want to know the backgrounds. Do you need further data? My 1.1.1 /etc/dovecot.conf looks like this: protocols = imap imaps pop3 pop3s ssl_disable = no ssl_cert_file = "/etc/*.hostname.com.crt" ssl_key_file = "/etc/*.hostname.com.key" ssl_ca_file = "/etc/*.hostname.com.bundle.crt" disable_plaintext_auth = no syslog_facility = mail login_user = dovecot login_process_per_connection = no login_processes_count = 1 login_greeting = hostname.com mailserver ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c login_log_format = %$: %s max_mail_processes = 100 verbose_proctitle = yes auth_verbose = yes mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u #default_mail_env = mbox:~/mail:INBOX=/var/spool/mail/%u mail_cache_min_mail_count = 30 mmap_disable=no mail_debug=no lock_method = flock mbox_read_locks = dotlock mbox_write_locks = dotlock fcntl mbox_dirty_syncs = yes mbox_very_dirty_syncs = yes mbox_lazy_writes = no ## ## IMAP specific settings ## protocol imap { login_executable = /usr/libexec/dovecot/imap-login imap_client_workarounds = outlook-idle netscape-eoh tb-extra-mailbox-sep delay-newmail mail_plugins = mail_log } ## ## POP3 specific settings ## protocol pop3 { ssl_disable = no login_executable = /usr/libexec/dovecot/pop3-login mail_executable = /usr/libexec/dovecot/pop3 pop3_no_flag_updates = no pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = oe-ns-eoh outlook-no-nuls } ## ## Authentication processes auth default { mechanisms = plain passdb shadow { } userdb passwd { } user = root } ## ## Plugins ## plugin { } Thanks Andre

3 2

[Dovecot] Can I stop users from creating and renaming folders?
by Linspeed 04 Jul '08

04 Jul '08

Hello I have a Dovecot IMAP account running. It's a shared account between a few people. I want to stop users being able to rename existing folders and to stop them creating new ones. I've searched for this, so I suspect the answer is no. Is it possible? Thanks -- View this message in context: http://www.nabble.com/Can-I-stop-users-from-creating-and-renaming-folders--… Sent from the Dovecot mailing list archive at Nabble.com.

2 3

Re: [Dovecot] litte problems upgrade from 1.0.x to 1.1.1
by Andre Hübner 04 Jul '08

04 Jul '08

Hi, > It's not UW-IMAP (the server). It's PINE or Alpine (the client). Those are > usually found in on-disk mbox files that have been created by PINE/Alpine. > The message is ignored by PINE/Alpine (obviously), but when you switch to > a different mailer, it doesn't know to ignore it (and shouldn't be > expected to). AFAIK, the only solution is to delete the messages. i do not think it is client related. (never heared of this clients) Seems to be a normal dovecot internal message (timo?) But dovecot should not deliver this message as real mail, regardless of which client is used. Furthermore we face this issue only by updating to 1.1.1, all earlier versions did not show this behavior. Andre

1 0

[Dovecot] Different PROXY for IMAP and POP3 using LDAP-auth
by Ralf Becker 04 Jul '08

04 Jul '08

Hello everybody! I'm trying to configure dovecot 1.1.1 with different proxy hosts and/or ports for different protocols (IMAP, POP3). I'm using LDAP for authentication. I've tried: 1) Variable in "auth default" configuration: [dovecot.conf] passdb ldap { args = /usr/local/etc/dovecot-ldap-%Ls.conf } userdb ldap { args = /usr/local/etc/dovecot-ldap-%Ls.conf } With results in dovecot not starting with error message: Can't open configuration file /usr/local/etc/dovecot-ldap-%Ls.conf: No such file or directory So %Ls was not replaced. 2) Variable in pass_attrs [dovecot-ldap.conf] pass_attrs = \ uid=user,userPassword=password,homeDirectory=userdb_home,\ uidNumber=userdb_uid,gidNumber=userdb_gid,\ dovecotProxy%Ls=proxy,dovecotHost%Ls=host,dovecotPort%Ls=port With results in this LDAP server log entries: SRCH attr=uid userPassword homeDirectory uidNumber gidNumber dovecotProxy%Ls dovecotHost%Ls dovecotPort%Ls So %Ls was not replaced also. mmmh... Would it be an option to use multiple "auth" sections? E.g: auth pop3 { ... passdb ldap { args = /usr/local/etc/dovecot-ldap-pop3.conf } userdb ldap { args = /usr/local/etc/dovecot-ldap-pop3.conf } ... } auth imap { ... passdb ldap { args = /usr/local/etc/dovecot-ldap-imap.conf } userdb ldap { args = /usr/local/etc/dovecot-ldap-imap.conf } ... } I'm in doubt because of http://markmail.org/message/rcpcm67g56kxxdyq Any ideas? Regards, Ralf Becker -- ______________________________________________________________________ Dipl.-Inform. (FH) Ralf Becker Rechenzentrum (r/ft) der FH Trier (Network|Mail|Web|Firewall) University of applied sciences Administrator Schneidershof, D-54293 Trier Mail: beckerr(a)fh-trier.de Fon: +49 651 8103 499 Web: http://www.fh-trier.de/~beckerr Fax: +49 651 8103 214 PubKey: http://www.fh-trier.de/~beckerr Crypto: GnuPG, S/MIME ______________________________________________________________________ Wenn Gott gewollt haette, dass E-Mail in HTML geschrieben wuerden, endeten Gebete traditionell mit </amen>. (Tom Listen)

3 3