[Dovecot] doveconf: Warning: Obsolete settings.... in /etc/dovecot/dovecot.conf: ...

[D Chen]

Got duplicated Warnings from the "doveconf -n" output ! Can anyone explain and 
fix them ? thx!

   admin@server:/etc/dovecot$ doveconf -n

    # 2.0.13: /etc/dovecot/dovecot.conf
    doveconf: Warning: NOTE: You can get a new clean config file with: doveconf 
-n > dovecot-new.conf
    doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:716: 
protocol managesieve {} has been replaced by protocol sieve { }
    doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:888: add 
auth_ prefix to all settings inside auth {} and remove the auth {} section 
completely
    doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:926: 
passdb pam {} has been replaced by passdb { driver=pam }
    doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1039: 
userdb passwd {} has been replaced by userdb { driver=passwd }
    doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1101: 
auth_user has been replaced by service auth { user }
    doveconf: Warning: NOTE: You can get a new clean config file with: doveconf 
-n > dovecot-new.conf
    doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:716: 
protocol managesieve {} has been replaced by protocol sieve { }
    doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:888: add 
auth_ prefix to all settings inside auth {} and remove the auth {} section 
completely
    doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:926: 
passdb pam {} has been replaced by passdb { driver=pam }
    doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1039: 
userdb passwd {} has been replaced by userdb { driver=passwd }
    doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1101: 
auth_user has been replaced by service auth { user }
    # OS: Linux 3.0.0-16-server x86_64 Ubuntu 11.10 
    log_timestamp = "%Y-%m-%d %H:%M:%S "
    mail_location = maildir:~/Maildir
    mail_privileged_group = mail
    managesieve_notify_capability = mailto
    managesieve_sieve_capability = fileinto reject envelope encoded-character 
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy 
include variables body enotify environment mailbox date
    passdb {
      driver = pam

- Ignored:
    }
    passdb {
      driver = pam
    }
    plugin {
      sieve = ~/.dovecot.sieve
      sieve_dir = ~/sieve
    }
    protocols = imap pop3 sieve
    service auth {
      unix_listener /var/spool/postfix/private/auth-client {
        group = postfix
        mode = 0660
        user = postfix
      }
      unix_listener /var/spool/postfix/private/dovecot-auth {
        group = postfix
        mode = 0660
        user = postfix
      }
      user = root
    }
    ssl_cert =  was automatically rejected:%n%r
    }

Re: [Dovecot] Multiple locations, 2 servers - planning questions...

[Stan Hoeppner]

On 3/3/2012 2:20 PM, Charles Marcus wrote:
> Thanks very much for taking the time for your detailed reply, Stan, but
> I'll need more time to study it...
> 
> On 2012-03-02 4:17 AM, Stan Hoeppner  wrote:
> 
>> My gut instinct, based on experience and the match, is that a single GbE
>> inter site MAN link will be plenty, without the need to duplicate server
>> infrastructure.
> 
> I just wanted to point out one thing - I have two primary goals - yes,
> one is to maximize performance, but the other is accomplish a level of
> *redundancy*...

What type of redundancy are you looking for?  I.e. is one reason for
duplicating servers at site #2 to avoid disruption in the event the MAN
link fails?  Do you currently have redundant GbE links to each closet
switch stack in site #1, and also redundant switches in the datacenter?
 I.e. do you skip a beat if a core or closet switch fails?

If you do not currently have, nor plan to create such network redundancy
internally at site #1, then why build application redundancy with the
single goal of mitigating failure of a single network link?  Do you have
reason to believe there is a higher probability of failure of the MAN
link than any other single link in the current network?

> Also - I already have the servers (I have 3 Poweredge 2970's available
> to me, only one of which is currently being used)...
> 
> So, the only extra expenses involved will be relatively minor hardware
> expenses (multi-port Gb NICs), and some consulting services for making
> sure I implement the VM environment (including the routing) correctly.

Again, you don't need multi-port GbE NICs or bonding for performance--a
single GbE link is all each server needs.  Your switches should be able
to demonstrate that, without even needing a sniffer, assuming they're
decent managed units.  If you're after link redundancy, use two single
port NICs per server, or one mobo mounted port and once single port NIC.
 Most dual port NICs duplicate the PHYs but not the ethernet chip nor
power circuits, etc.  Thus, when a dual port NIC fails you usually loose
both ports.

> So, honestly, we'd be incurring most of these expenses anyway, even if
> we didn't set up redundant servers, so I figure why not get redundancy
> too (now is the time to get the boss to pay for it)...

Don't forget power backup at site #2.  Probably not a huge cost in the
overall scheme of things, but it's still another $5000 or so.

In summary, my advice is:

1.  One 1000Mb MAN link is plenty of bandwidth for all users at site #2
including running internet traffic through site #1, saving the cost
of an internet pipe at site #2

2.  If truly concerned about link failure, get a backup 100Mb/s link,
or get two GbE links with a burst contract, depending on price

3.  Keep your servers in one place.  If you actually desire application
level redundancy (IMAP, SMB/CIFS, etc) unrelated to a network link
failure, then do your clustering etc "within the rack".  It will be
much easier to manage and troubleshoot this than two datacenters w/
all kinds of replication etc between them

4.  If site #1 is not already link redundant, it makes little sense to
make a big redundancy push to cover a possible single network link
failure, regardless of which link

5.  Building a 2nd datacenter and using the MAN link for data
replication gives you no performance advantage, and may actually
increase overall utilization, vs using the link as a regular trunk

6.  *Setup QOS appropriately to maintain low latency of IMAP and
other priority data, giving a back seat to SMB/CIFS/FTP/HTTP and
other bulk transfer protocols*  With proper QOS the single GbE
MAN link will simply scream for everyone, regardless of saturation
level

-- 
Stan

Re: [Dovecot] testing fts-solr?

[Bradley Giesbrecht]

On Mar 3, 2012, at 12:14 PM, Charles Marcus wrote:

> On 2012-03-02 5:13 PM, Robin  wrote:
>> This mailing list is for dovecot, not Thunderbird support.  The lack of
>> replies to Thunderbird usage questions no doubt reflects this.
> 
> What precisely about a possible bug with *any* IMAP client when using 
> dovecot+fts makes you think that this is not on topic for the dovecot list?


Show dovecot misbehaving.

On Feb 28, 2012, at 6:57 AM, Timo Sirainen wrote:

> On Tue, 2012-02-28 at 15:47 +0100, kfx wrote:
>>> Did you enable the 'Run search on server' option in the Advanced Search
>>> window? Doing this *should* result in Thunderbird using dovecots indexes
>>> server side.
>>> 
>> 
>> Yes I did.
>> 
>> Some more info:
>> 
>> by telnet'ing directly and issuing:
>> c search text pattern
>> * SEARCH 1208
>> c OK Search completed (0.003 secs).
> 
> So, Solr in Dovecot works perfectly.
> 
>> But the same search in thunderbird return "No matches found" :(
> 
> Thunderbird problem, nothing you can do about it from Dovecot's side.


Regards,
Bradley Giesbrecht

Re: [Dovecot] Multiple locations, 2 servers - planning questions...

[Piotr NetExpert]

So, the only extra expenses involved will be relatively minor hardware
expenses (multi-port Gb NICs), and some consulting services for making
sure I implement the VM environment (including the routing) correctly.


Take into account costs of administering a more complex environment too.

--
pozdrawiam
Piotr Szafarczyk

http://www.netexpert.pl

Re: [Dovecot] Dovecot clustering with dsync-based replication

[Michael Grimm]

Hi --

On 28.02.2012, at 15:03, Timo Sirainen wrote:

> This document describes a design for a dsync-replicated Dovecot cluster.

Whow! That's more than interesting, that's a real bummer ;-) At least for
my setup of redundant mail servers.

Looking forward to test it,
Michael

Re: [Dovecot] Multiple locations, 2 servers - planning questions...

[Charles Marcus]

Thanks very much for taking the time for your detailed reply, Stan, but 
I'll need more time to study it...


On 2012-03-02 4:17 AM, Stan Hoeppner  wrote:


My gut instinct, based on experience and the match, is that a single GbE
inter site MAN link will be plenty, without the need to duplicate server
infrastructure.


I just wanted to point out one thing - I have two primary goals - yes, 
one is to maximize performance, but the other is accomplish a level of 
*redundancy*...


Also - I already have the servers (I have 3 Poweredge 2970's available 
to me, only one of which is currently being used)...


So, the only extra expenses involved will be relatively minor hardware 
expenses (multi-port Gb NICs), and some consulting services for making 
sure I implement the VM environment (including the routing) correctly.


So, honestly, we'd be incurring most of these expenses anyway, even if 
we didn't set up redundant servers, so I figure why not get redundancy 
too (now is the time to get the boss to pay for it)...


--

Best regards,

Charles

Re: [Dovecot] testing fts-solr?

[Charles Marcus]

On 2012-03-02 5:13 PM, Robin  wrote:

This mailing list is for dovecot, not Thunderbird support.  The lack of
replies to Thunderbird usage questions no doubt reflects this.


What precisely about a possible bug with *any* IMAP client when using 
dovecot+fts makes you think that this is not on topic for the dovecot list?


--

Best regards,

Charles

[Dovecot] directly addressable public folders issues

[Tom Fernandes]

Hi,

I would like to have an address i...@example.com whose mails are stored in a 
public folder.
I also want certain users to be able to create sieve-filter-rules and 
subfolders.

From what I understand it's a good idea to have a separate location for home 
and 
for mail_location.

For my normal accounts I have:
home = /var/vmail/
mail_location = ~/Maildir

Is there a way to have the same for public folders? This are my current 
settings:

namespace public {
  separator = /
  prefix = public/
  location = maildir:/var/vmail/public
  subscriptions = no
}


user_attrs = homeDirectory=home=/var/vmail/%$, =mail=maildir:~/Maildir


The LDAP-homeDirectory-attribute for i...@example.com is "public/.info"


Like this an incoming mail is stored below /var/vmail/public/.info/Maildir 
which 
is good. The MUA seems to read to read from /var/vmail/public/.info though.

How can I make the MUA read from /var/vmail/public/.info/Maildir instead?

And in case this works - is it possible to have only certain users modify the 
sieve-rule for this public folder or do I definitely need a passdb-entry for 
i...@example.com?
Modifying  scripts via commandline is not an option...

I'm using dovecot 1.2.


regards,


Tom Fernandes

Re: [Dovecot] Failing: doveadm sync <--remote host--> dsync mirror

[Michael Grimm]

Hi --

On 03.03.2012, at 19:03, Michael Grimm wrote:

> Thus I can't test user suggestion.

s/user/your/

Sorry,
Michael

Re: [Dovecot] RFE: IMAP LIST Extension for Special-Use Mailboxes

[Thomas Leuxner]

Am 03.03.2012 um 13:07 schrieb Steven Haigh:

> I'm just wondering if anyone knows if this got implemented? I've been looking 
> at doing this for quite some time...


Yes it was. It has been discussed extensively:

http://www.dovecot.org/list/dovecot-news/2012-February/000213.html
http://www.dovecot.org/list/dovecot/2011-December/062327.html

Thomas

signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [Dovecot] Failing: doveadm sync <--remote host--> dsync mirror

[Michael Grimm]

Hi --

On 27.02.2012, at 13:45, Timo Sirainen wrote:
> On Thu, 2012-02-23 at 20:55 +0100, Michael Grimm wrote:

>> My working 2.0.18 syntax threw the following error:
>> 
>>  vmail> dsync -v -f -u test ssh vm...@remote-host.tld dsync -v -f -u test
>>  doveadm(vmail): Fatal: Unknown print formatter: -u
>>  dsync-local(test): Error: read() from worker server failed: EOF
> 
> You left out "mirror" from that command, but after adding it the latest
> hg version works.

I did use 'mirror', I just forgot to paste it.

JFTR:
vmail> dovecot --version
20120303 (1002733ca266+)

vmail> dsync -v -f -u test mirror ssh vm...@remote-host.tld dsync -v -f 
-u test
dsync-local(test): Error: remote: dsync: illegal option -- f
doveadm dsync-server [-u |-A] [-S ] 
dsync-local(test): Error: read() from worker server failed: EOF

If I do omit the remote '-f' the old syntax is being accepted. Thanks for 
fixing that.

>> Now I switched to the recommended new syntax as stated in 
>> http://wiki2.dovecot.org/Upgrading/2.1:
>> 
>>  vmail> doveadm sync -v -f -u test ssh vm...@remote-host.tld doveadm 
>> sync -v -f -u test
>>  doveadm: illegal option -- v
>>  doveadm sync [-u |-A] [-S ] [-fR] [-m ] 
>> 
> 
> The -v parameter is in wrong place now, needs to be "doveadm -v sync".


Ah, yes. That was my mistake, sorry.

>> After some trial by error I finally found a working syntax:
>> 
>>  vmail> doveadm sync -u test -f ssh vm...@remote-host.tld doveadm 
>> dsync-server -u test
> 
> Oh, hmm. I hadn't thought about this problem, it shouldn't have been
> necessary to give the dsync-server parameter. But I guess there's not a
> whole lot of other possibilities to do this. Hmm.
> 
> BTW. I think you can do this simply:
> 
> doveadm sync -f -u test t...@remote-host.tld

vmail> doveadm sync -f -u test ssh vm...@remote-host.tld
dsync-local(test): Error: remote: dsync-server: Command not found.
dsync-local(test): Error: read() from worker server failed: EOF

Users are virtual ones at both mail servers, and vmail is the only system user 
to run ssh. Thus I 
can't test user suggestion. But it's ok to add a 'doveadm dsync-server -u test'.

Now, I will stick to 2.1.x because syncing is done without loss of mails (after 
10 days of testing).
The only inconvenience remaining is reappearing of deleted and "undeletable" 
mail. But it seems that 
I'm the only one reporting that. How could I help to debug this issue?

Regards,
Michael

Re: [Dovecot] keywords/flags questions

[Timo Sirainen]

On 3.3.2012, at 18.06, Arnaud Abélard wrote:

> I am currently using dovecot 2.0.13 and I have been working on keywords 
> handling our webmail and I have a few questions about how dovecot handles 
> them.
> 
> First, if I am not mistaken keywords neeed to be UTF-7 encoded. That means I 
> need to encode special caracters using values between & and - chars. UTF-7 
> encoding is case sensitive, &AOA- isn't the same chars as &aoa-.  But docevot 
> save keywords in lowercase or am I mistaken?
> 
> For example:
> . STORE 1:1 flags &AOA-_refaire
> * 1 FETCH (FLAGS (&aoa-_refaire))
> 
> This makes retrieving the keyword properly impossible. What did I miss?

Sorry, doesn't work like that. This was recently discussed in imap-protocol 
mailing list though, but nothing has come of it.

> My other question is about the permanent flags being displayed upon selecting 
> a mailbox. I'm trying to understand why unused keywords are still showing up 
> in there. Is there a way to force the definitive removal of a keyword from a 
> mailbox? are old keywords kept undefinitely?

For now yes. I've been thinking about doing something about this for last 8 
years, but it has never become a real problem so I haven't bothered.

Re: [Dovecot] keywords/flags questions

[Алексей Сундуков]

3 марта 2012 г. 20:06 пользователь Arnaud Abélard
 написал:
> But docevot save keywords in lowercase

Yes.
http://www.dovecot.org/list/dovecot/2011-April/058493.html

[Dovecot] keywords/flags questions

[Arnaud Abélard]

Hello,

I am currently using dovecot 2.0.13 and I have been working on keywords 
handling our webmail and I have a few questions about how dovecot 
handles them.


First, if I am not mistaken keywords neeed to be UTF-7 encoded. That 
means I need to encode special caracters using values between & and - 
chars. UTF-7 encoding is case sensitive, &AOA- isn't the same chars as 
&aoa-.  But docevot save keywords in lowercase or am I mistaken?


For example:
. STORE 1:1 flags &AOA-_refaire
* 1 FETCH (FLAGS (&aoa-_refaire))

This makes retrieving the keyword properly impossible. What did I miss?

My other question is about the permanent flags being displayed upon 
selecting a mailbox. I'm trying to understand why unused keywords are 
still showing up in there. Is there a way to force the definitive 
removal of a keyword from a mailbox? are old keywords kept undefinitely?


Thanks in advance,

Arnaud


--
Arnaud Abélard
jabber: arnaud.abel...@univ-nantes.fr / twitter: ArnY
Administrateur Système
DSI Université de Nantes
-

Re: [Dovecot] Desperately need help ! a default dovecot.conf and/or Ubuntu 11.10 postfix/dovecot server configuration issue!

[Eliezer Croitoru]

On 02/03/2012 09:33, D Chen wrote:
use the command dovecot -n to get dovecot settings output and we can try 
to help you a bit.


Regards,
Eliezer

When ungraded from Ubuntu 11.04 to 11.10, dovecot can't start successfully with 
lots of errors i.e.
"dovecot: doveconf: Warning: ... 'imaps' protocol is no longer necessary, remove 
it"...

At any rate, I want to setup a postfix(MTA)/dovecot(MDA) servers on Ubuntu 11.10, by following the Postfix installation and configuration 
instruction in Ubuntu Serverguide, in "1.4 Configuring SASL" section on page 190, after run "sudo apt-get install 
dovecot-common", it requires to edit the section of "auth default" and the "socket listen" option...,in the 
/etc/dovecot/dovecot.conf file, BUT my /etc/dovecot/dovecot.conf (only about 4k byes) CAN'T find the "auth default" "socket 
listen" !

I also checked into the /usr/share/doc/dovecot-common/dovecot/example-config, 
there is a
dovecot.conf, it's also about 4k size, and there is no such "auth default" or 
"socket listen" words can be found ! where is the default dovecot.conf file I can get a 
copy ?

BTW, there is the dovecot.conf.ucf file (what is this for?) which's about 50k and has the 
"auth default" and "socket listen" words there ! what is supposed the size for 
the /etc/dovecot/dovecot.conf ? i'm confused!

Thx.

Re: [Dovecot] Desperately need help ! a default dovecot.conf and/or Ubuntu 11.10 postfix/dovecot server configuration issue!

[Charles Marcus]

On 2012-03-02 2:33 AM, D Chen  wrote:

When ungraded from Ubuntu 11.04 to 11.10, dovecot can't start
successfully with lots of errors i.e. "dovecot: doveconf: Warning:
... 'imaps' protocol is no longer necessary, remove it"...

At any rate, I want to setup a postfix(MTA)/dovecot(MDA) servers on
Ubuntu 11.10, by following the Postfix installation and configuration
instruction in Ubuntu Serverguide, in "1.4 Configuring SASL" section
on page 190, after run "sudo apt-get install dovecot-common", it
requires to edit the section of "auth default" and the "socket
listen" option...,in the /etc/dovecot/dovecot.conf file, BUT my
/etc/dovecot/dovecot.conf (only about 4k byes) CAN'T find the "auth
default" "socket listen" !


Distro specific questions are usually much better asked on the distro 
support lists...


--

Best regards,

Charles

Re: [Dovecot] RFE: IMAP LIST Extension for Special-Use Mailboxes

[Steven Haigh]

Hi all,

I'm just wondering if anyone knows if this got implemented? I've been 
looking at doing this for quite some time...


--
Steven Haigh

Email: net...@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299

>Timo,
>
>would you consider adding support for "IMAP LIST Extension for 
>Special-Use
>Mailboxes"  any time near 
>in the

>future?
>
>I would really love to get rid of all those folders created by all >those
>different mail clients just because they can't agree to use the same 
>folder

>for special purpose.
>
>Obviously clients need to support it too. Having Dovecot support it 
>certainly

>would make them adopt the standard sooner.



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [Dovecot] doveadm fetch prints duplicate results in 2.1

[Christoph Bußenius]

On 02/29/2012 10:31 AM, Christoph Bußenius wrote:

when the private namespace has "prefix = INBOX." and you use doveadm
fetch to search for "mailbox INBOX", then it prints every message twice:


Apparently the bug has been introduced with this changeset:

changeset:   14112:f5353573d3a0
user:Timo Sirainen 
date:Sun Feb 12 02:50:49 2012 +0200
summary: lib-storage: Added MAILBOX_LIST_ITER_LIST_PREFIXES flag.

http://hg.dovecot.org/dovecot-2.1/rev/f5353573d3a0

Cheers,
Christoph