Displaying 20 results from an estimated 10000 matches similar to: "Bug maybe already resolved? Sieve rule does not accept special use folder names"
2020 Apr 16
2
Bug maybe already resolved? Sieve rule does not accept special use folder names
I do not have the log file anymore from the home dir. It just complains
that the folder Spam does not exist.
dovecot: lmtp(xxxx): oG8YI6enmF7FIAAAI7dPvA: sieve: Execution of script
/xxxx/.dovecot.sieve failed, but implicit keep was successful (user
logfile /xxx/.dovecot.sieve.log may reveal additional details)
-----Original Message-----
From: Stephan Bosch [mailto:stephan at rename-it.nl]
2020 Apr 16
2
Bug maybe already resolved? Sieve rule does not accept special use folder names
It is a 'special use' folder, so it only appears to exist in mail
clients.
# spam folders merging
mailbox Junk {
special_use = \Junk
auto = create
}
mailbox Spam {
special_use = \Junk
auto = no
}
mailbox "Junk E-mail" {
special_use = \Junk
auto = no
}
On 16/04/2020 23:19, Marc Roos wrote:
> I do not have the log file anymore from the
2020 Apr 16
1
Bug maybe already resolved? Sieve rule does not accept special use folder names
Hmmm, confusing, clients should then display the mailbox name redirected
by the server.
If a user in a front end just sees the 'Junk E-mail', that is the name
he is going to be using in his mailbox rules. If he does not know that
this is actually the Junk folder on the server, he will make an
incorrect message rule.
So I guess you have to correct this server side, before storing
2020 Apr 16
0
Bug maybe already resolved? Sieve rule does not accept special use folder names
On 16/04/2020 23:38, Marc Roos wrote:
> It is a 'special use' folder, so it only appears to exist in mail
> clients.
>
> # spam folders merging
> mailbox Junk {
> special_use = \Junk
> auto = create
> }
> mailbox Spam {
> special_use = \Junk
> auto = no
> }
> mailbox "Junk E-mail" {
> special_use
2020 Apr 16
0
Bug maybe already resolved? Sieve rule does not accept special use folder names
On 16/04/2020 23:19, Marc Roos wrote:
> I do not have the log file anymore from the home dir. It just complains
> that the folder Spam does not exist.
>
> dovecot: lmtp(xxxx): oG8YI6enmF7FIAAAI7dPvA: sieve: Execution of script
> /xxxx/.dovecot.sieve failed, but implicit keep was successful (user
> logfile /xxx/.dovecot.sieve.log may reveal additional details)
So, does that
2020 Apr 16
0
Bug maybe already resolved? Sieve rule does not accept special use folder names
On 16/04/2020 21:04, Marc Roos wrote:
> Sieve rule fileinto Spam fails, while fileinto Junk succeeds
>
>
> mailbox Spam {
> special_use = \Junk
> auto = no
> }
>
> dovecot-pigeonhole-2.2.36-3.el7_7.1.x86_64
> dovecot-2.2.36-3.el7_7.1.x86_64
> CentOS Linux release 7.7.1908 (Core
I can't tell without insight in the error message and your full
2019 Dec 15
3
Local lmtp proxy on backend server
I receive a local mail when I do a 'mail test' on a backend svr1 with
this[0] configuration. However when I just add only one configuration
change 'lmtp_proxy = yes' I am getting these errors[1]. I would expect
this email to still be delivered locally, should this be working or do I
misunderstand the lmtp proxy functionality?
[0]
passdb {
args =
auth_verbose = default
2019 Dec 16
1
Local lmtp proxy on backend server
I added this:
passdb {
driver = passwd
skip = authenticated
}
Which enables indeed local delivery, I also noticed this. Maybe the
password field check shoud not be done, when you enable skip
authentication?
Dec 16 10:26:37 svr1 dovecot: auth-worker(12046): Debug: passwd(test):
lookup
Dec 16 10:26:37 svr1 dovecot: auth-worker(12046): passwd(test): invalid
password field '*'
2019 Dec 16
5
Local lmtp proxy on backend server
Hi Aki,
If I adapt this configuration on svr1 like this[0], should the mail not
be delivered at svr2
passdb {
driver = pam
# [session=yes] [setcred=yes] [failure_show_msg=yes]
[max_requests=<n>]
# [cache_key=<key>] [<service name>]
#args = dovecot
default_fields = proxy=y host=svr2
}
passdb {
driver = passwd
skip = authenticated
default_fields = proxy=y
2019 Dec 17
1
Local lmtp proxy on backend server
Hi Aki, you have some ingenious remark that could help?
-----Original Message-----
To: aki.tuomi; dovecot
Subject: RE: Local lmtp proxy on backend server
I am staring constantly at the same logs, this is what I get from
dovecot[1]. Sendmail[2] is sending with test at svr1 maybe this overrides
lmtp proxying? This is a test with a special-userdb passwd-file also
having host=svr2
[1]
Dec
2019 Oct 03
4
sieve cli
i am using dovecot-2.2.36-3.el7_7.1.x86_64 on centos 7
is it possible to activate / deactivate a sieve script for a mailbox
from the command line?
my mailboxes are currently stores in /../vmail/domain.tld/username
if i activate / deactivate a filter set using roundcube (webmail system)
then it creates or deletes a symbolic link
/../vmail/domain.tld/username/dovecot.sieve? which points to a
2020 Apr 15
2
INBOX folders disappeared after upgrading
Hi, tried to Google/etc to see what to tweak.. not finding anything helpful.
So.. I've been running my private mail through a Linux server since approx
year 2000. The OS has been various flavors of Fedora or CentOS, since for
work, I have to spend all day supporting some sort of Red Hat flavor.
So I run SquirrelMail on top of Dovecot and Postfix on CentOS 7, things
have been great for like
2020 Jan 23
2
yum update / kernal update failed - remove or repair
On 1/22/20 3:57 PM, Gary Stainburn wrote:
> I have managed to find out what happened in the yum update and it turns out it was a mess. It looks like the server ran out of memory in the middle and things then started to fail. Any advice on how to recover from this would be greatly appreciated
>
> The log below shows:
>
> [root at vps2 ~]# yum history info 22
> Loaded plugins:
2019 Dec 16
0
Local lmtp proxy on backend server
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 15/12/2019 23:09 Marc Roos <
<a href="mailto:m.roos@f1-outsourcing.eu">m.roos@f1-outsourcing.eu</a>> wrote:
</div>
<div>
2019 Dec 16
0
Local lmtp proxy on backend server
Hi Aki,
I also tried with changing the original ldap source to svr2. Although
everywhere svr2 is configured, still mails keep being delivered locally
on svr1. Do I need to configure more than 20-lmtp.conf?
[@svr1 conf.d]# cat 20-lmtp.conf | grep -v '^#'
lmtp_proxy = yes
protocol lmtp {
# Space separated list of plugins to load (default is global
mail_plugins).
mail_plugins
2019 Sep 26
0
CESA-2019:2836 Important CentOS 7 dovecot Security Update
CentOS Errata and Security Advisory 2019:2836 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2019:2836
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
11077bf3f1d84c1f6859b8fa47c9392fcd509f8d6bc7b9b988e6ed7577ed04f8 dovecot-2.2.36-3.el7_7.1.i686.rpm
2019 Sep 27
0
CentOS-announce Digest, Vol 175, Issue 4
Send CentOS-announce mailing list submissions to
centos-announce at centos.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-request at centos.org
You can reach the person managing the list at
centos-announce-owner at centos.org
When
2020 Apr 16
0
INBOX folders disappeared after upgrading
Dave> Hi, tried to Google/etc to see what to tweak.. not finding
Dave> anything helpful. So.. I've been running my private mail
Dave> through a Linux server since approx year 2000. The OS has been
Dave> various flavors of Fedora or CentOS, since for work, I have to
Dave> spend all day supporting some sort of Red Hat flavor.
Makes sense. I'm not a dovecot expert, but in
2019 Sep 27
2
Mail received but not indexed?
I have recently that some users are complaining about that they are not
getting emails. While I see that they are delivered and in the inbox.
When I do a doveadm force-resync -u xxxx INBOX it resolves the problem.
I think this is something recent. Where/how should I resolve this issue?
Recent changes
1. did some os updates 2019-08-27
2. provider took away the ssd for index storage (maybe
2019 Sep 27
2
Mail received but not indexed?
No, it is still old sendmail to /var/spool/mail/
-----Original Message-----
From: Sami Ketola [mailto:sami.ketola at dovecot.fi]
Sent: vrijdag 27 september 2019 15:17
To: dovecot
Cc: Marc Roos
Subject: Re: Mail received but not indexed?
> On 27 Sep 2019, at 16.06, Marc Roos via dovecot <dovecot at dovecot.org>
wrote:
> CentOS Linux release 7.6.1810 (Core)
>