Geting mail quota exceeded with plenty of space
I have a user that is getting mail quota exceeded: Feb 9 15:00:21 z9m9z dovecot: lda(d...@htt-consult.com): Error: sieve: msgid=38308773.1704736628308773ywdm@htt-consult.com853430: failed to store into mailbox 'INBOX': Quota exceeded (mailbox for user is full) Yet the quota is set for 1000Mb and the current reported use is 277Mb. There are only 28 messages in the in box and 842 in the spam. Where might the problem becoming from? The server is Redsleeve 6 (Centos6 on arm). I am running a combination of postfix/dovecot/roundcubemail with a mysql virtual domain database maintained with postfix.admin
Re: Geting mail quota exceeded with plenty of space
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Just modify and do dovecot reload. It'll ne alright
CONCAT('*:messages=1:bytes=', quota) as quota_rule FROM mailbox
WHERE username = '%u' AND active = '1'
Well there it is, clear as day. messages=1
Guess I can increase that. I suspect I will have to restart
dovecot
- --
CHUNKZ.NET - dodgy DIYer and computer technician
Bertrand Caplet, Flers (FR)
Feel free to send encrypted/signed messages
Key ID: FF395BD9
GPG FP: DE10 73FD 17EB 5544 A491 B385 1EDA 35DC FF39 5BD9
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1
iQJKBAEBCgA0BQJU2V0kLRxCZXJ0cmFuZCBDYXBsZXQgPGJlcnRyYW5kLmNhcGxl
dEBjaHVua3oubmV0PgAKCRAe2jXc/zlb2dfpD/41HrL10VzjkH2xJlcdUiCHdkTb
xwqh5eW7aINE501JUGdtRc58EVoNgSbXUCI7HYCWj83GFKWYvXXmDsenw/ARqrWU
4MBhxHDPYGbpdlCyVrtzjkaq192WyZgL8IJWERfc8Wu3s8K0j1xGGgS9q/dYh03i
MqRiooamRB6uQ6owFjrO0MFG5HYYrGsyjKb61cvsY2kXbyAjzI+ztk2w6Dbfmfne
WM02FlwjWBxeVaCJHJ9bqUPwuJaGJ+Bqby2UPv7tSP2/EButFoCIGXUnX8WXqgmG
MBh5QqEVfWTwWAIyAvSfNsXfopH2FJVgd0Ng1tfN8oCJQDQoFktQCriQPrEpXnOi
LKhKyLBiz4oiIn3icovn3AEjSqQTR5Q0cewwp18iJSDYa+7tMlsecincf6qd0ZFE
sfqCklkxfNVxBxKRgtaJIBCGWR9kx9VNU/g/5PjLfgzuewc1ku+24kBZYms0ZhIK
wqrkYLsy30aA/GXr8TPM42FFFCWwFDbDDeRpj8wS7t+p5fc5sUUMjzAILMyECueD
sMqrtIFm0dw7cbnsSTIzbD9MjbffvVMSvw3PA6WasWJgFEKjRoLS4S7U36svb9V1
triQybAqkIMTSk5fzeJXD0pv1gwW/1DLcUvSfHTHhFexkOxoVk7boLQ4lOU4tAlu
TOX+wuqJGIPHxF46yA==
=3kSh
-END PGP SIGNATURE-
Re: Geting mail quota exceeded with plenty of space
On 02/09/2015 03:37 PM, Bertrand Caplet wrote: Further checkings shows another user also getting Quota exceeded. This user has only 127Mb toward his quota. Only these two users have this problem. So far. Both are infrequent mail checkers. It might be the quota for number of messages : Could be. dm has over 9k of trashed messages. but.. Check with doveadm quota get -u user@domain.example If there is a limit for number of messages. doveadm(root): Fatal: Unknown command 'quota', but plugin quota exists. Try to set mail_plugins=quota
Re: Geting mail quota exceeded with plenty of space
On 02/09/2015 03:51 PM, Bertrand Caplet wrote: doveadm(root): Fatal: Unknown command 'quota', but plugin quota exists. Try to set mail_plugins=quota Show me your doveconf -n without your passwords. Tomorrow. Got a conference call that I am not ready for :(
Re: Geting mail quota exceeded with plenty of space
Further checkings shows another user also getting Quota exceeded. This user has only 127Mb toward his quota. Only these two users have this problem. So far. Both are infrequent mail checkers. On 02/09/2015 03:14 PM, Robert Moskowitz wrote: I have a user that is getting mail quota exceeded: Feb 9 15:00:21 z9m9z dovecot: lda(d...@htt-consult.com): Error: sieve: msgid=38308773.1704736628308773ywdm@htt-consult.com853430: failed to store into mailbox 'INBOX': Quota exceeded (mailbox for user is full) Yet the quota is set for 1000Mb and the current reported use is 277Mb. There are only 28 messages in the in box and 842 in the spam. Where might the problem becoming from? The server is Redsleeve 6 (Centos6 on arm). I am running a combination of postfix/dovecot/roundcubemail with a mysql virtual domain database maintained with postfix.admin
Re: Geting mail quota exceeded with plenty of space
that was it. Emptied trash and mail flowing. How is the message # quota managed? I never encountered it before. But don't have time today to dig into it. conference call coming up. You might have messages quota configured somewhere. And for : doveadm(root): Fatal: Unknown command 'quota', but plugin quota exists. Try to set mail_plugins=quota See http://wiki2.dovecot.org/Quota/Configuration you might haven't enabled quota plugin somewhere. -- CHUNKZ.NET - script kiddie and computer technician Bertrand Caplet, Flers (FR) Feel free to send encrypted/signed messages Key ID: FF395BD9 GPG FP: DE10 73FD 17EB 5544 A491 B385 1EDA 35DC FF39 5BD9 signature.asc Description: OpenPGP digital signature
Re: Geting mail quota exceeded with plenty of space
doveadm(root): Fatal: Unknown command 'quota', but plugin quota exists. Try to set mail_plugins=quota Show me your doveconf -n without your passwords. -- CHUNKZ.NET - script kiddie and computer technician Bertrand Caplet, Flers (FR) Feel free to send encrypted/signed messages Key ID: FF395BD9 GPG FP: DE10 73FD 17EB 5544 A491 B385 1EDA 35DC FF39 5BD9 signature.asc Description: OpenPGP digital signature
Re: Geting mail quota exceeded with plenty of space
Further checkings shows another user also getting Quota exceeded. This user has only 127Mb toward his quota. Only these two users have this problem. So far. Both are infrequent mail checkers. It might be the quota for number of messages : Check with doveadm quota get -u user@domain.example If there is a limit for number of messages. Regards, -- CHUNKZ.NET - script kiddie and computer technician Bertrand Caplet, Flers (FR) Feel free to send encrypted/signed messages Key ID: FF395BD9 GPG FP: DE10 73FD 17EB 5544 A491 B385 1EDA 35DC FF39 5BD9 signature.asc Description: OpenPGP digital signature
Re: Geting mail quota exceeded with plenty of space
On 02/09/2015 03:37 PM, Bertrand Caplet wrote: Further checkings shows another user also getting Quota exceeded. This user has only 127Mb toward his quota. Only these two users have this problem. So far. Both are infrequent mail checkers. It might be the quota for number of messages : that was it. Emptied trash and mail flowing. How is the message # quota managed? I never encountered it before. But don't have time today to dig into it. conference call coming up. Check with doveadm quota get -u user@domain.example If there is a limit for number of messages. Regards,
Re: Per-protocol ssl_protocols settings
Sorry for the bump... Anyone know if it is possible to have multiple protocols instances with different ssl_protocols settings? Regards. On 07/02/15 00:03, Gionatan Danti wrote: Hi all, anyone with some ideas? Thanks. Il 2015-02-02 23:08 Gionatan Danti ha scritto: Hi all, I have a question regarding the ssl_protocols parameter. I understand that editing the 10-ssl.conf file I can set the ssl_protocols variable as required. At the same time, I can edit a single protocol file (eg: 20-pop3.conf) to set the ssl_protocols for a specific protocol/listener. I wander if (and how) I can create a different listener for another POP3 instance, for example listening on port 10995, and using another ssl_protocol setting. In short, I would like to create a different, firewalled pop3s service enabling the SSLv3 stack, while disabling it at system-wide settings. I am able to successfully create a new listener for port 10995, but I don't understand how to associate the ssl_protocols value to the new listener. Simply putting the ssl_protocols value into the listener section give me a configuration error. Thank you all. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.da...@assyoma.it - i...@assyoma.it GPG public key ID: FF5F32A8
Re: Per-protocol ssl_protocols settings
I performed a quick test and it seems that the ssl_protocols setting is
per-IP only and shared among all listeners defined for that address. As you
want this setting to be active for one specific inet_listener only (with port
10995 in your case), dovecot would have to permit the ssl_protocols directive
in that scope, which it doesn’t.
As a workaround I suggest using a special, unused loopback address to which you
can apply the distinct SSL settings. You could use iptables/NAT to forward all
incoming traffic originating from your external IP on port 10995 to
127.0.0.2:10995 for example. Then configure the POP3 service with an
inet_listener for 127.0.0.2:10995 and use the local directive to set up the
SSL protocols without touching global settings:
local 127.0.0.2 {
ssl_protocols = !SSLv2
}
Regards,
Felix Zandanel
Am 09.02.2015 um 11:33 schrieb Gionatan Danti g.da...@assyoma.it:
Sorry for the bump...
Anyone know if it is possible to have multiple protocols instances with
different ssl_protocols settings?
Regards.
On 07/02/15 00:03, Gionatan Danti wrote:
Hi all,
anyone with some ideas?
Thanks.
Il 2015-02-02 23:08 Gionatan Danti ha scritto:
Hi all,
I have a question regarding the ssl_protocols parameter.
I understand that editing the 10-ssl.conf file I can set the
ssl_protocols variable as required.
At the same time, I can edit a single protocol file (eg: 20-pop3.conf)
to set the ssl_protocols for a specific protocol/listener.
I wander if (and how) I can create a different listener for another
POP3 instance, for example listening on port 10995, and using another
ssl_protocol setting.
In short, I would like to create a different, firewalled pop3s service
enabling the SSLv3 stack, while disabling it at system-wide settings.
I am able to successfully create a new listener for port 10995, but I
don't understand how to associate the ssl_protocols value to the new
listener. Simply putting the ssl_protocols value into the listener
section give me a configuration error.
Thank you all.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.da...@assyoma.it - i...@assyoma.it
GPG public key ID: FF5F32A8
Re: Postfix , Dovecot the Spam fight
Am 09.02.2015 um 22:29 schrieb Leander Schäfer: So my question is: Does AmaViS have any advantages compared to the current setup? I don't seem to find lots of qualified discussions for this on the net. The AmaViS related articles I found are freaking old. Would be nice the get your best practice as a change. Amavis is a framework, i has more stuff included you might like i.e you wanna use more antivir providers, use it for dkim and lot more, anyway if you dont wanna use it , it may better switch to clamav-milter and spamass-milter from you recent setup perhaps read http://www.ijs.si/software/amavisd/#features after all this isnt a true dovecot question, ask amavis postfix lists Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Re: Geting mail quota exceeded with plenty of space
On 02/09/2015 03:51 PM, Bertrand Caplet wrote:
doveadm(root): Fatal: Unknown command 'quota', but plugin quota exists.
Try to set mail_plugins=quota
Show me your doveconf -n without your passwords.
I looked and no passwords in my doveconf...
# 2.0.9: /etc/dovecot/dovecot.conf
# OS: Linux 3.4.61.sun7i+ armv7l Red Sleeve Enterprise Linux release 6
(Leap) ext4
auth_mechanisms = plain login
dict {
quotadict = mysql:/etc/dovecot/dovecot-dict-quota.conf
}
first_valid_gid = 12
first_valid_uid = 101
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
lmtp_save_to_detail_mailbox = yes
mail_location = maildir:/home/vmail/%d/%n
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date
passdb {
args = /etc/dovecot/dovecot-mysql.conf
driver = sql
}
plugin {
acl = vfile:/etc/dovecot/acls
quota = dict:user::proxy::quotadict
sieve = ~/dovecot.sieve
sieve_dir = ~/sieve
sieve_global_dir = /home/sieve/
sieve_global_path = /home/sieve/globalfilter.sieve
sieve_max_script_size = 1M
trash = /etc/dovecot/trash.conf
}
protocols = imap pop3 lmtp sieve
service anvil-auth-penalty {
name = anvil
}
service auth-worker {
name = auth-worker
}
service {
unix_listener {
group = postfix
mode = 0666
user = postfix
path = /var/spool/postfix/private/auth
}
unix_listener {
group = mail
mode = 0666
user = vmail
path = auth-userdb
}
name = auth
}
service config {
name = config
}
service {
unix_listener {
group = mail
mode = 0666
user = vmail
path = dict
}
name = dict
}
service login/proxy-notify {
name = director
}
service dns-client {
name = dns_client
}
service doveadm-server {
name = doveadm
}
service {
inet_listener {
port = 143
name = imap
}
inet_listener {
port = 993
ssl = yes
name = imaps
}
name = imap-login
}
service login/imap {
vsz_limit = 256 M
name = imap
}
service lmtp {
name = lmtp
}
service {
inet_listener {
port = 4190
name = sieve
}
process_min_avail = 0
service_count = 1
vsz_limit = 64 M
name = managesieve-login
}
service login/sieve {
name = managesieve
}
service {
inet_listener {
port = 110
name = pop3
}
inet_listener {
port = 995
ssl = yes
name = pop3s
}
name = pop3-login
}
service login/pop3 {
name = pop3
}
service login/ssl-params {
name = ssl-params
}
ssl_cert = /etc/pki/tls/certs/z9m9z.htt-consult.com.crt
ssl_key = /etc/pki/tls/private/z9m9z.htt-consult.com.key
userdb {
driver = prefetch
}
userdb {
args = /etc/dovecot/dovecot-mysql.conf
driver = sql
}
protocol lda {
mail_plugins = quota sieve
postmaster_address = postmas...@htt-consult.com
service anvil-auth-penalty {
name = anvil
}
service auth-worker {
name = auth-worker
}
service auth-client {
name = auth
}
service config {
name = config
}
service dict {
name = dict
}
service login/proxy-notify {
name = director
}
service dns-client {
name = dns_client
}
service doveadm-server {
name = doveadm
}
service imap {
name = imap-login
}
service login/imap {
name = imap
}
service lmtp {
name = lmtp
}
service sieve {
name = managesieve-login
}
service login/sieve {
name = managesieve
}
service pop3 {
name = pop3-login
}
service login/pop3 {
name = pop3
}
service login/ssl-params {
name = ssl-params
}
}
protocol imap {
imap_client_workarounds = delay-newmail
mail_plugins = quota imap_quota trash
service anvil-auth-penalty {
name = anvil
}
service auth-worker {
name = auth-worker
}
service auth-client {
name = auth
}
service config {
name = config
}
service dict {
name = dict
}
service login/proxy-notify {
name = director
}
service dns-client {
name = dns_client
}
service doveadm-server {
name = doveadm
}
service imap {
name = imap-login
}
service login/imap {
name = imap
}
service lmtp {
name = lmtp
}
service sieve {
name = managesieve-login
}
service login/sieve {
name = managesieve
}
service pop3 {
name = pop3-login
}
service login/pop3 {
name = pop3
}
service login/ssl-params {
name = ssl-params
}
}
protocol lmtp {
mail_plugins = sieve
service anvil-auth-penalty {
name = anvil
}
service auth-worker {
name = auth-worker
}
service auth-client {
name = auth
}
service config {
name = config
}
service dict {
name = dict
}
service login/proxy-notify {
name = director
}
service dns-client {
name = dns_client
}
service doveadm-server {
name = doveadm
}
service imap {
name = imap-login
}
service login/imap {
name = imap
}
service lmtp {
Postfix , Dovecot the Spam fight
Hi, I'm currently busy with a substiution of my current mail server. I'm currently using * Clam-SMTP and * SpamAssassin to fight Spam. I wonder if it is worth implementing AmaViS with SpamAssassin backend instead and also using AmaViS to speak to clamd directly. But I more and more wonder wether AmaViS is even worth it?! It currently looks to me as if AmaViS is eating LOTS of ressources and it is very uncomfortable for automated installations if you have to do dynamic batch changes on the AmaViS configs - sed(1) is your friend but this hectic escaping and workarrounds is really not sustainable to maintain. So my question is: Does AmaViS have any advantages compared to the current setup? I don't seem to find lots of qualified discussions for this on the net. The AmaViS related articles I found are freaking old. Would be nice the get your best practice as a change. Thanks a lot Best regards Leander
Re: Postfix , Dovecot the Spam fight
Am 09.02.2015 um 22:29 schrieb Leander Schäfer: I'm currently busy with a substiution of my current mail server. I'm currently using * Clam-SMTP and * SpamAssassin to fight Spam. I wonder if it is worth implementing AmaViS with SpamAssassin backend instead and also using AmaViS to speak to clamd directly. But I more and more wonder wether AmaViS is even worth it?! It currently looks to me as if AmaViS is eating LOTS of ressources and it is very uncomfortable for automated installations if you have to do dynamic batch changes on the AmaViS configs - sed(1) is your friend but this hectic escaping and workarrounds is really not sustainable to maintain. So my question is: Does AmaViS have any advantages compared to the current setup? I don't seem to find lots of qualified discussions for this on the net. The AmaViS related articles I found are freaking old. Would be nice the get your best practice as a change i don't see advantages but issues if you ask something on the SA list and finally find out that amavis handles configurations different ressource usage is mostly the same, amavis is only the glue the hard work is done anyways by spamassassin and clamav for both milters exists so you can reject spam instead only flag and deliver or even more worse silently discard it - not a real problem with postscreen and RBL scroing in front, happy running here since 2014/08 with zero load even at peaks of 400 junk attempts per minute smtpd_milters = unix:/run/spamass-milter/spamass-milter.sock, unix:/run/clamav-milter/clamav-milter.socket signature.asc Description: OpenPGP digital signature
Re: Postfix , Dovecot the Spam fight
Hi Harald puuhh - thank you for your positive feedback. I'm really relieved ;) It's been a pleasure to write batch scripts for configurin SpamAssassin - and it has also been running like a charm the past 6 years. Go to hell AmaViS ! Crap ;) Best regards Leander Am 09.02.15 um 22:33 schrieb Reindl Harald: Am 09.02.2015 um 22:29 schrieb Leander Schäfer: I'm currently busy with a substiution of my current mail server. I'm currently using * Clam-SMTP and * SpamAssassin to fight Spam. I wonder if it is worth implementing AmaViS with SpamAssassin backend instead and also using AmaViS to speak to clamd directly. But I more and more wonder wether AmaViS is even worth it?! It currently looks to me as if AmaViS is eating LOTS of ressources and it is very uncomfortable for automated installations if you have to do dynamic batch changes on the AmaViS configs - sed(1) is your friend but this hectic escaping and workarrounds is really not sustainable to maintain. So my question is: Does AmaViS have any advantages compared to the current setup? I don't seem to find lots of qualified discussions for this on the net. The AmaViS related articles I found are freaking old. Would be nice the get your best practice as a change i don't see advantages but issues if you ask something on the SA list and finally find out that amavis handles configurations different ressource usage is mostly the same, amavis is only the glue the hard work is done anyways by spamassassin and clamav for both milters exists so you can reject spam instead only flag and deliver or even more worse silently discard it - not a real problem with postscreen and RBL scroing in front, happy running here since 2014/08 with zero load even at peaks of 400 junk attempts per minute smtpd_milters = unix:/run/spamass-milter/spamass-milter.sock, unix:/run/clamav-milter/clamav-milter.socket
Re: Geting mail quota exceeded with plenty of space
On 02/09/2015 04:04 PM, Bertrand Caplet wrote:
that was it. Emptied trash and mail flowing. How is the message #
quota managed? I never encountered it before.
But don't have time today to dig into it. conference call coming up.
You might have messages quota configured somewhere.
And for :
doveadm(root): Fatal: Unknown command 'quota', but plugin quota
exists. Try to set mail_plugins=quota
See http://wiki2.dovecot.org/Quota/Configuration you might haven't
enabled quota plugin somewhere.
/etc/dovecot/dovecot-dict-quota.conf
connect = host=localhost dbname=postfix user=postfix password=***
map {
pattern = priv/quota/storage
table = quota2
username_field = username
value_field = bytes
}
map {
pattern = priv/quota/messages
table = quota2
username_field = username
value_field = messages
}
/etc/dovecot/dovecot-mysql.conf
driver = mysql
connect = host=localhost dbname=postfix user=postfix password=***
default_pass_scheme = MD5-CRYPT
password_query = SELECT username as user, password,
concat('/home/vmail/', maildir) as userdb_home,
concat('maildir:/home/vmail/', maildir) as userdb_mail, 101 as
userdb_uid, 12 as userdb_gid FROM mailbox WHERE username = '%u' AND
active = '1'
user_query = SELECT concat('/home/vmail/', maildir) as home,
concat('maildir:/home/vmail/', maildir) as mail, 101 AS uid, 12 AS gid,
CONCAT('*:messages=1:bytes=', quota) as quota_rule FROM mailbox
WHERE username = '%u' AND active = '1'
Well there it is, clear as day. messages=1
Guess I can increase that. I suspect I will have to restart dovecot
Mails Not Deleting in first POP3 Session
The dovecot -n output is attached to this email. Filename dovecot-n_filtered.conf. Dovecot Version: 2.2.10 OS: CentOS 6.6 MTA: Postfix version 2.6.6 The system is using dsync between two mailbox servers. Problem: When a pop3 session deletes a new message and the pop3 session ends, the message is not deleted. On a subsequent pop3 session, the same messages is deleted again and when the session ends, this time the messages is removed. This results in automated scripts getting duplicate messages. Previous mail server utilized postfix and dbmail. The problem did not exist. All of our replication settings are located in the file /etc/dovecot/conf.d/12-replicator.conf. When I move the above file out of /etc/dovecot/conf.d/ on both mailbox servers and restart dovecot, the pop3 deletion problem goes away and the system behaves as expected i.e. when a messages is deleted, it's removed when the session ends (of course its not replicated to the secondary server). Numerous tests using IMAP and deleted messages behaved as expected.with or without replication Here is some additional information that I hope helps: Below I'm running watch 'pwd; ls -l; echo ../cur; ls -l ../cur | tail -2' On the primary mailbox server: Every 2.0s: pwd; ls -l; echo ../cur; ls -l ../cur | t... Mon Feb 9 22:42:04 2015 /home/vmail/nascom.nasa.gov/test_u/new total 48 -rw--- 1 vmail mail 46223 Feb 9 22:41 1423521693.M193283P20903.mbox-open-1.nasc om.nasa.gov,S=46223,W=46902 ../cur -rw--- 1 vmail mail 3269 Nov 28 16:23 1417191796.M570666P7291.mbox-open-1.nascom .nasa.gov,S=3269,W=3980:2, -rw--- 1 vmail mail 3269 Nov 28 16:23 1417191797.M813970P7291.mbox-open-1.nascom .nasa.gov,S=3269,W=3980:2, On the backup mailbox server: Every 2.0s: pwd; ls -l; echo ../cur; ls -l ../cur... Mon Feb 9 22:44:12 2015 /home/vmail/nascom.nasa.gov/test_u/new total 48 -rw--- 1 vmail mail 46223 Feb 9 22:41 1423521693.M193283P20903.mbox-open-1. nascom.nasa.gov,S=46223,W=46902 ../cur -rw--- 1 vmail mail 3269 Nov 28 16:23 1417191796.M570666P7291.mbox-open-1.na scom.nasa.gov,S=3269,W=3980:2, -rw--- 1 vmail mail 3269 Nov 28 16:23 1417191797.M813970P7291.mbox-open-1.na scom.nasa.gov,S=3269,W=3980:2, After I connect to the primary mailbox server using openssl s_client -connect mail1.example.com:995 tls1_2 user test_u pass 123456 output below from the same watch command from above: Primary Every 2.0s: pwd; ls -l; echo ../cur; ls -l ../cur | t... Mon Feb 9 22:47:50 2015 /home/vmail/nascom.nasa.gov/test_u/new total 0 ../cur -rw--- 1 vmail mail 3269 Nov 28 16:23 1417191797.M813970P7291.mbox-open-1.nasco m.nasa.gov,S=3269,W=3980:2, -rw--- 1 vmail mail 46223 Feb 9 22:41 1423521693.M193283P20903.mbox-open-1.nasc om.nasa.gov,S=46223,W=46902:2, Secondary: Every 2.0s: pwd; ls -l; echo ../cur; ls -l ../cur... Mon Feb 9 22:48:14 2015 /home/vmail/nascom.nasa.gov/test_u/new total 48 -rw--- 1 vmail mail 46223 Feb 9 22:41 1423521693.M193283P20903.mbox-open-1. nascom.nasa.gov,S=46223,W=46902 ../cur -rw--- 1 vmail mail 3269 Nov 28 16:23 1417191796.M570666P7291.mbox-open-1.na scom.nasa.gov,S=3269,W=3980:2, -rw--- 1 vmail mail 3269 Nov 28 16:23 1417191797.M813970P7291.mbox-open-1.na scom.nasa.gov,S=3269,W=3980:2, So far, on the primary, the new message is moved to the cur directory while on the backup the new messages is still in new. I perform a list command to get the message I want to delete. In this case the message number is 2402 so it looks like this... list . . . 2401 2402 dele 2402 +OK Marked to be deleted quit Here's the primary: Every 2.0s: pwd; ls -l; echo ../cur; ls -l ../cur | t... Mon Feb 9 22:53:16 2015 /home/vmail/nascom.nasa.gov/test_u/new total 48 -rw--- 1 vmail mail 46223 Feb 9 22:41 1423521693.M193283P20903.mbox-open-1.nasc om.nasa.gov,S=46223,W=46902 ../cur -rw--- 1 vmail mail 3269 Nov 28 16:23 1417191796.M570666P7291.mbox-open-1.nascom .nasa.gov,S=3269,W=3980:2, -rw--- 1 vmail mail 3269 Nov 28 16:23 1417191797.M813970P7291.mbox-open-1.nascom .nasa.gov,S=3269,W=3980:2, Here's the secondary: Every 2.0s: pwd; ls -l; echo ../cur; ls -l ../cur... Mon Feb 9 22:53:38 2015 /home/vmail/nascom.nasa.gov/test_u/new total 48 -rw--- 1 vmail mail 46223 Feb 9 22:41 1423522362.M879542P21023.mbox-open-2. nascom.nasa.gov,S=46223,W=46902 ../cur -rw--- 1 vmail mail 3269 Nov 28 16:23 1417191796.M570666P7291.mbox-open-1.na scom.nasa.gov,S=3269,W=3980:2, -rw--- 1 vmail mail 3269 Nov 28 16:23 1417191797.M813970P7291.mbox-open-1.na scom.nasa.gov,S=3269,W=3980:2, See we see the message on the primary is moved back to new while the message on the secindary has a name change. Now for the second session (again using openssl): +OK Dovecot ready. user test_u +OK pass --- +OK Logged in. Here's the output on the primary: Every 2.0s: pwd; ls -l; echo ../cur; ls -l ../cur | t... Mon Feb 9 22:56:27 2015 /home/vmail/nascom.nasa.gov/test_u/new total 0 ../cur
