Re: v2.2.28 released

[Timo Sirainen]

On 6 Mar 2017, at 9.17, Tom Sommer  wrote:
> 
> 
> On 2017-02-24 14:34, Timo Sirainen wrote:
>> http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz
>> http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig
> 
> Are there any plans to do a bugfix-release, that includes the few issues seen 
> in the mailing-list, or do you consider 2.2.28 safe to upgrade to?

I don't see anything critical. A couple of bugs that might or might not affect 
you. We'll have 2.2.29 soon enough, so no plans for other releases before that.

Re: v2.2.28 released

[Tom Sommer]

On 2017-02-24 14:34, Timo Sirainen wrote:

http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig


Are there any plans to do a bugfix-release, that includes the few issues 
seen in the mailing-list, or do you consider 2.2.28 safe to upgrade to?


Thanks

---
Tom

Re: Transitioning away from mail_location = maildir:~

[Steffen Kaiser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, 4 Mar 2017, Chris Stankevitz wrote:


mail_home = /var/mail/vhosts/%d/%n
mail_location = maildir:~/mail


the default for maildir-type would be ~/Maildir :-) that enables 
auto-detection as well.



1. Should I manually create the maildir:~/mail directories?

2. Should I move files from /var/mail/vhosts/%d/%n into maildir:~/mail? Which 
files?  (In other words: which files are "home directory" files and which 
files are "mail files"?)



drwx--  .
drwxr-xr-x  ..
drwx--  .Archives


any dir with dot at the beginning except . and ..


drwx--  cur
drwx--  new
drwx--  tmp


these dirs hold the messages of the INBOX


-rw---  dovecot-keywords
-rw---  dovecot-uidlist
-rw---  dovecot-uidvalidity
-r--r--r--  dovecot-uidvalidity.55411048
-rw---  dovecot.index
-rw---  dovecot.index.cache
-rw---  dovecot.index.log
-rw---  dovecot.mailbox.log
-rw---  subscriptions


make it:
dovecot.index* dovecot-uid*
You do not seem to use mailbox sharing or ACLs, those features would add 
some other entries.


===

These not! They belong to Sieve in home:


lrwx--  .dovecot.sieve
-rw---  .dovecot.sieve.log
-rw---  .dovecot.sieve.log.0
-rw---  .dovecot.svbin
drwx--  sieve


Keep any directory without leading dot (except cur, new,& tmp) in home as 
well.


- -- 
Steffen Kaiser

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEVAwUBWL1aPXz1H7kL/d9rAQJO1Qf+LlWcW0yMVAYHurp4+LglYXmZiUiOpJl0
d/7K4pw0yiF0KMrvQaxxugkVJCvQoErWvCiNu9mld1dkg+zzNNBlunRVi/UiJweb
/Mp7tdmF7LQeDCdPnetqX9ASI2wr7TBtorOY/VWu+Haq98ZyLLbuhE/zz3CmF1gZ
80hdiOmsnzbakViIk37L0J9+gBZqbcHYQ2voey3UUw7cgd0yECGYCFJFuWK1X95a
qB8/nyMUiWAIySZT1jQirMpg21DFYY3qOqsD6VTXkMz0B5ZE4mxq2L7gTQ0Gs73u
m1v95QmLAKl8Y5cH7vuZivLt4ElIAAsTlL5Y7SHMkA7jIGjlhMUV3g==
=Hgrg
-END PGP SIGNATURE-

Re: quota-warning: possible to have size also?

[chaouche yacine]

Good point Alex, there's no real advantage that script was there from courier's 
time and I still use it but doveadm quota command does the trick just as well.

Actual quota : 
root@messagerie[10.10.10.19] ~ # doveadm  quota  get  -u sec-...@domain.tld 
2>/dev/null | sed -n 1p | awk '{print $4}'
559728
root@messagerie[10.10.10.19] ~ #

Max quota :

root@messagerie[10.10.10.19] ~ # doveadm  quota  get  -u sec-...@domain.tld 
2>/dev/null | sed -n 1p | awk '{print $5}'
1048576
root@messagerie[10.10.10.19] ~ # 



  -- Yassine.

Re: Do I need to configure director?

[@lbutlr]

On 03 Mar 2017, at 05:42, Angel L. Mateo  wrote:
>   Is there any advantage of running director in this scenario?

I haven't used director, but based on what it does it seems it would be of no 
benefit when the LDAP record has the information that director would otherwise 
provide.

Are your logs detailed enough to show what (if anything) director is doing with 
your current setup?

-- 
Apple broke AppleScripting signatures in Mail.app, so no random signatures.

Re: quota-warning: possible to have size also?

[Alex JOST]

Am 06.03.2017 um 10:39 schrieb chaouche yacine:

Hi,

I'am using a Maildir++ based quota setting which creates a maildirsize file in 
every Maildir. The first two lines of this file are the maximum quota in bytes 
then the actual consumption in bytes and number of messages, like so :


1073741824S
379317999 5169



This means this user has a quota of 1Gb and he is using ~ 379 Mb (you have to 
divide by 1024 to be more precise)

Since the script receieves the user as second argument, you can deduce it's 
current quota size and restriction by reading the maildirsize file (if you have 
it). I think you can do the same if your quota is in the database (querying).


This a piece of script I wrote once that shows the value of quota used and 
quota max (both in megas and perecent) that might help you if you know your way 
through bash scripting :


I might be missing something but what's the advantage over doveadm?

doveadm quota get -A

--
Alex JOST

Re: Transitioning away from mail_location = maildir:~

[chaouche yacine]

Thanks Alex. I myself ran into these problems as described above and having 
distinct Maildir and Homedir helped it. The main reason being dovecot not 
making any distinction between a folder and maildir folder, which seems to have 
a very simple solution though.

  -- Yassine.

Re: quota-warning: possible to have size also?

[chaouche yacine]

Hi,

I'am using a Maildir++ based quota setting which creates a maildirsize file in 
every Maildir. The first two lines of this file are the maximum quota in bytes 
then the actual consumption in bytes and number of messages, like so : 


1073741824S
379317999 5169



This means this user has a quota of 1Gb and he is using ~ 379 Mb (you have to 
divide by 1024 to be more precise)

Since the script receieves the user as second argument, you can deduce it's 
current quota size and restriction by reading the maildirsize file (if you have 
it). I think you can do the same if your quota is in the database (querying).


This a piece of script I wrote once that shows the value of quota used and 
quota max (both in megas and perecent) that might help you if you know your way 
through bash scripting : 


root@messagerie[10.10.10.19] ~/SCRIPTS/MAIL # cat showquota.single

mega=$((1024*1024))
inbox="${1%@*}"
maildir="/var/vmail/domain.tld/$inbox"
backup="/var/vmail/backup.domain.tld/$inbox"
[ ! -e $maildir ] && echo "Boite email inexistante. Veuillez vérifier encore 
une fois l'orthogrape de $in...@domain.tld" && exit 1
function get_quota {
mailfolder="$1"
maildirsize="$mailfolder/maildirsize" 
fields=$(echo $(head -2 $maildirsize))
max="${fields%%S*}"
cur="$(echo $fields | cut -f2 -d ' ')"
ratio=$(echo "scale=2; $cur * 100 / $max" | bc)
cur=$(echo "scale=2; $cur / $mega" | bc)
max=$(echo "scale=2; $max / $mega" | bc)
echo "$cur Mo /  $max Mo ( $ratio% )"
}
echo Quota sur la boite aux lettres "$inbox"
get_quota "$maildir"
echo Quota sur les archives
get_quota "$backup"
echo "-"
root@messagerie[10.10.10.19] ~/SCRIPTS/MAIL # 



  --Yassine.

Re: dovecot 2.2.x listening on multiple interfaces

[Alex JOST]

Am 06.03.2017 um 09:31 schrieb David Mehler:

Hello,

I'm wondering if it's possible to get dovecot to listen on multiple
interfaces without designating * for everything?

I've got a machine with three interfaces going to three different
networks. I'm not wanting to let dovecot listen on all interfaces *
just two of them, standard ports. Is this doable?


You could either set some IPs via the listen parameter (see [1]) for all 
services or specify different IPs for each service (see [2]).



[1]: http://www.dovecot.org/doc/dovecot-example.conf
[2]: http://wiki.dovecot.org/Services#inet_listeners

--
Alex JOST

Re: Transitioning away from mail_location = maildir:~

[Alex JOST]

Am 06.03.2017 um 09:06 schrieb chaouche yacine:

Hi Chris,


I have since learned that mail_home and mail_location should be



different.  I plan to use this:


I'm interested about any sources for this ?


http://wiki.dovecot.org/VirtualUsers/Home

	"Home directory shouldn't be the same as mail directory with mbox or 
Maildir formats (but with dbox/obox it's fine). It's possible to do 
that, but you might run into trouble with it sooner or later."


--
Alex JOST

Re: Upgrade from 2.0. to 2.2

[Jakob Curdes]

Ah, still better. I just want to upgrade to a package that is available 
from maintained repos, so that is good news for me.


Thx, Jakob

(The last message was crippled somewhere - in my sent folder it looks ok 
but on the list only our logo appeared...)




Am 05.03.2017 um 22:52 schrieb Alexander Dalloz:

Am 05.03.2017 um 22:49 schrieb Peter:

On 04/03/17 00:22, Jakob Curdes wrote:

Hello, we have a centos 6 server running dovecot 2.0 provided with the
OS, currently 2.0.9. We would like to upgrade to the 2.2.19 package
provided by the mailserver.guru repo.


Why upgrade to such an old version?  You can get 2.2.27 (2.2.28 in
testing) packages from GhettoForge plus:

http://ghettoforge.org/


+1


Peter


Alexander

Re: Upgrade from 2.0. to 2.2

[Jakob Curdes]

Am 03.03.2017 um 12:45 schrieb Aki Tuomi:



On 2017-03-03 13:22, Jakob Curdes wrote:
Hello, we have a centos 6 server running dovecot 2.0 provided with 
the OS, currently 2.0.9. We would like to upgrade to the 2.2.19 
package provided by the mailserver.guru repo. I read the upgrading 
docs for 2.1 and 2.2 and found the following issues:

(...)
Are there other things that we need to observe? Is a direct update 
from 2.0.9 to 2.2.19 feasible with the above precautions or do we 
need to put in a 2.1 version in between?


Thank you for hints,
Jakob


I would also consider possibility of upgrading the server too, so you 
would instead setup a new environment and migrate your users there 
instead of upgrading the old server. This way you could make sure 
everything works.




Well, then I have a different problem because in this way I upgrade the 
complete environment to eg. CentOS 7 and will need to test a plethora of 
other things.
I'd rather stick to the current system (which ist not "old", just the 
dovecot package in CentOS 6 is "old").


Ok so no other problems known?

Regards, Jakob

Re: Upgrade from 2.0. to 2.2

[Jakob Curdes]

Ah, still better. I just want to upgrade to a package that is available 
from maintained repos, so that is good news for me.


Thx, Jakob


Am 05.03.2017 um 22:52 schrieb Alexander Dalloz:

Am 05.03.2017 um 22:49 schrieb Peter:

On 04/03/17 00:22, Jakob Curdes wrote:

Hello, we have a centos 6 server running dovecot 2.0 provided with the
OS, currently 2.0.9. We would like to upgrade to the 2.2.19 package
provided by the mailserver.guru repo.


Why upgrade to such an old version?  You can get 2.2.27 (2.2.28 in
testing) packages from GhettoForge plus:

http://ghettoforge.org/


+1


Peter


Alexander


--
Untitled Document
Jakob Curdes


*Anschrift:*
iS information systems oHG
Postfach 3011
26020 Oldenburg
Tel.: (0)441 - 84 53 1
Fax: (0)441 - 88 59 378



*Sitz:*
Donnerschweer Str. 89-91
D 26123 Oldenburg


Web: www.info-systems.de 

Firmierung und Handelsregisterangaben finden Sie unter diesem Link: 
Firmendaten. 

dovecot 2.2.x listening on multiple interfaces

[David Mehler]

Hello,

I'm wondering if it's possible to get dovecot to listen on multiple
interfaces without designating * for everything?

I've got a machine with three interfaces going to three different
networks. I'm not wanting to let dovecot listen on all interfaces *
just two of them, standard ports. Is this doable?

Thanks.
Dave.

Re: Transitioning away from mail_location = maildir:~

[chaouche yacine]

It's even listed as a possible setup in dovecot's wiki, see : 
http://genius.it/wiki.dovecot.org/VirtualUsers/Home (annotated version).

  -- Yassine.

Re: Transitioning away from mail_location = maildir:~

[chaouche yacine]

Hi Chris,

>I have since learned that mail_home and mail_location should be 

>different.  I plan to use this:

I'm interested about any sources for this ? 


I find dovecot to be very flexible, so much that you can actual have the home 
dir inside the maildir instead of the traditional other way around, which is 
actually my setup ! 



In /etc/dovecot/conf.d/auth-sql.conf.ext 

userdb {
driver = static
args = uid=vmail gid=vmail home=/var/vmail/%d/%n/dovecot
}




In /etc/dovecot/conf.d/10-mail.conf
mail_location = Maildir:~/../




So in my case, the maildir is /var/vmail/%d/%n/ and the home dir is inside the 
maildir in a directory I named dovecot (home=/var/vmail/%d/%n/dovecot). This is 
because I migrated from courier which had the maildir directly in 
/var/vmail/%d/%n/, but since sieve scripts are also put there they are 
presented as maildir folders (which they're not of course), and this confused 
my users. So I used this little trick to hide the sieve scripts inside the 
dovecot directory and still have them working correctly.

   -- Yassine.