Re: Replication

2022-09-05 Thread ivan 



Make file 90-replication.com on primary and secudary mail server laik in 
example (change ip - or put hostname and password)


# Create 90-replication.conf

nano /etc/dovecot/conf.d/90-replication.conf

plugin {
  mail_replica = tcp:ip:12345
}

service replicator {
  process_min_avail = 1

  unix_listener replicator-doveadm {
mode = 0600
user = vmail
  }
}

service aggregator {
  fifo_listener replication-notify-fifo {
user = vmail
group = vmail
mode = 0666
  }
  unix_listener replication-notify {
user = vmail
group = vmail
mode = 0666
  }
}

service doveadm {
  inet_listener {
port = 12345
ssl = no
  }
}

doveadm_password = YourPassword

Dana 05.09.2022 12:15, Silvio Siefke je napisao(la):


Hello,

I try the replication of two Dovecot servers, but some errors always
appear. Maybe someone here has an idea what's going wrong.
As an MTA I use OpenSMTPD.

Thank You
Silvio

dovecot -n on MX 1
# 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.13 (cdd19fe3)
# OS: Linux 5.10.0-16-amd64 x86_64 Debian 11.4
# Hostname: asia.sisi-systems.ovh
auth_mechanisms = plain login
doveadm_password = # hidden, use -P to show it
doveadm_port = 2
mail_gid = vmail
mail_location = maildir:~/Maildir
mail_plugins = " notify replication"
mail_privileged_group = vmail
mail_uid = vmail
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 imapsieve vnd.dovecot.imapsieve

namespace inbox {
inbox = yes
location =
mailbox Drafts {
auto = subscribe
special_use = \Drafts
}
mailbox Sent {
auto = subscribe
special_use = \Sent
}
mailbox Spam {
auto = subscribe
special_use = \Junk
}
mailbox Trash {
auto = subscribe
special_use = \Trash
}
prefix =
}
passdb {
args = scheme=SHA512-CRYPT username_format=%u /etc/dovecot/users
driver = passwd-file
}
plugin {
imapsieve_mailbox1_before = 
file:/var/vmail/sieve/global/learn-spam.sieve

imapsieve_mailbox1_causes = COPY
imapsieve_mailbox1_name = Spam
imapsieve_mailbox2_before = 
file:/var/vmail/sieve/global/learn-ham.sieve

imapsieve_mailbox2_causes = COPY
imapsieve_mailbox2_from = Spam
imapsieve_mailbox2_name = *
mail_replica = tcp:192.168.1.112
quota = maildir:User quota
quota_exceeded_message = Benutzer %u hat das Speichervolumen 
überschritten. / User %u has exhausted allowed storage space.

replication_sync_timeout = 2
sieve = 
file:/var/vmail/sieve/%d/%n/scripts;active=/var/vmail/sieve/%d/%n/active-script.sieve

sieve_before = /var/vmail/sieve/global/spam-global.sieve
sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment
sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe
sieve_plugins = sieve_imapsieve sieve_extprograms
}
protocols = lmtp imap pop3 sieve
service aggregator {
fifo_listener replication-notify-fifo {
user = vmail
}
unix_listener replication-notify {
user = vmail
}
}
service doveadm {
inet_listener {
port = 2
}
}
service imap-login {
inet_listener imap {
port = 143
}
}
service lmtp {
unix_listener lmtp {
group = vmail
user = vmail
}
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
}
service pop3-login {
inet_listener pop3 {
port = 110
}
inet_listener pop3s {
port = 995
ssl = yes
}
}
service replicator {
process_min_avail = 1
unix_listener replicator-doveadm {
mode = 0600
user = vmail
}
}
ssl = required
ssl_cert = ssl_cipher_list = 
ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384

ssl_client_ca_dir = /etc/ssl/certs
ssl_dh = # hidden, use -P to show it
ssl_key = # hidden, use -P to show it
ssl_min_protocol = TLSv1.2
userdb {
args = username_format=%u /etc/dovecot/users
driver = passwd-file
override_fields = uid=vmail gid=vmail home=/home/vmail/%d/%n
}
protocol imap {
imap_idle_notify_interval = 29 mins
mail_max_userip_connections = 20
mail_plugins = " notify replication quota imap_quota imap_sieve"
}
protocol lmtp {
mail_plugins = " notify replication sieve notify push_notification"
postmaster_address = netw...@sisi-systems.ovh
}
protocol pop3 {
mail_max_userip_connections = 10
mail_plugins = " notify replication"
}

dovecot -n on MX 2
# 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.13 (cdd19fe3)
# OS: Linux 5.10.0-15-amd64 x86_64 Debian 11.4
# Hostname: bulgaria.sisi-systems.ovh
auth_mechanisms = plain login
doveadm_password = # hidden, use -P to show it
doveadm_port = 2
mail_gid = vmail
mail_location = maildir:~/Maildir
mail_plugins = " notify replication"
mail_privileged_group = vmail
mail_uid = vmail
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope 
encoded-character vacation subaddress

Re: Replicator: Panic: data stack: Out of memory

2022-06-09 Thread Ivan Jurišić 
Now is all ok, I put same configuration of Dovecot on primary and 
secondary server.


Dana 06.06.2022 14:14, Paul Kudla (SCOM.CA Internet Services Inc.) je 
napisao(la):



did you get this figured out / working

getting posts out of order - just wanted to make sure your ok?

Re: Replicator: Panic: data stack: Out of memory

2022-06-06 Thread Ivan Jurišić 
Dana 06.06.2022 14:14, Paul Kudla (SCOM.CA Internet Services Inc.) je 
napisao(la):

did you get this figured out / working
getting posts out of order - just wanted to make sure your ok?


Replication not work, now have problem with "data stack", error is:

Jun 06 15:49:32 
doveadm(ivan@myserv.local)<79253>: Panic: data 
stack: Out of memory when allocating 536870952 bytes


I have lots free memory and not sure what is problem?

# free -m
   totalusedfree  shared  buff/cache   
available
Mem:795626854966  26 305 
   5151

Swap:   7629   07629

Re: Replicator: Panic: data stack: Out of memory

2022-06-06 Thread Ivan Jurišić 

Sry, I check my logs and this configuration of replication is not help.

Jun 06 12:05:40 
doveadm(ivan@myserv.local)<2864367>: Panic: data 
stack: Out of memory when allocating 134217768 bytes
Jun 06 12:05:40 
doveadm(ivan@myserv.local)<2864367>: Error: Raw 
backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) 
[0x7f722cdb6582] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) 
[0x7f722cdb669e] -> /usr/lib/dovecot/libdovecot.so.0(+0x1022fb) 
[0x7f722cdc32fb] -> /usr/lib/dovecot/libdovecot.so.0(+0x102391) 
[0x7f722cdc3391] -> /usr/lib/dovecot/libdovecot.so.0(+0x55589) 
[0x7f722cd16589] -> /usr/lib/dovecot/libdovecot.so.0(+0x54d52) 
[0x7f722cd15d52] -> /usr/lib/dovecot/libdovecot.so.0(+0xfb808) 
[0x7f722cdbc808] -> 
/usr/lib/dovecot/libdovecot.so.0(t_strdup_until+0x21) [0x7f722cdf95c1] 
-> dovecot/doveadm-server(dsync_mailbox_tree_find_delete+0x1a5) 
[0x5622f20c6e05] -> dovecot/doveadm-server(+0x4fe05) [0x5622f20bbe05] -> 
dovecot/doveadm-server(dsync_brain_recv_mailbox_tree_deletes+0xd8) 
[0x5622f20bcd68] -> dovecot/doveadm-server(dsync_brain_run+0x1ce) 
[0x5622f20b938e] -> dovecot/doveadm-server(+0x4da85) [0x5622f20b9a85] -> 
dovecot/doveadm-server(+0x5f3cf) [0x5622f20cb3cf] -> 
/usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f722cdd9529] 
-> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x132) 
[0x7f722cddac12] -> 
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) 
[0x7f722cdd95d0] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) 
[0x7f722cdd9790] -> dovecot/doveadm-server(+0x31195) [0x5622f209d195] -> 
dovecot/doveadm-server(+0x33a05) [0x5622f209fa05] -> 
dovecot/doveadm-server(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x2ca) 
[0x5622f20a0aba] -> dovecot/doveadm-server(doveadm_cmd_run_ver2+0x501) 
[0x5622f20b1161] -> dovecot/doveadm-server(+0x495aa) [0x5622f20b55aa] -> 
/usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f722cdd9529] 
-> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x132) 
[0x7f722cddac12] -> 
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) 
[0x7f722cdd95d0] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) 
[0x7f722cdd9790] -> 
/usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) 
[0x7f722cd4c353] -> dovecot/doveadm-server(main+0x102) [0x5622f208ffc2] 
-> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) 
[0x7f722c9ded0a]



Dana 06.06.2022 10:03, Ivan Jurišić je napisao(la):

Dana 04.06.2022 15:34, Paul Kudla (SCOM.CA Internet Services Inc.) je 
napisao(la):

ok thanks for the info
from here you need to turn on full debugging and then filter the log 
by

"replicat"


Now replication work when set vsz_limit in service aggregator and 
remove parametar replication_dsync_parameters and 
replication_full_sync_interval from my 90-replicator.conf. Now my 
configuration work for replication on another mail server.


Config file for replication /etc/dovecot/conf.d/90-replicator.conf
--

service aggregator {
vsz_limit = 256M
fifo_listener replication-notify-fifo {
user = vmail
}
unix_listener replication-notify {
user = vmail
}
}

service replicator {
process_min_avail = 1
unix_listener replicator-doveadm {
mode = 0600
user = vmail
}
}

service doveadm {
inet_listener {
port = 12345
ssl = no
}
}

replication_max_conns = 100
#replication_dsync_parameters = -d -N -l 30 -U
#replication_full_sync_interval = 1 days

doveadm_port = 12345
doveadm_password = Jados82!

plugin {
mail_replica = tcp:imap.myserv2.local:12345
}

Re: Replicator: Panic: data stack: Out of memory

2022-06-06 Thread Ivan Jurišić 
Dana 04.06.2022 15:34, Paul Kudla (SCOM.CA Internet Services Inc.) je 
napisao(la):

   ok thanks for the info
   from here you need to turn on full debugging and then filter the log 
by

   "replicat"


Now replication work when set vsz_limit in service aggregator and remove 
parametar replication_dsync_parameters and 
replication_full_sync_interval from my 90-replicator.conf. Now my 
configuration work for replication on another mail server.


Config file for replication /etc/dovecot/conf.d/90-replicator.conf
--

service aggregator {
  vsz_limit = 256M
  fifo_listener replication-notify-fifo {
user = vmail
  }
  unix_listener replication-notify {
user = vmail
  }
}

service replicator {
  process_min_avail = 1
  unix_listener replicator-doveadm {
mode = 0600
user = vmail
  }
}

service doveadm {
  inet_listener {
port = 12345
ssl = no
  }
}

replication_max_conns = 100
#replication_dsync_parameters = -d -N -l 30 -U
#replication_full_sync_interval = 1 days

doveadm_port = 12345
doveadm_password = Jados82!

plugin {
  mail_replica = tcp:imap.myserv2.local:12345
}

Re: Replicator: Panic: data stack: Out of memory

2022-06-03 Thread Ivan Jurišić 




Ok a little more help :
vsz_limit = 0 --> means unlimited ram for allocation, change this/try 
2g etc pending avaliable ram.


I try with 524M, 1G, 2G, 4G and 8G but in any case repclicator proces 
got crash.

Replicator: Panic: data stack: Out of memory

2022-06-03 Thread Ivan Jurišić 

Reproduce of error (Replicator: Panic: data stack: Out of memory):
==

When replay on any mail I will got OOM.

I try add in service replicate vsz_limit = 0 but that not help (after 
proces dovecot/replicator eat all ram I got OOM)


Log error:
==

Jun 03 09:38:59 Warning: 
imap(ivan@myserv.local)<2533034>: 
replication(ivan@myserv.local): Sync failure: Timeout in 2 secs
Jun 03 09:39:03 Panic: replicator: data stack: Out of memory when 
allocating 4294967336 bytes
Jun 03 09:39:03 Error: replicator: Raw backtrace: 
/usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7feef08f0582] 
-> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7feef08f069e] 
-> /usr/lib/dovecot/libdovecot.so.0(+0x1022fb) [0x7feef08fd2fb] -> 
/usr/lib/dovecot/libdovecot.so.0(+0x102391) [0x7feef08fd391] -> 
/usr/lib/dovecot/libdovecot.so.0(+0x55589) [0x7feef0850589] -> 
/usr/lib/dovecot/libdovecot.so.0(+0x54d52) [0x7feef084fd52] -> 
/usr/lib/dovecot/libdovecot.so.0(+0xfb808) [0x7feef08f6808] -> 
/usr/lib/dovecot/libdovecot.so.0(+0x122938) [0x7feef091d938] -> 
/usr/lib/dovecot/libdovecot.so.0(+0xf76bf) [0x7feef08f26bf] -> 
/usr/lib/dovecot/libdovecot.so.0(+0xf777e) [0x7feef08f277e] -> 
/usr/lib/dovecot/libdovecot.so.0(buffer_append+0x61) [0x7feef08f2a21] -> 
dovecot/replicator(replicator_queue_push+0x15a) [0x55953ece9b7a] -> 
dovecot/replicator(+0x62b6) [0x55953ece92b6] -> 
dovecot/replicator(+0x594e) [0x55953ece894e] -> 
dovecot/replicator(+0x5b2c) [0x55953ece8b2c] -> 
/usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7feef0913529] 
-> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x132) 
[0x7feef0914c12] -> 
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) 
[0x7feef09135d0] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) 
[0x7feef0913790] -> 
/usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) 
[0x7feef0886353] -> dovecot/replicator(main+0x18d) [0x55953ece7cbd] -> 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7feef0651d0a] 
-> dovecot/replicator(_start+0x2a) [0x55953ece7d7a]
Jun 03 09:39:03 Fatal: replicator: master: service(replicator): child 
2532886 killed with signal 6 (core dumps disabled - 
https://dovecot.org/bugreport.html#coredumps)


My configuration:
==

# 2.3.19 (b3ad6004dc): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.19 (4eae2f79)
# OS: Linux 5.10.0-13-amd64 x86_64 Debian 11.3 ext4
# Hostname: mail.myserv.local
auth_mechanisms = plain login
auth_verbose = yes
debug_log_path = /var/log/dovecot.debug
default_client_limit = 5000
default_process_limit = 1000
default_vsz_limit = 2 G
deliver_log_format = msgid=%m, subject=%s, from=%f, size=%p(%w), %$
dict {
  quota = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext
}
doveadm_password = # hidden, use -P to show it
hostname = myserv.local
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
listen = *
log_path = /var/log/dovecot.log
mail_home = /var/mail/vhosts/%d/mail/%n
mail_location = 
maildir:/var/mail/vhosts/%d/mail/%n:INDEX=/var/mail/vhosts/%d/indexes/%n

mail_plugins = " quota fts fts_solr notify replication"
mail_privileged_group = vmail
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 imapsieve vnd.dovecot.imapsieve

namespace inbox {
  inbox = yes
  location =
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix =
  separator = /
}
passdb {
  args = /etc/dovecot/dovecot-sql.conf.ext
  driver = sql
}
plugin {
  autocreate = Sent
  autocreate2 = Drafts
  autocreate3 = Junk
  autocreate4 = Trash
  autosubscribe = Sent
  autosubscribe2 = Drafts
  autosubscribe3 = Junk
  autosubscribe4 = Trash
  expire = Trash
  expire2 = Trash/*
  expire3 = Spam
  fts = solr
  fts_autoindex = yes
  fts_solr = url=http://localhost:8983/solr/dovecot/
  imapsieve_mailbox1_before = file:/etc/dovecot/sieve/report-spam.sieve
  imapsieve_mailbox1_causes = COPY
  imapsieve_mailbox1_name = Junk
  imapsieve_mailbox2_before = file:/etc/dovecot/sieve/report-ham.sieve
  imapsieve_mailbox2_causes = COPY
  imapsieve_mailbox2_from = Junk
  imapsieve_mailbox2_name = *
  mail_replica = tcp:imap.myserv2.local:12345
  quota = dict:Mailbox::proxy::quota
  quota_rule = *:storage=1G
  quota_warning = storage=95%% quota-warning 95 %u
  quota_warning2 = storage=80%% quota-warning 80 %u
  replication_sync_timeout = 2
  sieve = 
file:/var/mail/vhosts/%d/sieve/%n;active=/var/mail/vhosts/%d/sieve/%n/.dovecot.siev

Re: Filesystem level backups?

2018-04-09 Thread Ivan Warren 



Le 4/9/2018 à 4:56 PM, DurgaPrasad - DatasoftComnet a écrit :

Hello all,
Does doveadm backup - backup the attachments as well when using SIS ?


As far as I know, it does (it de-shares shared attachments)

I've used that solution to stop using SIS at one point (it created more 
problems than it solved - especially permission issues). I backup up all 
my mailboxes - then made them active - all attachments were back in the 
individual mailboxes.


--Ivan
(Again sorry for the duplicate)



smime.p7s
Description: Signature cryptographique S/MIME

Re: Filesystem level backups?

2018-04-09 Thread Ivan Warren 



Le 4/9/2018 à 2:34 PM, Marc Stürmer a écrit :

Am 2018-04-09 00:55, schrieb Steve Atkins:


Will a simple backup of all the files of an multi-dbox give me a
consistent state when I recover, or do I need to do something (e.g.
lock writes to the mailbox) while I run a backup?


If you are doing this backup with a fully operational mail storage: 
no, it won't. The reason is quite simple: mdbox saves the data of an 
email in several files, so there's a good chance that those files 
might slightly change during backup, while with Maildir all necessary 
data for the restore is stored in the file names.


If you want to do a consistent backup, you do need file system 
snapshots and should make sure that this snapshot is consistent or to 
turn off the mail store during backup completely.


But just doing rsync on the fly as with Maildir is just begging on 
your side to run into problems sooner or later...


Personally, I always do a doveadm backup -u  to a different 
location (in mdbox format).


Then do a git -A, git commit, git repack *THEN* rsync the resulting .git 
directories to an off-site location (thus only sending the difference 
between one bakup and the next - in packed format).


The advantage is I can retrieve the status of any mailbox at any point 
in time (right now I have a year long of hour per hour backup of my 
servers mailboxes with a volume that is less than twice the size of the 
entire mailbox sizes).


Granted, it's a low volume, low trafic server, but it works !

--Ivan

(PS : Sorry Mark for the duplicate as I answered to you directly instead 
of the list)


smime.p7s
Description: Signature cryptographique S/MIME

Re: dmarc report faild ?

2017-08-24 Thread Ivan Warren 



Le 8/24/2017 à 9:43 PM, Ivan Warren a écrit :

And further funny things ...

By pasting "message headers" in the message body I got a truckload of 
forensic reports !


Looks like there something amiss in the DKIM/DMARC realm !

--Ivan


Or rather,

There is something rotten in the kingdom of DMARC

(Sorry couldn't resist.. and my apologies to all for hogging the list).

--Ivan



smime.p7s
Description: Signature cryptographique S/MIME

Re: dmarc report faild ?

2017-08-24 Thread Ivan Warren 

And further funny things ...

By pasting "message headers" in the message body I got a truckload of 
forensic reports !


Looks like there something amiss in the DKIM/DMARC realm !

--Ivan



smime.p7s
Description: Signature cryptographique S/MIME

Re: dmarc report faild ?

2017-08-24 Thread Ivan Warren 

In the same vein,

I am receiving forensic DMARC reports from mx01.nausch.org.

Whenever I send a message to the mailing list or when my server sends a 
DMARC report, I'm getting a DMARC Forensic report.


It's odd, because the actual report tells me both DKIM and SPF (in the 
the of a DMARC report) pass...


Here is what I am getting :

This is an authentication failure report for an email message received from IP
163.172.81.229 on Thu, 24 Aug 2017 19:45:10 +0200 (CEST).



Feedback-Type: auth-failure
Version: 1
User-Agent: OpenDMARC-Filter/1.3.2
Auth-Failure: dmarc
Authentication-Results: mx01.nausch.org; dmarc=fail header.from=vmfacility.fr
Original-Envelope-Id: 7AA88C00088
Original-Mail-From:mrep...@vmfacility.fr
Source-IP: 163.172.81.229 (db04.ivansoftware.com)
Reported-Domain: vmfacility.fr



Authentication-Results: mx1.nausch.org;
dkim=pass (2048-bit key) header.d=vmfacility.frheader.i=@vmfacility.fr  
header.b="oHXeoWbW"
Authentication-Results: mx1.nausch.org; spf=pass 
smtp.mailfrom=<mrep...@vmfacility.fr>  smtp.helo=db04.ivansoftware.com
Received: from db04 (localhost [127.0.0.1])
by db04.ivansoftware.com (Postfix) with ESMTP id A0447BE0870
for<dmarc-repo...@nausch.org>; Thu, 24 Aug 2017 19:45:02 +0200 (CEST)
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.99.2 at db04
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=vmfacility.fr;
s=mail; t=1503596702;
bh=NWT2THShdUTG/xaKKp+wC6e3AahFUjoRkNEGJfERGdM=;
h=To:From:Subject:Date:From;
b=oHXeoWbWTTYlWh0orXRIZS6kuMaJmLzui2oTkSS8BCcYQ8x7F0QbDZfSrhQJpt3gv
 0GOXiR1sgDgkXBOrd6Lms/ePsg33bCmmMgQdjPF62pACE7OlqVWxg6GYfsbFYUbBxC
 902xtjJo2TnEyDCYAyJP0/VPwQ+lLMNlMzjKSCtMFYoc8i+V7pOLsQizgfr2dvoMA5
 +RQ/ZkWoV42QrxxVzYN6beuQAdX3q5cB6N6XI9zHUw0cRB5scHc+M/3TH7XwTKmozm
 p1tAUzyLwhcYslktM348QA3hTMmvuH9Uo2th4wR3UdlkIX9WDjFWRw8JCbK9RUqmKu
 LePx9Q8z3nALg==
To:dmarc-repo...@nausch.org
From:mrep...@vmfacility.fr
Subject: Report Domain: nausch.org Submitter:  Report-ID: nausch.org-1503596702@
X-Mailer: opendmarc-reports v1.3.2
Date: Thu, 24 Aug 2017 19:45:02 +0200 (CEST)
Message-ID: <nausch.org-1503596702@>
Auto-Submitted: auto-generated
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="report_section"



Note that the first part says authentication failed, but the second part 
(which is the mail headers for a legit DMARC aggregate report sent to 
the published DMARC rua for nausch.org) passes all the tests - both DKIM 
and SPF.


I am also getting forensic reports from this MTA when posting to the list.

So my guess is some...@nausch.org on this mailing list might have a 
misbehaving DMARC responder/filter.


Note also that this is the only domain/MX I have had so far that 
responds in that way (that is - one that sends me a failed DMARC 
forensic report for a message I *KNOW* I sent - validated and through my 
SPF validated and with headers which are properly DKIM signed).


--Ivan


smime.p7s
Description: Signature cryptographique S/MIME

Re: dovecot umask for mail boxes

2017-08-24 Thread Ivan Warren 



Le 8/24/2017 à 6:46 PM, vadim a écrit :

I want to control the mode of newly created boxes.

The official documentation here: 
https://wiki.dovecot.org/SharedMailboxes/Permissions , under 
Permissions for new mailboxes says this:


"When creating a new mailbox, Dovecot copies the permissions from the 
mailbox root directory. For example with mboxes if you have directories"


But it seems to be untrue. I checked it, it soesn't work.

I found a topic in mail list archive:

https://dovecot.org/list/dovecot/2008-September/033395.html

Its recommended to create a 'dovecot-shared' file in each mailbox with 
proper rights. But how can I do that if mailbox is not exists yet ?


Can you provide any working solution to this problem ?


Hey,

Personally I always set the parent directory to have g+s (and group 
owner to "mail", or whatever you use for your dovecot installation), and 
this seems to do the trick.


I use mdbox, so it may be dependent on the backend being used for mail 
storage (mbox, maildir, sdbox, mdbox...)


--Ivan



smime.p7s
Description: Signature cryptographique S/MIME

Re: dmarc report faild ?

2017-08-24 Thread Ivan Warren 



Le 8/24/2017 à 3:47 PM, A. Schulze a écrit :


Maurizio Caloro:

Please i have new following Error, from DMARC Report, if i check my 
domain

on example mxtoolbox i dont see any problems.

Any from you know this Eror report, what i need to do to fix this issue?


I guess, the reports are about messages you sent to the list:
https://dovecot.org/pipermail/dovecot/2017-August/109097.html

As I explained to Maurizio (off list), he received an aggregate report.. 
(Actually from one of my mail servers) in the sample he sent...


It's an aggregate report, so even if everything was succesful, I (or 
rather opendmarc-reports since I'm using opendmarc) would still send a 
report !


So receiving a DMARC aggregate report isn't an indication of a problem !

Any SPF error in the report would be normal when received from a mailing 
list, but I think DMARC passes if either SPF or DKIM pass (you don't 
need both).


Note this is a bit OT, since dovecot has nothing to do with SPF, DKIM, 
DMARC or any of the postfix/sendmail MILTERs.


--Ivan



smime.p7s
Description: Signature cryptographique S/MIME

Question (haven't tried yet)

2017-08-16 Thread Ivan Warren 

Hello,

I have a question : if I have multiple servers sharing a single disk 
space (NFS... cluster), and a message is delivered via say LMTP or LDA 
to a mailbox, and an IMAP client is in IDLE mode on another server, Will 
it get notified of the arrival of the new message (and if yes, how ?)


Thanks,

--Ivan




smime.p7s
Description: Signature cryptographique S/MIME

Issue with dsync server - copy transaction record copying to wrong destination mailbox.

2017-06-22 Thread Ivan Warren 

Hello all,

I am encountering the following issue :

I have 2 dovecot servers with 2 way replication. Everything works fine 
except for one specific issue :


When my MUA (thunderbird) filters (junk & manual) refile a mail from my 
inbox, I then sometimes find multiple copies of the original message in 
the destination folder.


I have seen the following log entries which make me think (but I'm new 
to this) that there could be an issue with the processing of the COPY 
transaction record during DSYNC :


* TB Marking msg as Junk
Jun 22 20:36:14 db04 dovecot: imap(ivan): flag_change: box=INBOX, 
uid=502902, 
msgid=<RF7w0iVHwvOBtpFW7y7eTF3jazYxJeuFC9JvB9xsjnk.gI5bQ0w8OtJJT7-T4krQTG3XkEqb5Hti..., 
size=9942

* TB Copies msg to Junk Mailbox
Jun 22 20:36:14 db04 dovecot: imap(ivan): copy from INBOX: box=Junk, 
uid=32059, 
msgid=<RF7w0iVHwvOBtpFW7y7eTF3jazYxJeuFC9JvB9xsjnk.gI5bQ0w8OtJJT7-T4krQTG3XkEqb5Hti..., 
size=9942

* TB expunges mail from INBOX
Jun 22 20:36:14 db04 dovecot: imap(ivan): expunge: box=INBOX, 
uid=502902, 
msgid=<RF7w0iVHwvOBtpFW7y7eTF3jazYxJeuFC9JvB9xsjnk.gI5bQ0w8OtJJT7-T4krQTG3XkEqb5Hti..., 
size=9942
* Local server receives transaction from remote server and saves message 
again to INBOX
Jun 22 20:36:16 db04 dovecot: dsync-local(ivan): save: box=INBOX, 
uid=502903, 
msgid=<RF7w0iVHwvOBtpFW7y7eTF3jazYxJeuFC9JvB9xsjnk.gI5bQ0w8OtJJT7-T4krQTG3XkEqb5Hti..., 
size=9942
* Remote server copies message from INBOX to INBOX <<<<<<<<<<<<<< That's 
my issue
Jun 22 20:36:16 db04 dovecot: doveadm: Error: dsync-remote(ivan): Info: 
copy from INBOX: box=INBOX, uid=502903, 
msgid=<RF7w0iVHwvOBtpFW7y7eTF3jazYxJeuFC9JvB9xsjnk.gI5bQ0w8OtJJT7-T4krQTG3XkEqb5Hti..., 
size=9942

* Remote server expunges msg copy
Jun 22 20:36:16 db04 dovecot: doveadm: Error: dsync-remote(ivan): Info: 
expunge: box=INBOX, uid=502902, 
msgid=<RF7w0iVHwvOBtpFW7y7eTF3jazYxJeuFC9JvB9xsjnk.gI5bQ0w8OtJJT7-T4krQTG3XkEqb5Hti..., 
size=9942


Is this a known issue (I may not have looked deep enough..) ? Is more 
information needed ? (note again that for me dovecot is working 
perfectly fine except for that little issue).


(Version is 2.2.27 from Debian stretch)

Thanks,

--Ivan




smime.p7s
Description: S/MIME Cryptographic Signature

Doveadm option for a non-wildcard single-user with userdb

2017-02-02 Thread Ivan Zahariev 

Hello,

Most "doveadm" commands accept "[-A|-u user|-F file]" for user 
selection, or the environment "USER". I'm testing with "doveadm quota 
recalc".


The problem is that there is no way to ask "doveadm" to work in (1) 
single-user mode with (2) no wildcard support, and at the same time to 
(3) make a lookup in "userdb", in order to get the user's specific 
configuration. We have mailboxes which contain "?" and "*" symbols, and 
we can't work with them using "doveadm" now.


* If we use "-A", this works with all users. Not our case at all.
* If we use "-F" and provide just one user in the file, this works for a 
single user + lookup in "userdb", does not interpret wildcard, but 
"doveadm" works in a "users list" mode and the output is different. 
What's more problematic is that errors for an mbox do not end up in 
"doveadm" exiting with a non-zero exit code.
* If we use "-u", this works for a single user + lookup in "userdb", but 
interprets wildcards. Does not work for mailboxes which contain "?" and "*".
* If we use the USER environment, this works for a single users and does 
not interpret wildcards but does not do a lookup in "userdb".


Should we add another user-selection argument, for example "-U", which 
(1) selects a single-user like "-u", does a "userdb" lookup like "-u" 
does, but does not interpret wildcards unlike "-u" ?


Best regards.
--Ivan

Re: Upgrade Dovecot from 2.1.17 to 2.2.13 lmtp child killed with signal 6

2016-03-24 Thread Ivan Jurišić 
Hi Teemu,

I upgrade Dovecot on 2.2.22-1~auto+6 from repository
http://xi.dovecot.fi/debian/ and now all works well.

Thanks loot,
Ivan

On 03/22/2016 11:45 AM, Teemu Huovila wrote:
>
> On 22.03.2016 11:43, Ivan Jurišić wrote:
>> After upgrade Debian (Wheezy to Jessie) Dovecot version 2.1.17 is
>> upgraded to 2.2.13.
>> I have random crash of lmtp-a and I got lot message in queue. Any
>> solution for this problem?
> This looks like it is fixed by 
> https://github.com/dovecot/core/commit/98449946caeaf8a3b413a0d93128315b158cbffb
> Please upgrade, if possible.
>
> br,
> Teemu Huovila
>
>> -- Postqueue --
>>
>> 7A5B77F72B  1160457 Tue Mar 22 10:10:15  i...@jurisic.org
>> (delivery temporarily suspended: lost connection with
>> mail.jurisic.org[private/dovecot-lmtp] while sending end of data --
>> message may be sent more than once)
>>  ante.starce...@gmail.com
>>
>> -- Log file --
>>
>> Mar 22 10:10:15 lmtp(23497, i...@jurisic.org): Panic: file fs-api.c:
>> line 615 (fs_copy): assertion failed: (src->fs == dest->fs)
>>
>> Mar 22 10:10:15 lmtp(23497, i...@jurisic.org): Error: Raw backtrace:
>> /usr/lib/dovecot/libdovecot.so.0(+0x6b6fe) [0x7f7647a8b6fe] ->
>> /usr/lib/dovecot/libdovecot.so.0(+0x6b7ec) [0x7f7647a8b7ec] ->
>> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f7647a428fb] ->
>> /usr/lib/dovecot/libdovecot.so.0(fs_copy+0x90) [0x7f7647a4c4a0] ->
>> /usr/lib/dovecot/libdovecot-storage.so.0(sdbox_copy+0x4e0)
>> [0x7f7647d3ec10] ->
>> /usr/lib/dovecot/modules/lib10_quota_plugin.so(+0xbaab) [0x7f764726aaab]
>> -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x7d)
>> [0x7f7647d7b01d] ->
>> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x196)
>> [0x7f76480229d6] ->
>> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0xf3) [0x7f7648022e13]
>> -> dovecot/lmtp(+0x6171) [0x7f7648452171] ->
>> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x3f) [0x7f7647a9cd0f]
>> -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xf9)
>> [0x7f7647a9dd09] ->
>> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9)
>> [0x7f7647a9cd79] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38)
>> [0x7f7647a9cdf8] ->
>> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13)
>> [0x7f7647a47dc3] -> dovecot/lmtp(main+0x165) [0x7f76484509b5] ->
>> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f7647696b45]
>> -> dovecot/lmtp(+0x4a95) [0x7f7648450a95]
>>
>> Mar 22 10:10:15 lmtp(23497, i...@jurisic.org): Fatal: master:
>> service(lmtp): child 23497 killed with signal 6 (core dumps disabled)
>>
>> -- Dovecot configuration  --
>>
>> # 2.2.13: /etc/dovecot/dovecot.conf
>> # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.3 ext4
>> auth_mechanisms = plain login
>> debug_log_path = /var/log/dovecot.debug
>> default_client_limit = 1
>> default_process_limit = 1000
>> default_vsz_limit = 512 M
>> dict {
>>   quota = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext
>> }
>> hostname = mail.jurisic.org
>> info_log_path = /var/log/dovecot.info
>> lda_mailbox_autocreate = yes
>> lda_mailbox_autosubscribe = yes
>> listen = *
>> log_path = /var/log/dovecot.log
>> mail_attachment_dir = /var/mail/vhosts/%d/attachment
>> mail_home = /var/mail/vhosts/%d/mail/%n
>> mail_location = sdbox:/var/mail/vhosts/%d/mail/%n
>> mail_plugins = " quota"
>> mail_privileged_group = vmail
>> 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
>> 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" {
>> special_use = \Sent
>>   }
>>   mailbox Trash {
>> auto = subscribe
>> special_use = \Trash
>>   }
>>   prefix =
>> }
>> passdb {
>>   args = /etc/dovecot/dovecot-sql.conf.ext
>>   driver = sql
>> }
>> plugin {
>>   autocreate = Sent
>>   autocre

Upgrade Dovecot from 2.1.17 to 2.2.13 lmtp child killed with signal 6

2016-03-22 Thread Ivan Jurišić 
After upgrade Debian (Wheezy to Jessie) Dovecot version 2.1.17 is
upgraded to 2.2.13.
I have random crash of lmtp-a and I got lot message in queue. Any
solution for this problem?


-- Postqueue --

7A5B77F72B  1160457 Tue Mar 22 10:10:15  i...@jurisic.org
(delivery temporarily suspended: lost connection with
mail.jurisic.org[private/dovecot-lmtp] while sending end of data --
message may be sent more than once)
 ante.starce...@gmail.com

-- Log file --

Mar 22 10:10:15 lmtp(23497, i...@jurisic.org): Panic: file fs-api.c:
line 615 (fs_copy): assertion failed: (src->fs == dest->fs)

Mar 22 10:10:15 lmtp(23497, i...@jurisic.org): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.0(+0x6b6fe) [0x7f7647a8b6fe] ->
/usr/lib/dovecot/libdovecot.so.0(+0x6b7ec) [0x7f7647a8b7ec] ->
/usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f7647a428fb] ->
/usr/lib/dovecot/libdovecot.so.0(fs_copy+0x90) [0x7f7647a4c4a0] ->
/usr/lib/dovecot/libdovecot-storage.so.0(sdbox_copy+0x4e0)
[0x7f7647d3ec10] ->
/usr/lib/dovecot/modules/lib10_quota_plugin.so(+0xbaab) [0x7f764726aaab]
-> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x7d)
[0x7f7647d7b01d] ->
/usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x196)
[0x7f76480229d6] ->
/usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0xf3) [0x7f7648022e13]
-> dovecot/lmtp(+0x6171) [0x7f7648452171] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x3f) [0x7f7647a9cd0f]
-> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xf9)
[0x7f7647a9dd09] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9)
[0x7f7647a9cd79] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38)
[0x7f7647a9cdf8] ->
/usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13)
[0x7f7647a47dc3] -> dovecot/lmtp(main+0x165) [0x7f76484509b5] ->
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f7647696b45]
-> dovecot/lmtp(+0x4a95) [0x7f7648450a95]

Mar 22 10:10:15 lmtp(23497, i...@jurisic.org): Fatal: master:
service(lmtp): child 23497 killed with signal 6 (core dumps disabled)

-- Dovecot configuration  --

# 2.2.13: /etc/dovecot/dovecot.conf
# OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.3 ext4
auth_mechanisms = plain login
debug_log_path = /var/log/dovecot.debug
default_client_limit = 1
default_process_limit = 1000
default_vsz_limit = 512 M
dict {
  quota = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext
}
hostname = mail.jurisic.org
info_log_path = /var/log/dovecot.info
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
listen = *
log_path = /var/log/dovecot.log
mail_attachment_dir = /var/mail/vhosts/%d/attachment
mail_home = /var/mail/vhosts/%d/mail/%n
mail_location = sdbox:/var/mail/vhosts/%d/mail/%n
mail_plugins = " quota"
mail_privileged_group = vmail
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
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" {
special_use = \Sent
  }
  mailbox Trash {
auto = subscribe
special_use = \Trash
  }
  prefix =
}
passdb {
  args = /etc/dovecot/dovecot-sql.conf.ext
  driver = sql
}
plugin {
  autocreate = Sent
  autocreate2 = Drafts
  autocreate3 = Junk
  autocreate4 = Trash
  autosubscribe = Sent
  autosubscribe2 = Drafts
  autosubscribe3 = Junk
  autosubscribe4 = Trash
  expire = Trash
  expire2 = Trash/*
  expire3 = Spam
  expire_dict = proxy::expire
  quota = dict:user::proxy::quota
  quota_rule = *:storage=102400
  quota_warning = storage=75%% quota-warning 75 %u
  quota_warning2 = storage=90%% quota-warning 90 %u
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
}
postmaster_address = postmaster@%d
protocols = " imap lmtp sieve pop3"
service auth-worker {
  user = vmail
}
service auth {
  unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0666
user = postfix
  }
  unix_listener auth-userdb {
mode = 0600
user = vmail
  }
  user = dovecot
}
service dict {
  unix_listener dict {
mode = 0660
user = vmail
  }
}
service imap-login {
  process_min_avail = 4
  service_count = 0
  vsz_limit = 512 M
}
service imap {
  vsz_limit = 512 M
}
service lmtp {
  unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
  }
}
service quota-warning {
  executable = script /opt/mail-old.sh
  unix_listener quota-warning {
group = root
mode = 0666
user = root
  }
  user = root
}
ssl = required
ssl_cert =

[Dovecot] Sieve vacation issue - Dovecot + Postfix + LDA

2013-04-03 Thread Ivan Bogdanovic 
Hi to all,

I have an issue with Dovecot Sieve on sending vacation message... Actually
Sieve is working and I can use all the filters but just vacation is causing
a problem and only in specific case...

I have Dovecot + Postfix + LDA running on Ubuntu 11 without MySql database
for users but I'm using virtusertable instead. The problem is when linux
user ( mail user ) is different from mail allias in virtusertable...
Example: i...@domain.com  ivan1 ( from virtusertable ).

When alias and user are the same sieve vacation works just fine but when
it's not the sieve script collects the user(ivan1)@domain.com in from
instead i...@domain.com and this is when mail log shows like discarded
message because of implicitily no known envelope in message header etc...

Is there a way to adjust sieve to pickup the recipient address from mail
header or whatever and not to collect the user...?

I was trying to play with postfix master.cf using dovecot-lda switches -f
${sender} -a (or -d ) ${recipient} but without success...

Did anyone had this kind of problem? I would really appreciate some hints
on fixing this issue...

Thanks,
Ivan

[Dovecot] Please HELP, TRASH won't work at all

2011-06-06 Thread Ivan Rodrigues 
Folks,

I'm setting a imap server here to store our mails, no need for quota or
anything fancy, we just need trash can to work, when I mark a message to
delete, this message to be moved to trash folder.

that's all that I need.

any thoughts?

[Dovecot] Help with Trash setup

2011-06-05 Thread Ivan Rodrigues 
Folks,

I'm trying to setup a mail server just to store my mail, i use fetchmail to
retrieve my messages and I want to configure the trash can, can you guys
please help me with this mater?


Dovecot Version: 1.2.9

No SQL nor LDAP installed

dovecot -n
# 1.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-24-generic-pae i686 Ubuntu 10.04.2 LTS
log_timestamp: %Y-%m-%d %H:%M:%S
login_dir: /var/run/dovecot/login
login_executable: /usr/lib/dovecot/imap-login
mail_privileged_group: mail
mail_location: maildir:~/Maildir
mbox_write_locks: fcntl dotlock
mail_plugins: delete_to_trash
auth default:
  passdb:
driver: pam
  userdb:
driver: passwd
plugin:
  deleted_to_trash_folder: Trash

[Dovecot] mbox sync: UID inserted in the middle of mailbox

2009-11-20 Thread Ivan S 
Hi All, 

Our webmail having an issue with the harddrive so I build new webmail on other 
machine (using Squirrelmail+dovecot+postfix). After copy all data/home folder 
from the backup, when this user want to access his Sent item, nothing's in it. 
I've checked the log and found the message as below. 

mailserver dovecot: IMAP(x): mbox sync: UID inserted in the middle of 
mailbox /home//mail/Sent (691  657, seq=473, idx_msgs=10950)
mailserver dovecot: IMAP(x): mbox sync: UID inserted in the middle of 
mailbox /home//mail/Sent (691  657, seq=473, idx_msgs=10950)

This is only happen with the Sent items, since I also found other similar log 
and this user advised that everything is fine with that folder

mailserver dovecot: IMAP(x): mbox sync: UID inserted in the middle of 
mailbox /home/x/mail/Accountant Info (327  326, seq=306, idx_msgs=353)
mailserver dovecot: IMAP(x): mbox sync: UID inserted in the middle of 
mailbox /home/x/mail/Accountant Info (327  326, seq=306, idx_msgs=353)

I've rebuild the index file by delete the Sent item folder in .imap directory, 
no such luck.

Any help would be really appreciated

Thank you

[Dovecot] renameing users

2008-06-02 Thread Ivan Levchenko 
Hi All,

I have a pretty basic question - I'm just getting into this email business =).

There is a server that uses virtual users with dovecot. How could I go
by allowing the users to change their usernames and to let them save
all of their info? Access to the mailboxes is provided via
squirrelmail .
Thanks in advance!
 p.s. please cc me in the reply!
-- 
Best Regards,

Ivan Levchenko
[EMAIL PROTECTED]

Re: [Dovecot] backup dovecot

2007-11-25 Thread Ivan Shmakov 
 Benjamin R Haskell [EMAIL PROTECTED] writes:

[...]

  An example of syncing 2 directories over ssh, keeping all permissions
  intact. This command run on the source maildir server.

  rsync -av -essh /source_maildirs/ [EMAIL PROTECTED]:/destination/maildirs/

  Couple tips (not criticisms): Nowadays, ssh is the default (unless
  compiled otherwise). So, the '-essh' is likely unneccessary. As is the
  'username@' part, if the username is the same.

... Or if it's different, but one took care to provide an entry
in ~/.ssh/config, like:

$ cat ~/.ssh/config
...

Host alias remote.host
  HostName remote.host
  User remote.user

...
$ 

  And something to watch out for as a new rsync user:

  The trailing slash is important on the source path. From the rsync 'man'
  page (read it!): A trailing slash on the source changes this behavior to
  avoid creating an additional directory level at the destination.

To put it short, SRC-DIR refers to a directory, and SRC-DIR/ --
to its contents.

  (But, it doesn't do anything on the destination path.)

  That'd shorten the command to:

  rsync -av /source_maildirs/ hostname:/destination/maildirs

[Dovecot] src/lib/Makefile.am: a trivial ``$(srcdir)'' patch

2007-11-19 Thread Ivan Shmakov 
May I suggest the following trivial patch?

diff -r ff9e591a2aa5 src/lib/Makefile.am
--- a/src/lib/Makefile.am   Sun Nov 18 21:44:22 2007 +0200
+++ b/src/lib/Makefile.am   Tue Nov 20 00:29:04 2007 +0600
@@ -4,9 +4,9 @@ BUILT_SOURCES = unicodemap.c
 
 EXTRA_DIST = unicodemap.c unicodemap.pl
 
-unicodemap.c:
+$(srcdir)/unicodemap.c:
test -f UnicodeData.txt || wget 
http://www.unicode.org/Public/UNIDATA/UnicodeData.txt
-   perl unicodemap.pl  UnicodeData.txt  $@
+   perl $(srcdir)/unicodemap.pl  UnicodeData.txt  $@
 
 liblib_a_SOURCES = \
backtrace-string.c \