Re: [Dovecot] Advice on sieve vacation for aliases
Marcio Merlone wrote: > j...@domain.tld and meg...@domain.tld. I have created a > sieve_global_path = /etc/dovecot/global.sieve and it works, but not > the intended way: it sends two vacation messages, each From: each > employee, and not From: comerc...@domain.tld alias. Arguments to vacation are documented in RFC 5230: http://tools.ietf.org/html/rfc5230#page-10 Try to add:from comerc...@domain.tld parameter to the vacation command. This should at least change the "From:" header of the vacation messages. Regards, Daniel -- https://plus.google.com/103021802792276734820
Re: [Dovecot] dovecot index errors since 2.1.12
On 18.12.2012 23:44, Timo Sirainen wrote: On 19.12.2012, at 0.40, Morten Stevens wrote: Dec 10 15:21:04 mail dovecot: imap(u...@example.org): Error: Cached message size smaller than expected (5010 < 8192) Dec 10 15:21:04 mail dovecot: imap(u...@example.org): Error: Corrupted index cache file /var/vmail/example.org/user//mdbox/mailboxes/INBOX/Ubuntu/dbox-Mails/dovecot.index.cache: Broken physical size for mail UID 27517 Could you try if this fix helps? http://hg.dovecot.org/dovecot-2.1/rev/bded819417d9 Thanks for the quick reply, but it doesn't help. Can you easily reproduce this with a new empty user, using some simple IMAP commands? Or alternatively running imaptest tool? http://imapwiki.org/ImapTest I'm not able to reproduce this with a new empty user and I am also not able to reproduce this error after I deleted the affected folders and recreated them. Also send your full doveconf -n output. And especially: are you using zlib plugin compression? Storing attachments separately? No zlib compression and we do not save the attachments separately. Do you still need the full doveconf -n output? I think it's fixed with commit bded819417d9. Best regards, Morten
Re: [Dovecot] dovecot index errors since 2.1.12
On 19.12.2012, at 0.40, Morten Stevens wrote: >>> Dec 10 15:21:04 mail dovecot: imap(u...@example.org): Error: Cached message >>> size smaller than expected (5010 < 8192) >>> Dec 10 15:21:04 mail dovecot: imap(u...@example.org): Error: Corrupted >>> index cache file >>> /var/vmail/example.org/user//mdbox/mailboxes/INBOX/Ubuntu/dbox-Mails/dovecot.index.cache: >>> Broken physical size for mail UID 27517 >> >> Could you try if this fix helps? >> http://hg.dovecot.org/dovecot-2.1/rev/bded819417d9 > > Thanks for the quick reply, but it doesn't help. Can you easily reproduce this with a new empty user, using some simple IMAP commands? Or alternatively running imaptest tool? http://imapwiki.org/ImapTest Also send your full doveconf -n output. And especially: are you using zlib plugin compression? Storing attachments separately?
Re: [Dovecot] dovecot index errors since 2.1.12
On 18.12.2012 22:42, Timo Sirainen wrote: On 18.12.2012, at 23.37, Morten Stevens wrote: After upgrading to dovecot 2.1.12, I see a lot of these errors: # 2.1.12: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.14.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) # Filesystem: ext4 with mdbox storage Dec 10 15:21:04 mail dovecot: imap(u...@example.org): Error: Cached message size smaller than expected (5010 < 8192) Dec 10 15:21:04 mail dovecot: imap(u...@example.org): Error: Corrupted index cache file /var/vmail/example.org/user//mdbox/mailboxes/INBOX/Ubuntu/dbox-Mails/dovecot.index.cache: Broken physical size for mail UID 27517 Could you try if this fix helps? http://hg.dovecot.org/dovecot-2.1/rev/bded819417d9 Hi Timo, Thanks for the quick reply, but it doesn't help. Dec 18 23:25:28 mail dovecot: imap(us...@example.org): Error: Cached message size larger than expected (5437 > 3778) Dec 18 23:25:28 mail dovecot: imap(us...@example.org): Error: Corrupted index cache file /var/vmail/example.org/user2//mdbox/mailboxes/Commit/dbox-Mails/dovecot.index.cache: Broken physical size for mail UID 684475 Dec 18 23:25:28 mail dovecot: imap(us...@example.org): Error: read(/var/vmail/example.org/user2//mdbox/storage/m.15613) failed: Input/output error (FETCH for mailbox Commit UID 684475) Dec 18 23:25:28 mail dovecot: imap(us...@example.org): Disconnected: Internal error occurred. Refer to server log for more information. [2012-12-18 23:25:28] in=6602 out=5191621 Dec 18 23:25:52 mail dovecot: imap(us...@example.org): Error: Cached message size larger than expected (8371 > 7123) Dec 18 23:25:52 mail dovecot: imap(us...@example.org): Error: Corrupted index cache file /var/vmail/example.org/user2//mdbox/mailboxes/LKML/dbox-Mails/dovecot.index.cache: Broken physical size for mail UID 216722 Dec 18 23:25:52 mail dovecot: imap(us...@example.org): Error: read(/var/vmail/example.org/user2//mdbox/storage/m.15604) failed: Input/output error (FETCH for mailbox LKML UID 216722) Dec 18 23:25:52 mail dovecot: imap(us...@example.org): Disconnected: Internal error occurred. Refer to server log for more information. [2012-12-18 23:25:52] in=24312 out=41801670 Dec 18 23:26:00 mail dovecot: imap(us...@example.org): Error: Cached message size larger than expected (6008 > 5194) Dec 18 23:26:00 mail dovecot: imap(us...@example.org): Error: Corrupted index cache file /var/vmail/example.org/user2//mdbox/mailboxes/Google/dbox-Mails/dovecot.index.cache: Broken physical size for mail UID 935885 Dec 18 23:26:00 mail dovecot: imap(us...@example.org): Error: read(/var/vmail/example.org/user2//mdbox/storage/m.15620) failed: Input/output error (FETCH for mailbox Google UID 935885) Dec 18 23:26:00 mail dovecot: imap(us...@example.org): Disconnected: Internal error occurred. Refer to server log for more information. [2012-12-18 23:26:00] in=6334 out=7859459 Dec 18 23:26:38 mail dovecot: imap(us...@example.org): Error: Cached message size smaller than expected (4433 < 5226) Dec 18 23:26:38 mail dovecot: imap(us...@example.org): Error: Corrupted index cache file /var/vmail/example.org/user2//mdbox/mailboxes/Bugs/dbox-Mails/dovecot.index.cache: Broken physical size for mail UID 497733 Dec 18 23:26:38 mail dovecot: imap(us...@example.org): Error: read(/var/vmail/example.org/user2//mdbox/storage/m.15620) failed: Input/output error (FETCH for mailbox Bugs UID 497733) Dec 18 23:26:38 mail dovecot: imap(us...@example.org): Disconnected: Internal error occurred. Refer to server log for more information. [2012-12-18 23:26:38] in=1589 out=1320584 Do you have an idea? Best regards, Morten
Re: [Dovecot] When imapc can't connect to remote IMAP prevents user login (and blocks LDA)
W dniu 2012-12-18 23:10, Timo Sirainen pisze:
> On 19.12.2012, at 0.06, Marcin Mirosław wrote:
>
I'd like to ask is this behavior correct?
>>>
>>> You're using Dovecot as simple imapc proxy without local mails? Then
>>> yeah, what else could it really do?
>>
>> Here is problem, I'm using local mails also!:) So when remote imap
>> server doesn't want to talk with me I can't even check mail emails.
>> I can understand this behavior (e.g. lda can't deliver email because
>> sieve script could put such email in folder available via imapc) but it
>> looks like a kind of DoS for my mailbox;) Maybe some kind of switch
>> could be implemented: treat imapc errors as critical or not? Just an idea.
>
> I saw only one namespace in your configuration. Are you adding the imapc
> namespace somewhere else, or how exactly does your system work? Anyway, if
> you have a separate imapc namespace, I think you can simply set:
>
> namespace .. {
> ignore_on_failure = yes
> }
So I reinvented the wheel:] Thanks for tip!
I'm storing namespaces in database.
Thanks again,
Marcin
Re: [Dovecot] passdb to add extra fields?
At 11PM +0200 on 18/12/12 you (Timo Sirainen) wrote:
> Some passdbs like PAM can't really return any extra fields. Also some
> people have wanted to combine users' data from different passdb/userdbs
> so that for example you'd have userdb passwd give the uid/gid/home, but
> then you'd also have some other userdb give quota limits.
>
> So I was thinking something like this:
>
> passdb {
> driver = pam
> }
> passdb {
> driver = sql
> include = yes
> }
>
> or:
>
> userdb {
> driver = passwd
> }
> userdb {
> driver = passwd-file
> include = yes
> }
>
> I'm not sure about two things:
>
> 1) Should there be a way to replace all of the existing fields instead
> of just adding new ones?
>
> 2) Any thoughts of a better name than "include"? With passdb it would
> mean that it's included only when the authentication failed for some
> other passdb. With userdb it means it's included only if a previous
> userdb lookup succeeded.
>
> Also there are already "deny" and "pass" settings. Interaction with them
> can be somewhat confusing.. Maybe all of these should be replaced with:
>
> type=deny: Same as old deny=yes (deny auth if user is in list)
> type=precondition(?): Same as pass=yes (require another passdb to match)
> type=postcondition(?): Require user to exist in this passdb/userdb as
> well, adding any extra fields in it.
> type=add: Add any extra fields, if the user exists at all.
>
> (Better ideas for the names here? Is even "type" a good name?)
This sounds like the nsswitch.conf [notfound=continue] stuff, perhaps
you could use those names?
Status
success entry found
notfoundentry definitely not found
tryagaindatabase temporarily unavailable
unavail database not responding (an error of some kind)
Action
return return the current result
continuetry the next db and accumulate fields
with defaults of
success = return
notfound = continue
tryagain = continue
unavail = continue
You could potentially add other actions, like 'retry' which waits a bit
and retries. Some sort of 'tempfail' action, which returns temporary
failure to the client, would be good, but I don't think IMAP supports
that, unless you just drop the connection and assume the client will
reconnect and retry.
That would mean your first example would need to be
passdb {
driver = pam
success = continue
}
passdb {
driver = sql
}
You could also add an 'override' key so that with this
userdb {
driver = passwd
success = continue
}
userdb {
driver = sql
}
the SQL can't set 'home' (because passwd has already set it) but with
this
userdb {
driver = passwd
success = continue
}
userdb {
driver = sql
override = home
}
it can.
Ben
Re: [Dovecot] When imapc can't connect to remote IMAP prevents user login (and blocks LDA)
On 19.12.2012, at 0.06, Marcin Mirosław wrote:
>>> I'd like to ask is this behavior correct?
>>
>> You're using Dovecot as simple imapc proxy without local mails? Then
>> yeah, what else could it really do?
>
> Here is problem, I'm using local mails also!:) So when remote imap
> server doesn't want to talk with me I can't even check mail emails.
> I can understand this behavior (e.g. lda can't deliver email because
> sieve script could put such email in folder available via imapc) but it
> looks like a kind of DoS for my mailbox;) Maybe some kind of switch
> could be implemented: treat imapc errors as critical or not? Just an idea.
I saw only one namespace in your configuration. Are you adding the imapc
namespace somewhere else, or how exactly does your system work? Anyway, if you
have a separate imapc namespace, I think you can simply set:
namespace .. {
ignore_on_failure = yes
}
Re: [Dovecot] When imapc can't connect to remote IMAP prevents user login (and blocks LDA)
W dniu 2012-12-18 21:33, Timo Sirainen pisze: Hi Timo, hi all! > On Sat, 2012-12-15 at 18:14 +0100, Marcin Mirosław wrote: >> I'm using dovecot 2.1.12-r1. >> When remote imap server rejects connections then I can't login into >> account and MTA can't deliver emails to maildir also. >> >> I'm attaching snippets of logs: >> 2012-12-15T18:05:43.072594+01:00 meteor dovecot: imap-login: Login: >> user=, method=PLAIN, >> rip=2001:470:1f0b:1ab3:50af:bef4:6918:78ad, lip=2001:470:1f15:1b61::2, >> mpid=32533, TLS, session= >> 2012-12-15T18:05:43.442598+01:00 meteor dovecot: imap(mar...@mejor.pl) >> : Error: imapc(imap.wp.pl:143): Server >> disconnected: Connection reset by peer >> 2012-12-15T18:05:43.442598+01:00 meteor dovecot: imap(mar...@mejor.pl) >> : Error: imapc(imap.wp.pl:143): >> Authentication failed: Disconnected from server >> 2012-12-15T18:05:43.442598+01:00 meteor dovecot: imap(mar...@mejor.pl) >> : Error: imapc: Command failed: >> Disconnected from server >> 2012-12-15T18:05:43.442598+01:00 meteor dovecot: imap(mar...@mejor.pl) >> : Error: user mar...@mejor.pl: >> Initialization failed: Namespace 'xxx-wp-pl.': imapc: LIST failed: >> Internal error occurred. Refer to server log for more information. >> [2012-12-15 18:05:43] >> 2012-12-15T18:05:43.442598+01:00 meteor dovecot: imap(mar...@mejor.pl) >> : Error: Invalid user settings. Refer >> to server log for more information. > > Would be nice to have fewer and nicer error message lines of course. This isn't problem for me. >> I'd like to ask is this behavior correct? > > You're using Dovecot as simple imapc proxy without local mails? Then > yeah, what else could it really do? Here is problem, I'm using local mails also!:) So when remote imap server doesn't want to talk with me I can't even check mail emails. I can understand this behavior (e.g. lda can't deliver email because sieve script could put such email in folder available via imapc) but it looks like a kind of DoS for my mailbox;) Maybe some kind of switch could be implemented: treat imapc errors as critical or not? Just an idea. Thanks, Marcin
Re: [Dovecot] passdb to add extra fields?
On Tue, Dec 18, 2012 at 4:12 PM, Timo Sirainen wrote: > [[...]]] > 2) Any thoughts of a better name than "include"? With passdb it would > mean that it's included only when the authentication failed for some > other passdb. With userdb it means it's included only if a previous > userdb lookup succeeded. > Amend ??
Re: [Dovecot] dovecot index errors since 2.1.12
On 18.12.2012, at 23.37, Morten Stevens wrote: > After upgrading to dovecot 2.1.12, I see a lot of these errors: > > # 2.1.12: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.32-279.14.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) > # Filesystem: ext4 with mdbox storage > > Dec 10 15:21:04 mail dovecot: imap(u...@example.org): Error: Cached message > size smaller than expected (5010 < 8192) > Dec 10 15:21:04 mail dovecot: imap(u...@example.org): Error: Corrupted index > cache file > /var/vmail/example.org/user//mdbox/mailboxes/INBOX/Ubuntu/dbox-Mails/dovecot.index.cache: > Broken physical size for mail UID 27517 Could you try if this fix helps? http://hg.dovecot.org/dovecot-2.1/rev/bded819417d9
[Dovecot] dovecot index errors since 2.1.12
Hi, After upgrading to dovecot 2.1.12, I see a lot of these errors: # 2.1.12: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.14.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) # Filesystem: ext4 with mdbox storage Dec 10 15:21:04 mail dovecot: imap(u...@example.org): Error: Cached message size smaller than expected (5010 < 8192) Dec 10 15:21:04 mail dovecot: imap(u...@example.org): Error: Corrupted index cache file /var/vmail/example.org/user//mdbox/mailboxes/INBOX/Ubuntu/dbox-Mails/dovecot.index.cache: Broken physical size for mail UID 27517 Dec 10 15:21:04 mail dovecot: imap(u...@example.org): Error: read(/var/vmail/example.org/user//mdbox/storage/m.7123) failed: Input/output error (FETCH for mailbox INBOX/Ubuntu UID 27517) Dec 10 15:21:04 mail dovecot: imap(u...@example.org): Disconnected: Internal error occurred. Refer to server log for more information. [2012-12-10 15:21:04] in=3391 out=1383967 Dec 17 21:38:34 mail dovecot: imap(us...@example.org): Error: Cached message size larger than expected (1 > 12085) Dec 17 21:38:34 mail dovecot: imap(us...@example.org): Error: Corrupted index cache file /var/vmail/example.org/user2//mdbox/mailboxes/LKML/dbox-Mails/dovecot.index.cache: Broken physical size for mail UID 216231 Dec 17 21:38:34 mail dovecot: imap(us...@example.org): Error: read(/var/vmail/example.org/user2//mdbox/storage/m.15569) failed: Input/output error (FETCH for mailbox LKML UID 216231) Dec 17 21:38:34 mail dovecot: imap(us...@example.org): Disconnected: Internal error occurred. Refer to server log for more information. [2012-12-17 21:38:34] in=4079 out=61996358 Dec 17 21:40:34 mail dovecot: imap(us...@example.org): Error: Cached message size larger than expected (6726 > 5302) Dec 17 21:40:34 mail dovecot: imap(us...@example.org): Error: Corrupted index cache file /var/vmail/example.org/user2//mdbox/mailboxes/Google/dbox-Mails/dovecot.index.cache: Broken physical size for mail UID 930834 Dec 17 21:40:34 mail dovecot: imap(us...@example.org): Error: read(/var/vmail/example.org/user2//mdbox/storage/m.15544) failed: Input/output error (FETCH for mailbox Google UID 930834) Dec 17 21:40:34 mail dovecot: imap(us...@example.org): Disconnected: Internal error occurred. Refer to server log for more information. [2012-12-17 21:40:34] in=27666 out=29738162 Since the release of dovecot 2.1.x, I have never seen this error message. After downgrading to 2.1.10 the error is gone. Andy ideas? Best regards, Morten
[Dovecot] passdb to add extra fields?
Some passdbs like PAM can't really return any extra fields. Also some
people have wanted to combine users' data from different passdb/userdbs
so that for example you'd have userdb passwd give the uid/gid/home, but
then you'd also have some other userdb give quota limits.
So I was thinking something like this:
passdb {
driver = pam
}
passdb {
driver = sql
include = yes
}
or:
userdb {
driver = passwd
}
userdb {
driver = passwd-file
include = yes
}
I'm not sure about two things:
1) Should there be a way to replace all of the existing fields instead
of just adding new ones?
2) Any thoughts of a better name than "include"? With passdb it would
mean that it's included only when the authentication failed for some
other passdb. With userdb it means it's included only if a previous
userdb lookup succeeded.
Also there are already "deny" and "pass" settings. Interaction with them
can be somewhat confusing.. Maybe all of these should be replaced with:
type=deny: Same as old deny=yes (deny auth if user is in list)
type=precondition(?): Same as pass=yes (require another passdb to match)
type=postcondition(?): Require user to exist in this passdb/userdb as
well, adding any extra fields in it.
type=add: Add any extra fields, if the user exists at all.
(Better ideas for the names here? Is even "type" a good name?)
Then maybe a new setting to delete existing extra fields .. or perhaps
just extend passdb { override_fields } so that having "-field" would
delete the field if it already existed..
Re: [Dovecot] Adding a parameter to dovecot's deliver to get a meaningful return value
On Mon, 2012-12-17 at 18:20 +0100, Cyril RUSSO wrote: > Hi, > > First, please forgive me as I'm not subscribed to the list. > I'm using Dovecot 2 (2.1.7) for serving my local maildir. > This maildir is filled by an external process, fetching & merging mails from > different sources that's outside this scope (but it's working). > > Dovecot is thus acting as a MTA, but more as a MDA. > I've a web client running on the server, and it connects to Dovecot to get > the mails. > I've configured this web client & dovecot to use sieve to filter the mails. I > know that since Dovecot does not actually deliver the messages, it's not the > expected behavior. > Anyway, I can use the "deliver" software in your suite for passing sieve's > rules on each message in my maildir, and it's almost working. > I've a cron job that run deliver on each message of my maildir, but I'm a bit > puzzled now. > Basically, I'm not able to figure out if a message was matched by a sieve > filter or not. > > I'm a bit disappointed by two things: > 1) Sieve's reject doesn't make "deliver" to return an error, so a sieve rule > chain ending in "reject" can't be detected from my cron's script. > I wonder it's due to the step deliver is supposed to be run (after a mail is > already accepted). With dovecot-lda -e parameter you could at least in theory use ereject extension (not sure if Pigeonhole implements that now). Also alternatively the reject command will execute sendmail_path to send the rejection mail. You could catch that and e.g. create some flag file. > 2) "deliver" doesn't have a method to find out if it processed the given mail > as input. > > Basically, would it be possible to either add a parameter to "deliver" (for > example: "--fail-on-discarding") so it would fail if the sieve rules discard > or reject (/ereject) the mail ? > That way, I could detect the failure in my script, and know that I don't need > to delete the initial mail since it was not filtered. > > Or, thought differently, I wonder if "deliver" could open a socket/pipe/file > whatever, and write the number of processed mails in there (or using a > "--return-processed-mail"), so a sieve rule ending with "delete", would be > detectable by my script. All of this sounds like a rather complex and probably somewhat fragile solution. I don't think I'd want to add such features where there is only one user (you).
Re: [Dovecot] Undeserved permissions error with g+s folder permissions
On Tue, 2012-12-18 at 14:13 -0500, tlhackque wrote: > >> Unable to rename across conflicting directory permisssions > >> > >> If I chmod g-s Vendors, the RENAME command succeeds. > > Where are you renaming it to and what permissions that directory has? I > > can't seem to easily reproduce this. > > > > > Thanks for looking at this! .. > dovecot --version > 2.1.10 Looks like this was fixed in v2.1.11.
Re: [Dovecot] mail_log_events seem to be broken in HG 2.2
On Sun, 2012-12-16 at 10:17 +0100, Thomas Leuxner wrote:
> It seems along the way of 2.2alpha1 'mail_log_events' quietly stopped
> working. They don't log expunges etc. anymore.
>
> […]
> mail_log_events = expunge mailbox_delete
Dunno. Latest hg works with my test:
mail_plugins = " notify mail_log"
plugin {
mail_log_events = expunge mailbox_delete
mail_log_fields = uid box msgid size
}
x expunge
imap(tss 5414 ): Info: expunge: box=INBOX, uid=2369,
msgid=<1051291295.32159.381.camel@hurina>, size=4598
x delete foo
imap(tss 5414 ): Info: Mailbox deleted: foo
Re: [Dovecot] When imapc can't connect to remote IMAP prevents user login (and blocks LDA)
On Sat, 2012-12-15 at 18:14 +0100, Marcin Mirosław wrote: > I'm using dovecot 2.1.12-r1. > When remote imap server rejects connections then I can't login into > account and MTA can't deliver emails to maildir also. > > I'm attaching snippets of logs: > 2012-12-15T18:05:43.072594+01:00 meteor dovecot: imap-login: Login: > user=, method=PLAIN, > rip=2001:470:1f0b:1ab3:50af:bef4:6918:78ad, lip=2001:470:1f15:1b61::2, > mpid=32533, TLS, session= > 2012-12-15T18:05:43.442598+01:00 meteor dovecot: imap(mar...@mejor.pl) > : Error: imapc(imap.wp.pl:143): Server > disconnected: Connection reset by peer > 2012-12-15T18:05:43.442598+01:00 meteor dovecot: imap(mar...@mejor.pl) > : Error: imapc(imap.wp.pl:143): > Authentication failed: Disconnected from server > 2012-12-15T18:05:43.442598+01:00 meteor dovecot: imap(mar...@mejor.pl) > : Error: imapc: Command failed: > Disconnected from server > 2012-12-15T18:05:43.442598+01:00 meteor dovecot: imap(mar...@mejor.pl) > : Error: user mar...@mejor.pl: > Initialization failed: Namespace 'xxx-wp-pl.': imapc: LIST failed: > Internal error occurred. Refer to server log for more information. > [2012-12-15 18:05:43] > 2012-12-15T18:05:43.442598+01:00 meteor dovecot: imap(mar...@mejor.pl) > : Error: Invalid user settings. Refer > to server log for more information. Would be nice to have fewer and nicer error message lines of course. > I'd like to ask is this behavior correct? You're using Dovecot as simple imapc proxy without local mails? Then yeah, what else could it really do?
Re: [Dovecot] mdbox: more then one altstorage
On Sat, 2012-12-15 at 08:44 +0100, Peer Heinlein wrote: > The mdbox-format with the altstorage-feature is quite nice and important. > > But we're having much more then >> 30 TB of maildata and doing an fsck > on huge partitions takes too much (down-) time for our mailsystem. > > It would be much easier, if Dovecot would be able to use at least THREE > storage-paths for his m-Files (and not just TWO like now). People have asked for this a few times, but it's not that easy to implement (because of how altstorage code is now implemented), and I'm not really convinced that it's worth the trouble to add. > Having an altstorage1 and altstorage2, we would be able to move away all > mails from on altstorage-mountpoint, we could put this > storage-moungpoint into "maintenance" and do an fsck without Downtime > for Dovecot. > > > It would be nice having a doveadm-feature to put a altstorage-path in > "maintenance-mode", so to move easily away all m-files to other > alt-storage-paths and to let Dovecot know not to use this locked partition. The new "doveadm mount" stuff can handle this. If you unmount a filesystem (and maybe mounting it to another mountpoint), Dovecot will just fail all commands that attempt to access the altstorage (instead of assuming all the mails are gone and recreating the index). I think moving from one altstorage to another would be possible with rsync: 1. Mount the new storage 2. cp/rsync files to new storage [3. If it takes long enough that doveadm purge/altmove is already run, rsync again.] 5. Move the new storage's mountpoint over the old one (not sure if there's a way to do this atomically?) > Having even more then 3 storage-paths would be nice for huge setups: In > this case we could easily use different SMALLER partitions without > having just two or three huge partitions > 15 TB. Like others mentioned, you could do this also by dividing users to multiple different partitions.
Re: [Dovecot] Undeserved permissions error with g+s folder permissions
It's an MBox file that I'm trying to rename, not a directory. | file Vendors/|| ||Vendors/: setgid directory|| || file Vendors/Test|| ||Vendors/Test: empty|| | (Perhaps you missed that I said I created it "messages only", and the config I originally posted showed the file storage is mbox...) So perhaps dovecot is confused - expecting an mbox file to have directory permissions, when the directory it's in is setgid? At least that's how it has seemed to me all along... Thanks. This communication may not represent my employer's views, if any, on the matters discussed. On 18-Dec-12 14:28, Reindl Harald wrote: Am 18.12.2012 19:39, schrieb Timo Sirainen: On Sat, 2012-12-01 at 10:59 -0500, tlhackque wrote: It contains a subdirectory: -rw-rw 1 thlackque mail 84805345 Dec 1 10:34 Vendors/AVendor If I try to rename the AVendor folder (client is Thunderbird 17.0), I get this error: Unable to rename across conflicting directory permisssions this is 660 which is simply wrong for a directrory in case of diretcories you need the excue flag means 770 -- This communication may not represent my employer's views, if any, on the matters discussed.
Re: [Dovecot] Clear-text ldap passwords: {CLEAR} scheme?
On Fri, 2012-12-14 at 15:37 +0100, Kristof Bajnok wrote:
> Hi,
>
> if I read the documentation correctly, the clear-text password storage
> scheme in Dovecot is called PLAIN. Unfortunately, in Sun LDAP Directory
> Server I have to specify them as "{CLEAR}" [1].
>
> Is it somehow possible to make Dovecot recognise "{clear}foobar"
> passwords as plaintext? Now I get:
> auth: Error: ldap(username): Unknown scheme clear
Hmh. Okay: http://hg.dovecot.org/dovecot-2.1/rev/bde8963a3774
Re: [Dovecot] dovecot-lda (2.1.12) segfaults
On Thu, 2012-12-13 at 03:56 -0800, Joseph Tam wrote: > We uograded our dovecot from version 2.1.10 -> 2.10.12, but within > the first hour of use, dovecot-lda would segfault during delivery. > This left a lock file lying around causing the user's mail readers to > hang; much hilarity ensues. All further deliveries to the same user > will result in a crash. > > The only thing that fixes this condition is to blow away the user's > INBOX cache index. Reindexing with "doveadm index" does not fix > anything. > > I've installed a test version with one user's problematic INBOX > cache indices and ran > > gdb dovecot-lda > (gdb) run -t testuser > and it crashes with the following backtrace > > Program received signal SIGSEGV, Segmentation fault. > 0xff2a0440 in mail_cache_header_fields_read (cache=0x5c120) at > mail-cache-fields.c:323 > 323 if (field_hdr->size < sizeof(*field_hdr) + .. > (gdb) p field_hdr > $1 = (const struct mail_cache_header_fields *) 0x20 So mail_cache_map() returned a broken pointer.. > Is this enough debug info to work your magic, Timo? I can supply the cache > data > if you neded it. It's compiled on a Solaris10. Can you still reproduce this in any way? I found two bugs, would be nice to know if they solve it: http://hg.dovecot.org/dovecot-2.1/rev/2f848393f78e http://hg.dovecot.org/dovecot-2.1/rev/bded819417d9
Re: [Dovecot] NFS, deleting folder issue
Awesome, Thanks! Catalin Petrescu On Tue, Dec 18, 2012 at 2:16 PM, Timo Sirainen wrote: > On Wed, 2012-12-05 at 11:47 -0500, Catalin Petrescu wrote: > > > I use dovecot on a server with some Nightmare File Systerm (aka NFS) > > storage. > > When I delete a folder, its content gets deleted, but the folder itself > > does not. > .. > > So, the dovecot.index.log was deleted, but it's still open, and the > folder > > can't be deleted because of the pesky .nfs* file. > > Fixed: http://hg.dovecot.org/dovecot-2.1/rev/b53ab1c11843 > > >
Re: [Dovecot] SPECIAL-USE and mailbox names in various IMAP clients
On Wed, 2012-12-12 at 08:28 -0800, Bradley Giesbrecht wrote:
> On Dec 12, 2012, at 3:11 AM, Timo Sirainen wrote:
>
> > http://imapwiki.org/SpecialUse
> >
> > Please fill out for all clients with all languages you know of. Knowing the
> > mailbox names can be helpful with Dovecot's mailbox_alias plugin.
>
>
> Is there online documentation for testing an email clients support of
> SPECIAL-USE?
Create Dovecot configuration with:
mailbox testbox {
special_use = \Sent
auto = subscribe
}
Then see if the client saves a mail to "testbox" or to its
old/original/default "Sent".
Re: [Dovecot] Manually creating dovecot- files after isync/mbsync mirror
On Wed, 2012-12-12 at 11:00 +0200, Dale Gallagher wrote: > Hi everyone > > I'm using isync 1.0.5 patched to do recursive folder listing and mirroring > mail from an external party's IMAP server to a local Maildir, which will be > accessed by Dovecot 2.0.9. > > In order to prevent IMAP clients from re-downloading their mail, when > connecting to Dovecot, I'm busy writing a script to generate appropriate > dovecot-uidlist and dovecot-uidvalidity files, per Maildir. > > isync stores the uid in the filename, so that's extractable, per message, > and the uidvalidity and current max uid are stored in a file .uidvalidity, > in each Maildir. > > I've read the docs here: http://wiki2.dovecot.org/MailboxFormat/Maildir > > Regarding the dovecot-uidlist header (first line) - I've tried to search > for and figure out what exactly is meant by the "mailbox global uid" and > once I do, how to manually generate the 128 bit hex variation of it? Could > someone elaborate on this, please. > > How would omitting the global uid field, beginning with G, affect remote > clients' syncing of mail? Is this field mandatory? Not necessary. Dovecot will add it later if needed. > I also see that Dovecot's uidvalidity is of the form 4df8a4e2, whereas > isync uses an integer. I'd appreciate it if someone could elaborate on what > Dovecot uses and whether I can convert one to the other? dovecot-uidlist file isn't directly visible to IMAP client. The UIDVALIDITY is converted between hex and decimals as necessary.
Re: [Dovecot] Automatically Cleaning Kerberos Credential Cache Files
On Tue, 2012-12-11 at 19:13 -0800, Joseph Tam wrote: > Ben Morrow writes: > > > In any case, it's likely that the delivery process looks in the user's > > home directory even if delivery is to a separate mail spool, unless > > you've taken steps to prevent this. > > I can confirm this. I think the reason is that dovecot changes to the > user's home directory so that it has a place to dump core. This causes > problem for my setup since I user per-user NFS mounts, so a delivery to an > internal mailing list caused hundreds of NFS automounts. > > I patched this behaviour out, but there is probably a more elegant solution > (unset MAIL_STORAGE_SERVICE_FLAG_ENABLE_CORE_DUMPS? How?). If there is a home directory, Dovecot chdirs there. Maybe you can avoid returning a home directory? Of course that causes some other trouble then. A new mail_home_chdir=no setting would of course work, but kind of annoying to have such setting..
Re: [Dovecot] doveadm-lda - segfault
On Tue, 2012-12-11 at 23:15 +0100, Kamil Jońca wrote: > #0 0x7f99d591fe6f in mail_storage_try_copy (mail=0x198dbb0, > _ctx=0x7fff8914fc28) at mail-copy.c:56 > 56mail-copy.c: No such file or directory. raw-storage's envelope_sender is NULL. Fixed Dovecot to make sure NULL isn't returned: http://hg.dovecot.org/dovecot-2.1/rev/579984fdb6e5 But I think Pigeonhole also shouldn't set it to NULL. sieve-message.c:sieve_message_get_sender() apparently returns NULL if it can't find anything. Elsewhere this is used when nothing else is there: #define DEFAULT_ENVELOPE_SENDER "MAILER-DAEMON"
Re: [Dovecot] imap dumps core when connecting with mutt
On Sun, 2012-12-09 at 19:03 +0200, Arthur Titeica wrote: > Hello, > > I'm trying to investigate a problem with dovecot/imap dumping core when > connecting connecting mith mutt (everything else works). > > imap(user@domain): Fatal: master: service(imap): child 31752 killed with > signal 11 (core dumped) > > I managed to create a core file and passed that to gdb. The log is here [1]. > > I hope this helps - please tell me what else would be needed if not. First of all doveconf -n output would be helpful. The gdb backtrace would have been also a bit more useful with debug symbols.
Re: [Dovecot] Removing configured SSL certificate file from disk while Dovecot is running spams syslog
On Thu, 2012-12-06 at 18:13 +0900, Nils wrote: > [root@mikan ~]# dovecot --version > 2.1.12 > > When I remove the SSL certificate from disk while Dovecot is running, it > spams syslog with the following log message over and over: > > Dec 6 17:41:41 mikan dovecot: config: Fatal: Error in configuration > file /etc/dovecot/conf.d/10-ssl.conf line 12: ssl_cert: Can't open file > /etc/ssl/private/dovecot.pem: No such file or directory .. > Reporting that the certificate went away is fine and useful, but > spamming the syslog over and over with hundreds of entries per second(!) > is annoying. :( Fixed: http://hg.dovecot.org/dovecot-2.1/rev/bc11033ef035
Re: [Dovecot] Undeserved permissions error with g+s folder permissions
Am 18.12.2012 19:39, schrieb Timo Sirainen: > On Sat, 2012-12-01 at 10:59 -0500, tlhackque wrote: >> It contains a subdirectory: >> >> -rw-rw 1 thlackque mail 84805345 Dec 1 10:34 Vendors/AVendor >> >> If I try to rename the AVendor folder (client is Thunderbird 17.0), I >> get this error: >> >> Unable to rename across conflicting directory permisssions this is 660 which is simply wrong for a directrory in case of diretcories you need the excue flag means 770 signature.asc Description: OpenPGP digital signature
Re: [Dovecot] namespace subscription problem
On Fri, 2012-12-07 at 04:17 +0100, Holger Hegmanns wrote: > Hi all, > > my problem seems to be a cosmetic one (again). > > According to the docs: > > subscriptions: "yes" (default) if this namespace should handle its own > subscriptions. If "no", then the first parent namespace with > subscriptions=yes will handle it. > > Therefore is no way to create the following scenario: > > three namespaces (private, shared, public) > the private namespace has to handle its own subscriptions > the private namespace setup with "prefix = INBOX." > the both shared and public namespace setup with "subscriptions = no" > > cause there is no so called "parent" namespace. Private namespace setup > with "prefix = " works fine, but that's not what I want. First create all the namespaces you want and set subscriptions=no for all of them. Then create a new prefix="" namespace, and set it subscriptions=yes list=no hidden=yes.
Re: [Dovecot] During FTS reindexing, search commands unceremoniously exit
On Thu, 2012-12-06 at 12:31 -0500, Dave Abrahams wrote: > Is this intentional? Closing the connection without warning doesn't > seem like the best response... > > --8<---cut here---start->8--- > % printf "1 select \"INBOX\"\n2 search body quack\n3 logout\n" | > /opt/local/libexec/dovecot/imap > * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE > IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT > MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 > CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS > SPECIAL-USE SEARCH=FUZZY] Logged in as dave > * FLAGS (\Answered \Flagged \Deleted \Seen \Draft gnus-forward gnus-expire) > * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft gnus-forward > gnus-expire \*)] Flags permitted. > * 31 EXISTS > * 0 RECENT > * OK [UIDVALIDITY 1349969399] UIDs valid > * OK [UIDNEXT 1376] Predicted next UID > * OK [HIGHESTMODSEQ 2908] Highest > 1 OK [READ-WRITE] Select completed. > imap(dave): Info: Connection closed in=45 out=2027404 > % I think the problem is that SEARCH command returns to the main loop while it waits for the indexing to finish. The main loop then notices that the client has already disconnected. So that kind of piping of commands isn't very reliable. This probably works: (printf "1 select \"INBOX\"\n2 search body quack\n3 logout\n"; read) | /opt/local/libexec/dovecot/imap
Re: [Dovecot] Documentation of Redis and Memcache Backends
On Thu, 2012-12-06 at 14:46 +0100, Urban Loesch wrote: > Hi, > > in the release notes of 2.1.9 I read that dovecot supports memcache and redis > backends for > userdb/passdb authentication. This is very interesting for me and should > reduce queries and database load of > our mysql servers. > > My idea is to use memcache or redis in our IMAP/POP3 proxies in front of our > backend servers. > So I would like to try out if it's possible to store proxy information of our > backends. For > example the backend ip adress. > > But in the wiki I found only a few configuration settings for redis backend. > http://master.wiki2.dovecot.org/AuthDatabase/Dict That's all the Redis/memcached-specific configuration. Just make them return all the extra fields you want in the JSON values. You could for example put a passdb/userdb dict first and sql next. So requests are first tried from the dict and if that fails then from sql. > Also the mentioned example config file "dovecot-dict-auth.conf.ext" with full > list of configuration options > does not exits in the source of 2.1.11. Looks like it was missing from the Makefile. Will be in next version and you can also see it from: http://hg.dovecot.org/dovecot-2.1/file/tip/doc/example-config/dovecot-dict-auth.conf.ext
Re: [Dovecot] NFS, deleting folder issue
On Wed, 2012-12-05 at 11:47 -0500, Catalin Petrescu wrote: > I use dovecot on a server with some Nightmare File Systerm (aka NFS) > storage. > When I delete a folder, its content gets deleted, but the folder itself > does not. .. > So, the dovecot.index.log was deleted, but it's still open, and the folder > can't be deleted because of the pesky .nfs* file. Fixed: http://hg.dovecot.org/dovecot-2.1/rev/b53ab1c11843
Re: [Dovecot] Undeserved permissions error with g+s folder permissions
On 18-Dec-12 13:39, Timo Sirainen wrote: On Sat, 2012-12-01 at 10:59 -0500, tlhackque wrote: I have a (mbox/IMAP) directory under my mail directory with these permissions: drwxrws--- 4 tlhackque mail 4096 Dec 1 10:34 Vendors/ It contains a subdirectory: -rw-rw 1 thlackque mail 84805345 Dec 1 10:34 Vendors/AVendor If I try to rename the AVendor folder (client is Thunderbird 17.0), I get this error: Unable to rename across conflicting directory permisssions If I chmod g-s Vendors, the RENAME command succeeds. Where are you renaming it to and what permissions that directory has? I can't seem to easily reproduce this. Thanks for looking at this! Here it is from the top with every step from creating the subfolder thru the fail to success without -s, reproduced today: On the server, in my ~mail directory: | ||ls -ld Vendors drwxrws--- 4 tlhackque mail 4096 Dec 18 13:56 Vendors/ ls -ld Vendors/Test ls: Vendors/Test: No such file or directory Right-click on Vendors in TB New Folder Test Subfolder of Vendors [Server restricts] x Messages only Create ls -ld Vendors/Test -rw-rw 1 tlhackque mail 0 Dec 18 13:58 Vendors/Test Right click on Test Rename Test Rename RENAME Brief pop-up with this text; retrieved from the TB Activity manager window: The current command did not succeed. The mail server for account (tlhackque) responded: [CANNOT} Renaming not supported across conflicting directory permissions. chmod g-s Vendors; ls -ld Vendors drwxrwx--- 4 tlhackque mail 4096 Dec 18 13:58 Vendors Right click on Test Rename Test Rename RENAME Succeeds | dovecot --version 2.1.10 Thunderbird 17.0 OS: cat /proc/sys/kernel/osrelease 2.6.22.14-72.fc6 SELinux is enabled, there are no errors in the log. -- This communication may not represent my employer's views, if any, on the matters discussed.
Re: [Dovecot] Error: unlink_directory(.../lucene-indexes) with doveadm index
> -Original Message- > From: dovecot-boun...@dovecot.org [mailto:dovecot-boun...@dovecot.org] > On Behalf Of Timo Sirainen > Sent: Tuesday, December 18, 2012 12:52 PM > To: Fred Kilbourn > Cc: dovecot@dovecot.org > Subject: Re: [Dovecot] Error: unlink_directory(.../lucene-indexes) with > doveadm index > > On Wed, 2012-12-05 at 05:08 -0600, Fred Kilbourn wrote: > > I am updating search indexes on all my mailboxes via a nightly cronjob > that > > runs: doveadm index -A '*' > > > > The problem we're running into is that random mailboxes will throw the > > following error during the update (sanitized to conceal actual domain > name): > > > > doveadm(u...@domain.com): Error: > > unlink_directory(/var/spool/mail/domain.com/user/sdbox/lucene-indexes) > > failed: Permission denied > > > > We have around 250 domains on the server, with a handful of mailboxes > on > > average in each domain. We get this for a varying number of total > mailboxes > > (1 to 6 every night). It is common for the same mailbox to show up a > few > > days in a row and then stop throwing the error. The script is running > as > > root, so there shouldn't be any file level permissions. > > Try if this works: doveadm index -A -q '*' > > This way the indexing is done by indexer processes with proper > permissions. Although I wonder if it floods the indexer processes too > quickly with the commands if there are a lot of users.. Okay I'll give that a try. I don't see that option anywhere in the documentation, but I do see it in the source so I'll see what happens. Thanks.
Re: [Dovecot] Error: unlink_directory(.../lucene-indexes) with doveadm index
On Wed, 2012-12-05 at 05:08 -0600, Fred Kilbourn wrote: > I am updating search indexes on all my mailboxes via a nightly cronjob that > runs: doveadm index -A '*' > > The problem we're running into is that random mailboxes will throw the > following error during the update (sanitized to conceal actual domain name): > > doveadm(u...@domain.com): Error: > unlink_directory(/var/spool/mail/domain.com/user/sdbox/lucene-indexes) > failed: Permission denied > > We have around 250 domains on the server, with a handful of mailboxes on > average in each domain. We get this for a varying number of total mailboxes > (1 to 6 every night). It is common for the same mailbox to show up a few > days in a row and then stop throwing the error. The script is running as > root, so there shouldn't be any file level permissions. Try if this works: doveadm index -A -q '*' This way the indexing is done by indexer processes with proper permissions. Although I wonder if it floods the indexer processes too quickly with the commands if there are a lot of users..
Re: [Dovecot] indexer-worker Panic
On Tue, 2012-12-04 at 13:26 -0500, Dave Abrahams wrote: > I just found this in my logs. Any idea? > > --8<---cut here---start->8--- > 12/4/12 12:33:43.831 PM dovecot[2660]: indexer-worker(dave): Panic: file > mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: > (mailbox_list_is_valid_pattern(_list, name)) > 12/4/12 12:33:43.831 PM dovecot[2660]: indexer-worker(dave): Error: Raw > backtrace: 2 libdovecot.0.dylib 0x00010840e6c4 > default_fatal_finish + 36 -> 3 libdovecot.0.dylib > 0x00010840f3e1 i_internal_fatal_handler + 49 -> 4 libdovecot.0.dylib > 0x00010840e98e i_panic + 158 -> 5 > libdovecot-storage.0.dylib 0x000108340693 fs_list_get_path + 467 > -> 6 indexer-worker 0x0001082e7341 > master_connection_input + 513 -> 7 libdovecot.0.dylib > 0x00010841b5 > 12/4/12 12:33:43.831 PM dovecot[2660]: indexer-worker(dave): Error: ce > io_loop_call_io + 46 -> 8 libdovecot.0.dylib > 0x00010841c737 io_loop_handler_run + 215 -> 9 libdovecot.0.dylib > 0x00010841b7e8 io_loop_run + 88 -> 10 libdovecot.0.dylib >0x0001084079c8 master_service_run + 24 -> 11 indexer-worker >0x0001082e7001 main + 321 -> 12 libdyld.dylib > 0x7fff93d117e1 start + 0 -> 13 ??? > 0x0001 0x0 + 1 Fixed: http://hg.dovecot.org/dovecot-2.1/rev/04704d1eb6c3
Re: [Dovecot] Undeserved permissions error with g+s folder permissions
On Sat, 2012-12-01 at 10:59 -0500, tlhackque wrote: > I have a (mbox/IMAP) directory under my mail directory with these > permissions: > > drwxrws--- 4 tlhackque mail 4096 Dec 1 10:34 Vendors/ > > It contains a subdirectory: > > -rw-rw 1 thlackque mail 84805345 Dec 1 10:34 Vendors/AVendor > > If I try to rename the AVendor folder (client is Thunderbird 17.0), I > get this error: > > Unable to rename across conflicting directory permisssions > > If I chmod g-s Vendors, the RENAME command succeeds. Where are you renaming it to and what permissions that directory has? I can't seem to easily reproduce this.
Re: [Dovecot] Too many imap connections in state "idling"
On 18.12.2012, at 18.48, 3.lis...@adminlinux.com.br wrote: > root@server:~# ps aux |grep imap |grep idling > dovemail 1141 0.0 0.0 16836 2148 ?DDec15 0:01 > dovecot/imap [idling] > dovemail 3375 0.0 0.0 16828 2120 ?D15:48 0:00 > dovecot/imap [idling] > dovemail 4833 0.0 0.0 16828 2212 ?D15:49 0:00 > dovecot/imap [idling] > … "D" state means they're hanging in kernel. Can you look with gdb and strace what they're doing? gdb -p 1141 bt full strace -tt -p 1141
Re: [Dovecot] Too many imap connections in state "idling"
Thanks Steffen Kaiser ! I think not. The server is currently always 60% of imap processes in state "idling". IDLE processes are like this: root@server:/root# ps aux |grep imap dovemail617 0.0 0.0 23136 2260 ?SDec15 0:01 dovecot/imap [Username1 IP1 IDLE] dovemail677 0.0 0.0 23104 2172 ?SDec15 0:01 dovecot/imap [Username2 IP2 IDLE] ... My "idling" processes are seen as follows: root@server:~# ps aux |grep imap |grep idling dovemail 1141 0.0 0.0 16836 2148 ?DDec15 0:01 dovecot/imap [idling] dovemail 3375 0.0 0.0 16828 2120 ?D15:48 0:00 dovecot/imap [idling] dovemail 4833 0.0 0.0 16828 2212 ?D15:49 0:00 dovecot/imap [idling] ... Thanks! -- Thiago Henrique www.adminlinux.com.br On 14-12-2012 06:40, Steffen Kaiser wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 13 Dec 2012, 3.lis...@adminlinux.com.br wrote: Is it normal this large amount of connections in state 'idling' ? If they actually using the "IDLE" command to wait for PUSH mails on much more folders than on the other server? Regards, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUMrmFmoxLS8a3A9mAQKmjgf/RbVzZet2+PUDQpMkrquB8zURR+WaBpxa OCnNahjCV3kkuyLSciU8cq54vQhfPEXoyeqoQric/QmMOIZwhaVclLGpnSGa6lGR fjk6x1PgcUDpqncktTJ+aUuJYTiigQbZ1wLWUfCHNZMXx5smReUMV+IdYV/0UH2a NCnQMX7+FfUWOfZdU6QbomgTXAEgjUD+YRo0JqQ6ja/ELWfbUrYAXwhGXAXyskJT 0eygy3FSEBJQMaIO+o5Dco7AbaCGs19xRagZWGZV5/1j17dHqOHwLdp8MnO4wCI8 4IPzuTUbAY0gnCEJLcSYmQG1FzNi5SjPfMV/dypB7wcPdIx4rIzsww== =OQSw -END PGP SIGNATURE-
[Dovecot] Advice on sieve vacation for aliases
Greetings,
I have a working mail server with sieve 1:1.2.9-1ubuntu6.5 working just
fine. My commercial dept. has asked me to set a vacation message for
comerc...@domain.tld, but this is an alias to j...@domain.tld and
meg...@domain.tld. I have created a sieve_global_path =
/etc/dovecot/global.sieve and it works, but not the intended way: it
sends two vacation messages, each From: each employee, and not From:
comerc...@domain.tld alias.
Is there how to make dovecot send only one vacation message From:
comerc...@domain.tld or will I have to survive with one message from
jhon and another from meggie? Also, is there how to have a
dovecot.lda-dupes for the alias instead the users?
/etc/dovecot/global.sieve:
require ["vacation"];
# rule:[Ferias coletivas]
if anyof (header :contains "To" "comerc...@domain.tld")
{
vacation :days 7 :subject "Férias coletivas de 20/12/2012 a
07/01/2013" text:
bla bla bla.
;
stop;
}
Thanks in advance and nice holidays.
--
Marcio Merlone
Re: [Dovecot] Non-dovecot user looking for feedback
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 18 Dec 2012, Chris Ross wrote: I did used UW-imap until it gave lots of problems, because of mbox-Format located in user's home folders. It also seemed to become problematic in point of performance, because some users keep any message. Then I migrated to Courier. Maildir solved one and another problem. Then I migrated to Dovecot, which I had no larger trouble with, once setup and running. Sieve works well and other plugins very useful, too! Is there some "give me all the details to read through" document somewhere? What it does, it's capabilities, and how it does things? http://wiki2.dovecot.org/ http://wiki2.dovecot.org/DovecotFeatures http://wiki2.dovecot.org/MailboxFormat http://wiki2.dovecot.org/Pigeonhole/Sieve - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUNA3JmoxLS8a3A9mAQLOkwgAoLctclnBCwAohYxbgsEdf/DGGsM9t5Kl Qo4U3Y9+vjnblvFyvYtOc7bxzhx8MKzTZfBOXWs7m8eJgwPkg1WK9HJhtv32uZ8G +t6/2hZARR8hzqzIYu2+S2/Df7oVpR5cwoxzrIZ1ctoF0GrWKZDkeez5Z+z6bFSt kXm2rHYcGwJSi0VDO3ZInSmty97/bvi7dg1AXcyZ5MEIBCwmXFV/6XNV0XlS2DMa 3SAGbCZQiIBvmvvbn9q7HNMQmMtZeonaHJ7e12XBkOU3FrTAdLBbHkB3CfAg8TiN hTdrX97+6EELLoiEMUMAbysbeEr1xemXmHXk9EJD/DedbMLoWeYHsw== =a0jl -END PGP SIGNATURE-
