Ok, it seems the version I am having here is older than the cited patch allows.
It is likely pigeonhole-0.4.21 from 2017 where the lib-smtp does not exist at
all.
So I am a bit stuck ...
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe sen
Thank you John for that hint, it looks promising. I will try to check that out
and report back.
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
On 12/08/2024 19:06, skraw--- via dovecot wrote:
As I already said, this setup is way too complex to think about an update.
The cause of this problem cannot be a problem of the same size. If somebody
(probably you or Stephan) already found the cause I could concentrate on
backporting a soluti
As I already said, this setup is way too complex to think about an update.
The cause of this problem cannot be a problem of the same size. If somebody
(probably you or Stephan) already found the cause I could concentrate on
backporting a solution.
And future readers of the thread may be interest
2.1.17 is way older than 2.3.2.1
Please try with 2.3.21 (latest version).
Aki
> On 12/08/2024 17:11 EEST skraw--- via dovecot wrote:
>
>
> I see it happening with dovecot 2.1.17 in a setup that is complex to update.
> So I am interested in the cause and possible solutions to bring them into
I see it happening with dovecot 2.1.17 in a setup that is complex to update. So
I am interested in the cause and possible solutions to bring them into this old
setup.
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to doveco
Have you verified that it happens with dovecot 2.3.21 and pigeonhole 0.5.21?
Aki
> On 12/08/2024 16:39 EEST skraw--- via dovecot wrote:
>
>
> And what was the proposed solution to this?
> ___
> dovecot mailing list -- dovecot@dovecot.org
> To unsubs
And what was the proposed solution to this?
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
On 11/3/2023 14:23:48, joe a wrote:
Working dovecot 2.3, wish to be able to implement "server side" filtering.
My understanding is that is done with "sieve". My further understanding
is that "dovecot-pigeonhole" and be used to manage "sieve" in some
Working dovecot 2.3, wish to be able to implement "server side" filtering.
My understanding is that is done with "sieve". My further understanding
is that "dovecot-pigeonhole" and be used to manage "sieve" in some fashion.
Attempting to comp
5 [1]: Abort transaction
Feb 16 11:32:29 lda(mymail@mydomain)<36105>: Debug:
smtp-client: conn 127.0.0.1:25 [1]: command BDAT: Destroy (0 commands pending, 0 commands
queued)
Feb 16 11:32:29 lda(mymail@mydomain)<36105>: Debug:
smtp-client: conn 127.0.0.1:25 [1]: Disconnected
Feb 16 11:32
1:32:29 lda(mymail@mydomain)<36105>: Debug:
smtp-client: conn 127.0.0.1:25 [1]: command BDAT: Destroy (0 commands pending,
0 commands queued)
Feb 16 11:32:29 lda(mymail@mydomain)<36105>: Debug:
smtp-client: conn 127.0.0.1:25 [1]: Disconnected
Feb 16 11:32:29 lda(mymail@mydoma
> On 16/02/2021 13:00 Bug Report wrote:
>
>
> it looks like sieve_after gets executed only when sending to an address
> defined in script failsTemat: Re: sieve_after seems to not bring any effect
> to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13
> Data: 2021-02-
it looks like sieve_after gets executed only when sending to an address defined
in script failsTemat: Re: sieve_after seems to not bring any effect to life in
dovecot 2.3.13 dovecot-pigeonhole-0.5.13
Data: 2021-02-12 10:27
Nadawca: "Aki Tuomi"
Adresat: "Bug Report" ;
021 13:30 Bug Report wrote:
> >>
> >>
> >> dovecot 2.3.13 (89f716dc2)
> >>
> >> dovecot-pigeonhole-0.5.13
> >>
> >> OS: FreeBSD amd64 12.2-RELEASE
> >>
> >> After following code
> >>
> >> ---
3:30 Bug Report wrote:
>>
>>
>> dovecot 2.3.13 (89f716dc2)
>>
>> dovecot-pigeonhole-0.5.13
>>
>> OS: FreeBSD amd64 12.2-RELEASE
>>
>> After following code
>>
>> --
>>
>> require ["copy"
> On 11/02/2021 13:30 Bug Report wrote:
>
>
> dovecot 2.3.13 (89f716dc2)
>
> dovecot-pigeonhole-0.5.13
>
> OS: FreeBSD amd64 12.2-RELEASE
>
> After following code
>
> --
>
> require ["copy"];
>
> # rule:[redirect]
dovecot 2.3.13 (89f716dc2)
dovecot-pigeonhole-0.5.13
OS: FreeBSD amd64 12.2-RELEASE
After following code
--
require ["copy"];
# rule:[redirect]
if true
{
redirect :copy "m...@mail.com";
keep;
}
--
(both with keep and without keep) is executed
Hello,
I like to install Update my server but after the last update I have this Error
System centos 7.7
when I Install "sieve" I have this error
Mar 9 11:51:47 mx02 dovecot: master: Warning: Corrected permissions for login
directory /var/run/dovecot/token-login
Mar 9 11:51:47 mx02 dovecot: mast
Il 03-01-2020 19:51 @lbutlr ha scritto:
On 03 Jan 2020, at 06:16, Gionatan Danti wrote:
What surprises me is that hard-linking identical messages saves so
much space, yet nobody seems to asking/using such feature.
So, either a) few cares about saving space or b) few are using the
pigeonhole pl
Il 03-01-2020 13:11 Stephan Bosch ha scritto:
I think this used to work in the past. Still need to look at this one.
Regards,
Stephan.
Hi Stephan, thank for your reply.
What surprises me is that hard-linking identical messages saves so much
space, yet nobody seems to asking/using such featu
today: is dovecot+pigeonhole capable of
storing the same incoming message, sent to multiple rcpt or to a
group/alias expanding in multiple recipients, as a single hardlink?
Note: I know about SIS, but it has some important drawback and I
would avoid using it.
Thanks.
Hi all, any thoughts on the
messages, using pigeonhole broke the hardlink (ie: some
message-specific data was appended to the actual mail file). Here you
can find the original thread:
https://dovecot.org/pipermail/dovecot/2015-November/102579.html
I would ask the same things today: is dovecot+pigeonhole capable of
storing the
: some message-specific
data was appended to the actual mail file). Here you can find the
original thread:
https://dovecot.org/pipermail/dovecot/2015-November/102579.html
I would ask the same things today: is dovecot+pigeonhole capable of
storing the same incoming message, sent to multiple rcpt or
the actual mail file). Here you can find the
original thread:
https://dovecot.org/pipermail/dovecot/2015-November/102579.html
I would ask the same things today: is dovecot+pigeonhole capable of
storing the same incoming message, sent to multiple rcpt or to a
group/alias expanding in multiple
we have a problem after updating the software with the operation of sieve
> scripts sending a copy of the e-mails, e-mails are not transferred.
>
> Configuration:
> dovecot-2.3.2.1 + dovecot-pigeonhole-0.5.2 + FreeBSD 11.2
>
> log:
> Sep 06 13:28:17 lda(XXX@XXX)<38615>: Info:
.
Configuration:
dovecot-2.3.2.1 + dovecot-pigeonhole-0.5.2 + FreeBSD 11.2
log:
Sep 06 13:28:17 lda(XXX@XXX)<38615>: Info: sieve:
msgid=: stored mail into mailbox 'INBOX'
Sep 06 13:28:17 lda(XXX@XXX)<38615>: Info: sieve: Execution
of script /usr/home/XXX/mail/XXX@XXX/.dov
d configuration:
dovecot 2.2 + dovecot-pigeonhole- 0.4 + FreeBSD 11.2
we don't have problem.
Has anyone had a similar problem, knows the solution?
Can you send me a pcap log (e.g. using Wireshark) from the connection
between Dovecot and the MTA? Does it happen for every message?
Never mind. I
Op 07/09/2018 om 21:32 schreef Jan Nowak:
Hello,
we have a problem after updating the software with the operation of
sieve scripts sending a copy of the e-mails, e-mails are not transferred.
Configuration:
dovecot-2.3.2.1 + dovecot-pigeonhole-0.5.2 + FreeBSD 11.2
log:
Sep 06 13:28:17 lda
Hello,
we have a problem after updating the software with the operation of sieve
scripts sending a copy of the e-mails, e-mails are not transferred.
Configuration:
dovecot-2.3.2.1 + dovecot-pigeonhole-0.5.2 + FreeBSD 11.2
log:
Sep 06 13:28:17 lda(XXX@XXX)<38615>: Info: sieve:
msgid=:
You should use sieve-test -u valid-username when running as root
---Aki TuomiDovecot oy
Original message From: Larry Rosenman
Date: 08/07/2018 13:36 (GMT+02:00) To: Dovecot Mailing List
Subject: Re: New error message with Dovecot/Pigeonhole
Can we get a doveconf -n
Can we get a doveconf -n please?
I'm the FreeBSD port maintainer for both dovecot and pigeonhole.
From: dovecot on behalf of Jerry
Sent: Sunday, July 8, 2018 5:32:32 AM
To: Dovecot Mailing List
Subject: New error message with Dovecot/Pigeonhole
FreeBSD
FreeBSD 11.1 / amd64
dovecot --version 2.3.2 (582970113)
Pigeonhole version 0.5.2 (7704de5e)
I have run 'sieve-test" many times to check out changes in my "sieve" scripts.
This morning, it suddenly started issuing this error message:
sieve-test(root): Fatal: Couldn't drop privileges: User is miss
doveconf: Error: managesieve-login: dump-capability
> >process returned 89
> >
> >There doesn't seem to be that plugin present or provided by
> >dovecot-pigeonhole
> >
> ># ls -lah /usr/lib64/dovecot/sieve/
> >total 56K
> >drwxr-xr-x. 2 roo
>
>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
>
>There doesn't seem to be that plugin present or provided by
/usr/lib64/dovecot/sieve
dovecot[22026]: doveconf: Error: managesieve-login: dump-capability process
returned 89
There doesn't seem to be that plugin present or provided by dovecot-pigeonhole
# ls -lah /usr/lib64/dovecot/sieve/
total 56K
drwxr-xr-x. 2 root root 46 Jun 5 12:16 .
drwxr-xr-x. 7 roo
On 29.12.2017 16:50, Alexander Dalloz wrote:
> Am 29.12.2017 um 15:08 schrieb Fabian A. Santiago:
>> December 28, 2017 6:38 PM, "Peter" wrote:
>>
>>> On 29/12/17 10:00, Fabian A. Santiago wrote:
>>>
i've now completely uninstalled all traces of dovecot and reinstalled
from your repo an
On December 29, 2017 9:50:37 AM EST, Alexander Dalloz
wrote:
>Am 29.12.2017 um 15:08 schrieb Fabian A. Santiago:
>> December 28, 2017 6:38 PM, "Peter" wrote:
>>
>>> On 29/12/17 10:00, Fabian A. Santiago wrote:
>>>
i've now completely uninstalled all traces of dovecot and
>reinstalled
Am 29.12.2017 um 15:08 schrieb Fabian A. Santiago:
December 28, 2017 6:38 PM, "Peter" wrote:
On 29/12/17 10:00, Fabian A. Santiago wrote:
i've now completely uninstalled all traces of dovecot and reinstalled
from your repo and still the same issue persists with the same
errors.
I'd be inte
Am 29.12.2017 um 00:37 schrieb Peter:
On 29/12/17 10:00, Fabian A. Santiago wrote:
i've now completely uninstalled all traces of dovecot and reinstalled
from your repo and still the same issue persists with the same
errors.
I'd be interested to know if the dovecot23* packages in GhettoForge
Tes
December 28, 2017 6:38 PM, "Peter" wrote:
> On 29/12/17 10:00, Fabian A. Santiago wrote:
>
>> i've now completely uninstalled all traces of dovecot and reinstalled
>> from your repo and still the same issue persists with the same
>> errors.
>
> I'd be interested to know if the dovecot23* packag
> On December 28, 2017 at 11:00 PM "Fabian A. Santiago"
> wrote:
>
>
> December 28, 2017 2:52 PM, "Fabian A. Santiago"
> wrote:
>
> > December 28, 2017 1:21 PM, "Aki Tuomi" wrote:
> >
> >>> On December 28, 2017 at 7:43 PM "Fabian A. Santiago"
> >>> wrote:
> >>>
> >>> December 28, 2017
On 29/12/17 10:00, Fabian A. Santiago wrote:
> i've now completely uninstalled all traces of dovecot and reinstalled
> from your repo and still the same issue persists with the same
> errors.
I'd be interested to know if the dovecot23* packages in GhettoForge
Testing have the same issue:
http://mi
December 28, 2017 2:52 PM, "Fabian A. Santiago"
wrote:
> December 28, 2017 1:21 PM, "Aki Tuomi" wrote:
>
>>> On December 28, 2017 at 7:43 PM "Fabian A. Santiago"
>>> wrote:
>>>
>>> December 28, 2017 12:14 PM, "Aki Tuomi" wrote:
>>>
>>> On December 28, 2017 at 7:07 PM "Fabian A. Santiago"
December 28, 2017 1:21 PM, "Aki Tuomi" wrote:
>> On December 28, 2017 at 7:43 PM "Fabian A. Santiago"
>> wrote:
>>
>> December 28, 2017 12:14 PM, "Aki Tuomi" wrote:
>>
>> On December 28, 2017 at 7:07 PM "Fabian A. Santiago"
>> wrote:
>>
>> Hello,
>>
>> After upgrading to dovecot 2.3.0, m
> On December 28, 2017 at 7:43 PM "Fabian A. Santiago"
> wrote:
>
>
> December 28, 2017 12:14 PM, "Aki Tuomi" wrote:
>
> >> On December 28, 2017 at 7:07 PM "Fabian A. Santiago"
> >> wrote:
> >>
> >> Hello,
> >>
> >> After upgrading to dovecot 2.3.0, my sieve filtering is broken. I manage
> On December 28, 2017 at 8:07 PM "Fabian A. Santiago"
> wrote:
>
>
> December 28, 2017 12:43 PM, "Fabian A. Santiago"
> wrote:
>
> > December 28, 2017 12:14 PM, "Aki Tuomi" wrote:
> >
> >>> On December 28, 2017 at 7:07 PM "Fabian A. Santiago"
> >>> wrote:
> >>>
> >>> Hello,
> >>>
> >
December 28, 2017 12:43 PM, "Fabian A. Santiago"
wrote:
> December 28, 2017 12:14 PM, "Aki Tuomi" wrote:
>
>>> On December 28, 2017 at 7:07 PM "Fabian A. Santiago"
>>> wrote:
>>>
>>> Hello,
>>>
>>> After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed
>>> it via roundc
December 28, 2017 12:14 PM, "Aki Tuomi" wrote:
>> On December 28, 2017 at 7:07 PM "Fabian A. Santiago"
>> wrote:
>>
>> Hello,
>>
>> After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it
>> via roundcube's
>
> managesieve plugin. my emails are not being filtered accord
> On December 28, 2017 at 7:07 PM "Fabian A. Santiago"
> wrote:
>
>
> Hello,
>
> After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it
> via roundcube's
managesieve plugin. my emails are not being filtered accordingly into their
folders and when i attempt to access t
Hello,
After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it
via roundcube's managesieve plugin. my emails are not being filtered
accordingly into their folders and when i attempt to access the filter
interface in roundcube, my maillog reports:
Dec 28 12:05:07 mail round
The commit [1] fixes the issue, thanks.
[1] https://github.com/stephanbosch/pigeonhole-core/commit/
321a39be974deb2e7eff7b2a509a3ee6ff2e5ae1
On pondělí 25. prosince 2017 13:44:12 CET Oleksandr Natalenko wrote:
> Hi all.
>
> My dovecot setup:
>
> pf@vulcan:~ » dovecot --version
> 2.3.0 (c8b89eb)
Hi all.
My dovecot setup:
pf@vulcan:~ » dovecot --version
2.3.0 (c8b89eb)
on Arch Linux, x86_64 (full config here: [0])
uses sieve plugin to train rspamd system as described in the wiki [1]. It used
to work fine prior to 2.3.0/0.5.0 update, but now "imap" process crashes when
I move spam lett
Am 12.07.2017 um 16:53 schrieb Stephan Bosch:
> That smells a lot like this issue:
>
> https://github.com/dovecot/pigeonhole/commit/c80aa7c25b0b4e61bb8e3a91864a355f7f2fa89f
>
> Fix will be included in next release.
>
> Regards,
>
> Stephan.
Hello Stephan,
you
<>, method=PLAIN, rip=192.168.1.138, lip=1192.168.1.135, TLS:
Disconnected, session=
Does this mean that managesieve-login doesn't get authentication data from SOGo?
SOGo logs for this error:
S[0x7f368f2bab60]: "IMPLEMENTATION" "Dovecot Pigeonhole"
S[0x7f368f2bab60]: &
s in 0 secs): user=<>, method=PLAIN, rip=192.168.1.138,
> lip=1192.168.1.135, TLS: Disconnected, session=
Does this mean that managesieve-login doesn't get authentication data from SOGo?
SOGo logs for this error:
> S[0x7f368f2bab60]: "IMPLEMENTATION" "Dovecot Pigeonhole&q
.
I'm testing with ubuntu zesty and it's still at dovecot 2.2.25 so
where might I find the docs for the relevant changes in 2.2.27 that
will no doubt affect me in another month or three?
And would anyone have an example of how to use dovecot-pigeonhole
to call spamprobe as an external
t;
> - Originale Nachricht -
> Von: Tobi
> Gesendet: 08.01.17 - 12:22
> An: Dovecot Mailing List
> Betreff: Re: dovecot-pigeonhole running external script ends with signal 11
>
> > Hi Stephan
> >
> > currently the rpm is built based on 0.4.14
> >
etreff: Re: dovecot-pigeonhole running external script ends with signal 11
> Hi Stephan
>
> currently the rpm is built based on 0.4.14
> Should I try with 0.4.16? I will build it again this afternoon with the
> version you suggested and report back with the results.
>
> Tha
: tobs...@brain-force.ch@pgp.brain-force.ch,
Dovecot Mailing List
Betreff: Re: dovecot-pigeonhole running external script ends with signal 11
> Op 1/8/2017 om 10:00 AM schreef Tobi:
>> Hi Stephan
>>
>> according to ps aux the process that segfaults is (pid 18261)
>
Op 1/8/2017 om 10:00 AM schreef Tobi:
> Hi Stephan
>
> according to ps aux the process that segfaults is (pid 18261)
>
> vmail18261 0.0 0.0 0 0 pts/0Z09:39 0:00 [lmtp]
>
>
> the gdb backtrace I attached to my mail was the deepest one I got
That looks like it happens in Do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 4 Jan 2017, Tobi wrote:
[New process 20844]
Program received signal SIGSEGV, Segmentation fault.
[Switching to process 20844]
0x77203694 in _IO_vfprintf_internal (s=s@entry=0x7fffd710,
format=,
format@entry=0x55764938 "chr
Op 1/4/2017 om 9:37 AM schreef Tobi:
> Hi Aki
>
> yes I built dovecot and pigeonhole rpms in the same rpmbuild. pigeonhole
> rpm is based on 0.4.14
> Do you think that the error might come from self building the rpms?
But what version of Pigeonhole are you actually using? Version 0.4.16 is
release
Nachricht -
Von: Tobi
Gesendet: 04.01.17 - 09:37
An: dovecot@dovecot.org
Betreff: Re: dovecot-pigeonhole running external script ends with signal 11
> Hi Aki
>
> yes I built dovecot and pigeonhole rpms in the same rpmbuild. pigeonhole
> rpm is based on 0.4.14
> Do you think that
Hi Aki
yes I built dovecot and pigeonhole rpms in the same rpmbuild. pigeonhole
rpm is based on 0.4.14
Do you think that the error might come from self building the rpms?
Regards
tobi
Am 04.01.2017 um 08:55 schrieb Aki Tuomi:
> On 04.01.2017 09:49, Tobi wrote:
>> Hi Stephan
>>
>> Am 03.01.2017
On 04.01.2017 09:49, Tobi wrote:
> Hi Stephan
>
> Am 03.01.2017 um 21:12 schrieb Stephan Bosch:
>
>> Since you're using LMTP, you could try to run the lmtp service from
>> command line in GDB. In essence, this looks as follows (you will need to
>> run this as the mail user, e.g. vmail, or you can r
Hi Stephan
Am 03.01.2017 um 21:12 schrieb Stephan Bosch:
> Since you're using LMTP, you could try to run the lmtp service from
> command line in GDB. In essence, this looks as follows (you will need to
> run this as the mail user, e.g. vmail, or you can run it as root):
>
> $ gdb --args /usr/lib
Op 1/3/2017 om 4:28 PM schreef Tobi:
> I have no idea why the manual call runs perfect and the call from sieve
> file ends up in this error.
> Does anyone have an idea how I could narrow down the source of this
> error? Or even better how to fix it? :-)
In the most likely scenario, there is some s
On 01/03/2017 05:28 PM, Tobi wrote:
Hi,
I'm running a dovecot 2.2.26 (self compiled) on a Centos 7.
I have a sieve script which should run an external script (in filter
mode) that encrypts the mail using the users pub key.
I configured 90-plugin.conf as follows
plugin {
sieve_plugins =
Hi,
I'm running a dovecot 2.2.26 (self compiled) on a Centos 7.
I have a sieve script which should run an external script (in filter
mode) that encrypts the mail using the users pub key.
I configured 90-plugin.conf as follows
plugin {
sieve_plugins = sieve_extprograms
sieve_extensions =
Op 9/21/2015 om 12:16 AM schreef T.B.:
> Hi Stephan Bosch,
> any update on this?
Unfortunately, no.
It is not high up my list at the moment. :/
Regards,
Stephan.
>
>
> Regards,
>
> T.B.
>
>
> Am 08.05.2014 um 14:37 schrieb Stephan Bosch:
>> T.B. schreef op 7-5-2014 10:40:
>>> I think it would
Hi Stephan Bosch,
any update on this?
Regards,
T.B.
Am 08.05.2014 um 14:37 schrieb Stephan Bosch:
T.B. schreef op 7-5-2014 10:40:
I think it would not be a problem to develop a solution to remotely
trigger re-filtering for me, myself and I. But that is not the point
here. Clients like the Th
Op 8/4/2015 om 5:03 PM schreef Christoph Gröver:
> Hello ML, Hello Stephan,
>
>> Hmm. Probably, the timezone configuration (i.e. the contents of TZ
>> timezone environment variable) somehow doesn't reach the final stages
>> of e-mail delivery.
> Well. I tried several ways of telling the lda or wha
Hello ML, Hello Stephan,
> Hmm. Probably, the timezone configuration (i.e. the contents of TZ
> timezone environment variable) somehow doesn't reach the final stages
> of e-mail delivery.
Well. I tried several ways of telling the lda or whatever is setting up
the INTERNALDATE to use the CEST +0
Hallo Stephan,
>
> Hmm. Probably, the timezone configuration (i.e. the contents of TZ
> timezone environment variable) somehow doesn't reach the final stages of
> e-mail delivery.
I investigated further.
I just did a telnet into the server and discoverered that dovecot knows the
localtime. If
Thanks Stephan for your answer.
>
> Hmm. Probably, the timezone configuration (i.e. the contents of TZ
> timezone environment variable) somehow doesn't reach the final stages of
> e-mail delivery.
Sorry, I just found out we had pigeonhole-0.4.3 running on the old server.
The sources of 0.2.5 w
Christoph Gröver schreef op 31-7-2015 om 16:01:
We are using the following setup:
Dovecot-2.2.18
Pigeonhole-0.4.8 (for Dovecot-2.2)
After the mail is finally delivered via a fileinto by the Sieve filter
it gets an updated timestamp (modification time).
The server has localtime setup correctl
Hi List,
We are using the following setup:
Dovecot-2.2.18
Pigeonhole-0.4.8 (for Dovecot-2.2)
After the mail is finally delivered via a fileinto by the Sieve filter
it gets an updated timestamp (modification time).
The server has localtime setup correctly IMO (UTC +0200), but still the
delivere
Timothy Murphy wrote:
> I'm running postfix + dovecot + dovecot-pigeonhole
> on my CentOS-7 home server.
> I would like spam to end up in ~/Maildir/.Spam/ .
> Spam is being marked, but is not separated -
> it ends up with all the other email in ~/Maildir/cur/ .
> Evident
Timothy Murphy wrote on 28.07.2014 00:08:
> I'm running postfix + dovecot + dovecot-pigeonhole
> on my CentOS-7 home server.
> I would like spam to finish up in ~/Maildir/.Spam/ .
> Spam is being marked, but is not separated -
> it ends up with all the other email in ~/Maildi
On 7/27/2014 1:16 PM, Pascal Volk wrote:
On 07/27/2014 05:08 PM, Timothy Murphy wrote:
I'm running postfix + dovecot + dovecot-pigeonhole
on my CentOS-7 home server.
I would like spam to finish up in ~/Maildir/.Spam/ .
Spam is being marked, but is not separated -
it ends up with all the
On 07/27/2014 05:08 PM, Timothy Murphy wrote:
> I'm running postfix + dovecot + dovecot-pigeonhole
> on my CentOS-7 home server.
> I would like spam to finish up in ~/Maildir/.Spam/ .
> Spam is being marked, but is not separated -
> it ends up with all the other em
I'm running postfix + dovecot + dovecot-pigeonhole
on my CentOS-7 home server.
I would like spam to finish up in ~/Maildir/.Spam/ .
Spam is being marked, but is not separated -
it ends up with all the other email in ~/Maildir/cur/ .
Evidently there is some step I have omitted to take.
I giv
On 6/2/2014 11:11 PM, Skeffling wrote:
> Hello,
>
> I'm testing dovecot replication alongside pigeonhole and liking it.
>
> Dovecot v2.2.13
> Pigeonhole v0.4.3
>
> If I create or edit a sieve script on one server (via managesieve, using
> the thunderbird plugin as it happens) then it does get
Hello,
I'm testing dovecot replication alongside pigeonhole and liking it.
Dovecot v2.2.13
Pigeonhole v0.4.3
If I create or edit a sieve script on one server (via managesieve, using
the thunderbird plugin as it happens) then it does get replicated to the
other - great!
However, if I set a
Hi
are you delivering your mails through dovecot lmtp/lda or does your postfix
write directly to your mail folders?
Maybe show your postconf -n or kindly ask on the postfix mailing list.
If dovecot LDA and LMTP are both not involved in delivery, SIEVE filtering via
dovecot pigeonhole will
Hi,
i've read LDA/Postfix
Virtual users section , and i added
dovecot unix - n n - - pipe
flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/dovecot-lda
-f ${sender} -d ${recipient}
my master.cf, also
I added
dovecot_destination_recipient_limit = 1
vi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 16 May 2014, Selcuk Yazar wrote:
yes i try to change deliver to dovecot.
Please don't top post.
What about the logs (last sentences in my previous mail)?
On Fri, May 16, 2014 at 11:49 AM, Steffen Kaiser <
skdove...@smail.inf.fh-brs.de>
Hi, stefan,
yes i try to change deliver to dovecot.
thanks.
On Fri, May 16, 2014 at 11:49 AM, Steffen Kaiser <
skdove...@smail.inf.fh-brs.de> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> On Fri, 16 May 2014, Selcuk Yazar wrote:
>
> ok first our deliver command procmail.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 16 May 2014, Selcuk Yazar wrote:
ok first our deliver command procmail.
you mean that your current MDA is procmail, which you want to replace by
Dovecot deliver?
in master.cf i added
dovecot unix - n n - -
Hi,
i still try to sieve system.
ok first our deliver command procmail. our user accounts stored in
openldap, mail files are in Maildir folders
in 15-lda.conf recommented
protocol lda {
# Space separated list of plugins to load (default is global
mail_plugins).
mail_plugins = $mail_plugins
Am 14.05.2014 17:18, schrieb Götz Reinicke - IT Koordinator:
> Am 14.05.14 16:20, schrieb Robert Schetterer:
>> Am 14.05.2014 16:09, schrieb Götz Reinicke - IT Koordinator:
>>> Hi,
>>>
>>> dont ask :) but I have two accounts for which I have to configure an
>>> auto reply for any e-mail send to it.
Am 14.05.14 16:20, schrieb Robert Schetterer:
> Am 14.05.2014 16:09, schrieb Götz Reinicke - IT Koordinator:
>> Hi,
>>
>> dont ask :) but I have two accounts for which I have to configure an
>> auto reply for any e-mail send to it.
>
> you shouldnt do that , you risk endless mail ping pong
Hi,
t
Götz Reinicke - IT Koordinator schreef op 14-5-2014 16:09:
Hi,
dont ask :)
ok...
but I have two accounts for which I have to configure an
auto reply for any e-mail send to it.
As far as I understand Sieve yet, I do have to set
sieve_vacation_min_period = 0 in the dovecot config and set the d
Am 14.05.2014 16:09, schrieb Götz Reinicke - IT Koordinator:
> Hi,
>
> dont ask :) but I have two accounts for which I have to configure an
> auto reply for any e-mail send to it.
you shouldnt do that , you risk endless mail ping pong
Best Regards
MfG Robert Schetterer
--
[*] sys4 AG
http://
Hi,
dont ask :) but I have two accounts for which I have to configure an
auto reply for any e-mail send to it.
As far as I understand Sieve yet, I do have to set
sieve_vacation_min_period = 0 in the dovecot config and set the days
value in the sieve rule.
But as there is a limit of 1 day, I thin
Am 13.05.2014 13:23, schrieb Selcuk Yazar:
>>> 2.0.9 is too old and unsupported. You need to upgrade first (be sure to
> read the upgrade info on the wiki)...
>
> our system is Redhat EL 6, and rin redhat portal thereis no update for 2.0.9
than Redhat is your support contact, that's why you use
Hi,
>>2.0.9 is too old and unsupported. You need to upgrade first (be sure to
read the upgrade info on the wiki)...
our system is Redhat EL 6, and rin redhat portal thereis no update for 2.0.9
.
On Tue, May 13, 2014 at 2:06 PM, Stephan Bosch wrote:
> Selcuk Yazar schreef op 13-5-2014 12:58:
Selcuk Yazar schreef op 13-5-2014 12:58:
Hi,
we have running system postfix+dovecot+openldap. i have installed pigeon
hole, and afterlogic webmail php my test system.
http://wiki2.dovecot.org/Pigeonhole/Sieve/Troubleshooting
Regards,
Stephan.
On 5/13/2014 6:58 AM, Selcuk Yazar wrote:
[root@trakyamail ~]# dovecot -n
# 2.0.9: /etc/dovecot/dovecot.conf
2.0.9 is too old and unsupported. You need to upgrade first (be sure to
read the upgrade info on the wiki)...
--
Best regards,
Charles
1 - 100 of 267 matches
Mail list logo
