Resubmission after N days

2015-02-03 Thread Thomas Güttler
Hi, I would like to implement a 43Folder system[1] with dovecot and a mail user agent. Use case: - I have a new mail in my inbox. I read it and see that I can't handle it now. I want to handle this mail in 5 days. - Now I want to have some sort of resubmission: the mail should be moved to a

AW: Resubmission after N days

2015-02-03 Thread André Peters
Hi, Sounds to me like it can be implemented using sieve. Something like if is in inbox is read is older than n days; then mark as unread. But this means you need to redeliever this mail somehow. Maybe like this: http://serverfault.com/questions/418681/run-sieve-on-maildir

Re: Resubmission after N days

2015-02-03 Thread Steffen Kaiser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 4 Feb 2015, Steffen Kaiser wrote: On Wed, 4 Feb 2015, Thomas Güttler wrote: I would like to implement a 43Folder system[1] with dovecot and a mail user agent. Use case: - I have a new mail in my inbox. I read it and see that I can't

Re: Resubmission after N days

2015-02-03 Thread Steffen Kaiser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 4 Feb 2015, Thomas Güttler wrote: I would like to implement a 43Folder system[1] with dovecot and a mail user agent. Use case: - I have a new mail in my inbox. I read it and see that I can't handle it now. I want to handle this mail in

Re: Corruption of index files

2015-02-03 Thread Oliver Welter
Am 25.01.2015 um 12:45 schrieb Oliver Welter: Hi Andreas, Am 25.01.2015 um 12:41 schrieb Andreas Schulze: Oliver Welter: after upgrading my mail server (dovecot 1.1.7 - 2.2.13) I get tons of messages about corrupted index files in the syslog (Error: Corrupted transaction log and Warning:

Re: AW: Resubmission after N days

2015-02-03 Thread Randall Gellens
Is there an extension to allow Sieve to reprocess messages? Normally, Sieve is executed as new messages arrive. Once the message is filed or rejected, Sieve is done and won't get called again on the same message. Now, you could have some other external script that checked periodically for the

Re: Hitting wall at 2048 IMAP connections

2015-02-03 Thread Florian Pritz
On 03.02.2015 15:35, Ron Cleven wrote: /proc/sys/fs/inotify/max_user_instances = 4096 Maybe you are hitting some file descriptor limit (kernel or ulimit)? This could help: https://unix.stackexchange.com/questions/36841/why-is-number-of-open-files-limited-in-linux signature.asc Description:

Re: Hitting wall at 2048 IMAP connections

2015-02-03 Thread Steffen Kaiser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 3 Feb 2015, Ron Cleven wrote: We are gradually rolling out Dovecot (IMAP only, no POP3) to our customer base. We are replicating between a pair of CentOS 7 boxes. All has been working wonderfully. However, to be sure our rollout

Hitting wall at 2048 IMAP connections

2015-02-03 Thread Ron Cleven
We are gradually rolling out Dovecot (IMAP only, no POP3) to our customer base. We are replicating between a pair of CentOS 7 boxes. All has been working wonderfully. However, to be sure our rollout continues to go smoothly, we put together a simple benchmark client program to fire up X

Re: Hitting wall at 2048 IMAP connections

2015-02-03 Thread Jiri Bourek
On 02/03/2015 03:35 PM, Ron Cleven wrote: We are gradually rolling out Dovecot (IMAP only, no POP3) to our customer base. We are replicating between a pair of CentOS 7 boxes. All has been working wonderfully. However, to be sure our rollout continues to go smoothly, we put together a simple

Re: Upstart script for Poolmon

2015-02-03 Thread Listas@Adminlinux
If any of you need, this worked for me: root@director-server:~# cat /etc/init/poolmon.conf # Starts the poolmon daemon # # Description: # Poolmon is a director mailserver pool monitoring script for Dovecot, meant # toroughly duplicate the functionality of node health monitors on dedicated #

Re: Master user without pass=yes error

2015-02-03 Thread Thomas HUMMEL
On Mon, Feb 02, 2015 at 05:55:26PM +0100, Thomas HUMMEL wrote: Hello Timo, Hello again. I'll try to answer my own question myself ;-) I think my problem was that pass=yes just becomes _mandatory_ when using _only one_ and _prefetched_ userdb because retrieving the normal user userdb attributes