1

Topic: managesieve incoming redirected email limit

==== Required information ====
- iRedMail version (check /etc/iredmail-release): latest
- Linux/BSD distribution name and version: centos 7.2
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): mysql
- Web server (Apache or Nginx):apache
- Manage mail accounts with iRedAdmin-Pro?no
- Related log if you're reporting an issue:

Is there a limit of incoming emails which can be redirected to specific folder?
I have 58 emails which are redirected to specific folder but can't add it anymore.
I get error when I try to save.

====

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: managesieve incoming redirected email limit

I'm confused what the "redirect" we're talking about. Could you please show us the sieve rule?

3 (edited by Blisk 2016-10-10 17:09:19)

Re: managesieve incoming redirected email limit

here is print screen of rule, I can put 58 emails in one rule but that's it id doesn't allow more.
So where is that limit set?

Post's attachments

2016-10-10 11_05_53-Roundcube Webmail __ Filtri.png 163.6 kb, file has never been downloaded. 

You don't have the permssions to download the attachments of this post.

4

Re: managesieve incoming redirected email limit

No idea yet.

1) It seems a limit by Roundcube, but i cannot find any setting in its config file (plugins/managesieve/).
2) A POSSIBLE solution is increasing size of Dovecot setting "managesieve_max_line_length =", default is 65536, you can try to increase it and try again. Reference:
http://wiki2.dovecot.org/Pigeonhole/Man … figuration

If #2 doesn't work for you, please try to get support from Roundcube mailing list or issue tracker:
https://roundcube.net/support/

5

Re: managesieve incoming redirected email limit

Sorry can't find this "managesieve_max_line_length ="
in dovecot.conf or everywhere else in dovecot folder.

6

Re: managesieve incoming redirected email limit

Just add it manually inside "protocol sieve {}" block.