Re: [Dovecot] .dovecot.sieve/tmp)failed: Not a directory
On 4/25/2013 3:20 PM, JC Putter wrote: stat(/var/spool/vmail/example.com/user/.dovecot.sieve/tmp)failed: Not a directory Could you send dovecot -n output? The config data you sent looks incomplete. Regards, Stephan.
[Dovecot] Replication fails with "Remote dsync doesn't use compatible protocol"
I can't get replication to work in Dovecot 2.2.1. I'm getting the following error on the machine where I'm initiating the replication: richatwork dovecot: doveadm: Error: dsync-remote(richatwork): Error: dsync(local): Remote dsync doesn't use compatible protocol Both the local and remote servers are running identical versions of Dovecot (2.2.1), so I don't understand why I would be having any sort of "compatible protocol" problem. Any ideas? I posted the "dovecot -n" output for both servers in my earlier e-mail on this issue, which I sent about 24 hours ago (and which I assume was too long for people to be willing to read). Rich Wales ri...@richw.org
Re: [Dovecot] .dovecot.sieve/tmp)failed: Not a directory
On 2013-04-25 9:20 AM, JC Putter wrote: stat(/var/spool/vmail/example.com/user/.dovecot.sieve/tmp)failed: Not a directory auth_mechanisms = plain login Looks like an ancient version, since the version info is not included with doveconf -n output? According to the Wiki Always provide a link too... is this the wiki for version 1 (wiki1.) or 2 (wiki2.)? "It is not wise to place this link inside your mail store, as it may be mistaken for a mail folder. Inside a maildir for instance, the default .dovecot.sieve would show up as phantom folder */dovecot/sieve* in your IMAP tree." Sorry i am a bit of a noob, the docs don't explain clearly what to do... You need to create and set a 'home' directory for each user for this kind of things (even if they are virtual users, they need a 'home' dir)... http://wiki2.dovecot.org/MailLocation Scroll down to where it discusses 'Homeless users'... If you are still on version 1, the first thing you need to do is upgrade to at least the latest 2.1, but I'd recommend just upgrading to the latest 2.2 (currently 2.2.1)... -- Best regards, Charles
Re: [Dovecot] Lucene and Zlib with 2.2.1
Am 25.04.2013 18:55, schrieb Kyle Wheeler: > As you can probably tell, I'm using the fts_lucene plugin, which used to > work just fine (with Dovecot 2.1.x). Is this expected behavior? Are > these errors truly ignorable? Why are these compressed mailboxes not > selectable? sorry to ask , but did you compile with lucene ? Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich
[Dovecot] Lucene and Zlib with 2.2.1
Hello, I have an "archive" folder in my inbox, where I manually stick old mails into a compressed mbox format. Since upgrading to Dovecot 2.2.1, I've started seeing messages like the following in my log files: imap(...): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable indexer-worker(...): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable indexer-worker(...): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable indexer-worker(...): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable imap(...): Error: indexer failed to index mailbox INBOX/Archive/2007/Sent.gz These errors *appear* to be mostly benign; I still get results from searching the mailbox. But for whatever reason, the indexer appears to not be working for those folders. As you can probably tell, I'm using the fts_lucene plugin, which used to work just fine (with Dovecot 2.1.x). Is this expected behavior? Are these errors truly ignorable? Why are these compressed mailboxes not selectable? ~Kyle -- Where justice is denied, where poverty is enforced, where ignorance prevails, and where any one class is made to feel that society is an organized conspiracy to oppress, rob and degrade them, neither persons nor property will be safe. -- Frederick Douglas pgpjUsJjJskam.pgp Description: PGP signature
[Dovecot] search and UTF-8 normalization forms (NFD)
Hello,
on a system with dovecot 2.2 I've got a mailbox containing multiple mails
from a person called Krüger, but From: header encoded differently.
Some are encoded in UTF-8 normalization form decomposed (as used by Mac OSX),
that is u and umlaut accent as sperate combined codepoints
instead of one ü:
From: =?utf-8?Q?replaced_Kru=CC=88ger?=
Searching within roundcube webmail for "krüger" as sender
missis this mails.
Roundcube sends (dovecot rawlog):
A0003 UID THREAD REFS UTF-8 ALL HEADER FROM {7+}krüger
Is this supposed to work? Haven't done any more debugging
(other search variants) or read RFCs. As a user I would expect
Unicode equivalence rules be applied (see
http://en.wikipedia.org/wiki/Unicode_equivalence)
Regards,
Lutz
[Dovecot] .dovecot.sieve/tmp)failed: Not a directory
stat(/var/spool/vmail/example.com/user/.dovecot.sieve/tmp)failed: Not
a directory
auth_mechanisms = plain login
disable_plaintext_auth = no
first_valid_uid = 2000
last_valid_uid = 2000
mail_gid = 2000
mail_location = maildir:/var/spool/vmail/%d/%n
mail_uid = 2000
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
mbox_write_locks = fcntl
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
service auth {
unix_listener auth-userdb {
group = vmail
mode = 0600
user = vmail
}
}
ssl_cert =
[Dovecot] doveadm search causes replication error message
Hi # 2.2.1 (83d83f55e5c2+) / dsync replicated setup I just noticed that 'doveadm search' apparently tries to replicate mailboxes and spits out errors if a mailbox in the search query is not found: #doveadm search -u u...@example.com mailbox Spamreport doveadm(u...@example.com): Error: Syncing mailbox Spamreport failed: Mailbox doesn't exist: Spamreport this is especially problematic with -A searches as this causes a error message for every user which doesn't have that folder. Is this a bug or intended behaviour? Should I just 2>/dev/null these errors in doveadm scripts? Thanks Oli -- message transmitted on 100% recycled electrons
