RE: Server administration

[Marc Roos via dovecot]

Is it not better you either employ a proper educated/trained person or 
outsouce the work to a company that has the know how?



-Original Message-
From: Aleksandr Mette via dovecot [mailto:dovecot@dovecot.org] 
Sent: zondag 1 september 2019 14:42
To: dovecot@dovecot.org
Subject: Server administration

Dear Sirs,

 

There is Postfix+Dovecot+Sogo installation in our company. 





I have attentively red Installation and Configuration Guide.


However, I could not find some information.

 

Could you give me an advise how to:

 

1. Add/remove e-mail address

2. Change user e-mail address password

3. Add user e-mail address into mail alias

4. Forward e-mail

5. List all users e-mails




What is the best GUI interface for Dovecot administration?


 

With kind regards,

Alex

Re: Server administration

[Michael Hallager via dovecot]

1. Add/remove e-mail address

2. Change user e-mail address password

3. Add user e-mail address into mail alias

4. Forward e-mail

5. List all users e-mails


I agree with Mark.

We can't answer them anyway because we don't know what backend you are 
using. Typically all of the above would be done in an SQL database with 
queries which you have written into various config files like 
/etc/postfix/main.conf and /etc/dovecot/conf.d/auth-sql.conf.ext (and 
likely others!)

AW: CVE-2019-11500: Critical vulnerability in Dovecot and Pigeonhole

[MK via dovecot]

Good Morning List,

just a short question to this vulnerability. We are using a setup with dovecot 
redirector/proxy frontend servers
and some backend server, which store the mailboxes. 
Is it anough to update the frontend servers if I like to fix the the 
vulnerability?

greetings,
Oliver

Re: Server administration

[Alexander Dalloz via dovecot]

Am 2019-09-02 09:55, schrieb Michael Hallager via dovecot:

1. Add/remove e-mail address

2. Change user e-mail address password

3. Add user e-mail address into mail alias

4. Forward e-mail

5. List all users e-mails


I agree with Mark.

We can't answer them anyway because we don't know what backend you are
using. Typically all of the above would be done in an SQL database
with queries which you have written into various config files like
/etc/postfix/main.conf and /etc/dovecot/conf.d/auth-sql.conf.ext (and
likely others!)


No, please don't spread the info that you would need an SQL DB for 
running a mail service. Unless you run a big install with lots of 
accounts where it can be handy to use some sort of meta tool (modoboa, 
postfixadmin, ...) there is zero need for an SQL backend. And in 
enterprise environments you would normally use an LDAP / AD 
infrastructure component where your user base lives.


Anyhow, someone like the OP who appears not to be much experienced in 
the field of running his own mail service should not get the idea a 
database backend is what he really needs. Start KISS and master all the 
complex requirements in a simple manner first.


Or outsource the task to a mail service provider.

Alexander

Re: CVE-2019-11500: Critical vulnerability in Dovecot and Pigeonhole

[Sami Ketola via dovecot]

> On 2 Sep 2019, at 11.01, MK via dovecot  wrote:
> 
> Good Morning List,
> 
> just a short question to this vulnerability. We are using a setup with 
> dovecot redirector/proxy frontend servers
> and some backend server, which store the mailboxes. 
> Is it anough to update the frontend servers if I like to fix the the 
> vulnerability?

No. 

Sami

Re: Dovecot 2.3.7 - char "-" missing

[Sami Ketola via dovecot]

> On 30 Aug 2019, at 13.44, Domenico Pastore via dovecot  
> wrote:
> 
> Hello,
> 
> i have update dovecot from version 2.2.15 to 2.3.7.2.
> I have a problem with mine java software because there is a different 
> response when open connection to doveadm.
> 
> I need open socket to doveadm for get imap quota of a mailbox.
> 
> With version 2.2.15:
> # telnet 192.160.10.4 924
> Trying 192.160.10.4...
> Connected to 192.160.10.4.
> Escape character is '^]'.
> -
> 
> 
> With version 2.3.7.2:
> # telnet 192.160.10.3 924
> Trying 192.160.10.3...
> Connected to 192.160.10.3.
> Escape character is '^]'.
> 
> 
> The difference is "-" character. The version 2.3.7 not respond with "-" 
> character after opening the connection.
> 
> Is it possible to add the character again with a parameter?
> 
> Why did doveadm's answer change?


Because the behaviour in 2.2.15 was a bug. It was against the specification:

https://wiki.dovecot.org/Design/DoveadmProtocol 


Fix you app to handshake first or use doveadm http api:

https://wiki.dovecot.org/Design/DoveadmProtocol/HTTP 


Sami

AW: CVE-2019-11500: Critical vulnerability in Dovecot and Pigeonhole

[MK via dovecot]

>> On 2 Sep 2019, at 11.01, MK via dovecot  wrote:
>> 
>> Good Morning List,
>> 
>> just a short question to this vulnerability. We are using a setup with 
>> dovecot redirector/proxy frontend servers
>> and some backend server, which store the mailboxes. 
>> Is it anough to update the frontend servers if I like to fix the the 
>> vulnerability?

>No. 
>
>Sami

Thanks. Do I understand this correct that updating the frontends fixes only the 
vulnerability for anonymous requests 
and for users logged in the vulnerability still exists if I don't update the 
backend servers?

Oliver

Re: AW: CVE-2019-11500: Critical vulnerability in Dovecot and Pigeonhole

[Aki Tuomi via dovecot]

On 2.9.2019 12.51, MK via dovecot wrote:
>>> On 2 Sep 2019, at 11.01, MK via dovecot  wrote:
>>>
>>> Good Morning List,
>>>
>>> just a short question to this vulnerability. We are using a setup with 
>>> dovecot redirector/proxy frontend servers
>>> and some backend server, which store the mailboxes. 
>>> Is it anough to update the frontend servers if I like to fix the the 
>>> vulnerability?
>> No. 
>>
>> Sami
> Thanks. Do I understand this correct that updating the frontends fixes only 
> the vulnerability for anonymous requests 
> and for users logged in the vulnerability still exists if I don't update the 
> backend servers?
>
> Oliver
>

You are correct. After authentication proxies & directors will forward
data as-is to backend, which leaves you vulnerable to post-auth
vulnerability.

Aki

Re: purge causing reappearing mails?

[telsch via dovecot]

Hello,

today i got reappearing mails again, but not from purging. In the logs i
only found this. I've got massive problems by many users because
reappearing mails. If you need more information, i could provide.


Sep 02 12:58:43 doveadm: Warning: Transaction log file
/var/spool/mail//storage/dovecot.map.index.log was locked for 43
second
s (mdbox storage rebuild)
Sep 02 12:58:43 doveadm: Warning: fscking index file
/var/spool/mail//storage/dovecot.map.index
Sep 02 12:58:43 doveadm: Warning: mdbox /var/spool/mail//storage:
rebuilding indexes
Sep 02 12:59:01 dsync-local(): Error:
Couldn't lock /var/spool/mail//.dovecot-sync.lock:
fcntl(/var/spool/mail//.dovecot-sync.lock, write-lock, F_SETLKW)
locking failed: Timed out after 600 seconds (WRITE lock held by pid 7584)
Sep 02 12:59:34 doveadm: Warning: Transaction log file
/var/spool/mail//storage/dovecot.map.index.log was locked for 51
seconds (mdbox storage rebuild)
Sep 02 12:59:34 doveadm: Warning: fscking index file
/var/spool/mail//storage/dovecot.map.index
Sep 02 12:59:34 doveadm: Warning: fscking index file
/var/spool/mail//storage/dovecot.map.index
Sep 02 12:59:35 doveadm: Warning: mdbox /var/spool/mail//storage:
rebuilding indexes
Sep 02 13:00:22 doveadm: Warning: Transaction log file
/var/spool/mail//storage/dovecot.map.index.log was locked for 48
seconds (mdbox storage rebuild)
Sep 02 13:00:23 doveadm: Warning: fscking index file
/var/spool/mail//storage/dovecot.map.index

On 26.08.19 18:06, sch tel via dovecot wrote:

Hello,
i'm running 2 dovecot 2.3.4.1 servers with replication. once a week
purge command is executed. but from time to time it seems there are
deleted messages reappering after purge is executed. so i run in debug
mode. i saw in the past a few questions about reappearing messages here
on list.
doveadm -v -D purge -A
doveadm(user): Error: Corrupted dbox file
/var/spool/mail/user/storage/m.10603 (around offset=7148503): invalid
metadata magic
doveadm(user): Warning: fscking index file
/var/spool/mail/user/storage/dovecot.map.index
doveadm(user): Warning: mdbox /var/spool/mail/user/storage: rebuilding
indexes
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
bc4aa501fc4f7df7ac275f8c79279ff5 in m.2171:525629 (size=2026) and
m.855:946779 (size=1784)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
b48e29a402f8683e7c91f32d16c52936 in m.2086:305158 (size=89091) and
m.2732:614638 (size=88842)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
43d2f95804075dc336d8c4224bbba0b5 in m.2290:1234440 (size=1942) and
m.9021:224875 (size=1943)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
df24cd27a10a8d431e01fabc157e66d0 in m.756:16 (size=47961) and
m.1133:1693832 (size=47960)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
6e196b915f37623455521cc591b15294 in m.2263:63985 (size=2036) and
m.1933:21800 (size=2037)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
7e890f08cef769c1800d24fd2c206c2d in m.2133:1658427 (size=64459) and
m.2268:1012431 (size=64193)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
ab95f2c3b9df8950518e8064f1a89b2a in m.2133:827558 (size=23629) and
m.2268:1304070 (size=23637)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
f4a82d0705e4072908ea4937ff49a6e1 in m.2144:1673818 (size=4380) and
m.1638:2079685 (size=4117)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
82e1f95de0473e0425ce5e81055e6578 in m.1322:16 (size=2264817) and
m.1280:16 (size=2264818)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
144c8f800e3201960cc197ea47169691 in m.2140:1820601 (size=2396) and
m.2003:275867 (size=2127)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
52ea5e1729d92b384efd7b8796c798b5 in m.2268:1774031 (size=5661) and
m.2292:117114 (size=5665)
doveadm(user): Error: Corrupted dbox file
/var/spool/mail/user/storage/m.10603 (around offset=7148503): metadata
header has bad magic value
doveadm(user): Warning: dbox: Copy of the broken file saved to
/var/spool/mail/user/storage/m.10603.broken

Re: purge causing reappearing mails?

[Aki Tuomi via dovecot]

Any idea what pid 7584 is?

Aki

On 2.9.2019 14.08, telsch via dovecot wrote:
> Hello,
>
> today i got reappearing mails again, but not from purging. In the logs i
> only found this. I've got massive problems by many users because
> reappearing mails. If you need more information, i could provide.
>
>
> Sep 02 12:58:43 doveadm: Warning: Transaction log file
> /var/spool/mail//storage/dovecot.map.index.log was locked for 43
> second
> s (mdbox storage rebuild)
> Sep 02 12:58:43 doveadm: Warning: fscking index file
> /var/spool/mail//storage/dovecot.map.index
> Sep 02 12:58:43 doveadm: Warning: mdbox /var/spool/mail//storage:
> rebuilding indexes
> Sep 02 12:59:01 dsync-local(): Error:
> Couldn't lock /var/spool/mail//.dovecot-sync.lock:
> fcntl(/var/spool/mail//.dovecot-sync.lock, write-lock, F_SETLKW)
> locking failed: Timed out after 600 seconds (WRITE lock held by pid 7584)
> Sep 02 12:59:34 doveadm: Warning: Transaction log file
> /var/spool/mail//storage/dovecot.map.index.log was locked for 51
> seconds (mdbox storage rebuild)
> Sep 02 12:59:34 doveadm: Warning: fscking index file
> /var/spool/mail//storage/dovecot.map.index
> Sep 02 12:59:34 doveadm: Warning: fscking index file
> /var/spool/mail//storage/dovecot.map.index
> Sep 02 12:59:35 doveadm: Warning: mdbox /var/spool/mail//storage:
> rebuilding indexes
> Sep 02 13:00:22 doveadm: Warning: Transaction log file
> /var/spool/mail//storage/dovecot.map.index.log was locked for 48
> seconds (mdbox storage rebuild)
> Sep 02 13:00:23 doveadm: Warning: fscking index file
> /var/spool/mail//storage/dovecot.map.index
>
> On 26.08.19 18:06, sch tel via dovecot wrote:
>> Hello,
>> i'm running 2 dovecot 2.3.4.1 servers with replication. once a week
>> purge command is executed. but from time to time it seems there are
>> deleted messages reappering after purge is executed. so i run in debug
>> mode. i saw in the past a few questions about reappearing messages here
>> on list.
>> doveadm -v -D purge -A
>> doveadm(user): Error: Corrupted dbox file
>> /var/spool/mail/user/storage/m.10603 (around offset=7148503): invalid
>> metadata magic
>> doveadm(user): Warning: fscking index file
>> /var/spool/mail/user/storage/dovecot.map.index
>> doveadm(user): Warning: mdbox /var/spool/mail/user/storage: rebuilding
>> indexes
>> doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
>> bc4aa501fc4f7df7ac275f8c79279ff5 in m.2171:525629 (size=2026) and
>> m.855:946779 (size=1784)
>> doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
>> b48e29a402f8683e7c91f32d16c52936 in m.2086:305158 (size=89091) and
>> m.2732:614638 (size=88842)
>> doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
>> 43d2f95804075dc336d8c4224bbba0b5 in m.2290:1234440 (size=1942) and
>> m.9021:224875 (size=1943)
>> doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
>> df24cd27a10a8d431e01fabc157e66d0 in m.756:16 (size=47961) and
>> m.1133:1693832 (size=47960)
>> doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
>> 6e196b915f37623455521cc591b15294 in m.2263:63985 (size=2036) and
>> m.1933:21800 (size=2037)
>> doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
>> 7e890f08cef769c1800d24fd2c206c2d in m.2133:1658427 (size=64459) and
>> m.2268:1012431 (size=64193)
>> doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
>> ab95f2c3b9df8950518e8064f1a89b2a in m.2133:827558 (size=23629) and
>> m.2268:1304070 (size=23637)
>> doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
>> f4a82d0705e4072908ea4937ff49a6e1 in m.2144:1673818 (size=4380) and
>> m.1638:2079685 (size=4117)
>> doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
>> 82e1f95de0473e0425ce5e81055e6578 in m.1322:16 (size=2264817) and
>> m.1280:16 (size=2264818)
>> doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
>> 144c8f800e3201960cc197ea47169691 in m.2140:1820601 (size=2396) and
>> m.2003:275867 (size=2127)
>> doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
>> 52ea5e1729d92b384efd7b8796c798b5 in m.2268:1774031 (size=5661) and
>> m.2292:117114 (size=5665)
>> doveadm(user): Error: Corrupted dbox file
>> /var/spool/mail/user/storage/m.10603 (around offset=7148503): metadata
>> header has bad magic value
>> doveadm(user): Warning: dbox: Copy of the broken file saved to
>> /var/spool/mail/user/storage/m.10603.broken

Re: purge causing reappearing mails?

[telsch via dovecot]

if it's still the same pid, yes:

   7584 13.2  1.5 221168 63508 ?R12:48   3:36
dovecot/doveadm-server

On 02.09.19 13:13, Aki Tuomi via dovecot wrote:

Any idea what pid 7584 is?

Aki

On 2.9.2019 14.08, telsch via dovecot wrote:

Hello,

today i got reappearing mails again, but not from purging. In the logs i
only found this. I've got massive problems by many users because
reappearing mails. If you need more information, i could provide.


Sep 02 12:58:43 doveadm: Warning: Transaction log file
/var/spool/mail//storage/dovecot.map.index.log was locked for 43
second
s (mdbox storage rebuild)
Sep 02 12:58:43 doveadm: Warning: fscking index file
/var/spool/mail//storage/dovecot.map.index
Sep 02 12:58:43 doveadm: Warning: mdbox /var/spool/mail//storage:
rebuilding indexes
Sep 02 12:59:01 dsync-local(): Error:
Couldn't lock /var/spool/mail//.dovecot-sync.lock:
fcntl(/var/spool/mail//.dovecot-sync.lock, write-lock, F_SETLKW)
locking failed: Timed out after 600 seconds (WRITE lock held by pid 7584)
Sep 02 12:59:34 doveadm: Warning: Transaction log file
/var/spool/mail//storage/dovecot.map.index.log was locked for 51
seconds (mdbox storage rebuild)
Sep 02 12:59:34 doveadm: Warning: fscking index file
/var/spool/mail//storage/dovecot.map.index
Sep 02 12:59:34 doveadm: Warning: fscking index file
/var/spool/mail//storage/dovecot.map.index
Sep 02 12:59:35 doveadm: Warning: mdbox /var/spool/mail//storage:
rebuilding indexes
Sep 02 13:00:22 doveadm: Warning: Transaction log file
/var/spool/mail//storage/dovecot.map.index.log was locked for 48
seconds (mdbox storage rebuild)
Sep 02 13:00:23 doveadm: Warning: fscking index file
/var/spool/mail//storage/dovecot.map.index

On 26.08.19 18:06, sch tel via dovecot wrote:

Hello,
i'm running 2 dovecot 2.3.4.1 servers with replication. once a week
purge command is executed. but from time to time it seems there are
deleted messages reappering after purge is executed. so i run in debug
mode. i saw in the past a few questions about reappearing messages here
on list.
doveadm -v -D purge -A
doveadm(user): Error: Corrupted dbox file
/var/spool/mail/user/storage/m.10603 (around offset=7148503): invalid
metadata magic
doveadm(user): Warning: fscking index file
/var/spool/mail/user/storage/dovecot.map.index
doveadm(user): Warning: mdbox /var/spool/mail/user/storage: rebuilding
indexes
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
bc4aa501fc4f7df7ac275f8c79279ff5 in m.2171:525629 (size=2026) and
m.855:946779 (size=1784)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
b48e29a402f8683e7c91f32d16c52936 in m.2086:305158 (size=89091) and
m.2732:614638 (size=88842)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
43d2f95804075dc336d8c4224bbba0b5 in m.2290:1234440 (size=1942) and
m.9021:224875 (size=1943)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
df24cd27a10a8d431e01fabc157e66d0 in m.756:16 (size=47961) and
m.1133:1693832 (size=47960)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
6e196b915f37623455521cc591b15294 in m.2263:63985 (size=2036) and
m.1933:21800 (size=2037)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
7e890f08cef769c1800d24fd2c206c2d in m.2133:1658427 (size=64459) and
m.2268:1012431 (size=64193)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
ab95f2c3b9df8950518e8064f1a89b2a in m.2133:827558 (size=23629) and
m.2268:1304070 (size=23637)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
f4a82d0705e4072908ea4937ff49a6e1 in m.2144:1673818 (size=4380) and
m.1638:2079685 (size=4117)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
82e1f95de0473e0425ce5e81055e6578 in m.1322:16 (size=2264817) and
m.1280:16 (size=2264818)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
144c8f800e3201960cc197ea47169691 in m.2140:1820601 (size=2396) and
m.2003:275867 (size=2127)
doveadm(user): Error: mdbox /var/spool/mail/user/storage: Duplicate GUID
52ea5e1729d92b384efd7b8796c798b5 in m.2268:1774031 (size=5661) and
m.2292:117114 (size=5665)
doveadm(user): Error: Corrupted dbox file
/var/spool/mail/user/storage/m.10603 (around offset=7148503): metadata
header has bad magic value
doveadm(user): Warning: dbox: Copy of the broken file saved to
/var/spool/mail/user/storage/m.10603.broken

dovecot 2.2 repo

[Bas van Rooijen via dovecot]

Hi,

>From the v2.2.36.4 announcement message: "Binary packages are available at 
>https://repo.dovecot.org/";

My question is, where exactly? There's an instruction at repo.dovecot.org that 
tells you to replace 'ce-latest-2.3' with 'ce-' but the given url 
doesn't even contain 'ce-latest-2.3' and http://repo.dovecot.org/ce-2.2.36 
returns a 404.

Thanks in advance!
bvr.

Re: dovecot 2.2 repo

[Aki Tuomi via dovecot]

On 2.9.2019 14.27, Bas van Rooijen via dovecot wrote:
> Hi,
>
> From the v2.2.36.4 announcement message: "Binary packages are available at 
> https://repo.dovecot.org/";
>
> My question is, where exactly? There's an instruction at repo.dovecot.org 
> that tells you to replace 'ce-latest-2.3' with 'ce-' but the given 
> url doesn't even contain 'ce-latest-2.3' and 
> http://repo.dovecot.org/ce-2.2.36 returns a 404.
>
> Thanks in advance!
> bvr.


Should not copy-paste messages. I thought I removed that from the
2.2.36.4 announcement. Sorry, there are no 2.2 binary packages on
repo.dovecot.org.

Aki

dovecot 2.2 repo

[bvr--- via dovecot]

On 9/2/19 1:32 PM, Aki Tuomi via dovecot wrote:
> On 2.9.2019 14.27, Bas van Rooijen via dovecot wrote:
>> Hi,
>>
>> From the v2.2.36.4 announcement message: "Binary packages are available at 
>> https://repo.dovecot.org/";
>>
>> My question is, where exactly? There's an instruction at repo.dovecot.org 
>> that tells you to replace 'ce-latest-2.3' with 'ce-' but the given 
>> url doesn't even contain 'ce-latest-2.3' and 
>> http://repo.dovecot.org/ce-2.2.36 returns a 404.
>>
>> Thanks in advance!
>> bvr.
> 
> 
> Should not copy-paste messages. I thought I removed that from the
> 2.2.36.4 announcement. Sorry, there are no 2.2 binary packages on
> repo.dovecot.org.

No problem, thanks for the info!

greets,
bvr.

dsync and altpath on shared storage.

[Peter Mogensen via dovecot]

Hi,

I was wondering...

If one had mdbox ALT path set to a shared storage mount (say, on NFS)
and one wanted to move a mailbox to a different host... I guess it in
principle wouldn't be necessary to copy all the ALT storage through
dsync, when the volume could just be mounted on the new host.

Is there anyway for dsync to avoid moving Gigabytes of data for could
just be "moved" by moving the mount?

/Peter

Repo for Debian-Buster

[slater.ch via dovecot]

Hi,

is there already a release date for Debian Buster packages?

kind regards

Christian

Re: dsync and altpath on shared storage.

[Sami Ketola via dovecot]

> On 2 Sep 2019, at 15.25, Peter Mogensen via dovecot  
> wrote:
> 
> Hi,
> 
> I was wondering...
> 
> If one had mdbox ALT path set to a shared storage mount (say, on NFS)
> and one wanted to move a mailbox to a different host... I guess it in
> principle wouldn't be necessary to copy all the ALT storage through
> dsync, when the volume could just be mounted on the new host.
> 
> Is there anyway for dsync to avoid moving Gigabytes of data for could
> just be "moved" by moving the mount?


Not tested but you can probably do something like this in the target server:

doveadm backup -u victim -R ssh sudouser@old-server "sudo doveadm dsync-server 
-o mail_location=sdbox:/location-to-your-sdbox/ -u victim"

just leave ALT storage path from the setting.

Sami

Sieve vacation :addresses match only case-sensitive?

[Philipp Faeustlin via dovecot]

The recipients in the vacation :addresses String list are matched 
case-sensitive.


If the recipient gets a mail with wrong case, the message is discarded with:
"discarding vacation response for implicitly delivered message; no known 
(envelope) recipient address found in message headers"


I think the matching should be case-insensitive.

Is this a bug or do I miss some option?

I'm using Dovecot 2.3.7.2, Pigeonhole version 0.5.7.2.

--
Philipp Fäustlin



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Message delivered twice caused by an LMTP error "Got unexpected reply" during upgrade to 2.3

[Gabriele Nencioni via dovecot]

On 10/8/18 5:33 PM, Stephan Bosch wrote:
> Op 8-10-2018 om 11:43 schreef Gabriele Nencioni:
>> On 8/17/18 8:17 AM, Gabriele Nencioni wrote:
>>> On 08/16/2018 11:48 PM, Stephan Bosch wrote:
 Op 16/08/2018 om 12:01 schreef Stephan Bosch:
> I have a theory. Will try something later today.
 Yes, I can reproduce the problem. I am working on a fix.
>>> Thank you very much!
>>> I'm here if you need something.
>> Hi,
>> does the release 2.3.3 fix this problem?
> 
> Unfortunately, no.
> 
> Regards,
> 
> Stephan.


Hi Stephan,
does the release v2.2.36.4 or v2.3.7.2 fix this problem?

Thanks in advance
Regards,
-- 
Gabriele Nencioni

Experimental docker images

[aki.tuomi--- via dovecot]

Hi,

you can now find experimental Docker images for dovecot CE releases (starting 
from 2.3.7.2) from

https://hub.docker.com/r/dovecot/dovecot

You can find instructions and more details on the repository page.

Aki


signature.asc
Description: PGP signature

Re: dovecot 2.2 repo

[Peter via dovecot]

On 2/09/19 11:53 PM, bvr--- via dovecot wrote:

Sorry, there are no 2.2 binary packages on
repo.dovecot.org.


No problem, thanks for the info!


GhettoForge has 2.2 packages for CentOS / RHEL / SL, etc in the gf-plus 
repostitory:


www.ghettoforge.org


Peter

How are imap images supposed to be stored

[d.gentner--- via dovecot]

Hello.

This is a question about the imap protocol, since I am having a hard 
time finding these things out, so I hope you guys can help me.  We are 
using Dovecot to receive mails and having an issue with Thunderbird.
Basically, we are running into this bug with a lot of people: 
https://bugzilla.mozilla.org/show_bug.cgi?id=216308.



The gist of it is, that sometimes, when there is an image linked with 
the imap:// protocol in the mail, then Thunderbird wants to subscribe to 
the folder that contains this mail, but fails.
If I pull the mail off the server, it also has that link in the raw 
mail.  However, most mails store the images as a base64 code block.


I  have actually seen mails getting changed over night, from imap:// 
links to base64 code blocks, but I can't reproduce that. All computers 
are supposed to have the same Thunderbird version and they do.


My questions right now are:

* Speaking about the general imap/mail protocol, do mails store images 
as base64 or imap:// links. What is the standard here?
* Is there anything we can do to prevent Thunderbird from running into 
this bug? We are using Dovecot 2.2.36.4
* What can cause an email getting changed over night or getting synced 
back with the base64 blocks? It was already read, when we ran into the 
issue.


With best regards,

Domeniko Gentner