Displaying 20 results from an estimated 4000 matches similar to: "imapsieve: setting imapsieve_url disables admin scripts"
2020 Oct 27
0
imapsieve: setting imapsieve_url disables admin scripts
On 27/10/2020 11:32, Gedalya wrote:
> Hello,
>
> The documentation says imapsieve_url "has no effect on the administrator-controlled Sieve scripts". However, when setting this item, I get lines such as:
>
> Error: imapsieve: mailbox INBOX: Failed to read /shared/imapsieve/script mailbox attribute: Mailbox attributes not enabled
>
> and that's it.
2017 Aug 22
2
imapsieve: failed to read mailbox attribute
On Tue, Aug 22, 2017 at 01:55:45PM +0300, Aki Tuomi wrote:
>
>
>On 22.08.2017 13:37, Darac Marjal wrote:
>> Hello all,
>>
>> Hopefully this is something fairly simple.
>>
>> I've been trying to set up the Sieve Antispam system as detailed at
>> https://wiki2.dovecot.org/HowTo/AntispamWithSieve, but at the moment,
>> whenever I change mailboxes
2017 Aug 22
2
imapsieve: failed to read mailbox attribute
Hello all,
Hopefully this is something fairly simple.
I've been trying to set up the Sieve Antispam system as detailed at
https://wiki2.dovecot.org/HowTo/AntispamWithSieve, but at the moment,
whenever I change mailboxes I get the following message logged:
Aug 22 09:30:45 remy dovecot: imap(darac at darac.org.uk): Error: imapsieve:
mailbox INBOX: Failed to read /shared/imapsieve/script
2017 Dec 25
3
Sieve 0.5.0/Dovecot 2.3.0
Updated (current) doveconf -n attached....
On Mon, Dec 25, 2017 at 04:33:16PM -0600, Larry Rosenman wrote:
> FTR, this is being delivered via LMTP from Exim using the recommended transport / director.
>
> headers from one of my tests:
> Return-Path: <ler at lerctr.org>
> Delivered-To: ler at lerctr.org
> Received: from thebighonker.lerctr.org
> by
2017 Dec 25
2
Sieve 0.5.0/Dovecot 2.3.0
Using 2.3.0/0.5 and the below scripts/config, why doesn?t a mail addressed to ler_freebsd at lerctr.org get the FreeBSD flag?
.dovecot.sieve points to master.sieve.
Scripts:
http://www.lerctr.org/~ler/sieve/
doveconf -n:
thebighonker.lerctr.org /home/ler/sieve $ doveconf -n
# 2.3.0 (c8b89eb): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.0 (d68c23a1)
# OS: FreeBSD
2017 Jul 13
5
passwd-file, getting invalid uid 0
Per my earlier post about system and virtual users, I have everything working, but I'm seeing the
following message, and wondering:
1) does it matter?
2) is there a way to suppress it?
I have an Exim /etc/aliases entry that sends root to me.
Jul 13 14:38:47 thebighonker dovecot: auth-worker(13055): Error: passwd-file /etc/passwd: User root has invalid UID '0'
doveconf -n:
# 2.2.31
2019 Sep 27
3
Dovecote IMAPSieve user scripts
Hello,
I wonder how to configure IMAPSieve with user scripts. I can't find much
information on the internet.
I have Sieve and IMAPSieve for spam configured as described in the wiki
and it works.
Documentation mentions that imapsieve_url has to be set to appropriate
ManageSieve server but no further explanation is given.
What I want to achieve: let users create their own sieve scripts and
2019 Sep 08
1
Subscribe to a fileinto :create mailbox?
Is it possible in pigeonhole?
I.E. I do a fileinto :create "some/mail/box"
How can I make it autosubscribe?
doveconf -n:
# 2.3.7.2 (3c910f64b): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.7.2 (7372921a)
# OS: FreeBSD 12.0-STABLE amd64
# Hostname: thebighonker.lerctr.org
auth_default_realm = lerctr.org
auth_mechanisms = plain login
auth_realms = lerctr.org
2017 Jul 18
1
passwd-file, getting invalid uid 0
Did you miss the part about 0 also being hardcoded?
On Tue, Jul 18, 2017 at 1:34 PM Larry Rosenman <larryrtx at gmail.com> wrote:
> On Tue, Jul 18, 2017 at 3:31 PM, Larry Rosenman <larryrtx at gmail.com>
> wrote:
>
> > That didn't change it :(
> > Jul 18 15:28:14 thebighonker dovecot: auth-worker(77908): Error:
> > passwd-file /etc/passwd: User root has
2017 Jun 02
2
SIG11/Auth/FreeBSD
I'm seeing lots of:
Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM
IN) [52.40.16.7]:51339 I=[192.147.25.65]:465: 535 Incorrect authentication data (set_id=web)
Jun 2 00:00:06 thebighonker exim[57439]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM
IN)
2017 Jul 18
1
passwd-file, getting invalid uid 0
# Valid UID range for users, defaults to 500 and above. This is mostly
# to make sure that users can't log in as daemons or other system users.
# Note that denying root logins is hardcoded to dovecot binary and can't
# be done even if first_valid_uid is set to 0.
#first_valid_uid = 500
#last_valid_uid = 0
Aki
> On July 18, 2017 at 9:23 PM Larry Rosenman <larryrtx at gmail.com>
2017 Aug 23
0
imapsieve: failed to read mailbox attribute
Op 22-8-2017 om 13:03 schreef Darac Marjal:
> On Tue, Aug 22, 2017 at 01:55:45PM +0300, Aki Tuomi wrote:
>>
>>
>> On 22.08.2017 13:37, Darac Marjal wrote:
>>> Hello all,
>>>
>>> Hopefully this is something fairly simple.
>>>
>>> I've been trying to set up the Sieve Antispam system as detailed at
>>>
2018 Feb 26
1
dovecot solr and users
Hello,
I'm trying to get fts searching done with dovecot. I keep getting the
below error. Any help appreciated?
Thanks.
Dave.
#doveadm index -A inbox
doveadm(user at example.com): Info: User no longer exists, skipping
#doveconf -n
# 2.2.33.2 (d6601f4ec): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.21 (92477967)
# OS: FreeBSD 11.1-RELEASE-p4 amd64
auth_cache_size = 10 M
2018 Jun 07
2
dovecot-pigeonhole Missing sieve_imapsieve Plugin?
Hi Folks,
I am having a problem configuring imapsieve via dovecot-pidgeonhole on CentOS7.
After following the docs here:
https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve
I get:
dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve
dovecot[22026]: doveconf: Error: managesieve-login: dump-capability process returned 89
2017 Jun 05
0
fts_solr: uid0?
I'm seeing the following:
Jun 5 11:10:52 thebighonker dovecot: imap(ler): Error: fts_solr: received invalid uid '0'
Is there something I can get for you to debug?
doveconf -n:
# 2.2.30.1 (eebd877): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.18 (29cc74d)
# OS: FreeBSD 11.1-PRERELEASE amd64
auth_debug_passwords = yes
auth_default_realm = lerctr.org
auth_mechanisms
2017 Jun 30
0
uid '0' from fts_solr?
I'm getting lots of:
Jun 30 14:41:34 thebighonker dovecot: imap(ler/14135): Error: fts_solr: received invalid uid '0'
in my logs.
Ideas?
doveconf -n:
# 2.2.31 (65cde28): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.19 (e5c7051)
# OS: FreeBSD 11.1-BETA2 amd64
auth_default_realm = lerctr.org
auth_mechanisms = plain login
auth_realms = lerctr.org
2017 Jun 04
0
SIG11/Auth/FreeBSD
On Fri, Jun 02, 2017 at 11:15:41AM -0500, Larry Rosenman wrote:
> I'm seeing lots of:
[snipped]
> Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM
> IN) [52.40.16.7]:51339 I=[192.147.25.65]:465: 535 Incorrect authentication data (set_id=web)
> Jun 2 00:00:06 thebighonker exim[57439]: dovecot_login
2017 Jun 16
0
Error: fts_solr: received invalid uid '0'?
I'm getting a lot of:
Jun 16 11:40:40 thebighonker dovecot: imap(ler/58755): Error: fts_solr: received invalid uid '0'
Jun 16 11:40:40 thebighonker dovecot: imap(ler/58755): Error: fts_solr: received invalid uid '0'
in my logs. What can I supply to help get to the bottom of it?
doveconf -n:
# 2.2.30.2 (c0c463e): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version
2018 Oct 19
1
Fatal: setgid, imap connections dropped.
On 18.10.2018 21.24, J. de Meijer wrote:
>> On 16.10.2018 21.32, J. de Meijer wrote:
>>> I'm still trying to fix this problem. Hopefully someone can help.
>>>
>>> I've upgraded dovecot to 2.3.3
>>> # dovecot --version
>>> 2.3.3 (dcead646b)
>>>
>>> That didn't help.
>>>
>>> Next I switched
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>: