Il 28/07/2015 11:53, Michael Borgelt ha scritto:
Hi.
I have tried this email also with thunderbird imap which works. So this is
as special Problem with the imap-module of the Horde framework. I will do
some more debugging this evening.
My Horde framework has the following Versions:
Horde Groupwa
On 14-08-15 15:08, Andrew McN wrote:
>
> I have a fairly standard antispam/dspam setup: postfix delivers to
> dspam, which classifies and tags the mail, and then passes it to postfix
> which uses sieve to put mail into the appropriate folders based on
> dspam's classification. I also have the a
On 22/6/2015 9:49 am, Wolfgang Hennerbichler wrote:
It turns out that if I enable this option:
pop3_deleted_flag = "$POP3Deleted”
The issue no longer persists. I have to manually expunge the kept mails that
have been deleted via pop3 though:
doveadm expunge mailbox INBOX KEYWORD '$POP3Deleted'
On Sun Aug 16 19:01:46 2015, Stephan Bosch wrote:
> Op 8/13/2015 om 4:33 PM schreef Jost Krieger:
> > ...
> > Unfortunately the mail will arrive there but will also be left in the
> > source folder
> > Spam/U0 and will be processed again every 4 minutes ...
> >
> > This is probably not intentional
On Thu, 2015-08-06 at 16:10 +0200, Stephan Bosch wrote:
> Since the extdata plugin is not part of the normal Debian packages (not
> afaik anyway), you likely compiled and installed the extdata plugin
> manually in the past while using Dovecot 2.1. Do that again, but use
> this repository: http:/
Andrew Beverley schreef op 17-8-2015 om 14:05:
On Thu, 2015-08-06 at 16:10 +0200, Stephan Bosch wrote:
Since the extdata plugin is not part of the normal Debian packages (not
afaik anyway), you likely compiled and installed the extdata plugin
manually in the past while using Dovecot 2.1. Do th
On Mon, 2015-08-17 at 14:13 +0200, Stephan Bosch wrote:
> but until then you can avoid this by using the the exdata hg revision before
> tip
> (57c8d3e6b562).
Great, thanks for the quick reply, that fixed the compilation problem.
I'm still getting a segfault though. This time the backtrace is:
On 17/8/2015 2:29 μμ, Wolfgang Hennerbichler wrote:
I was wondering if the same behavior persists with latest version(s), for
example 2.2.18.
I don’t know, I have to deal with the packages that come with my distribution’s
repository.
>If so, how do you overcome this issue? What is the sugges
Andrew Beverley schreef op 17-8-2015 om 14:35:
On Mon, 2015-08-17 at 14:13 +0200, Stephan Bosch wrote:
but until then you can avoid this by using the the exdata hg revision before tip
(57c8d3e6b562).
Great, thanks for the quick reply, that fixed the compilation problem.
I'm still getting a s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2015-08-14 7:52 AM, Chad M Stewart wrote:
>
> The problem happened again this morning. Removing fsync calls helped,
but I'm not sure about leaving that enabled long term.
>
> I still believe the problem is multiple dovecot processes trying to
w
On Mon, 2015-08-17 at 15:23 +0200, Stephan Bosch wrote:
> Still looks like the executed extdata plugin was compiled against a
> different pigeonhole.
Got it. There was an old version in /usr/lib/dovecot/modules/sieve/, whereas the
new one was installed into /usr/local/lib/dovecot/sieve/. That all
Thanks I'll look into that.
knute...
On 8/15/2015 16:03, Eduardo Ramos wrote:
For sure Knute.
Take a look at this: http://wiki2.dovecot.org/Replication
I think a good implementation would be using a dovecot director layer
+ dovecot replication.
On 08/15/2015 06:26 PM, Knute Johnson wrote:
Andrew Beverley schreef op 17-8-2015 om 16:50:
On Mon, 2015-08-17 at 15:23 +0200, Stephan Bosch wrote:
Still looks like the executed extdata plugin was compiled against a
different pigeonhole.
Got it. There was an old version in /usr/lib/dovecot/modules/sieve/, whereas the
new one was install
On Aug 17, 2015, at 9:30 AM, Gregory Finch wrote:
<..snip..>
> With that many messages, it may be the index updates that are slowing
> things down. Depending on your needs or how you use this folder (it
> sounds automated to me), you may not need the indexes on disk at all. If
> you set the ind
Hi.
If $otheruser shares a mailbox to $myuser, my private index is stored
in *my* Maildir, according to this template (from the dovecot docs):
mail_location = maildir:%%h/Maildir:INDEXPVT=%h/Maildir/shared/%%u
If $otheruser renames the shared mailbox, all my private mail flags
(Seen) are lost be
On Mon, 2015-08-17 at 17:37 +0200, Stephan Bosch wrote:
> > Unfortunately my vacation rule no longer works though. I'm getting "sieve:
> > user's script dict:proxy::sieve;name=active doesn't exist (trying default
> > script location instead)"
> [...]
> > I guess I'm doing something stupid. Any ide
Op 8/18/2015 om 2:04 AM schreef Andrew Beverley:
> On Mon, 2015-08-17 at 17:37 +0200, Stephan Bosch wrote:
>>> Unfortunately my vacation rule no longer works though. I'm getting "sieve:
>>> user's script dict:proxy::sieve;name=active doesn't exist (trying default
>>> script location instead)"
>> [
17 matches
Mail list logo
