[Dovecot] Proxying, pertinent values and features, SNI
Hello, I'm looking into deploying dovecot as a proxy, currently using perdition. Have been using dovecot on the actual servers for years, nearly a decade. So far just 1.x, but for the proxy it will have to be 2.x (2.1.7 is the current Debian version), as the trigger for this change is the need to support multiple SSL certificates. All that happens on the proxy seems to be handled by the login processes, so that is why we're not seeing anything useful in the process titles or with doveadm, right? And from past comments by Timo I guess that adding such functionality isn't on his to-do list at all. A configurable capabilities string for POP would be quite welcome, but at least nothing is different between the 1.x backends and the 2.x proxy in that protocol. Speaking of 1.x versus 2.x, the feature to pass on the remote IP from the proxy to the backend is a 2.x thing only, correct? So I suppose any parameters really affecting this setup are default_process_limit and default_client_limit as well as the settings in service-imap-login and service pop-login. In particular mail_max_userip_connections never is looked at on the proxy as this check happens in the respective protocol AFTER login, rite? I presume to best support all(?) clients out there is to have "local_name" sections for SNI first and then "local" sections for IP address based certs. It is my understanding that SNI needs to be requested by the client, so aside from client bugs (nah, those don't exist ^o^) every client should get an appropriate response for TLS. Has anybody done a setup like that already? Regards, Christian -- Christian BalzerNetwork/Systems Engineer ch...@gol.com Global OnLine Japan/Fusion Communications http://www.gol.com/
Re: [Dovecot] Separate log file for Sieve
On 03/31/13 14:43, Stephan Bosch wrote: Op 3/31/2013 10:34 AM, Timo Sirainen schreef: On 27.3.2013, at 16.57, Ewald Dieterich wrote: Is it possible to configure a separate log file for Sieve? No, unless you use some syslog feature. There are some plans to reduce the number of errors that Sieve logs though. Some of which is already implemented, but still pending release. I merged with the trunk and like the changes you did, thanks! Ewald
[Dovecot] Sieve vacation issue - Dovecot + Postfix + LDA
Hi to all,
I have an issue with Dovecot Sieve on sending vacation message... Actually
Sieve is working and I can use all the filters but just vacation is causing
a problem and only in specific case...
I have Dovecot + Postfix + LDA running on Ubuntu 11 without MySql database
for users but I'm using virtusertable instead. The problem is when linux
user ( mail user ) is different from mail allias in virtusertable...
Example: i...@domain.com > ivan1 ( from virtusertable ).
When alias and user are the same sieve vacation works just fine but when
it's not the sieve script collects the user(ivan1)@domain.com in from
instead i...@domain.com and this is when mail log shows like "discarded
message because of implicitily no known envelope in message header etc...
Is there a way to adjust sieve to pickup the recipient address from mail
header or whatever and not to collect the user...?
I was trying to play with postfix master.cf using dovecot-lda switches -f
${sender} -a (or -d ) ${recipient} but without success...
Did anyone had this kind of problem? I would really appreciate some hints
on fixing this issue...
Thanks,
Ivan
Re: [Dovecot] Sieve vacation issue - Dovecot + Postfix + LDA
On 4/3/2013 11:49 AM, Ivan Bogdanovic wrote:
Hi to all,
I have an issue with Dovecot Sieve on sending vacation message... Actually
Sieve is working and I can use all the filters but just vacation is causing
a problem and only in specific case...
I have Dovecot + Postfix + LDA running on Ubuntu 11 without MySql database
for users but I'm using virtusertable instead. The problem is when linux
user ( mail user ) is different from mail allias in virtusertable...
Example: i...@domain.com > ivan1 ( from virtusertable ).
When alias and user are the same sieve vacation works just fine but when
it's not the sieve script collects the user(ivan1)@domain.com in from
instead i...@domain.com and this is when mail log shows like "discarded
message because of implicitily no known envelope in message header etc...
Is there a way to adjust sieve to pickup the recipient address from mail
header or whatever and not to collect the user...?
I was trying to play with postfix master.cf using dovecot-lda switches -f
${sender} -a (or -d ) ${recipient} but without success...
Did anyone had this kind of problem? I would really appreciate some hints
on fixing this issue...
With a recent enough Pigeonhole you can try using the original recipient:
http://hg.rename-it.nl/dovecot-2.1-pigeonhole/raw-file/tip/doc/extensions/vacation.txt
http://wiki2.dovecot.org/LDA#Parameters (-a and -r)
Regards,
Stephan.
Re: [Dovecot] Proxying, pertinent values and features, SNI
Hi I presume to best support all(?) clients out there is to have "local_name" sections for SNI first and then "local" sections for IP address based certs. It is my understanding that SNI needs to be requested by the client, so aside from client bugs (nah, those don't exist ^o^) every client should get an appropriate response for TLS. Has anybody done a setup like that already? Although not what you asked for, just so you are aware, Godaddy (boo hiss, etc) offer reasonably inexpensive multi subject alt name based certs. This means you can have a single cert which is valid for lots of completely different domain names. The mild benefit is that this doesn't require SNI support for SSL (which I'm unsure is supported by many mail clients?) Although it's more expensive, I think it's a good solution (I'm using it for a small 5 domain installation) Good luck Ed W
Re: [Dovecot] sieve-filter ignoring separator
On 3/22/2013 3:17 PM, isakrubin wrote: Stephan Bosch-2 wrote On 3/4/2013 9:21 PM, Isak Rubin wrote: # dovecot --version 2.1.9 This Dovecot is very old, so is probably your Pigeonhole version. Recent versions should work fine in this regard. Regards, Stephan. Upgraded to # dovecot --version 2.2.rc3 still same issue :/ Could you show me your `dovecot -n` output? Regards, Stephan.
Re: [Dovecot] Outlook 2013 - mounting folders with XLIST
On Sun, 2013-03-31 at 17:40 +0300, Timo Sirainen wrote: > > namespace/inbox/mailbox=hallohallo^Atnamespace/inbox/mailbox/hallohallo/auto=subscribe > > same line occurs when querying ...userdb_import as userdb_import... in > place of ...userdb_import as userdb_userdb_import. http://hg.dovecot.org/dovecot-2.1/rev/cd919c490ea6 makes userdb_userdb_import work. Ugh. Not really. OK, latest v2.1 hg has passdb_import, userdb_import and userdb_userdb_import and they all work. In addition, here's a list of settings that are required for adding two new mailboxes without them being in the configuration: /usr/local/libexec/dovecot/imap -o 'namespace/inbox/mailbox=foo bar' -o namespace/inbox/mailbox/foo/name=foo -o namespace/inbox/mailbox/bar/name=bar -o namespace/inbox/mailbox/foo/auto=create -o namespace/inbox/mailbox/bar/auto=create -o namespace/inbox/mailbox/foo/special_use=\\sent -o namespace/inbox/mailbox/bar/special_use=\\drafts That way you can easily test them. They work just the same (without -o parameter of course) in userdb_import. thanks, this is working. now it is possible to let the single user choose his favorite foldernames if client is not very helpful. it results in some more configuration, but is helpful in some situations. but i only achieved this without userdb prefetching. latest patch i added latest patch http://hg.dovecot.org/dovecot-2.1/rev/cd919c490ea6 is included this is the old combined query: password_query = SELECT `inbox` as `user`, `password`, `home` as userdb_home, `uid` AS userdb_uid, `gid` AS userdb_gid,userdb_import AS userdb_userdb_import FROM `mail_users` WHERE `login` = '%u' AND `active`='Y' i had to edit the conf and split this query into user and pwd query to make it work password_query = SELECT `inbox` as `user`, `password` FROM `mail_users` WHERE `login` = '%u' AND `active`='Y' user_query = SELECT `inbox` as `user`, `password`, `home`, `uid`, `gid`, userdb_import FROM `mail_users` WHERE `login` = '%u' AND `active`='Y' i would like to save one query at loginprocess, but its not existentially needed. Thanks, Hajo
Re: [Dovecot] sieve-filter ignoring separator
Here you go, http://pastebin.com/LA0kJteM Regards, Isak 2013/4/3 Stephan Bosch > On 3/22/2013 3:17 PM, isakrubin wrote: > >> Stephan Bosch-2 wrote >> >>> On 3/4/2013 9:21 PM, Isak Rubin wrote: >>> # dovecot --version 2.1.9 >>> This Dovecot is very old, so is probably your Pigeonhole version. Recent >>> versions should work fine in this regard. >>> >>> Regards, >>> >>> Stephan. >>> >> Upgraded to >> # dovecot --version >> 2.2.rc3 >> >> >> still same issue :/ >> > > Could you show me your `dovecot -n` output? > > Regards, > > Stephan. >
Re: [Dovecot] sieve-filter ignoring separator
Op 4/3/2013 1:56 PM, Isak Rubin schreef:
Here you go
You're using the listescape plugin. Try putting that in the global
mail_plugins setting, e.g.:
# usually located in /etc/dovecot/conf.d/10-mail.conf
mail_plugins = listescape
protocol lda {
mail_plugins = $mail_plugins sieve autocreate
}
protocol imap {
mail_plugins = $mail_plugins autocreate
}
Regards,
Stephan.
Re: [Dovecot] sieve-filter ignoring separator
Thanks :)
Solved the filtering problem
but got a new problem.
Filtering now works as expected, but only to existing folders.
I tried moving the autocreate plugin to a global level but still does not
seem to work.
http://pastebin.com/ykvWQg3w
Regards
Isak
2013/4/3 Stephan Bosch
> Op 4/3/2013 1:56 PM, Isak Rubin schreef:
>
>> Here you go
>>
>
> You're using the listescape plugin. Try putting that in the global
> mail_plugins setting, e.g.:
>
> # usually located in /etc/dovecot/conf.d/10-mail.**conf
> mail_plugins = listescape
>
> protocol lda {
> mail_plugins = $mail_plugins sieve autocreate
> }
> protocol imap {
> mail_plugins = $mail_plugins autocreate
> }
>
>
> Regards,
>
> Stephan.
>
Re: [Dovecot] sieve-filter ignoring separator
Am 03.04.2013 14:40, schrieb Isak Rubin:
> Thanks :)
> Solved the filtering problem
>
> but got a new problem.
>
> Filtering now works as expected, but only to existing folders.
>
> I tried moving the autocreate plugin to a global level but still does not
> seem to work.
>
>
> http://pastebin.com/ykvWQg3w
>
>
>
> Regards
> Isak
>
die you use
fileinto :create in the sieve rule ?
what is lda_mailbox_autocreate set ?
else read i.e
http://wiki2.dovecot.org/LDA
-m : Destination mailbox (default is INBOX). If the mailbox
doesn't exist, it will not be created (unless the lda_mailbox_autocreate
setting is set to yes). If message couldn't be saved to the mailbox for
any reason, it's delivered to INBOX instead.
If Sieve plugin is used, this mailbox is used as the "keep" action's
mailbox. It's also used if there is no Sieve script or if the script
fails for some reason.
Deliveries to namespace prefix will result in saving the mail to
INBOX instead. For example if you have "Mail/" namespace, this allows
you to specify dovecot-lda -m Mail/$mailbox where mail is stored to
Mail/$mailbox or to INBOX if $mailbox is empty.
The mailbox name is specified the same as it's visible in IMAP
client. For example if you've a Maildir with .box.sub/ directory and
your namespace configuration is prefix=INBOX/, separator=/, the correct
way to deliver mail there is to use -m INBOX/box/sub
>
>
>
> 2013/4/3 Stephan Bosch
>
>> Op 4/3/2013 1:56 PM, Isak Rubin schreef:
>>
>>> Here you go
>>>
>>
>> You're using the listescape plugin. Try putting that in the global
>> mail_plugins setting, e.g.:
>>
>> # usually located in /etc/dovecot/conf.d/10-mail.**conf
>> mail_plugins = listescape
>>
>> protocol lda {
>> mail_plugins = $mail_plugins sieve autocreate
>> }
>> protocol imap {
>> mail_plugins = $mail_plugins autocreate
>> }
>>
>>
>> Regards,
>>
>> Stephan.
>>
>
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
Re: [Dovecot] sieve-filter ignoring separator
# egrep -rn lda_mailbox_autocreate /etc/dovecot/conf.d/
/etc/dovecot/conf.d/15-lda.conf:41:lda_mailbox_autocreate = yes
if header :regex "From" "([a-zA-Z0-9._%+-]+)(@)([a-zA-Z0-9._%+-]+)" {
set :lower "person" "${1}";
set :lower "domain" "${3}";
fileinto "INBOX/bydomain/${domain}/${person}";
stop;
}
Robert: Autocreate works fine using lda, the issue here is when running
sieve filters manually using sieve-filter
When receiving mails they are sorted and created and everything works fine,
but I need to be able to manually execute sieve scripts on some folders,
and that's when it seems unable to autocreate.
But i guess lda_mailbox_autocreate is not used at all when running
sieve-filter manually, as i assume it just bypass the lda all together
Regards
Isak
2013/4/3 Robert Schetterer
> Am 03.04.2013 14:40, schrieb Isak Rubin:
> > Thanks :)
> > Solved the filtering problem
> >
> > but got a new problem.
> >
> > Filtering now works as expected, but only to existing folders.
> >
> > I tried moving the autocreate plugin to a global level but still does not
> > seem to work.
> >
> >
> > http://pastebin.com/ykvWQg3w
> >
> >
> >
> > Regards
> > Isak
> >
>
> die you use
>
> fileinto :create in the sieve rule ?
>
> what is lda_mailbox_autocreate set ?
>
> else read i.e
>
> http://wiki2.dovecot.org/LDA
>
> -m : Destination mailbox (default is INBOX). If the mailbox
> doesn't exist, it will not be created (unless the lda_mailbox_autocreate
> setting is set to yes). If message couldn't be saved to the mailbox for
> any reason, it's delivered to INBOX instead.
>
> If Sieve plugin is used, this mailbox is used as the "keep" action's
> mailbox. It's also used if there is no Sieve script or if the script
> fails for some reason.
>
> Deliveries to namespace prefix will result in saving the mail to
> INBOX instead. For example if you have "Mail/" namespace, this allows
> you to specify dovecot-lda -m Mail/$mailbox where mail is stored to
> Mail/$mailbox or to INBOX if $mailbox is empty.
>
> The mailbox name is specified the same as it's visible in IMAP
> client. For example if you've a Maildir with .box.sub/ directory and
> your namespace configuration is prefix=INBOX/, separator=/, the correct
> way to deliver mail there is to use -m INBOX/box/sub
>
>
> >
> >
> >
> > 2013/4/3 Stephan Bosch
> >
> >> Op 4/3/2013 1:56 PM, Isak Rubin schreef:
> >>
> >>> Here you go
> >>>
> >>
> >> You're using the listescape plugin. Try putting that in the global
> >> mail_plugins setting, e.g.:
> >>
> >> # usually located in /etc/dovecot/conf.d/10-mail.**conf
> >> mail_plugins = listescape
> >>
> >> protocol lda {
> >> mail_plugins = $mail_plugins sieve autocreate
> >> }
> >> protocol imap {
> >> mail_plugins = $mail_plugins autocreate
> >> }
> >>
> >>
> >> Regards,
> >>
> >> Stephan.
> >>
> >
>
>
>
> 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
>
Re: [Dovecot] sieve-filter ignoring separator
Am 03.04.2013 14:59, schrieb Isak Rubin:
> # egrep -rn lda_mailbox_autocreate /etc/dovecot/conf.d/
> /etc/dovecot/conf.d/15-lda.conf:41:lda_mailbox_autocreate = yes
>
> if header :regex "From" "([a-zA-Z0-9._%+-]+)(@)([a-zA-Z0-9._%+-]+)" {
> set :lower "person" "${1}";
> set :lower "domain" "${3}";
> fileinto "INBOX/bydomain/${domain}/${person}";
> stop;
> }
>
> Robert: Autocreate works fine using lda, the issue here is when running
> sieve filters manually using sieve-filter
> When receiving mails they are sorted and created and everything works fine,
> but I need to be able to manually execute sieve scripts on some folders,
> and that's when it seems unable to autocreate.
>
> But i guess lda_mailbox_autocreate is not used at all when running
> sieve-filter manually, as i assume it just bypass the lda all together
>
try fileinto :create .
http://wiki2.dovecot.org/Pigeonhole/Sieve/Examples
i.e like
require ["variables","date","fileinto","mailbox"];
# Extract date info
if currentdate :matches "year" "*" { set "year" "${1}"; }
if currentdate :matches "month" "*" { set "month" "${1}"; }
# Archive Dovecot mailing list items by year and month.
# Create folder when it does not exist.
if header :is "list-id" "dovecot.dovecot.org" {
fileinto :create "INBOX.Lists.${year}.${month}.dovecot";
}
>
> Regards
> Isak
>
>
>
> 2013/4/3 Robert Schetterer
>
>> Am 03.04.2013 14:40, schrieb Isak Rubin:
>>> Thanks :)
>>> Solved the filtering problem
>>>
>>> but got a new problem.
>>>
>>> Filtering now works as expected, but only to existing folders.
>>>
>>> I tried moving the autocreate plugin to a global level but still does not
>>> seem to work.
>>>
>>>
>>> http://pastebin.com/ykvWQg3w
>>>
>>>
>>>
>>> Regards
>>> Isak
>>>
>>
>> die you use
>>
>> fileinto :create in the sieve rule ?
>>
>> what is lda_mailbox_autocreate set ?
>>
>> else read i.e
>>
>> http://wiki2.dovecot.org/LDA
>>
>> -m : Destination mailbox (default is INBOX). If the mailbox
>> doesn't exist, it will not be created (unless the lda_mailbox_autocreate
>> setting is set to yes). If message couldn't be saved to the mailbox for
>> any reason, it's delivered to INBOX instead.
>>
>> If Sieve plugin is used, this mailbox is used as the "keep" action's
>> mailbox. It's also used if there is no Sieve script or if the script
>> fails for some reason.
>>
>> Deliveries to namespace prefix will result in saving the mail to
>> INBOX instead. For example if you have "Mail/" namespace, this allows
>> you to specify dovecot-lda -m Mail/$mailbox where mail is stored to
>> Mail/$mailbox or to INBOX if $mailbox is empty.
>>
>> The mailbox name is specified the same as it's visible in IMAP
>> client. For example if you've a Maildir with .box.sub/ directory and
>> your namespace configuration is prefix=INBOX/, separator=/, the correct
>> way to deliver mail there is to use -m INBOX/box/sub
>>
>>
>>>
>>>
>>>
>>> 2013/4/3 Stephan Bosch
>>>
Op 4/3/2013 1:56 PM, Isak Rubin schreef:
> Here you go
>
You're using the listescape plugin. Try putting that in the global
mail_plugins setting, e.g.:
# usually located in /etc/dovecot/conf.d/10-mail.**conf
mail_plugins = listescape
protocol lda {
mail_plugins = $mail_plugins sieve autocreate
}
protocol imap {
mail_plugins = $mail_plugins autocreate
}
Regards,
Stephan.
>>>
>>
>>
>>
>> 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
>>
>
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
Re: [Dovecot] Mongo backend for userdb and passdb
On 20 March 2013 10:59, Damien Churchill wrote:
> On 20 March 2013 10:54, Timo Sirainen wrote:
> > On Wed, 2013-03-20 at 10:40 +, Damien Churchill wrote:
> >> On 20 March 2013 10:39, Timo Sirainen wrote:
> >> > On Wed, 2013-03-20 at 10:29 +, Damien Churchill wrote:
> >> >
> >> >> I've been messing about with this and I think a similar configuration
> >> >> format to the sql dict driver would be handy, although I imagine the
> >> >> same could also be achieved with just lots of uri arguments. Mongo
> >> >> isn't really a key/value store so you'd want to be able to specify
> >> >> fields within the document to query upon/fetch.
> >> >>
> >> >> I'm still getting to grips with the architecture of things so not
> >> >> entirely sure what the best course of action would be here. If using
> >> >> the map style config would be desirable then creating some shared
> >> >> parser that sql and mongodb can use would be good.
> >> >
> >> > I've been planning on having one generic dict sql-like configuration
> for
> >> > all dict backends, so you could map different dict paths to different
> >> > backends. So the idea is good, but probably quite a lot of work.
> >> >
> >>
> >> Would it not be just some bastardised version of dict-sql-settings?
> >
> > I guess you could do that for now. The grand plans of how to put
> > everything nicely together can wait. :)
> >
>
> For now I think I can get away with just tacking on uri arguments.
> Seems silly duplicating effort, although if you'd like me to give it a
> shot I'm happy to do so!
>
Hi,
I've pushed an initial copy of what I've got so far to bitbucket[0]. I'm in
two minds currently about how to correctly handle returning the json object
that the userdb/passdb backend expects. Currently the config file is
copying mostly what dict-sql does:
connect = host=localhost:port=27017:db=mail
map {
pattern= shared/passdb/$user
collection = users
username_field = email
value_field= password
fields {
email = $user
}
}
map {
pattern= shared/userdb/$user
collection = users
username_field = email
value_field= password
fields {
email = $user
}
values {
home = /home/vmail
uid = 5000
gid = 5000
}
}
value_field isn't currently used at all, and the values map just provides
some default values that will be replaced if they exist in the returned
document.
The part I'm wondering is how to allow the object you end returning as
flexible as what is currently possible with the sql passdb/userdb queries.
May have to ultimately bite the bullet and accept that it won't be.
Primarily it would be good to be able to concat strings with fields
returned for building the quota rule or something similar. Just wondered
what your thoughts were on this?
[0]
https://bitbucket.org/damoxc/dovecot-2.2-mongodb/commits/0dee37209ff9f4b2f84979beb29a1315a0ba00a9
Re: [Dovecot] sieve-filter ignoring separator
Thanks!
I had :create on 90% of the filters but it was missing on a few, added it
on the rest and now everything is working perfectly.
Thanks a lot for the help
Regards
Isak
2013/4/3 Robert Schetterer
> Am 03.04.2013 14:59, schrieb Isak Rubin:
> > # egrep -rn lda_mailbox_autocreate /etc/dovecot/conf.d/
> > /etc/dovecot/conf.d/15-lda.conf:41:lda_mailbox_autocreate = yes
> >
> > if header :regex "From" "([a-zA-Z0-9._%+-]+)(@)([a-zA-Z0-9._%+-]+)" {
> > set :lower "person" "${1}";
> > set :lower "domain" "${3}";
> > fileinto "INBOX/bydomain/${domain}/${person}";
> > stop;
> > }
> >
> > Robert: Autocreate works fine using lda, the issue here is when running
> > sieve filters manually using sieve-filter
> > When receiving mails they are sorted and created and everything works
> fine,
> > but I need to be able to manually execute sieve scripts on some folders,
> > and that's when it seems unable to autocreate.
> >
> > But i guess lda_mailbox_autocreate is not used at all when running
> > sieve-filter manually, as i assume it just bypass the lda all together
> >
>
>
> try fileinto :create .
>
> http://wiki2.dovecot.org/Pigeonhole/Sieve/Examples
>
> i.e like
>
> require ["variables","date","fileinto","mailbox"];
>
> # Extract date info
> if currentdate :matches "year" "*" { set "year" "${1}"; }
> if currentdate :matches "month" "*" { set "month" "${1}"; }
>
> # Archive Dovecot mailing list items by year and month.
> # Create folder when it does not exist.
> if header :is "list-id" "dovecot.dovecot.org" {
> fileinto :create "INBOX.Lists.${year}.${month}.dovecot";
> }
>
> >
> > Regards
> > Isak
> >
> >
> >
> > 2013/4/3 Robert Schetterer
> >
> >> Am 03.04.2013 14:40, schrieb Isak Rubin:
> >>> Thanks :)
> >>> Solved the filtering problem
> >>>
> >>> but got a new problem.
> >>>
> >>> Filtering now works as expected, but only to existing folders.
> >>>
> >>> I tried moving the autocreate plugin to a global level but still does
> not
> >>> seem to work.
> >>>
> >>>
> >>> http://pastebin.com/ykvWQg3w
> >>>
> >>>
> >>>
> >>> Regards
> >>> Isak
> >>>
> >>
> >> die you use
> >>
> >> fileinto :create in the sieve rule ?
> >>
> >> what is lda_mailbox_autocreate set ?
> >>
> >> else read i.e
> >>
> >> http://wiki2.dovecot.org/LDA
> >>
> >> -m : Destination mailbox (default is INBOX). If the mailbox
> >> doesn't exist, it will not be created (unless the lda_mailbox_autocreate
> >> setting is set to yes). If message couldn't be saved to the mailbox for
> >> any reason, it's delivered to INBOX instead.
> >>
> >> If Sieve plugin is used, this mailbox is used as the "keep" action's
> >> mailbox. It's also used if there is no Sieve script or if the script
> >> fails for some reason.
> >>
> >> Deliveries to namespace prefix will result in saving the mail to
> >> INBOX instead. For example if you have "Mail/" namespace, this allows
> >> you to specify dovecot-lda -m Mail/$mailbox where mail is stored to
> >> Mail/$mailbox or to INBOX if $mailbox is empty.
> >>
> >> The mailbox name is specified the same as it's visible in IMAP
> >> client. For example if you've a Maildir with .box.sub/ directory and
> >> your namespace configuration is prefix=INBOX/, separator=/, the correct
> >> way to deliver mail there is to use -m INBOX/box/sub
> >>
> >>
> >>>
> >>>
> >>>
> >>> 2013/4/3 Stephan Bosch
> >>>
> Op 4/3/2013 1:56 PM, Isak Rubin schreef:
>
> > Here you go
> >
>
> You're using the listescape plugin. Try putting that in the global
> mail_plugins setting, e.g.:
>
> # usually located in /etc/dovecot/conf.d/10-mail.**conf
> mail_plugins = listescape
>
> protocol lda {
> mail_plugins = $mail_plugins sieve autocreate
> }
> protocol imap {
> mail_plugins = $mail_plugins autocreate
> }
>
>
> Regards,
>
> Stephan.
>
> >>>
> >>
> >>
> >>
> >> 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
> >>
> >
>
>
>
> 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] Username and Email
Ave Maria! I'm completely new to Dovecot, I was just wondering if the username (POP3) can be completely different to the POP3 email? God Bless Dan
Re: [Dovecot] Username and Email
No reason why not. Just set it up so that the given login gets the right home/mail location http://wiki2.dovecot.org/PasswordDatabase http://wiki2.dovecot.org/UserDatabase On 04/03/2013 09:41 AM, Dan Clovis wrote: Ave Maria! I'm completely new to Dovecot, I was just wondering if the username (POP3) can be completely different to the POP3 email? God Bless Dan
[Dovecot] Maildirs location migration
Hello Timo,
I'm using dovecot-2.1.15 with Maildir mailboxes located on an NFS filer.
Postfix is used to deliver mail through procmail ("mailbox_command) as LDA.
Our team has bought another filer and everything is meant to go on it, so we're
planning to migrate those mailboxes to the new filer.
To test it only on a subset of users, I ended up to the following solution :
1. keep new messages in postfix mailqueue for those users (via a service and a
transport)
2. prevent new dovecot authentication for those users (via the "auth-deny"
passwd-file type passdb)
3. doveadm kick those users
4. copy or rsync the mailboxes
5. symlink maildir, control and indexes directories to the new filer (nfs
mounted on the mail server)
6. re-enable mail delivery and imap authentication
I was wondering if such a migration could be done differently in order to be
seamless to the user :
- for the postfix part, it would be easy, I guess, to create a new service (and
a new transport map using this service) to deliver to the new location
- but for the imap part, I'm not sure if it can be done. My guess is that, if
feasible, it would involve some namespace settings and a dsync copy but I
cannot figure out how exactly.
What do you think ?
Thanks
--
Thomas Hummel | Institut Pasteur
| Groupe Exploitation et Infrastructure
[Dovecot] Error : File too large
Hi , When accessing mails through webmail(roundcube), we were getting below error's in huge Please help to know .. what this error is related to.. dovecot version , we are using is 2.1.15 Mar 28 15:37:47 imapserver dovecot: imap(cel_default): Error: rename(/mail/mailstore/linoquery.com/lino_default/Maildir/new/1364463180.M563166P30867.imapserver,S=3263,W=3309, /mail/mailstore/linoquery.com/lino_default/Maildir/cur/1364463180.M563166P30867.imapserver,S=3263,W=3309:2,) failed: File too large Thanks, Kavish Karkera
Re: [Dovecot] Error : File too large
Kavish Karkera writes: > Hi , > > > When accessing mails through webmail(roundcube), we were getting below > error's in huge > > Please help to know .. what this error is related to.. > > dovecot version , we are using is 2.1.15 > > > Mar 28 15:37:47 imapserver dovecot: imap(cel_default): Error: > rename(/mail/mailstore/linoquery.com/lino_default/Maildir/new/1364463180.M563166P30867.imapserver,S=3263,W=3309, > /mail/mailstore/linoquery.com/lino_default/Maildir/cur/1364463180.M563166P30867.imapserver,S=3263,W=3309:2,) > failed: File too large What filesystem? And how many files in /mail/mailstore/linoquery.com/lino_default/Maildir/cur/ so far? It sounds than you reached files-per-dir limit (~32K for ext3, 64K for ext4, for example) -- http://modnebzdury.wordpress.com/2009/10/01/niewiarygodny-list-prof-majewskiej-wprowadzenie/ Made with real ingredients.
Re: [Dovecot] Error : File too large
Thanks Kamil for your instant reply :) Our /mail partion is nfs mounted.(NetApp) There are about 1,70,000 files in Maildir Regards, Kavish Karkera From: Kamil Jońca To: dovecot@dovecot.org Sent: Wednesday, 3 April 2013 10:14 PM Subject: Re: [Dovecot] Error : File too large Kavish Karkera writes: > Hi , > > > When accessing mails through webmail(roundcube), we were getting below > error's in huge > > Please help to know .. what this error is related to.. > > dovecot version , we are using is 2.1.15 > > > Mar 28 15:37:47 imapserver dovecot: imap(cel_default): Error: > rename(/mail/mailstore/linoquery.com/lino_default/Maildir/new/1364463180.M563166P30867.imapserver,S=3263,W=3309, > /mail/mailstore/linoquery.com/lino_default/Maildir/cur/1364463180.M563166P30867.imapserver,S=3263,W=3309:2,) > failed: File too large What filesystem? And how many files in /mail/mailstore/linoquery.com/lino_default/Maildir/cur/ so far? It sounds than you reached files-per-dir limit (~32K for ext3, 64K for ext4, for example) -- http://modnebzdury.wordpress.com/2009/10/01/niewiarygodny-list-prof-majewskiej-wprowadzenie/ Made with real ingredients.
Re: [Dovecot] Error : File too large
kjo...@o2.pl (Kamil Jońca) writes: [...] > > What filesystem? And how many files in > /mail/mailstore/linoquery.com/lino_default/Maildir/cur/ so far? > It sounds than you reached files-per-dir limit (~32K for ext3, 64K for > ext4, for example) Sorry for that noise. These limits in ext3/4 are for subdir count. KJ -- http://sporothrix.wordpress.com/2011/01/16/usa-sie-krztusza-kto-nastepny/ Keyboard error press F1 continue
Re: [Dovecot] Error : File too large
On 04/ 3/13 12:55 PM, Kavish Karkera wrote: Our /mail partion is nfs mounted.(NetApp) There are about 1,70,000 files in Maildir Probably reached NetApp's "maxdirsize" limit...
[Dovecot] maildirsize problem
i am currently using roundcube my webmail and configure using dovecot quota
plugins.
but it seems to not be updating the maildirsize when new mails comes.Deleting
the
maildirsize will recreate the files correctly.Is there any solutions to this
problem with
dovecot.
Either you're not using dovecot-lda to deliver the mails, or you haven't
configured quota
plugin correctly for it. dovecot -n output and logs about a mail delivery would
help.
My configuration is using Centos 6.dovecot 2.1.1.and i have
configure the quota plugin.but i am not sure what you mean by dovecot-lda.i
just follow
the guides on the internet and skim through dovecots documentation.i am using
the local
unix account for mail account not using virtual users.here is my configuration:
[root@mail ~]# dovecot -n
# 2.1.1: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-279.el6.x86_64 x86_64 CentOS release 6.3 (Final)
base_dir = /var/run/dovecot/
mail_debug = yes
mail_location = maildir:~/Maildir
mail_plugins = " quota"
maildir_broken_filename_sizes = yes
mbox_write_locks = fcntl
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
driver = pam
}
plugin {
quota = maildir:User quota
quota_rule = *:storage=1G
quota_rule2 = Trash:storage=+100M
}
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0666
user = postfix
}
}
ssl = required
ssl_cert = http://thirdpartyoffers.netzero.net/TGL3231/515ce5588c8f765586e9dst01duc
Re: [Dovecot] Proxying, pertinent values and features, SNI
On Wed, 03 Apr 2013 11:13:41 +0100 Ed W wrote: > Hi > > > I presume to best support all(?) clients out there is to have > > "local_name" sections for SNI first and then "local" sections for IP > > address based certs. It is my understanding that SNI needs to be > > requested by the client, so aside from client bugs (nah, those don't > > exist ^o^) every client should get an appropriate response for TLS. > > Has anybody done a setup like that already? > > > > Although not what you asked for, just so you are aware, Godaddy (boo > hiss, etc) offer reasonably inexpensive multi subject alt name based > certs. This means you can have a single cert which is valid for lots of > completely different domain names. The mild benefit is that this > doesn't require SNI support for SSL (which I'm unsure is supported by > many mail clients?) > Yeah, I'm aware of multi-domain (SAN) certs, however there are 2 gotchas with those that our support and the OEMs this is for might not approve of: 1. Only the primary host will actually be validated/authenticated, which at least with some browsers will result in this being pointed out to the user when they connect to a SAN. Not sure about mail clients, but webmail is also in that overall deal, so support is probably not going to like the potential "concerned you got hacked" phone calls from customers. 2. Despite the fact that it will be trivial for anybody to determine that OEM A is now hosted with us, a SAN SSL makes all the SANs visible in one go, something they probably don't want. We're talking a small (10ish) number of OEMs here, so I'm happy and willing to throw some IP addresses at this particular problem and have everybody use (and deal with!) their own certs. As for SNI, supposedly most PC clients will support it, while most mobile ones don't. In my scenario it doesn't matter either way, the idea is to hand the correct cert to a client that requests it via SNI and for all the others based on the IP address they connected to. If everybody can be taught to use only TLS (not IMAPS/POP3S) and all the clients do support SNI, we can do away with the dedicated IP addresses. Might even happen before the heat death of the universe. ^o^ Regards, Christian -- Christian BalzerNetwork/Systems Engineer ch...@gol.com Global OnLine Japan/Fusion Communications http://www.gol.com/
Re: [Dovecot] maildirsize problem
On Thu, 2013-04-04 at 02:27 +, mastertoi...@netzero.net wrote:
> passdb {
> driver = pam
> }
>
> i am still not sure why maildirsize is not updating.thanks
> ___
Because dovecot (dovecot-lda) is not delivering the mails to the
maildir, postfix is.
signature.asc
Description: This is a digitally signed message part
