Hello,
just for information, the update to version 3.0.6 did not fix the
problem for me, I'm still having the same issue. I had to apply my
workaround (create symbolic links) to make it work again.
Regards,
Ralf
Am 02.03.2018 um 20:11 schrieb rfk:
Hi Ken,
my distribution is Gentoo and my
Hi Ken,
my distribution is Gentoo and my previous cyrus version was 2.5.10. Then
I upgraded to 3.0.4 but this ebuild (though marked stable by the Gentoo
devs) was terminating "abnormally" all the time. Finally I upgraded to
3.0.5 which is running fine until now - well, except for sieve.
Rega
Hi Sebastian,
in my second post you can see my cyrus.conf:
https://lists.andrew.cmu.edu/pipermail/info-cyrus/2018-February/039985.html
No "-C" flags in use though.
Regards,
Ralf
Am 02.03.2018 um 09:21 schrieb Sebastian Hagedorn:
Hi Ralf,
thanks a lot for your feedback, seems like we're com
I've done some investigating this morning and it appears that you are
correct in that lmtpd and timsieved differ in how they handle the
hierarchy separator. But I'm not sure just yet when this split happened.
Did you upgrade from 3.0.4 or from 2.x?
On 03/01/2018 03:36 PM, rfk wrote:
Hey Seb
Hi Ralf,
thanks a lot for your feedback, seems like we're coming closer. Although
I'm not sure what port 24 is supposed to be in your swaks command I just
sent myself an e-mail while strace was attached to cyrusmaster.
The log revealed the following:
readlink("/var/imap/sieve/u/user^domain^de/d
Hey Sebastian,
thanks a lot for your feedback, seems like we're coming closer. Although
I'm not sure what port 24 is supposed to be in your swaks command I just
sent myself an e-mail while strace was attached to cyrusmaster.
The log revealed the following:
readlink("/var/imap/sieve/u/user^dom
Not really. My best suggestion would be to strace the lmtp process to see
if the sieve scripts are even found and opened. On a test system I did it
like this:
strace -f -ff -o /tmp/lmtptrace -p
It might be better to prefork an lmtpd and to specifically strace that pid,
but in my case it didn
Hello,
still no other ideas?
Ralf
Am 15.02.2018 um 19:37 schrieb rfk:
Hi,
I'm so sorry, don't know how this could happen, but the last line of my
configuration was lost during copy and paste:
altnamespace: 0
So it is already disabled.
Ralf
Am 15.02.2018 um 19:32 schrieb Michael Menge
Hi,
I'm so sorry, don't know how this could happen, but the last line of my
configuration was lost during copy and paste:
altnamespace: 0
So it is already disabled.
Ralf
Am 15.02.2018 um 19:32 schrieb Michael Menge:
Hi,
Quoting rfk :
Hi,
thanks for your feedback. Unfortunately sieve
Hi,
Quoting rfk :
Hi,
thanks for your feedback. Unfortunately sievec reports nothing:
# grep -v ^# roundcube.script
require ["imapflags","fileinto"];
if anyof (header :contains "Subject" "test")
{
setflag "\\Seen";
fileinto "INBOX/Trash";
stop;
}
# sievec roundcube.
Hi,
thanks for your feedback. Unfortunately sievec reports nothing:
# grep -v ^# roundcube.script
require ["imapflags","fileinto"];
if anyof (header :contains "Subject" "test")
{
setflag "\\Seen";
fileinto "INBOX/Trash";
stop;
}
# sievec roundcube.script test
#
Here's
Hi,
Does the "sievec" compiler report any errors if you try to compile your sieve
scripts by hand?
Its manpage is here:
https://www.cyrusimap.org/imap/reference/manpages/systemcommands/sievec.html
Cheers,
ellie
On Thu, Feb 15, 2018, at 5:28 AM, rfk wrote:
> Hello,
>
> recently I updated my
Hello,
recently I updated my cyrus-imapd installation from verion 2.5.10 to
version 3.0.5. Unfortunately the sieve filters stopped working since
then. The rest is working fine.
The filters are listed in the sieveshell and all incoming mails get
tagged with "X-Sieve: CMU Sieve 3.0". However e
> On 3/26/11 3:33 AM, Simon Matter wrote:
>>> On 3/23/11 12:56 AM, Simon Matter wrote:
>
>>
>> What I meant was running skiplist only, then you don't have to worry
>> about
>> BerkeleyDB anymore.
>>
>
> I see, so currently I am using skiplist for some stuff, but the
> BerkelyDB for other stuff, an
On 3/26/11 3:33 AM, Simon Matter wrote:
>> On 3/23/11 12:56 AM, Simon Matter wrote:
>
> What I meant was running skiplist only, then you don't have to worry about
> BerkeleyDB anymore.
>
I see, so currently I am using skiplist for some stuff, but the
BerkelyDB for other stuff, and I should switc
> On 3/23/11 12:56 AM, Simon Matter wrote:
>>> Hello,
>>>
>>> I need to update my databases from 4.2 to 4.7. Unfortunately the guide
>>> I
>>
>> I see, you mean updating BerkeleyDB.
>>
>>> used last time to update my database has disappeared. All of the stuff
>>> I
>>> find currently on the web say
On 3/23/11 12:56 AM, Simon Matter wrote:
>> Hello,
>>
>> I need to update my databases from 4.2 to 4.7. Unfortunately the guide I
>
> I see, you mean updating BerkeleyDB.
>
>> used last time to update my database has disappeared. All of the stuff I
>> find currently on the web says just use cvt_cyr
> Hello,
>
> I need to update my databases from 4.2 to 4.7. Unfortunately the guide I
I see, you mean updating BerkeleyDB.
> used last time to update my database has disappeared. All of the stuff I
> find currently on the web says just use cvt_cyrusdb to update your
> database. Which seems pretty
Hello,
I need to update my databases from 4.2 to 4.7. Unfortunately the guide I
used last time to update my database has disappeared. All of the stuff I
find currently on the web says just use cvt_cyrusdb to update your
database. Which seems pretty straight-forward when I look at the man
page,
Ok, I got it working. There were two problems. One is that my symbolic
link to /usr/lib/sasl2 was broken. The second was that I changed my
imapd.conf to exactly how I had it with the old version of cyrus-sasl
and cyrus-imapd. Interestingly, that measn that the only line starting
with sasl_
[EMAIL PROTECTED] wrote:
I'm guessing that one of my configuration files is the problem.
My only configuration options when compiling sasl and imapd were:
--with-bdb-libdir=/usr/lib/ --with-bdb-incdir=/usr/include/db4 --disable-krb4
--disable-gssapi
The only other information I can think of that m
First, let me say that this list has been useful to me in the past when reading
the archives, so thanks to those that contribute.
I just updated cyrus-sasl from 1.5.27 to 2.1.20 and cyrus-imapd from 2.0.16 to
2.2.10. I followed the steps for upgrading that was included in the
documentation and
On Tue, 17 Feb 2004, Edward Rudd wrote:
>You have encountered the famed DB4 and NPTL bug. Goto
>http://www.invoca.ch/pub/packages/cyrus-imapd/ and download the updated
>db4.spec for fedora core 1 and recompile.
Given I'd like to stay running a non-FC kernel (2.4.24), does this change
anything?
On Mon, 2004-02-16 at 00:36, Ruth Ivimey-Cook wrote:
> Summary: I want to get imap running again, but it refuses to read my bdb
> (version 3) databases. How to I recover?
If you still have access to the original host, you can dump them using
Cyrus tools (most importantly `ctl_mboxlist -d` for mai
You have encountered the famed DB4 and NPTL bug. Goto
http://www.invoca.ch/pub/packages/cyrus-imapd/ and download the updated
db4.spec for fedora core 1 and recompile.
On Sun, 2004-02-15 at 10:36, Ruth Ivimey-Cook wrote:
> Hi folks,
>
> I hope this case isn't a 'told you so', but I have a bit of
Hi folks,
I hope this case isn't a 'told you so', but I have a bit of a problem...
Summary: I want to get imap running again, but it refuses to read my bdb
(version 3) databases. How to I recover?
I have been using Cyrus IMAPd 2.1.16 on a RH9 Linux server successfully
for some time now. I decide
On Tue, 31 Dec 2002, [iso-8859-1] Víctor Guerra wrote:
> Hello everybody, i want to update my cyrus-imap server from 2.0.16 to
> 2.1.11 and i have two questions:
> 1) What are the steps that i must do?
Read doc/install-upgrade.html, doc/changes.html might also be interesting.
> 2) Can I separat
Hello everybody, i want to update my cyrus-imap
server from 2.0.16 to 2.1.11 and i have two questions:
1) What are the steps that i must do?
2) Can I separate mailboxes in diferent partitions
depending of their first letter? (for example: if mailbox name is
exampleAmydomaincom must be deliver
28 matches
Mail list logo
