Re: Replication going away?

[David Morsberger]

In order to prepare for the upcoming release:

Is there an estimated release date when replication will be removed?

What is the best way (reconfigure, turn off auto replication, etc.) to migrate 
to an environment to test and run using ‘doveadm sync -d’ in a scheduled job 
(e.g., cron)? 



Sent from my iPad

> On Jul 18, 2023, at 9:42 AM, Aki Tuomi via dovecot  
> wrote:
> 
> 
>> On 18/07/2023 15:19 EEST i...@joergschulz.de wrote:
>> 
>> 
>> Just to understand that correctly: I could setup a (cron) based process for 
>> doveadm sync, but no longer a setup like 
>> plugin { 
>>  mail_replica = tcp:$IMAP_REPLICA_SERVER:$IMAP_REPLICA_PORT 
>> } 
>> where the cron would lead to some delay and would have to check for 
>> concurrent jobs?
> 
> You can also have that too.
> 
> doveadm sync -d 
> 
> makes it use mail_replica setting.
> 
> Aki
> ___
> dovecot mailing list -- dovecot@dovecot.org
> To unsubscribe send an email to dovecot-le...@dovecot.org
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: Replicator Failure

[David Morsberger]

Resolved

There was a network glitch that resulted in the two nodes to not be able to 
reach each other. It started working after I restarted a network on one of the 
hosts.

David 

> On Sep 19, 2022, at 8:59 AM, David Morsberger  wrote:
> 
> I didn’t see anything useful when setting  mail_debug=true 
> 
> Sent from my iPhone
> 
>> On Sep 19, 2022, at 08:13, David Morsberger  wrote:
>> 
>> Hello,
>> 
>> I recently noticed the following errors in my log file and replicator status 
>> shows all accounts failed.  I am seeing the same error on both hosts. 
>> 
>> "dovecot: doveadm(n...@domain.com): Fatal: connect(192.168.1.250:12345) 
>> failed: Interrupted system call”
>> 
>> # doveadm replicator status
>> Queued 'sync' requests0  
>>
>> Queued 'high' requests0  
>>
>> Queued 'low' requests 0  
>>
>> Queued 'failed' requests  0  
>>
>> Queued 'full resync' requests 0  
>>
>> Waiting 'failed' requests 8  
>>
>> Total number of known users   8 
>> 
>> Replication used to work and I do not know when it started failing. 
>> 
>> I restarted dovecot on both hosts to no avail. 
>> 
>> Any idea on how to get more information and resolve this issue? I cannot 
>> find anything else in the logs 
>> 
>> David

Re: Replicator Failure

[David Morsberger]

I didn’t see anything useful when setting  mail_debug=true 

Sent from my iPhone

> On Sep 19, 2022, at 08:13, David Morsberger  wrote:
> 
> Hello,
> 
> I recently noticed the following errors in my log file and replicator status 
> shows all accounts failed.  I am seeing the same error on both hosts. 
> 
> "dovecot: doveadm(n...@domain.com): Fatal: connect(192.168.1.250:12345) 
> failed: Interrupted system call”
> 
> # doveadm replicator status
> Queued 'sync' requests0   
>   
> Queued 'high' requests0   
>   
> Queued 'low' requests 0   
>   
> Queued 'failed' requests  0   
>   
> Queued 'full resync' requests 0   
>   
> Waiting 'failed' requests 8   
>   
> Total number of known users   8 
> 
> Replication used to work and I do not know when it started failing. 
> 
> I restarted dovecot on both hosts to no avail. 
> 
> Any idea on how to get more information and resolve this issue? I cannot find 
> anything else in the logs 
> 
> David

Replicator Failure

[David Morsberger]

Hello,

I recently noticed the following errors in my log file and replicator status 
shows all accounts failed.  I am seeing the same error on both hosts. 

"dovecot: doveadm(n...@domain.com): Fatal: connect(192.168.1.250:12345) failed: 
Interrupted system call”

# doveadm replicator status
Queued 'sync' requests0 

Queued 'high' requests0 

Queued 'low' requests 0 

Queued 'failed' requests  0 

Queued 'full resync' requests 0 

Waiting 'failed' requests 8 

Total number of known users   8 

Replication used to work and I do not know when it started failing. 

I restarted dovecot on both hosts to no avail. 

Any idea on how to get more information and resolve this issue? I cannot find 
anything else in the logs 

David

LDA File Permissions

[David Morsberger]

All,

I am looking for an easy way to setup LDA so that it creates files with group 
read permission. Currently LDA/Sieve create the '.dovecot.lda-dupes’ file with 
‘0600’. My backup process needs to be able to read the file because it runs as 
a user that is in the same group as the LDA process. I looked into the source 
code and the file is opened with mode ‘0666’ as "

fd = open(lock_info->lock_path, O_RDWR | O_EXCL | O_CREAT, 0666);

This implies it is a umask issue.

What is the best way to view and set the umask value for the LDA process on 
Ubuntu 20.04?

Thanks,
David 

Re: Monitoring Dovecot Replication

[David Morsberger]

Oliver,

What’s your observable event that indicates replication has failed or is 
behind? Log message? Different file checksums?

David 

> On Feb 18, 2021, at 10:54 AM, MK  wrote:
> 
> Hello Andrea,
> 
> thanks for sharing your script to the community.
> 
> But think your script does not solve my problem. Monitoring failed 
> replication with the output of "doveadm replicator status"
> I have allready tried. In my opinion there is nothing in this output and also 
> in other status output I found that shows me the
> user that failed longer time and where the replication process does not solve 
> this failure by itself. 
> I'm searching for something that shows me an alarm if dovecot could not fix a 
> replication by itself
> after > 10 min. With my experience the most replication failures where fixed 
> by dovecot automatically
> in under 10 min. Because dovecot starts every 5min another try. 
> Or did you have a logic outside this script, maybe in Check_MK that knows 
> when a user is greater than 10 min 
> out of replication or something like hat? Until now I don't unterstand how 
> this works for you as monitoring the 
> replication. 
> 
> To understand my side better. We are using OpenNMS to monior our servers and 
> in this case I would use a 
> nrpe check on the cluster to monitor this. OpenNMS polls this check every 5 
> min and if it gives a fail result
> I have an alarm. Maybe this helps a little bit to understand my problem.
> 
> Regards,
> Oliver
> 
> -Ursprüngliche Nachricht-
> Von: dovecot [mailto:dovecot-boun...@dovecot.org] Im Auftrag von Andrea 
> Gabellini
> Gesendet: Montag, 15. Februar 2021 11:04
> An: Steven Varco; dovecot@dovecot.org
> Betreff: Re: Monitoring Dovecot Replication
> 
> Hello,
> 
> here my script. I'm not a professional programmer... ;-)
> 
> Andrea
> 
> Il 12/02/21 17:53, Steven Varco ha scritto:
>> Hi Andrea
>> 
>> It would be great if oyu could post that here, as I (and possibly others) 
>> would also be interested. :)
>> 
>> thanks,
>> Steven
>> 
> 
> -- 
> __
> hAS ANYONE SEEN MY cAPSLOCK KEY?
> __
> 
> TIM San Marino S.p.A.
> Andrea Gabellini
> Engineering R&D
> TIM San Marino S.p.A. - https://www.telecomitalia.sm
> Via Ventotto Luglio, 212 - Piano -2
> 47893 - Borgo Maggiore - Republic of San Marino
> Tel: (+378) 0549 886237
> Fax: (+378) 0549 886188
> 
> 
> 
> --
> Informativa Privacy
> 
> Questa email ha per destinatari dei contatti presenti negli archivi di TIM 
> San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel 
> rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 
> 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione 
> dei vostri dati presenti nei nostri archivi potete inviare una email a 
> priv...@telecomitalia.sm.
> 
> Avviso di Riservatezza
> 
> Il contenuto di questa e-mail e degli eventuali allegati e' strettamente 
> confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete 
> ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo 
> immediatamente e di cancellarla dal vostro computer. E' fatto divieto di 
> copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo 
> delle informazioni qui contenute da parte di persone terze o comunque non 
> indicate nella presente e-mail potra' essere perseguito ai sensi di legge.

Re: Initial Replication

[David Morsberger]

Thanks Ross! Your instructions worked like a charm. 

I’ve been monitoring both sides for days and everything looks great. 

Sent from my iPhone

> On Dec 29, 2020, at 15:30, Marc Roos  wrote:
> 
> 
> 
> Hi David, 
> 
> Afaik you have to put the 'old' emails before replicating on both, 
> because replicating only works on new arriving.
> 
> I just migrated to a server on a different platform keeping same os and 
> dovecot version. One namespace had mbox storage which on the new server 
> became mdbox.
> 
> For the mbox -> mdbox namespace I used this
> 
> doveadm backup -f -n inbox -F /root/backup-accounts.txt 
> tcp:mailXX.local:542
> 
> Test first with one account, depending on the permissions of the 
> directories on the destination, dovecot will create all the files.
> 
> I had a 2nd namespace that I needed to migrate that was already in 
> mdbox. I decided the rsync that, because here it was 2 days vs 5 hours 
> syncing.
> 
> After the rsync I did again the backup on that namespace
> 
> doveadm backup -f -n Archive -F /root/backup-accounts.txt 
> tcp:mailXX.local:542
> 
> Then I ran a script counting messages in mailboxes of all users on both 
> servers and a diff showed that everything was ok.
> 
> I guess if you handle it like this you will not loose a message. ;)
> 
> 
> 
> 
> -Original Message-
> From: David Morsberger [mailto:da...@mmpcrofton.com] 
> Sent: 29 December 2020 20:09
> To: dovecot mailing list
> Subject: Initial Replication
> 
> I searched the archives and do not see a question/answer for this. 
> 
> Should I perform a set of ordered steps after setting up replication? I 
> have setup dovecot on both ends with identical config except for the 
> remote hostname. 
> 
> Main concern is the existing server gets replicated to the new server. I 
> want nothing from new server replicated to the old server. Risking 
> "Trial and error" and "crossing fingers doesnt work with production 
> emails
> 
> Specifically:
> 
> Do I need to setup the mail directories for the various virtual users on 
> the remote? If so, do the directories need to empty?
> 
> Should I initially do a manually one-way synch using doveadm from the 
> existing server? If so, is there a way of turning off automatic 
> replication while the manual one runs?
> 
> Anything else?
> 
> T
> 
> David 
> 

Initial Replication

[David Morsberger]

I searched the archives and do not see a question/answer for this. 

Should I perform a set of ordered steps after setting up replication? I have 
setup dovecot on both ends with identical config except for the remote 
hostname. 

Main concern is the existing server gets replicated to the new server. I want 
nothing from new server replicated to the old server. Risking "Trial and error" 
and "crossing fingers” doesn’t work with production emails

Specifically:

Do I need to setup the mail directories for the various virtual users on the 
remote? If so, do the directories need to empty?

Should I initially do a manually one-way synch using doveadm from the existing 
server? If so, is there a way of turning off automatic replication while the 
manual one runs?

Anything else?

T

David 

Re: Using dovecot with RoundCubeMail - where is the information for new mail in (blue coloured) directories?

[David Morsberger]

Phil,

I looked around and this is deep in the Roundcube service side code. It is 
detecting a new message in a folder since the last time you viewed the contents 
of the folder.  

I see has the folder list items are changed through css and how the server side 
code is receiving the request to check for recent. It get complicated after 
that. I cannot determine if it is keep state in roundcube or making a call to 
the IMAP provider. I am leaning to roundcube state. 

> On Dec 19, 2020, at 12:19 AM, Philip Rhoades  wrote:
> 
> David,
> 
> 
> On 2020-12-19 00:08, David Morsberger wrote:
>> Phil,
>> Are you trying to find out how dovecot marks emails as unread?
> 
> 
> No - I am trying to work out how New Unread Mails are highlighted in blue - 
> see the attached partial screen capture - the two blue-highlighted RCM 
> folders are highlighted in blue AND are also in bold - folders with OLD but 
> UNREAD mails are just in bold.
> 
> I want to create a script or find out some way of marking a folder blue 
> according to the datestamp of the most recent mail in the folder.
> 
> Does that make sense?
> 
> Thanks,
> 
> Phil.
> 
> 
>> Assuming you are using maildir format, it appears to be encoded as
>> flags in the email filename on disk.
>> It’s briefly covered in 'Filename examples'
>> https://wiki2.dovecot.org/MailboxFormat/Maildir
>> And in 'What can I put in info?'
>> https://cr.yp.to/proto/maildir.html
>>> On Dec 17, 2020, at 7:12 PM, Philip Rhoades 
>>> wrote:
>>> Benny,
>>> On 2020-12-18 09:28, Benny Pedersen wrote:
>>> Philip Rhoades skrev den 2020-12-17 22:14:
>>> Every few years I try to work this problem out
>>> User-Agent: Roundcube Webmail/1.4-rc1
>>> please upgrade first
>> It is a long-standing problem and upgrading RCM is not a solution . .
>>>> - occasionally I would
>>>> like to re-mark a dir as having new mail so that the dir shows up
>>>> as
>>>> blue-coloured in RCM.
>>> please dont modify mails outside of imap protocol,
>> Then how do I do what I want with IMAP?
>>> if you use
>>> roundcube it will not be needed to mangle shell accounts
>> That comment doesn't make sense . .
>>>> Every time I Google in vain and then have a go
>>>> at working it out myself
>>> if google have no answer to it, its simple not supported
>> Quite frequently not true . .
>>>> but the only thing I can see is that there is
>>>> a change in the appropriate dir dovecot.index.log file after
>>>> having
>>>> the blue dir clicked on
>>> dont mangle files outside of imap protocol
>> You already said that - what is your solution then?
>>>> (and the colour of the dir name changes back
>>>> to black) - so is the information stored somewhere in RCM itself?
>>> no
>> OK, overall not a very helpful response . . but thanks anyway.
>> P.
>> --
>> Philip Rhoades
>> PO Box 896
>> Cowra  NSW  2794
>> Australia
>> E-mail:  p...@pricom.com.au
> 
> -- 
> Philip Rhoades
> 
> PO Box 896
> Cowra  NSW  2794
> Australia
> E-mail:  p...@pricom.com.au 
> <mailto:p...@pricom.com.au>

Re: Using dovecot with RoundCubeMail - where is the information for new mail in (blue coloured) directories?

[David Morsberger]

Phil,

Are you trying to find out how dovecot marks emails as unread?

Assuming you are using maildir format, it appears to be encoded as flags in the 
email filename on disk. 


It’s briefly covered in 'Filename examples'
https://wiki2.dovecot.org/MailboxFormat/Maildir 


And in 'What can I put in info?'
https://cr.yp.to/proto/maildir.html 



> On Dec 17, 2020, at 7:12 PM, Philip Rhoades  wrote:
> 
> Benny,
> 
> 
> On 2020-12-18 09:28, Benny Pedersen wrote:
>> Philip Rhoades skrev den 2020-12-17 22:14:
>>> Every few years I try to work this problem out
>> User-Agent: Roundcube Webmail/1.4-rc1
>> please upgrade first
> 
> 
> It is a long-standing problem and upgrading RCM is not a solution . .
> 
> 
>>> - occasionally I would
>>> like to re-mark a dir as having new mail so that the dir shows up as
>>> blue-coloured in RCM.
>> please dont modify mails outside of imap protocol,
> 
> 
> Then how do I do what I want with IMAP?
> 
> 
>> if you use
>> roundcube it will not be needed to mangle shell accounts
> 
> 
> That comment doesn't make sense . .
> 
> 
>>> Every time I Google in vain and then have a go
>>> at working it out myself
>> if google have no answer to it, its simple not supported
> 
> 
> Quite frequently not true . .
> 
> 
>>> but the only thing I can see is that there is
>>> a change in the appropriate dir dovecot.index.log file after having
>>> the blue dir clicked on
>> dont mangle files outside of imap protocol
> 
> 
> You already said that - what is your solution then?
> 
> 
>>> (and the colour of the dir name changes back
>>> to black) - so is the information stored somewhere in RCM itself?
>> no
> 
> 
> OK, overall not a very helpful response . . but thanks anyway.
> 
> P.
> -- 
> Philip Rhoades
> 
> PO Box 896
> Cowra  NSW  2794
> Australia
> E-mail:  p...@pricom.com.au

Re: Files in tmp directory

[David Morsberger]

The files in the tmp directory were not showing up in my mailbox. 

I resolved both using the following technique. Anyone can see the solution in 
the archives if they run into the same situation.

Create a temporary mailbox (.INBOX.tmp_email).

For each mailbox that had an issue, Items 1) and 2) below)
   Move in Linux (mv command) all suspect files from 1) and 2) below into the 
.INBOX.tmp_email/cur directory. 

   Use mail client to move the messages from tmp_email mailbox to the . 

   Verify in Linux that the files are correctly formatted in the /cur directory

Everything is running smoothly now.

David 

> On Nov 29, 2020, at 4:09 PM, Aki Tuomi  wrote:
> 
> Not sure if this actually has any impact, do you get an error?
> 
> Aki
> 
>> On 29/11/2020 20:02 David Morsberger  wrote:
>> 
>> 
>> Ping - anyone know how I should clean up my “mess”? :) 
>> 
>> 
>> 
>>> On Nov 26, 2020, at 7:42 PM, David Morsberger  wrote:
>>> 
>>> 
>>> I had to restore many thousands of dovecot emails from a crashed Mac Server 
>>> to a new Ubuntu server. After completing I am noticing a few things that 
>>> may be okay or may need to be fixed.
>>> 
>>> 1) a couple of mailboxes have a lot (one has 102462) emails in the tmp 
>>> directory. The files do not have the standard Mairdir++ filename format. An 
>>> example:
>>> 1581262582.M397740P72267.mini.mmpcrofton.com 
>>> (http://1581262582.m397740p72267.mini.mmpcrofton.com/) (missing the stuff 
>>> at the end,,S=,W=:2,S)
>>> 
>>> 2) I see files in the cur directory that do not have the Maildir++ format. 
>>> An example:
>>> 1601287326.V810Ie80087M240104.mmp-mail.mmpcrofton.com 
>>> (http://1601287326.v810ie80087m240104.mmp-mail.mmpcrofton.com/):2,S. (do 
>>> not have the,S=,W= values and the second value, V810Ie80087M240104, is 
>>> longer that the other file names)
>>> 
>>> 
>>> How do I get the emails in (1) out of tmp?
>>> 
>>> Do I need to convert the emails in (2)?
>>> 
>>> David
>> 

Re: Files in tmp directory

[David Morsberger]

Ping - anyone know how I should clean up my “mess”? :) 

> On Nov 26, 2020, at 7:42 PM, David Morsberger  wrote:
> 
> I had to restore many thousands of dovecot emails from a crashed Mac Server 
> to a new Ubuntu server. After completing I am noticing a few things that may 
> be okay or may need to be fixed.
> 
> 1) a couple of mailboxes have a lot (one has 102462) emails in the tmp 
> directory. The files do not have the standard Mairdir++ filename format. An 
> example:
>  1581262582.M397740P72267.mini.mmpcrofton.com 
> <http://1581262582.m397740p72267.mini.mmpcrofton.com/>  (missing the stuff at 
> the end, ,S=,W=:2,S)
> 
> 2) I see files in the cur directory that do not have the Maildir++ format. An 
> example:
>  1601287326.V810Ie80087M240104.mmp-mail.mmpcrofton.com 
> <http://1601287326.v810ie80087m240104.mmp-mail.mmpcrofton.com/>:2,S. (do not 
> have the ,S=,W= values and the second value, V810Ie80087M240104, is longer 
> that the other file names)
> 
> 
> How do I get the emails in (1) out of tmp?
> 
> Do I need to convert the emails in (2)?
> 
> David 

Files in tmp directory

[David Morsberger]

I had to restore many thousands of dovecot emails from a crashed Mac Server to 
a new Ubuntu server. After completing I am noticing a few things that may be 
okay or may need to be fixed.

1) a couple of mailboxes have a lot (one has 102462) emails in the tmp 
directory. The files do not have the standard Mairdir++ filename format. An 
example:
 1581262582.M397740P72267.mini.mmpcrofton.com 
  (missing the stuff at 
the end, ,S=,W=:2,S)

2) I see files in the cur directory that do not have the Maildir++ format. An 
example:
 1601287326.V810Ie80087M240104.mmp-mail.mmpcrofton.com:2,S. (do not have 
the ,S=,W= values and the second value, V810Ie80087M240104, is longer that the 
other file names)


How do I get the emails in (1) out of tmp?

Do I need to convert the emails in (2)?

David 

Re: LMTP Authentication Error

[David Morsberger]

Mark,

Thanks! You pointed me in the right direction.

It works and I always like posting the final solution. 

Here is what I have in my 10-master.conf

  unix_listener auth-userdb {
#group =
#mode = 0666
#user = $default_internal_user
  }
  unix_listener auth-userdb-postfix {
path = /var/spool/postfix/private/auth
user = postfix
group = postfix
mode = 0666
  }

Adding what you recommended verbatim created a duplicate auth-userdb error. I 
think because it was due to the default value with the same path. 

The auth section from doveconf:

service auth {
  chroot = 
  client_limit = 0
  drop_priv_before_exec = no
  executable = auth
  extra_groups = 
  group = 
  idle_kill = 0
  privileged_group = 
  process_limit = 1
  process_min_avail = 0
  protocol = 
  service_count = 0
  type = 
  unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0666
user = postfix
  }
  unix_listener auth-client {
group = 
mode = 0600
user = $default_internal_user
  }
  unix_listener auth-login {
group = 
mode = 0600
user = $default_internal_user
  }
  unix_listener auth-master {
group = 
mode = 0600
user = 
  }
  unix_listener auth-userdb {
group = 
mode = 0666
user = $default_internal_user
  }
  unix_listener login/login {
group = 
mode = 0666
user = 
  }
  unix_listener token-login/tokenlogin {
group = 
mode = 0666
user = 
  }
  user = $default_internal_user
  vsz_limit = 18446744073709551615 B
}


> On Oct 11, 2020, at 4:10 PM, Mark Moseley  wrote:
> 
> 
> 
> On Sat, Oct 10, 2020 at 12:08 PM David Morsberger  <mailto:da...@mmpcrofton.com>> wrote:
> I wish someone could help me. I’m trying to track auth in the lmtp code. Nice 
> code base but I’m having trouble tracking the call stack for the error 
> 
> Sent from my iPhone
> 
> > On Oct 9, 2020, at 08:00, David Morsberger  > <mailto:da...@mmpcrofton.com>> wrote:
> > 
> > Alexander,
> > 
> > Do you see anything wrong in my config?
> > 
> > David 
> > 
> > Sent from my iPhone
> > 
> >> On Oct 7, 2020, at 18:19, David Morsberger  >> <mailto:da...@mmpcrofton.com>> wrote:
> >> On 2020-10-07 12:43, Alexander Dalloz wrote:
> >>>>> Am 07.10.2020 um 18:20 schrieb da...@mmpcrofton.com 
> >>>>> <mailto:da...@mmpcrofton.com>:
> >>>>> Any ideas on how to resolve the Userdb connect/lookup problem? My users 
> >>>>> are pinging me on Sieve support.
> >>>>> Thanks,
> >>>>> David
> >>> Provide a full output of "doveconf -n"?
> >>> Alexander
> >> Alexandar,
> >> Thanks and here you go.
> >> # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
> >> # Pigeonhole version 0.5.7.2 ()
> >> # OS: Linux 5.4.0-48-generic x86_64 Ubuntu 20.04.1 LTS
> >> # Hostname: mmp-mail.mmpcrofton.com <http://mmp-mail.mmpcrofton.com/>
> >> base_dir = /var/run/dovecot/
> >> first_valid_uid = 150
> >> login_greeting = Dovecot ready.
> >> mail_gid = 150
> >> mail_location = mbox:~/mail:INBOX=/var/mail/%u
> >> mail_privileged_group = mail
> >> mail_uid = 150
> >> 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 index ihave 
> >> duplicate mime foreverypart extracttext
> >> namespace inbox {
> >> inbox = yes
> >> location =
> >> mailbox Drafts {
> >> auto = subscribe
> >> special_use = \Drafts
> >> }
> >> mailbox Junk {
> >> auto = subscribe
> >> special_use = \Junk
> >> }
> >> mailbox Sent {
> >> auto = subscribe
> >> special_use = \Sent
> >> }
> >> mailbox "Sent Messages" {
> >> auto = no
> >> special_use = \Sent
> >> }
> >> mailbox Spam {
> >> auto = create
> >> special_use = \Junk
> >> }
> >> mailbox Trash {
> >> auto = subscribe
> >> special_use = \Trash
> >> }
> >> prefix =
> >> }
> >> passdb {
> >> args = /etc/dovecot/dovecot-sql.conf.ext
> >> driver = sql
> >> }
> >> plugin {
> >> sieve = file:/home/mail/rules/%u/;active=/home/mail/rules/%u/.dovecot.sieve
> >> sieve_dir = /home/mail/rules/%u
> >> }
> >> protocols = " imap lmtp sieve pop3 sieve"
> 

Re: LMTP Authentication Error

[David Morsberger]

I wish someone could help me. I’m trying to track auth in the lmtp code. Nice 
code base but I’m having trouble tracking the call stack for the error 

Sent from my iPhone

> On Oct 9, 2020, at 08:00, David Morsberger  wrote:
> 
> Alexander,
> 
> Do you see anything wrong in my config?
> 
> David 
> 
> Sent from my iPhone
> 
>> On Oct 7, 2020, at 18:19, David Morsberger  wrote:
>> On 2020-10-07 12:43, Alexander Dalloz wrote:
>>>>> Am 07.10.2020 um 18:20 schrieb da...@mmpcrofton.com:
>>>>> Any ideas on how to resolve the Userdb connect/lookup problem? My users 
>>>>> are pinging me on Sieve support.
>>>>> Thanks,
>>>>> David
>>> Provide a full output of "doveconf -n"?
>>> Alexander
>> Alexandar,
>> Thanks and here you go.
>> # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
>> # Pigeonhole version 0.5.7.2 ()
>> # OS: Linux 5.4.0-48-generic x86_64 Ubuntu 20.04.1 LTS
>> # Hostname: mmp-mail.mmpcrofton.com
>> base_dir = /var/run/dovecot/
>> first_valid_uid = 150
>> login_greeting = Dovecot ready.
>> mail_gid = 150
>> mail_location = mbox:~/mail:INBOX=/var/mail/%u
>> mail_privileged_group = mail
>> mail_uid = 150
>> 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 index ihave 
>> duplicate mime foreverypart extracttext
>> namespace inbox {
>> inbox = yes
>> location =
>> mailbox Drafts {
>> auto = subscribe
>> special_use = \Drafts
>> }
>> mailbox Junk {
>> auto = subscribe
>> special_use = \Junk
>> }
>> mailbox Sent {
>> auto = subscribe
>> special_use = \Sent
>> }
>> mailbox "Sent Messages" {
>> auto = no
>> special_use = \Sent
>> }
>> mailbox Spam {
>> auto = create
>> special_use = \Junk
>> }
>> mailbox Trash {
>> auto = subscribe
>> special_use = \Trash
>> }
>> prefix =
>> }
>> passdb {
>> args = /etc/dovecot/dovecot-sql.conf.ext
>> driver = sql
>> }
>> plugin {
>> sieve = file:/home/mail/rules/%u/;active=/home/mail/rules/%u/.dovecot.sieve
>> sieve_dir = /home/mail/rules/%u
>> }
>> protocols = " imap lmtp sieve pop3 sieve"
>> service auth {
>> unix_listener /var/spool/postfix/private/auth {
>> group = postfix
>> mode = 0660
>> user = postfix
>> }
>> }
>> service lmtp {
>> unix_listener /var/spool/postfix/private/dovecot-lmtp {
>> group = postfix
>> mode = 0600
>> user = postfix
>> }
>> }
>> ssl = required
>> ssl_cert = > ssl_client_ca_dir = /etc/ssl/certs
>> ssl_dh = # hidden, use -P to show it
>> ssl_key = # hidden, use -P to show it
>> userdb {
>> driver = prefetch
>> }
>> userdb {
>> args = /etc/dovecot/dovecot-sql.conf.ext
>> driver = sql
>> }
>> protocol lmtp {
>> mail_plugins = " sieve"
>> postmaster_address = da...@mmpcrofton.com
>> }
>> protocol imap {
>> mail_max_userip_connections = 50
>> }

Re: LMTP Authentication Error

[David Morsberger]

Alexander,

Do you see anything wrong in my config?

David 

Sent from my iPhone

> On Oct 7, 2020, at 18:19, David Morsberger  wrote:
> 
> On 2020-10-07 12:43, Alexander Dalloz wrote:
>>> Am 07.10.2020 um 18:20 schrieb da...@mmpcrofton.com:
>>> Any ideas on how to resolve the Userdb connect/lookup problem? My users are 
>>> pinging me on Sieve support.
>>> Thanks,
>>> David
>> Provide a full output of "doveconf -n"?
>> Alexander
> 
> Alexandar,
> 
> Thanks and here you go.
> 
> # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.5.7.2 ()
> # OS: Linux 5.4.0-48-generic x86_64 Ubuntu 20.04.1 LTS
> # Hostname: mmp-mail.mmpcrofton.com
> base_dir = /var/run/dovecot/
> first_valid_uid = 150
> login_greeting = Dovecot ready.
> mail_gid = 150
> mail_location = mbox:~/mail:INBOX=/var/mail/%u
> mail_privileged_group = mail
> mail_uid = 150
> 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 index ihave 
> duplicate mime foreverypart extracttext
> namespace inbox {
> inbox = yes
> location =
> mailbox Drafts {
>   auto = subscribe
>   special_use = \Drafts
> }
> mailbox Junk {
>   auto = subscribe
>   special_use = \Junk
> }
> mailbox Sent {
>   auto = subscribe
>   special_use = \Sent
> }
> mailbox "Sent Messages" {
>   auto = no
>   special_use = \Sent
> }
> mailbox Spam {
>   auto = create
>   special_use = \Junk
> }
> mailbox Trash {
>   auto = subscribe
>   special_use = \Trash
> }
> prefix =
> }
> passdb {
> args = /etc/dovecot/dovecot-sql.conf.ext
> driver = sql
> }
> plugin {
> sieve = file:/home/mail/rules/%u/;active=/home/mail/rules/%u/.dovecot.sieve
> sieve_dir = /home/mail/rules/%u
> }
> protocols = " imap lmtp sieve pop3 sieve"
> service auth {
> unix_listener /var/spool/postfix/private/auth {
>   group = postfix
>   mode = 0660
>   user = postfix
> }
> }
> service lmtp {
> unix_listener /var/spool/postfix/private/dovecot-lmtp {
>   group = postfix
>   mode = 0600
>   user = postfix
> }
> }
> ssl = required
> ssl_cert =  ssl_client_ca_dir = /etc/ssl/certs
> ssl_dh = # hidden, use -P to show it
> ssl_key = # hidden, use -P to show it
> userdb {
> driver = prefetch
> }
> userdb {
> args = /etc/dovecot/dovecot-sql.conf.ext
> driver = sql
> }
> protocol lmtp {
> mail_plugins = " sieve"
> postmaster_address = da...@mmpcrofton.com
> }
> protocol imap {
> mail_max_userip_connections = 50
> }

Re: Feature request.

[David Morsberger]

Automatic renewal

The Ubuntu package for certbot comes pre-configured with systemd timer that 
will automatically renew existing certificates. What it does not handle however 
is reloading postfix/dovecot so that they will begin using the new 
certificates. For that, we need to implement a hook.

Certbot has both pre and post hooks that you can use to execute a script prior 
to and after the renewal process. It also has a renew hook that is run whenever 
a certificate is successfully renewed.

Both the renew hook and post hook are good candidates for our reload script. 
Each has a downside however. The post hook will be run after every renewal 
attempt, regardless of if anything was actually renewed or not. This will 
result in the services being reloaded many times for no reason.

The renew hook only runs if a certificate was successfully renewed, but it will 
be run once for each certificate. This could mean reloading services multiple 
times if you have multiple certificates. If you only have a single certificate 
however it'll work great.

In my case I only have a single certificate, so the renew hook is what I'm 
going to use. To setup the hooks a configuration file for certbot needs to be 
created at /etc/letsencrypt/cli.ini. The configuration file consists of simple 
name=value pairs where the name is taken from the list of command line 
parameters.

To configure a renew hook, add the following to the configuration file:

renew-hook = /root/bin/certbot-renew
Next, create the renew hook script at /root/bin/certbot-renew with the 
following contents:

#!/bin/sh
systemctl reload postfix
systemctl reload dovecot

Sent from my iPhone

> On Oct 9, 2020, at 04:17, Rogier Wolff  wrote:
> 
> Hi, 
> 
> I get my Email from my own SMTP server on the internet using
> "fetchmail". Some time ago I did the smart thing and configured
> dovecot to use SSL and the letsencrypt certificate that automatically
> renews.
> 
> Wel. a few days ago my certificate expired and the fetchmail
> deamon running in the background had nowhere to complain. So I didn't
> notice. 
> 
> It turns out that dovecot had been running uninterrupted since august
> 13th, the certificate was renewed on september 7th and I suspect it
> expired on october 7th.
> 
> So Feature request: check the expiry date on the SSL certificate
> as it is being loaded and check for a new certificate if it HAS
> expired.
> 
> If you worry about performance, this could be done where: 
> 
> TLS handshaking: SSL_accept() failed: error:14094415:SSL 
> routines:ssl3_read_bytes:sslv3 alert certificate expired: SSL alert number 45
> 
> is reported. That would mean that ONE client will once get the error
> before dovecot fixes it. My personal fix is to restart dovecot once a
> week from now on.
> 
> I might be running an older version: 
> 
> # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.4.21 (92477967)
> # OS: Linux 4.15.0-34-generic x86_64 Ubuntu 18.04.5 LTS 
> 
> if it has already been fixed, please accept my apologies.
> 
>Roger. 
> 
> -- 
> ** r.e.wo...@bitwizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 **
> **Delftechpark 11 2628 XJ  Delft, The Netherlands.  KVK: 27239233**
> f equals m times a. When your f is steady, and your m is going down
> your a is going up.  -- Chris Hadfield about flying up the space shuttle.

Re: LMTP Authentication Error

[David Morsberger]

On 2020-10-07 12:43, Alexander Dalloz wrote:
> Am 07.10.2020 um 18:20 schrieb da...@mmpcrofton.com:
>> Any ideas on how to resolve the Userdb connect/lookup problem? My users are 
>> pinging me on Sieve support.
>> Thanks,
>> David
> Provide a full output of "doveconf -n"?
> Alexander

Alexandar,

Thanks and here you go.

# 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.7.2 ()
# OS: Linux 5.4.0-48-generic x86_64 Ubuntu 20.04.1 LTS
# Hostname: mmp-mail.mmpcrofton.com
base_dir = /var/run/dovecot/
first_valid_uid = 150
login_greeting = Dovecot ready.
mail_gid = 150
mail_location = mbox:~/mail:INBOX=/var/mail/%u
mail_privileged_group = mail
mail_uid = 150
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 index ihave duplicate 
mime foreverypart extracttext
namespace inbox {
 inbox = yes
 location =
 mailbox Drafts {
   auto = subscribe
   special_use = \Drafts
 }
 mailbox Junk {
   auto = subscribe
   special_use = \Junk
 }
 mailbox Sent {
   auto = subscribe
   special_use = \Sent
 }
 mailbox "Sent Messages" {
   auto = no
   special_use = \Sent
 }
 mailbox Spam {
   auto = create
   special_use = \Junk
 }
 mailbox Trash {
   auto = subscribe
   special_use = \Trash
 }
 prefix =
}
passdb {
 args = /etc/dovecot/dovecot-sql.conf.ext
 driver = sql
}
plugin {
 sieve = file:/home/mail/rules/%u/;active=/home/mail/rules/%u/.dovecot.sieve
 sieve_dir = /home/mail/rules/%u
}
protocols = " imap lmtp sieve pop3 sieve"
service auth {
 unix_listener /var/spool/postfix/private/auth {
   group = postfix
   mode = 0660
   user = postfix
 }
}
service lmtp {
 unix_listener /var/spool/postfix/private/dovecot-lmtp {
   group = postfix
   mode = 0600
   user = postfix
 }
}
ssl = required
ssl_cert = 

LMTP Authentication Error

[David Morsberger]

I am stuck enabling LMTP so that I can use Sieve rules. I have a postfix -> dovecot setup on Ubuntu. I am using virtual users with a SQL backend for virtual_users, password maps, and maildir. I have searched for a solution and implemented everything I have read. I do not understand why lmtp is trying to go to /var/run/dovecot/auth-userdb (file does not exist). Everything works until I uncomment "virtual_transport = lmtp:unix:private/dovecot-lmtp” in postfix/main.cfAnyone have a solution? Here is the lmtp error with surrounding messagesOct  4 00:37:29 mmp-mail dovecot: lmtp(i...@domain.com)<268290>: Debug: auth-master: userdb lookup(i...@domain.com): Started userdb lookupOct  4 00:37:29 mmp-mail dovecot: lmtp(i...@domain.com)<268290>: Debug: auth-master: conn unix:/var/run/dovecot//auth-userdb: ConnectingOct  4 00:37:29 mmp-mail dovecot: lmtp(i...@domain.com)<268290>: Error: auth-master: userdb lookup(i...@domain.com): connect(/var/run/dovecot//auth-userdb) failed: No such file or directoryOct  4 00:37:29 mmp-mail dovecot: lmtp(i...@domain.com)<268290>: Debug: auth-master: userdb lookup(i...@domain.com): Userdb lookup failedOct  4 00:37:29 mmp-mail dovecot: lmtp(268290): Error: lmtp-server: conn unix:pid=268289,uid=129 [1]: rcpt i...@domain.com: Failed to lookup user i...@domain.com: Internal error occurred. Refer to server log for more information.I do see "auth_socket_path = auth-userdb” in doveconf outputIn 10-master.conf (-rw-r--r-- 1 root root  3784 Oct  4 00:26 10-master.conf)service auth {  unix_listener auth-userdb {    path = /var/spool/postfix/private/auth    mode = 0660    user = postfix    group = postfix  }}In auth-sql-conf.ext (-rw-r--r-- 1 root root   785 Oct  3 22:39 auth-sql.conf.ext)userdb {  driver = sql  args = /etc/dovecot/dovecot-sql.conf.ext}In dovecot-sql.conf.ext (-rw-r- 1 root dovecot 6086 Oct  3 22:37 dovecot-sql.conf.ext)user_query = \  SELECT email as user, 150 AS uid, 150 AS gid  'maildir:/home/mail/'||maildir as mail \  FROM virtual_mailbox_maps WHERE email = '%u'

Mac Mojave Server

[David Morsberger]

Is there any information on using dovecot on Mojave? I have been using Mac OS 
Server for a few years and looking for the preferred way to move to Mojave 
since dovecot and postfix admin support has been dropped by Apple. 

Re: [Dovecot] Missing Emails

[David Morsberger]

Sven,

Thanks for the response. 

1. Nobody should be using pop3. The missing email appears to be random. I 
believe pop downloads would delete them all. I have now turned off pop3.

2. Would a mail rule place it in the 'Trash'? I did not find the email on the 
file system. I'm trying a wider search.

3. I followed the instructions on the wiki but it still doesn't appear to be 
logging everything.

conf.d/10-logging.conf

# Log file to use for informational messages. Defaults to log_path.
#info_log_path =
info_log_path = /Library/Logs/Mail/dovecot_info.log
# Log file to use for debug messages. Defaults to info_log_path.
debug_log_path = /Library/Logs/Mail/dovecot_debug.log


mail_plugins = $mail_plugins mail_log notify

plugin {
  # Events to log. Also available: flag_change append
  mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename 
flag_change append
  # Available fields: uid, box, msgid, from, subject, size, vsize, flags
  # size and vsize are available only for expunge and copy events.
  mail_log_fields = uid box msgid size from subject size flags
}

I am not seeing messages of the following form in the dovecot_debug.log or 
dovecot_info.log
imap(user): copy -> Trash: uid=908, msgid=<123.foo@bar>
imap(user): deleted: uid=908, msgid=<123.foo@bar>
imap(user): expunged: uid=908, msgid=<123.foo@bar>


On Dec 27, 2012, at 10:54 PM, Sven Hartge  wrote:

> David Morsberger  wrote:
> 
>> I reported a problem with disappearing emails on my Apple Mountain
>> Lion server. Not sure if it ever stopped but I do know it is happening
>> again.
> 
>> Help This is a company email server. They live and die by their
>> emails. 
> 
>> Emails show up in inbox and then disappear. 
> 
>> Anyone know why our emails are disappearing?
> 
> You should configure the mail_log plugin to log all actions clients do
> to your mails: http://wiki2.dovecot.org/Plugins/MailLog
> 
> I've had to debug similar problems in the past time (on a different IMAP
> server) and in _all_ cases it was something the user did, like having a
> client downloading the mails via POP3 (and forgetting about this) and
> complaining about missing mails from "the Webmailer Website". Or having
> configured a filter inside Thunderbird (and forgetting about this),
> instructing the client to delete mails matching a special rule.
> 
>> I see a reference to it in the dovecot.index.cache file (last item)
> 
> If there is a reference in this file, the mail must have reached
> dovecot. So the next step would be to find out, _what exactly_ the
> client does with it. See mail_log again.
> 
> Grüße,
> Sven.
> 
> -- 
> Sigmentation fault. Core dumped.
> 

[Dovecot] Missing Emails

[David Morsberger]

I reported a problem with disappearing emails on my Apple Mountain Lion server. 
Not sure if it ever stopped but I do know it is happening again.

Help This is a company email server. They live and die by their emails. 

Emails show up in inbox and then disappear. 

Anyone know why our emails are disappearing?

I see a reference to it in the dovecot.index.cache file (last item)

^@^@^@Q^@^@^@0^@^@^@^@^@^@^@Message-ID: 
<1356660917.93498.yahoomail...@web163605.mail.gq1.yahoo.com>
^@^@^@^M^@^@^@7^@^@^@4^@^@^@^@^@^@^@Subject: Funeral program for Eileen 
Zbignewich
^@^E^@^@^@^@^@^@^@^F^@^@^@Z^@^@^@7^@^@^@^@^@^@^@Content-Type: multipart/mixed; 
boundary="-1578497492-264297203-1356660917=:93498"
^@^@^G^@^@^@4^@^@^@1^@^@^@^@^@^@^@Date: Thu, 27 Dec 2012 18:15:17 -0800 (PST)

^@^@^@^@^@^@^@^K^@^@^@^@^@^@^@^L^@^@^@^@^@^@^@^N^@^@^@8^@^@^@5^@^@^@^@^@^@^@To: 
"i...@mmpcrofton.com" 

I searched the filesystem and cannot find them.

bash-3.2# find . -exec grep Zbignewich {} \; -print

Dec 04 00:30:26 master: Info: Dovecot v2.0.19apple1 starting up (core dumps 
disabled)

I believe I turned on all debug and info messages.

Here is what I see in postfix log:

Dec 27 21:15:39 mini.mmpcrofton.com postfix/smtpd[20081]: 3CE164F4420: 
client=pascal.junkemailfilter.com[184.105.182.188]
Dec 27 21:15:39 mini.mmpcrofton.com postfix/cleanup[20086]: 3CE164F4420: 
message-id=<1356660917.93498.yahoomail...@web163605.mail.gq1.yahoo.com>
Dec 27 21:15:40 mini.mmpcrofton.com postfix/qmgr[95]: 3CE164F4420: 
from=, size=307659, nrcpt=1 (queue active)
Dec 27 21:15:40 mini.mmpcrofton.com postfix/smtpd[20081]: disconnect from 
pascal.junkemailfilter.com[184.105.182.188]
Dec 27 21:15:40 mini.mmpcrofton.com postfix/smtpd[20106]: connect from 
localhost[127.0.0.1]
Dec 27 21:15:40 mini.mmpcrofton.com postfix/smtpd[20106]: 5168E4F4447: 
client=localhost[127.0.0.1]
Dec 27 21:15:40 mini.mmpcrofton.com postfix/cleanup[20086]: 5168E4F4447: 
message-id=<1356660917.93498.yahoomail...@web163605.mail.gq1.yahoo.com>
Dec 27 21:15:40 mini.mmpcrofton.com postfix/smtpd[20106]: disconnect from 
localhost[127.0.0.1]
Dec 27 21:15:40 mini.mmpcrofton.com postfix/qmgr[95]: 5168E4F4447: 
from=, size=308299, nrcpt=1 (queue active)
Dec 27 21:15:40 mini.mmpcrofton.com postfix/smtp[20102]: 3CE164F4420: 
to=, relay=127.0.0.1[127.0.0.1]:10024, delay=1.1, 
delays=0.85/0.01/0/0.27, dsn=2.0.0, status=sent (250 2.0.0 from 
MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 5168E4F4447)
Dec 27 21:15:40 mini.mmpcrofton.com postfix/qmgr[95]: 3CE164F4420: removed
Dec 27 21:15:40 mini.mmpcrofton.com postfix/pipe[20110]: 5168E4F4447: 
to=, orig_to=, 
relay=dovecot, delay=0.39, delays=0.03/0.01/0/0.35, dsn=2.0.0, status=sent 
(delivered via dovecot service)
Dec 27 21:15:41 mini.mmpcrofton.com postfix/qmgr[95]: 5168E4F4447: removed

dovecot_info.log
Dec 27 21:15:40 lda(pid 20111 user graphicartist): Info: 
msgid=<1356660917.93498.yahoomail...@web163605.mail.gq1.yahoo.com>: saved mail 
to INBOX
Dec 27 21:15:40 lda(pid 20111 user graphicartist): Info: push-notify: push 
notification enabled
Dec 27 21:15:40 lda(pid 20111 user graphicartist): Info: push-notify: notify: 
graphicartist
Dec 27 21:15:40 lda(pid 20111 user graphicartist): Info: push-notify: data 
sent: 1680


dovecot_debug.log
Dec 27 21:15:40 lda: Debug: Loading modules from directory: 
/Applications/Server.app/Contents/ServerRoot/usr/lib/dovecot
Dec 27 21:15:40 lda: Debug: Module loaded: 
/Applications/Server.app/Contents/ServerRoot/usr/lib/dovecot/lib10_quota_plugin.so
Dec 27 21:15:40 lda: Debug: Module loaded: 
/Applications/Server.app/Contents/ServerRoot/usr/lib/dovecot/lib20_fts_plugin.so
Dec 27 21:15:40 lda: Debug: Module loaded: 
/Applications/Server.app/Contents/ServerRoot/usr/lib/dovecot/lib20_push_notify_plugin.so
Dec 27 21:15:40 lda: Debug: Module loaded: 
/Applications/Server.app/Contents/ServerRoot/usr/lib/dovecot/lib20_zlib_plugin.so
Dec 27 21:15:40 lda: Debug: Module loaded: 
/Applications/Server.app/Contents/ServerRoot/usr/lib/dovecot/lib21_fts_sk_plugin.so
Dec 27 21:15:40 lda: Debug: Module loaded: 
/Applications/Server.app/Contents/ServerRoot/usr/lib/dovecot/lib90_sieve_plugin.so
Dec 27 21:15:40 lda: Debug: auth input: graphicartist uid=214 gid=6 
quota=maildir:User quota:noenforcing quota_rule=*:storage=0 
mail=maildir:/Library/Server/Mail/Data/mail/B5E3E436-DEA0-4D5A-A5DF-34D6AB56FED6
 
mail_location=maildir:/Library/Server/Mail/Data/mail/B5E3E436-DEA0-4D5A-A5DF-34D6AB56FED6
 
sieve=/Library/Server/Mail/Data/rules/B5E3E436-DEA0-4D5A-A5DF-34D6AB56FED6/dovecot.sieve
 sieve_dir=/Library/Server/Mail/Data/rules/B5E3E436-DEA0-4D5A-A5DF-34D6AB56FED6 
sieve_storage=/Library/Server/Mail/Data/rules/B5E3E436-DEA0-4D5A-A5DF-34D6AB56FED6
Dec 27 21:15:40 lda: Debug: Added userdb setting: plugin/quota=maildir:User 
quota:noenforcing
Dec 27 21:15:40 lda: Debug: Added userdb setting: plugin/quota_rule=*:storage=0
Dec 27 21:15:40 lda: Debug: Added userdb setting: 
mail=maildir:/Library/Server/Mail/Data/mail/B5E3E

Re: [Dovecot] Non-dovecot user looking for feedback

[David Morsberger]

Check out:

http://imapwiki.org/ImapTest/ServerStatus

--
David Morsberger
301-758-7387
Sent from my iPhone

On Dec 17, 2012, at 2:00 AM, Chris Ross  wrote:


 I've been using UW-IMAPd for neigh on forever (at least since 2001).  But,
as it's basically stalled, and I'm about to update the hardware that is my
mail server, I thought it was time to review existing open-source IMAP
servers.  Dovecot is the top three in my looking.

 The other of the top three candidates, because I know of people who've
used it, is Cyrus IMAP.  So, I should note that my thoughts are "uw-imapd,
because I already know how to use it", "Cyrus, because someone I know/trust
liked it years ago", and dovecot, because "it seems stable, professional,
and to meet all of my needs".

 I guess the biggest question I have is how files/folders are stored in the
filesystem.  uw-imapd has a "mbx" format that all of my folders are in, and
also has support for mbox and maildir (i think).  mbx had some advantages
for speed access, which would be unimportant I assume with dovecot's
indexes, but IIRC there was also some reason the mbox format coped poorly
with multiple clients accessing the same folder at the same time.

 So, am I right that dovecot supports only the "one big full file" mbox
format, and the maildir format?  And if so, is it known to allow multiple
simultaneous IMAP clients to access and monitor and/or modify the same
folder simultaneously?

 After those questions, it's just a "what do you think the pros and cons of
each are?"  I know asking in this forum, that I will get most if not all
votes for Dovecot. And that's fine, as long as you have specific reasons
why it would be better for someone with only a handful of users and minimal
time available to administer the systems in question.

 Thanks!  I appreciate any and all feedback.

- Chris

Re: [Dovecot] Missing Messages on IOS device

[David Morsberger]

I checked again and I did not see any log entries on the server or client. Not 
sure how to debug iPhone/iPad.

I'm sure this isn't a bug in dovecot per se because the behavior is different 
on the different client types. I was just wondering if someone else has seen 
similar behavior before and worked through it.

Thanks,
David

On Nov 28, 2012, at 12:49 AM, Stan Hoeppner  wrote:

> On 11/27/2012 9:21 PM, David Morsberger wrote:
>> Resending because I didn't get any responses from my first post:
>> 
>> I just converted my old server running UW/Panda to a Mac Mini Server running 
>> Mountain Lion (ML) Server. I'm using the postfix / dovecot setup provided by 
>> Apple.
>> 
>> My IMAP clients are not showing all my emails. The Mail App on my iPhone and 
>> iPad is behaving the worse. I can see the emails that are not showing up in 
>> the cur directory.
>> 
>> The ML Mail App is stating there are 3854 emails in my INBOX. There are 3948 
>> files in the 'cur' directory ('ls cur | wc -l' returns 3948). Other 
>> mailboxes and directories have the same behavior. I'm not sure what to 
>> expect here.
>> 
>> My method of conversion was to bulk copy (drag and drop) all the messages 
>> from one the UW server to the Dovecot server using the Apple Desktop Mail 
>> App in Mountain Lion. 
>> 
>> Any idea why these messages are not showing up on my devices and how I can 
>> get them to show up?
> 
> Not really.  Problem reports are typically accompanied by errors in log
> files.  You've provided none.  You've provided only subjective
> observation which is rarely useful in troubleshooting.  If you provide
> some Dovecot logging related to the problem we may be able to help.
> Short of that we can only make wild ass guesses.
> 
> Are your clients subscribing all IMAP folders?  Are your clients
> checking all folders for new mail?
> 
> -- 
> Stan
> 

[Dovecot] Missing Messages on IOS device

[David Morsberger]

Resending because I didn't get any responses from my first post:

I just converted my old server running UW/Panda to a Mac Mini Server running 
Mountain Lion (ML) Server. I'm using the postfix / dovecot setup provided by 
Apple.

My IMAP clients are not showing all my emails. The Mail App on my iPhone and 
iPad is behaving the worse. I can see the emails that are not showing up in the 
cur directory.

The ML Mail App is stating there are 3854 emails in my INBOX. There are 3948 
files in the 'cur' directory ('ls cur | wc -l' returns 3948). Other mailboxes 
and directories have the same behavior. I'm not sure what to expect here.

My method of conversion was to bulk copy (drag and drop) all the messages from 
one the UW server to the Dovecot server using the Apple Desktop Mail App in 
Mountain Lion. 

Any idea why these messages are not showing up on my devices and how I can get 
them to show up?

bash-3.2# /Applications/Server.app/Contents/ServerRoot/usr/sbin/dovecotd 
--version
2.0.19apple1

bash-3.2# /Applications/Server.app/Contents/ServerRoot/usr/sbin/dovecotd -n
# 2.0.19apple1: /Library/Server/Mail/Config/dovecot/dovecot.conf
# OS: Darwin 12.2.1 x86_64  hfs
aps_topic = com.apple.mail.XServer.fc3bb7c3-c8ef-4fe2-aff3-95ecd927fb11
auth_mechanisms = cram-md5 x-plain-submit plain login apop digest-md5
auth_socket_path = /var/run/dovecot/auth-userdb
auth_username_format = %n
default_internal_user = _dovecot
default_login_user = _dovenull
disable_plaintext_auth = no
first_valid_gid = 6
first_valid_uid = 6
mail_access_groups = mail
mail_location = maildir:/Library/Server/Mail/Data/mail/%u
mail_log_prefix = "%s(pid %p user %u): "
mail_plugins = quota zlib fts fts_sk
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 ihave
mdbox_rotate_size = 200 M
passdb {
 args = /Library/Server/Mail/Config/dovecot/submit.passdb
 driver = passwd-file
 pass = yes
 submit = yes
}
passdb {
 driver = od
}
plugin {
 fts = sk
 quota = maildir:User quota
 quota_warning = storage=100%% quota-exceeded %u
 sieve = /Library/Server/Mail/Data/rules/%u/dovecot.sieve
 sieve_dir = /Library/Server/Mail/Data/rules/%u
}
postmaster_address = postmas...@mini.mmpcrofton.com
protocols = imap pop3 lmtp sieve
quota_full_tempfail = yes
service auth {
 extra_groups = _keytabusers
 idle_kill = 15 mins
 unix_listener auth-userdb {
   user = _dovecot
 }
}
service dns_client {
 unix_listener dns-client {
   mode = 0600
 }
}
service imap-login {
 inet_listener imap {
   port = 143
 }
 inet_listener imaps {
   port = 993
   ssl = yes
 }
 service_count = 0
}
service imap {
 client_limit = 5
 process_limit = 200
 service_count = 0
}
service lmtp {
 unix_listener lmtp {
   mode = 0600
 }
}
service managesieve-login {
 inet_listener sieve {
   port = 4190
 }
}
service pop3-login {
 inet_listener pop3 {
   port = 110
 }
 inet_listener pop3s {
   port = 995
   ssl = yes
 }
}
service pop3 {
 client_limit = 5
 process_limit = 200
 service_count = 0
}
service quota-exceeded {
 executable = script 
/Applications/Server.app/Contents/ServerRoot/usr/libexec/dovecot/quota-exceeded.sh
 unix_listener quota-exceeded {
   group = mail
   mode = 0660
   user = _dovecot
 }
 user = _dovecot
}
service quota-warning {
 executable = script 
/Applications/Server.app/Contents/ServerRoot/usr/libexec/dovecot/quota-warning.sh
 unix_listener quota-warning {
   group = mail
   mode = 0660
   user = _dovecot
 }
 user = _dovecot
}
ssl_ca = 

[Dovecot] Missing Messages on IOS device

[David Morsberger]

I just converted my old server running UW/Panda to a Mac Mini Server running 
Mountain Lion (ML) Server. I'm using the postfix / dovecot setup provided by 
Apple.

My IMAP clients are not showing all my emails. The Mail App on my iPhone and 
iPad is behaving the worse. I can see the emails that are not showing up in the 
cur directory.

The ML Mail App is stating there are 3854 emails in my INBOX. There are 3948 
files in the 'cur' directory ('ls cur | wc -l' returns 3948). Other mailboxes 
and directories have the same behavior. I'm not sure what to expect here.

My method of conversion was to bulk copy (drag and drop) all the messages from 
one the UW server to the Dovecot server using the Apple Desktop Mail App in 
Mountain Lion. 

Any idea why these messages are not showing up on my devices and how I can get 
them to show up?

bash-3.2# /Applications/Server.app/Contents/ServerRoot/usr/sbin/dovecotd 
--version
2.0.19apple1

bash-3.2# /Applications/Server.app/Contents/ServerRoot/usr/sbin/dovecotd -n
# 2.0.19apple1: /Library/Server/Mail/Config/dovecot/dovecot.conf
# OS: Darwin 12.2.1 x86_64  hfs
aps_topic = com.apple.mail.XServer.fc3bb7c3-c8ef-4fe2-aff3-95ecd927fb11
auth_mechanisms = cram-md5 x-plain-submit plain login apop digest-md5
auth_socket_path = /var/run/dovecot/auth-userdb
auth_username_format = %n
default_internal_user = _dovecot
default_login_user = _dovenull
disable_plaintext_auth = no
first_valid_gid = 6
first_valid_uid = 6
mail_access_groups = mail
mail_location = maildir:/Library/Server/Mail/Data/mail/%u
mail_log_prefix = "%s(pid %p user %u): "
mail_plugins = quota zlib fts fts_sk
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 ihave
mdbox_rotate_size = 200 M
passdb {
  args = /Library/Server/Mail/Config/dovecot/submit.passdb
  driver = passwd-file
  pass = yes
  submit = yes
}
passdb {
  driver = od
}
plugin {
  fts = sk
  quota = maildir:User quota
  quota_warning = storage=100%% quota-exceeded %u
  sieve = /Library/Server/Mail/Data/rules/%u/dovecot.sieve
  sieve_dir = /Library/Server/Mail/Data/rules/%u
}
postmaster_address = postmas...@mini.mmpcrofton.com
protocols = imap pop3 lmtp sieve
quota_full_tempfail = yes
service auth {
  extra_groups = _keytabusers
  idle_kill = 15 mins
  unix_listener auth-userdb {
user = _dovecot
  }
}
service dns_client {
  unix_listener dns-client {
mode = 0600
  }
}
service imap-login {
  inet_listener imap {
port = 143
  }
  inet_listener imaps {
port = 993
ssl = yes
  }
  service_count = 0
}
service imap {
  client_limit = 5
  process_limit = 200
  service_count = 0
}
service lmtp {
  unix_listener lmtp {
mode = 0600
  }
}
service managesieve-login {
  inet_listener sieve {
port = 4190
  }
}
service pop3-login {
  inet_listener pop3 {
port = 110
  }
  inet_listener pop3s {
port = 995
ssl = yes
  }
}
service pop3 {
  client_limit = 5
  process_limit = 200
  service_count = 0
}
service quota-exceeded {
  executable = script 
/Applications/Server.app/Contents/ServerRoot/usr/libexec/dovecot/quota-exceeded.sh
  unix_listener quota-exceeded {
group = mail
mode = 0660
user = _dovecot
  }
  user = _dovecot
}
service quota-warning {
  executable = script 
/Applications/Server.app/Contents/ServerRoot/usr/libexec/dovecot/quota-warning.sh
  unix_listener quota-warning {
group = mail
mode = 0660
user = _dovecot
  }
  user = _dovecot
}
ssl_ca =