similar to: Pigeonhole: Typo in 20-managesieve.conf

Displaying 20 results from an estimated 20000 matches similar to: "Pigeonhole: Typo in 20-managesieve.conf"

2019 Jan 11
2
managesieve configuration
Hi Dominik, I have set ssl = required in 10-ssl.conf globally but no ssl here: service managesieve-login { inet_listener sieve { port = 4190 } ... } Nevertheless, STARTTLS is offered "IMPLEMENTATION" "Dovecot Pigeonhole" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags
2015 Oct 30
2
updating and wsitching repo to yum.dovecot.fi - Unknown protocol: sieve
Am 30.10.15 um 11:49 schrieb Teemu Huovila: > > > On 30.10.2015 12:18, G?tz Reinicke - IT Koordinator wrote: >> Hi, >> >> winter is coming and so I start to clean up some left overs of the year. >> >> One thing is to use the yum.dovecot.fi repository. >> >> After installing the current availabel dovecot and dovecot-ee-pigeonhole >> package
2019 Jan 11
2
managesieve configuration
On 10.1.2019 18.28, Dominik Menke wrote: > I've missed a part at the end: > >> This leads me to my question: How do I force Dovecot to print at >> least a STARTTLS line after a client connects to port 4190? Looking > > ... at the default configuration files in /etc/dovecot/conf.d/ I don't > see an obvious difference. > > > --Dominik Can you provide
2017 Mar 08
2
Dovecot 2.2.27 proxy - enforcing per client IP connection limits
Hi, Trying to keep abusive/buggy IMAP clients at bay on a number of Dovecot proxy servers, I've reconfigured them to use "mail_max_userip_connections = 50" in the "protocol imap" section, followed by restarting Dovecot. Yet, I'm still seeing 160+ established connections from a single IP address for the same email account. Am I missing anything? # 2.2.27
2016 Apr 06
2
[help]enotify "mail to" run fine edit via managesieve 0.4.4 complied failed
hi all edit via vi editor to change dovecot.sieve and enotify works fine.but when I telnet 4190 port via managesieve to edit it with the same code,the managesieve said "NO "Error in MANAGESIEVE command CHECKSCRIPT: "", find many topic in wiki and maillist but not solved. need you help!thanks!!dovecot version 2.2.15,pigonhole version 0.4.4 here are more infos
2015 May 06
0
dovecot-proxy with managesieve, director and backend dovecot imap
hi all, I've been tasked to add sieve/managesieve to an existing dovecot cluster running 2.1.7 on debian wheezy which is made up of 2 dovecot-proxy hosts as directors and some back end dovecot imap hosts all running the same version. My problem is that I thought to put the service on the director/proxy hosts since they wouldn't have too much load on it, but when I do I get the
2017 Mar 14
3
Dovecot 2.2.27 proxy - enforcing per client IP connection limits
Hi, mail_max_userip_connections is only enforced at the backend level. The setting has no effect on proxy. If you want to force the limit then you can only do it in the backend. Sami > On 9 Mar 2017, at 12.05, Adi Pircalabu <adi at ddns.com.au> wrote: > > Quick follow-up: updated the proxies to 2.2.28, but I still couldn't find a way to limit the inbound IMAP connections per
2012 Mar 06
1
dovecot 2.1.1 + pigeonhole + avelsieve
Hello all, I've squirrelmail-webmail-1.4.22, dovecot 2.1.1, dovecot-2.1-pigeonhole-0.3.0 installed and working. But I've problems to get the avelsieve plugin for squirrelmail working with dovecot. The "Message Filters" show up in "Options" of squirrelmail, but "Could not log on to timsieved daemon on your IMAP server ........." dovecot log shows: Mar 6
2015 Apr 17
4
ManageSieve Dovecot v2 listen on localhost only
Hi, How can I only listen on localhost for ManageSieve? I tried: port = localhost:4190 still listening *: tcp 0 0 0.0.0.0:4190 0.0.0.0:* LISTEN 0 515675 20540/dovecot Would did I not get here? Thanks, -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-keys Size: 1718
2016 Sep 13
2
Replication: Can't unsubscribe from shared mailbox
Hi, I am running two dovecot servers active/active. Everything runs pretty great, except for the replication of subscriptions in a shared namespace. When I unsubscribe from a folder the subscription instantly re-appears. The timestamp on the subscriptions file is updated, but the entry is still in there. If the other node is shut down, everything works as expected, which leads me to believe that
2020 Aug 19
3
sieve_max_script_size is ignored
I am in troubles with compiling sieve scripts larger than 1MB. I see in logs following errors: Aug 19 13:10:26 mail dovecot: lmtp(z.z at xxx.xxx)<22117><uNBGHKIIPV9lVgAA5ldI4A>: Error: sieve: autoreply: line 16818: quoted string started at line 3 is too long (longer than 1048576 bytes) Aug 19 13:10:26 mail dovecot: lmtp(z.z at xxx.xxx)<22117><uNBGHKIIPV9lVgAA5ldI4A>:
2013 Jan 02
2
Trouble with expire plugin
Hi all, Maybe someone here can help me with this problem, not sure if this is a configuration issue or an actual bug. my daily cron job says: #!/bin/sh doveadm expunge -A mailbox Junk savedbefore 14d doveadm expunge -A mailbox Trash savedbefore 30d doveadm expunge -A mailbox "Trash.*" savedbefore 30d But it hasn't been deleting any messages in a long time, I'm not sure when
2012 Feb 21
1
dovecot 2 doesn't start with managesieve
Hi I build dovecot 2.0.16 and and dovecot-pigeonhole-0.2.5 on two machines with the same options. The config files are equivalent. On the first machine everything works fine - on the second dovecot with managesive won't start (without sieve protocol it does). Error: socket() failed: Protocol not supported Error: service(managesieve-login): listen(::, 4190) failed: Protocol not supported
2019 Oct 29
1
Sieve problem - Timeout while waiting for lock
Hi, I have an issue with dovecot 2.3.7.2. When lmtp stores a message into INBOX, I get this error: 2019-10-29 16:32:53 lmtp(?test at XXXX?)<28874><4IPiEytbuF3KcAAAioI89A>: Error: sieve: Execution of script /config/dovecot/common/default.sieve was aborted due to temporary failure 2019-10-29 16:32:53 lmtp(?test at XXXX?)<23470>: Error: sieve:
2019 Jun 09
2
Case sensitive problem for vacation with dovecot lmtp pigeonhole
Hi list, This issue was raised here by John Fawcett on 12/02/19 but got no response. So, as I'm facing the same issue, I would like to try again: When using the vacation sieve extension, if I send an email to user.name at mydomain.com it will work, but not to User.Name at mydomain.com. Is there a way to make the user part case insensitive so that the vacation auto-reply is fired whatever
2018 Nov 14
2
huge increase in storage activity afther dovecot upgrade
Hi, we upgraded our servers from version 2.2.13 to 2.2.27. After the upgrade we notice a 10x increase in traffic with the nfs storage an errors like this in the logfile: Nov 12 09:48:16 mail dovecot: imap(...): Error: Corrupted index cache file /.../dovecot.index.cache: invalid record size Nov 12 09:48:16 mail dovecot: imap(...): Error: unlink(/.../dovecot.index.cache) failed: No such file or
2010 Jun 25
1
Pigeonhole Managesieve issue with Dovecot 2.0
Hi all, ok, I am running version v2.0.beta6 and the latest pigeonhole build to run managesieve and the sieve delivery filters... I am getting the following response from the managesieve port when connecting : Escape character is '^]'. "IMPLEMENTATION" "Dovecot" "SIEVE" "" "SASL" "PLAIN" "STARTTLS" "VERSION"
2018 Feb 17
4
2.2.33.2 - Virtual Mailbox Issue bug maybe ?
Been experimenting with virtual mailbox and have a question :- I have defined 2 virtual mailboxes 'all' and 'combined' as follows ... virtual/all/dovecot-virtual virtual/combined inthread refs x-mailbox INBOX virtual/combined/dovecot-virtual !INBOX INBOX/Sent INBOX/Drafts all When new mail comes I would assume that both virtual mailboxes should actually see the message
2015 Aug 31
1
Problem with the Path argument in pigeonhole 0.4.3 at ubuntu 14.04
Hello list members I want dovecot managesieve to store its config unter ~/.dovecot.sieve additionally dovecot should read as sieve_after the file ~/.sieve It's working fine BUT dovecot managesieve is always symlinking the sieve file at activation to ~/.sieve and not to ~/.dovecot.sieve as i configured it. Any idears about this strange behaviour? dovecot is configured as follows # 2.2.9:
2018 Nov 14
2
huge increase in storage activity afther dovecot upgrade
Thank you ! I was little concerned that the following settings are not in line with the new version: mail_nfs_index = yes mail_nfs_storage = yes mail_fsync = always mailbox_list_index = yes maildir_stat_dirs = yes mmap_disable = yes On Wed, Nov 14, 2018 at 10:19 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > It should eventually wind down once all the problems are fixed. Of