Re: Cyrus bug when returning mailbox names
On Thu 03 Apr 2003 at 13:45:46 -0500, you wrote: > How was this mailbox created? I can't duplicate this behavior with a > simple case: > > x create "inbox.xyzzy " > x OK Completed > x list "" "inbox.xyzz*" > * LIST (\HasNoChildren) "." "inbox.xyzzy " > x OK Completed To be honest, I don't know for sure. I think it was a version of Outlook, but when it was done is unknown, so it's impossible to tell. Ian -- Ian Macdonald | boss forgot system password System Administrator| Google, Inc.| [EMAIL PROTECTED] | +1 650-623-4265 |
Re: Cyrus bug when returning mailbox names
Ian Macdonald wrote: Hi, There seems to be a bug in the Cyrus code that incorrectly returns the name of a mailbox with a trailing space as that name without the space: [EMAIL PROTECTED] telnet cyrus 143 Trying 1.2.3.4... Connected to cyrus. Escape character is '^]'. * OK babbage.corp.google.com Cyrus IMAP4 v2.1.12 server ready . login tommy password . OK User logged in . list user.tommy.Agencies *Realty* * LIST (\HasNoChildren) "." "user.tommy.Agencies.Bay Area Agencies.Street Media.VIP Realty" . OK Completed (0.000 secs 2 calls) [EMAIL PROTECTED] root]# ls -ld /var/spool/imap/user/tommy/Agencies/Bay\ Area\ Agencies/Street\ Media/VIP\ Realty/ ls: /var/spool/imap/user/tommy/Agencies/Bay Area Agencies/Street Media/VIP Realty/: No such file or directory [EMAIL PROTECTED] root]# ls -ld /var/spool/imap/user/tommy/Agencies/Bay\ Area\ Agencies/Street\ Media/VIP\ Realty\ / drwx--2 cyrusroot 552 Aug 9 2002 /var/spool/imap/user/tommy/Agencies/Bay Area Agencies/Street Media/VIP Realty / Is there a simple way to rename this mailbox without the space, so that attempts to perform operations on it do not fail? Maybe it's as simple as renaming it at the file-system level, as Cyrus seems to think it lacks the space, anyway. Ian Try doing some mailbox manipulation. First, dump the mailboxes.db file to something you can edit: su - cyrus cd /var/spool/imap ctl_mboxlist -d > badmailboxes Edit badmailboxes to remove the problem name, and move the bad directory on the filesystem to the new name. Now load the mailboxes file back to db format: ctl_mboxlist -u < badmailboxes ctl_cyrusdb -c That should fix your problem.
Re: Cyrus bug when returning mailbox names
On Thu, 3 Apr 2003, Ian Macdonald wrote: > [EMAIL PROTECTED] telnet cyrus 143 > Trying 1.2.3.4... > Connected to cyrus. > Escape character is '^]'. > * OK babbage.corp.google.com Cyrus IMAP4 v2.1.12 server ready > . login tommy password > . OK User logged in > . list user.tommy.Agencies *Realty* > * LIST (\HasNoChildren) "." "user.tommy.Agencies.Bay Area Agencies.Street Media.VIP > Realty" > . OK Completed (0.000 secs 2 calls) > > [EMAIL PROTECTED] root]# ls -ld /var/spool/imap/user/tommy/Agencies/Bay\ Area\ > Agencies/Street\ Media/VIP\ Realty/ > ls: /var/spool/imap/user/tommy/Agencies/Bay Area Agencies/Street Media/VIP Realty/: > No such file or directory > [EMAIL PROTECTED] root]# ls -ld /var/spool/imap/user/tommy/Agencies/Bay\ Area\ > Agencies/Street\ Media/VIP\ Realty\ / > drwx--2 cyrusroot 552 Aug 9 2002 > /var/spool/imap/user/tommy/Agencies/Bay Area Agencies/Street Media/VIP Realty / > > Is there a simple way to rename this mailbox without the space, so that > attempts to perform operations on it do not fail? Maybe it's as simple > as renaming it at the file-system level, as Cyrus seems to think it > lacks the space, anyway. How was this mailbox created? I can't duplicate this behavior with a simple case: x create "inbox.xyzzy " x OK Completed x list "" "inbox.xyzz*" * LIST (\HasNoChildren) "." "inbox.xyzzy " x OK Completed -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
Cyrus bug when returning mailbox names
Hi, There seems to be a bug in the Cyrus code that incorrectly returns the name of a mailbox with a trailing space as that name without the space: [EMAIL PROTECTED] telnet cyrus 143 Trying 1.2.3.4... Connected to cyrus. Escape character is '^]'. * OK babbage.corp.google.com Cyrus IMAP4 v2.1.12 server ready . login tommy password . OK User logged in . list user.tommy.Agencies *Realty* * LIST (\HasNoChildren) "." "user.tommy.Agencies.Bay Area Agencies.Street Media.VIP Realty" . OK Completed (0.000 secs 2 calls) [EMAIL PROTECTED] root]# ls -ld /var/spool/imap/user/tommy/Agencies/Bay\ Area\ Agencies/Street\ Media/VIP\ Realty/ ls: /var/spool/imap/user/tommy/Agencies/Bay Area Agencies/Street Media/VIP Realty/: No such file or directory [EMAIL PROTECTED] root]# ls -ld /var/spool/imap/user/tommy/Agencies/Bay\ Area\ Agencies/Street\ Media/VIP\ Realty\ / drwx--2 cyrusroot 552 Aug 9 2002 /var/spool/imap/user/tommy/Agencies/Bay Area Agencies/Street Media/VIP Realty / Is there a simple way to rename this mailbox without the space, so that attempts to perform operations on it do not fail? Maybe it's as simple as renaming it at the file-system level, as Cyrus seems to think it lacks the space, anyway. Ian -- Ian Macdonald | The most important things, each person must System Administrator| do for himself. Google, Inc.| [EMAIL PROTECTED] | +1 650-623-4265 |
Re: sieve: Too many levels of symbolic links
You didn't activate the sieve script. -Rob On Thu, 3 Apr 2003, Dmitry Alyabyev wrote: > > > Ken Murchison wrote: > > Rob Siemborski wrote: > >> > >> On Thu, 3 Apr 2003, Dmitry Alyabyev wrote: > >> > >> > > Yeah, you made a recursive symlink. > >> > > >> > I see :) > >> > but it was made not by me but by sieve, yeah ? > >> > so I'd like to know why it happened > >> > >> Yes, it was made by sieve. So we need to make sieve reject scripts named > >> "default". > > > > Right. > > > >> Until then, don't call your script "default". > > > > FYI, Websieve does this automatically when no script is present, unless > > the user overrides it. > > Well, I did as John A. Tamplin suggested - set $defaultscript="default_sieve" in > websieve. And now I got: > $ ls -l sieve/domain/e/example.com/u/user/ > total 4 > -rw--- 1 cyrus cyrus 128 Apr 3 19:23 default_sieve.bc > -rw--- 1 cyrus cyrus 424 Apr 3 19:23 default_sieve.script > > and when I send a message to the user I see: > lmtpunix[11154]: IOERROR: fstating sieve script > /usr/local/cyrus/sieve/domain/e/example.com/u/user/default.bc: No such file or > directory > > ??? > > -- > Dimitry > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski | Andrew Systems Group * Research Systems Programmer PGP:0x5CE32FCC | Cyert Hall 207 * [EMAIL PROTECTED] * 412.268.7456 -BEGIN GEEK CODE BLOCK Version: 3.12 GCS/IT/CM/PA d- s+: a-- C$ ULS$ P+++$ L+++() E W+ N o? K- w O- M-- V-- PS+ PE++ Y+ PGP+ t+@ 5+++ R@ tv-@ b+ DI+++ G e h r- y? --END GEEK CODE BLOCK-
Re: Groups
Quoting Sebastian Konstanty Zdrojewski <[EMAIL PROTECTED]>: > The Cyrus server runs as group defined in the configure procedure. The > use of a different kind of authentication doesn't affect this, so all > the users are assigned to the Cyrus' master process. > > Of course, if I understood well how it works! :) > I mean not the group the cyrus master server is running under, but groups which I want to use to set ACL permissions on mailboxes, like "sam user/[EMAIL PROTECTED] group:mygroup read" So my question is: where I should define the groups and users who are members of these groups. Dmitry
Re: sieve: Too many levels of symbolic links
Ken Murchison wrote: > Rob Siemborski wrote: >> >> On Thu, 3 Apr 2003, Dmitry Alyabyev wrote: >> >> > > Yeah, you made a recursive symlink. >> > >> > I see :) >> > but it was made not by me but by sieve, yeah ? >> > so I'd like to know why it happened >> >> Yes, it was made by sieve. So we need to make sieve reject scripts named >> "default". > > Right. > >> Until then, don't call your script "default". > > FYI, Websieve does this automatically when no script is present, unless > the user overrides it. Well, I did as John A. Tamplin suggested - set $defaultscript="default_sieve" in websieve. And now I got: $ ls -l sieve/domain/e/example.com/u/user/ total 4 -rw--- 1 cyrus cyrus 128 Apr 3 19:23 default_sieve.bc -rw--- 1 cyrus cyrus 424 Apr 3 19:23 default_sieve.script and when I send a message to the user I see: lmtpunix[11154]: IOERROR: fstating sieve script /usr/local/cyrus/sieve/domain/e/example.com/u/user/default.bc: No such file or directory ??? -- Dimitry
Re: trouble settting up cyrus
Maik Knittel wrote: > > > I can't get cyrus working. I'm trying to install version > 2.1.12 with SASLv2 on a debian 3.0 system. I don't want > to create debian users for every imap user so I'd like > to use the sasldb athentication. I don't want to use > PAM/mySQL. > > I've got the cyrus daemon running but I can't login > either with cyradm nor imtest. I've already created > a sasl user with saslpasswd2, but the log still says: > > badlogin: X.XXX[XXX.XXX.XXX.XXX] DIGEST-MD5 [SASL(-13): user not > found: no secret in database] > > imtest says: > > imtest -u cyrus localhost > S: * OK SF111 Cyrus IMAP4 v2.1.12-Debian-2.1.12-6 server ready > C: C01 CAPABILITY > S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS > NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND SORT > THREAD=ORDEREDSUBJECT THREAD=REFERENCES IDLE AUTH=NTLM AUTH=DIGEST-MD5 > AUTH=CRAM-MD5 LISTEXT LIST-SUBSCRIBED ANNOTATEMORE > S: C01 OK Completed > C: A01 AUTHENTICATE DIGEST-MD5 > [...] > Please enter your password: > C: [...] > S: A01 NO user not found > Authentication failed. generic failure > Security strength factor: 128 > > entries in imapd.conf: > > sasl_pwcheck_method: auxprop > sasl_auxprop_plugin: sasldb > sasl_sasldb_path: /etc/sasldb2 Does the "cyrus" user have read access to /etc/sasldb2? -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
trouble settting up cyrus
I can't get cyrus working. I'm trying to install version 2.1.12 with SASLv2 on a debian 3.0 system. I don't want to create debian users for every imap user so I'd like to use the sasldb athentication. I don't want to use PAM/mySQL. I've got the cyrus daemon running but I can't login either with cyradm nor imtest. I've already created a sasl user with saslpasswd2, but the log still says: badlogin: X.XXX[XXX.XXX.XXX.XXX] DIGEST-MD5 [SASL(-13): user not found: no secret in database] imtest says: imtest -u cyrus localhost S: * OK SF111 Cyrus IMAP4 v2.1.12-Debian-2.1.12-6 server ready C: C01 CAPABILITY S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES IDLE AUTH=NTLM AUTH=DIGEST-MD5 AUTH=CRAM-MD5 LISTEXT LIST-SUBSCRIBED ANNOTATEMORE S: C01 OK Completed C: A01 AUTHENTICATE DIGEST-MD5 [...] Please enter your password: C: [...] S: A01 NO user not found Authentication failed. generic failure Security strength factor: 128 entries in imapd.conf: sasl_pwcheck_method: auxprop sasl_auxprop_plugin: sasldb sasl_sasldb_path: /etc/sasldb2 I have no clue about auxprop. Do I have to conifigure it separately? Am I missing something? regards
Re: sieve: Too many levels of symbolic links
Ken Murchison wrote: FYI, Websieve does this automatically when no script is present, unless the user overrides it. The administrator can change that configuration in websieve.conf, variable $defaultscript. -- John A. Tamplin Unix System Administrator Emory University, School of Public Health +1 404/727-9931
Re: sieve: Too many levels of symbolic links
Rob Siemborski wrote: > > On Thu, 3 Apr 2003, Dmitry Alyabyev wrote: > > > > Yeah, you made a recursive symlink. > > > > I see :) > > but it was made not by me but by sieve, yeah ? > > so I'd like to know why it happened > > Yes, it was made by sieve. So we need to make sieve reject scripts named > "default". Right. > Until then, don't call your script "default". FYI, Websieve does this automatically when no script is present, unless the user overrides it. -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: sieve - flags : delivery failure [addendum]
Manuele wrote: > > removeflag is the breaking point... > anytime (anyway) I call it, it breaks things... Yeah, if there is only one flag present, removeflag is broken. Apply the following patch that I just committed to CVS: http://bugzilla.andrew.cmu.edu/cgi-bin/cvsweb.cgi/src/sieve/script.c.diff?r1=1.55&r2=1.56&f=u -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: message in /var/log/messages
Nicolas Gauvrit wrote: i post this message yesterday, but i got no answer... (is my question to stupid for you ?) i'd like to know what does mean those message, is i do something wrong ? is my Cyrus Imap will work fine, even if i got thoses Error messages ? i was searching several hours, but i do not found anything yet... Apr 1 07:04:29 ilemadame master: setrlimit: Unable to set file descriptors limit to -1: Operation not permitted Apr 1 07:04:29 ilemadame master: retrying with 1024 (current max) Apr 1 07:04:40 ilemadame lmtpd[1177]: DBERROR db4: 7 lockers Apr 1 07:04:40 ilemadame pop3d[1176]: DBERROR db4: 8 lockers These are just warnings about lock contention, but you should probably switch from Berkeley DB to skiplist for your mailboxdb. The setrlimit failure is just warning you that it was unable to set unlimited file descriptors, but unless you have 1000 simultaneous connections you don't need to worry about it. -- John A. Tamplin Unix System Administrator Emory University, School of Public Health +1 404/727-9931
RE: cyrus sieve notify can't work !
You need to take a look at your /var/log/maillog and see what messages
are going in there when you send a message to this address. If you need
help, we would all probably need to start with that information to help
you diagnose it.
These are the lines I see due to sieve's reply function if I have a rule
that uses it:
(NOSPAM) substituted for personal email addy
Apr 3 09:30:47 human postfix/pickup[72586]: 462FACE51: uid=60 from=<>
Apr 3 09:30:47 human postfix/cleanup[73000]: 462FACE51:
message-id=<[EMAIL PROTECTED]>
Apr 3 09:30:47 human postfix/pipe[73009]: DEEAACE47:
to=<[EMAIL PROTECTED]>, relay=cyrus, delay=1, status=sent
(email.NOSPAM.com)
Apr 3 09:30:47 human postfix/qmgr[52566]: 462FACE51: from=<>, size=566,
nrcpt=1 (queue active)
Apr 3 09:30:47 human postfix/smtp[73064]: 462FACE51:
to=<[EMAIL PROTECTED]>, relay=mx2.clickcom.com[209.198.22.7],
delay=0, status=sent (250 Ok: queued as 606C550CD0)
>
Hope this helps!
John
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Brasseur Valéry
> Sent: Thursday, April 03, 2003 8:59 AM
> To: [EMAIL PROTECTED]
> Subject: cyrus sieve notify can't work !
>
>
> I am trying to use sieve notify but have no success.
> here is my sieve script :
>
> require "notify";
>
> if header :contains "from" "[EMAIL PROTECTED]" {
> notify :message "bonjour!";
> redirect "[EMAIL PROTECTED]";
> }
>
>
> when receiving a mail the redirect is working but the notify
> is not done !
>
> what's wrong ?
>
> thanks
> valery
>
>
Re: sieve: Too many levels of symbolic links
On Thu, 3 Apr 2003, Dmitry Alyabyev wrote: > > Yeah, you made a recursive symlink. > > I see :) > but it was made not by me but by sieve, yeah ? > so I'd like to know why it happened Yes, it was made by sieve. So we need to make sieve reject scripts named "default". Until then, don't call your script "default". -Rob. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
Re: message in /var/log/messages
It all depends on how many simultaneous connections you're trying to serve.
If you only need to serve a couple hundred, you're going to be fine with
this. However, if you're going to get up past 3-400 simultaneous
connections, the master is going to start to need to have more file
descriptors open in order to maintain communication with the worker
threads. I'm having trouble remembering off the top of my head what order
the open file descriptor number is going to be in relation to the
connections, but if you have more than 1024 simultaneous connections, you
will certainly run into this.
If you're on a small site, then you'll be fine, and can just ignore these.
If you're on a large site, particularly with most users keeping imap
connections open all the time, you might bump up against the max file
descriptors problem. It's your call.
Michael
--On Thursday, April 03, 2003 1:44 AM -0800 Nicolas Gauvrit
<[EMAIL PROTECTED]> wrote:
I m running a Red Hat Psyche 8.0
("fully updated")
i've found this :
http://asg.web.cmu.edu/cyrus/download/imapd/faq.html
Q: I'm getting messages in imapd.log like:
Sep 11 17:23:55 ogg lmtpd[773]: DBERROR db3: 16
lockers
Sep 11 17:23:55 ogg lmtpd[1409]: DBERROR db3: 17
lockers
Sep 11 17:23:56 ogg lmtpd[1508]: DBERROR db3: 9
lockers
Sep 11 17:23:56 ogg lmtpd[776]: DBERROR db3: 9 lockers
What's wrong?
A: Nothing is wrong. These messages are logged
whenever Berkeley db encounters lock contention, but
isn't necessarily a problem by themselves. This is
especially likely when you have an empty or small
duplicate delivery database and are receiving a large
volume of e-mail.
Berkeley db 4.0 has a bug where the number of lockers
isn't decremented properly, causing this number to be
unreliable.
and this :
http://www.irbs.net/internet/info-cyrus/0211/0174.html
On Wed, 13 Nov 2002, Andrei Loukinykh wrote:
Well, now I have Cyrus installed (yet not completely
tested though)
The only 2 things left, which are bothering me now ,
2 king of messages
in syslog:
1:
"lmtpd[10260]: DBERROR db4: 9 lockers"
These are usually harmless, unless they go up in a
sudden spike or are
accompanied by other problems, its ok.
2:
"master: setrlimit: Unable to set file descriptors
limit to
-1: Operation not permitted"
This is also mostly harmless, it indicates that cyrus
was unable to
unlimit its max # of file descriptors, which is
generally ok.
But, may be there's something I can do to fix those
bugs , to live with
clean logs...?
change the code? turn off logging? Since the setrlimit
one only occurs
at startup, it shouldn't be that big a deal. I can see
the DBERROR one
being more annoying I guess, but it would require a
change to the code.
-Rob
So i don't think this is really a problem .. ?? isn't
it ?
Best regards
--- Michael Bacon <[EMAIL PROTECTED]> wrote:
What operating system?
--On Wednesday, April 02, 2003 10:26 PM -0800
Nicolas Gauvrit
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> i post this message yesterday, but i got no
answer...
> (is my question to stupid for you ?)
>
> i'd like to know what does mean those message,
> is i do something wrong ?
>
> is my Cyrus Imap will work fine, even if i got
thoses
> Error messages ?
>
> i was searching several hours, but i do not found
> anything yet...
>
> Apr 1 07:04:29 ilemadame master: setrlimit:
Unable to
> set file descriptors limit to -1: Operation not
> permitted
> Apr 1 07:04:29 ilemadame master: retrying with
1024
> (current max)
>
> Apr 1 07:04:40 ilemadame lmtpd[1177]: DBERROR
db4: 7
> lockers
> Apr 1 07:04:40 ilemadame pop3d[1176]: DBERROR
db4: 8
> lockers
>
> Thank you.
>
>
> --- Nicolas Gauvrit <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> i had installed cyrus-imapd-2.1.11 with options :
>>
>> ./configure --with-auth=unix
>> --with-sasl=/usr/lib/sasl2
--with-cyrus-group=cyrus
>> --with-openssl=/usr/include/openssl --no-create
>> --no-recursion --with-mboxlist-db=skiplist
>>
>> I got those messages in /var/log/messages
>>
>> Apr 1 07:04:29 ilemadame master: setrlimit:
Unable
>> to
>> set file descriptors limit to -1: Operation not
>> permitted
>> Apr 1 07:04:29 ilemadame master: retrying with
1024
>> (current max)
>> Apr 1 07:04:29 ilemadame master[1170]: process
>> started
>> Apr 1 07:04:29 ilemadame ctl_cyrusdb[1171]:
>> recovering cyrus databases
>> Apr 1 07:04:39 ilemadame ctl_cyrusdb[1171]: done
>> recovering cyrus databases
>> Apr 1 07:04:39 ilemadame master[1170]: ready for
>> work
>> Apr 1 07:04:39 ilemadame ctl_cyrusdb[1172]:
>> checkpointing cyrus databases
>> Apr 1 07:04:40 ilemadame lmtpd[1177]: DBERROR
db4:
>> 7
>> lockers
>> Apr 1 07:04:40 ilemadame pop3d[1176]: DBERROR
db4:
>> 8
>> lockers
>> Apr 1 07:05:17 ilemadame ctl_cyrusdb[1172]: done
>> checkpointing cyrus databases
>>
>>
>>
>> What does it really mean ?
>> is it ok ?
>>
>> i've seen ( here :
>>
>
http://www.irbs.net/internet/info-cyrus/0211/0174.html
>> )
>> that it might be not a problem, but i'd like read
>> your
>> advises
>>
>>
>> thank yo
cyrus sieve notify can't work !
I am trying to use sieve notify but have no success.
here is my sieve script :
require "notify";
if header :contains "from" "[EMAIL PROTECTED]" {
notify :message "bonjour!";
redirect "[EMAIL PROTECTED]";
}
when receiving a mail the redirect is working but the notify is not done !
what's wrong ?
thanks
valery
sieve - flags : delivery failure [addendum]
removeflag is the breaking point...
anytime (anyway) I call it, it breaks things...
well, i can live with that...
but looks like a strange bug...
anyhelp still appreciated :)
Manuele
> - Original Message -
> From: "Manuele" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, April 03, 2003 12:54 PM
> Subject: Re: sieve - flags : delivery failure
>
>
> > Since
> > fatal("Virtual memory exhausted", EC_TEMPFAIL);
> > comes with xmalloc.c
> > I though to give you also some info about the machine
> >
> > Linux doorbell 2.4.20 #5 Tue Mar 25 03:20:28 CET 2003 i686 unknown
> > Slackware 8.1
> > Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/2.95.3/specs
> > gcc version 2.95.3 20010315 (release)
> > libc.so.6 -> libc-2.2.5.so
> >
> > can't really help more...
> > I'm too stupid that :/
> > tia tia tia
> > oh, btw, all the rest, so far, works fine :)
> >
> >
> > - Original Message -
> > From: "Manuele" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, April 03, 2003 11:56 AM
> > Subject: Re: sieve - flags : delivery failure
> >
> >
> > > First of all, thanks for the attention and sorry for the lack of
> > > informations...
> > > I will try my best now to provide relevant data...
> > >
> > > UPDATE WHILE WRITING (and testing)
> > > Messages GETS delivered and correctly flagged, but deliver
> > > returns a temporary fail, so that at the first try:
> > > postfix enqueues the message
> > > and later tries:
> > > deliver says message is a duplicate,
> > > postfix enqueues the message again
> > > and so on...
> > >
> > > The point is: there's some error at some point of the mail delivery
> > process
> > > if sieve is due to use imapflags
> > >
> > > Sieve is installed properly (I guess) and supports imapflags
> > > "IMPLEMENTATION" "Cyrus timsieved v2.1.12"
> > > "SASL" "PLAIN"
> > > "SIEVE" "fileinto reject envelope vacation imapflags notify
> subaddress
> > > relational regex"
> > >
> > > runng test program (which I learned the existence of now...) returns
the
> > > following:
> > > filing message 'mail' into 'INBOX.spam'
> > > with flags '\deleted'
> > > fatal error: Virtual memory exhausted
> > >
> > > trying ulimit -d unlimited did not help
> > >
> > > the sieve script looks like that:
> > > require ["imapflags", "fileinto"];
> > >
> > > # New Rule
> > > if header :comparator "i;ascii-casemap" :contains
> "X-Spam-Status"
> > > "Yes" {
> > > addflag "\\Deleted";
> > > fileinto "INBOX.spam";
> > > removeflag "\\Deleted";
> > > stop;
> > > }
> > >
> > > While the message contains X-Spam-Status: Yes
> > >
> > >
> > > software versions:
> > > cyrus-imap-2.1.12
> > > cyrus-sasl-2.1.5 + ldap/mysql patch
> > > postfix 2.0.7 + mysql support
> > > amavisd-new
> > >
> > > software configurations:
> > > /etc/imapd.conf
> > > configdirectory: /var/imap
> > > partition-default: /usr/data/spool/imap
> > > quotawarn: 90
> > > admins: cyrus root
> > > srvtab: /var/imap/srvtab
> > > allowanonymouslogin: no
> > > pwcheck_method: auxprop
> > > tls_cert_file: /var/imap/server.pem
> > > tls_key_file: /var/imap/server.pem
> > >
> > > /etc/cyrus.conf is a copy of prefork.conf
> > >
> > > /etc/postfix/master.cf
> > > cyrus unix - n n - - pipe
> > >flags= user=cyrus argv=/usr/cyrus/bin/deliver -r ${sender} -m
> > > ${extension} ${user}
> > >
> > > /etc/postfix/main.cf
> > > mailbox_transport = cyrus
> > >
> > > btw: haven't been able to use other LDA methods...
> > > maybe we'll talk about that later...
> > >
> > >
> > > note:
> > > amavisd+postfix
> > > amavisd is configured to run a smtp style forwarding of
> > > the message, via localhost 10025, where postfix listens without
> > > content_filter
> > >
> > > amavisd itself works fine with postfix
> > > I spent 5 hours debugging it, while I thought the problem was
somewhere
> > > there...
> > >
> > >
> > > Now the log...
> > > it's a *.* log of an incoming mail from: [EMAIL PROTECTED] to:
> > > [EMAIL PROTECTED] (which is user manu)
> > > mail gets parsed by amavisd, headers (X-Spam-Status: Yes) is added,
> > > message gets back to postfix which attempts first deliver
> > > gets a temporary fail, and enqueues the message
> > >
> > > for better reading amavisd related stuff was suppressed...
> > >
> > >
> > > postfix/smtpd[2206]: warning: dict_nis_init: NIS domain name not set -
> NIS
> > > lookups disabled
> > > postfix/smtpd[2206]: connect from unknown[192.168.1.5]
> > > postfix/smtpd[2206]: 122C3862C: client=unknown[192.168.1.5]
> > > imapd[1380]: accepted connection
> > > master[2211]: about to exec /usr/cyrus/bin/imapd
> > > imap[2211]: executed
> > > postfix/cleanup[2208]: 122C3862C:
> > > message-id=<[EMAIL PROTECTED]>
> > > postfix/qmgr[364]: 122C3862C: from=<[EMAIL PROTECTED]>, size=435,
nrcpt=1
> >
RE: 2.2a, virtual domains and squirrelmail
Yes! I use SM and hold domains and users in mySQL. Works well with 2.2a and has worked for ages with 2.2prealpha. > -Original Message- > From: Mike O'Rourke [mailto:[EMAIL PROTECTED] > Sent: 03 April 2003 13:04 > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: 2.2a, virtual domains and squirrelmail > > > Mine works! > > cyrus-imapd 2.2 cvs from about Mar. 26 (OK, I am busy and haven't had > time to get the recently released version, but it is working for me > (TM)) > squirrelmail 1.4rc2a (see excuse above) > PHP 4.3.2rc1 > Apache 2.0.44 > > Mike. > > >>> "Kervin L. Pierre" <[EMAIL PROTECTED]> 04/03/03 05:39am > >>> > > Has anyone tried using squirrelmail with 2.2 virtual domains > and got it > > to work with a mailbox on a virtual domain? > > http://www.squirrelmail.org/ > -- > > > Kervin Pierre > > [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED] > >
Re: 2.2a, virtual domains and squirrelmail
Mine works! cyrus-imapd 2.2 cvs from about Mar. 26 (OK, I am busy and haven't had time to get the recently released version, but it is working for me (TM)) squirrelmail 1.4rc2a (see excuse above) PHP 4.3.2rc1 Apache 2.0.44 Mike. >>> "Kervin L. Pierre" <[EMAIL PROTECTED]> 04/03/03 05:39am >>> Has anyone tried using squirrelmail with 2.2 virtual domains and got it to work with a mailbox on a virtual domain? http://www.squirrelmail.org/ -- Kervin Pierre [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: sieve - flags : delivery failure
Since
fatal("Virtual memory exhausted", EC_TEMPFAIL);
comes with xmalloc.c
I though to give you also some info about the machine
Linux doorbell 2.4.20 #5 Tue Mar 25 03:20:28 CET 2003 i686 unknown
Slackware 8.1
Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/2.95.3/specs
gcc version 2.95.3 20010315 (release)
libc.so.6 -> libc-2.2.5.so
can't really help more...
I'm too stupid that :/
tia tia tia
oh, btw, all the rest, so far, works fine :)
- Original Message -
From: "Manuele" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 03, 2003 11:56 AM
Subject: Re: sieve - flags : delivery failure
> First of all, thanks for the attention and sorry for the lack of
> informations...
> I will try my best now to provide relevant data...
>
> UPDATE WHILE WRITING (and testing)
> Messages GETS delivered and correctly flagged, but deliver
> returns a temporary fail, so that at the first try:
> postfix enqueues the message
> and later tries:
> deliver says message is a duplicate,
> postfix enqueues the message again
> and so on...
>
> The point is: there's some error at some point of the mail delivery
process
> if sieve is due to use imapflags
>
> Sieve is installed properly (I guess) and supports imapflags
> "IMPLEMENTATION" "Cyrus timsieved v2.1.12"
> "SASL" "PLAIN"
> "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress
> relational regex"
>
> runng test program (which I learned the existence of now...) returns the
> following:
> filing message 'mail' into 'INBOX.spam'
> with flags '\deleted'
> fatal error: Virtual memory exhausted
>
> trying ulimit -d unlimited did not help
>
> the sieve script looks like that:
> require ["imapflags", "fileinto"];
>
> # New Rule
> if header :comparator "i;ascii-casemap" :contains "X-Spam-Status"
> "Yes" {
> addflag "\\Deleted";
> fileinto "INBOX.spam";
> removeflag "\\Deleted";
> stop;
> }
>
> While the message contains X-Spam-Status: Yes
>
>
> software versions:
> cyrus-imap-2.1.12
> cyrus-sasl-2.1.5 + ldap/mysql patch
> postfix 2.0.7 + mysql support
> amavisd-new
>
> software configurations:
> /etc/imapd.conf
> configdirectory: /var/imap
> partition-default: /usr/data/spool/imap
> quotawarn: 90
> admins: cyrus root
> srvtab: /var/imap/srvtab
> allowanonymouslogin: no
> pwcheck_method: auxprop
> tls_cert_file: /var/imap/server.pem
> tls_key_file: /var/imap/server.pem
>
> /etc/cyrus.conf is a copy of prefork.conf
>
> /etc/postfix/master.cf
> cyrus unix - n n - - pipe
>flags= user=cyrus argv=/usr/cyrus/bin/deliver -r ${sender} -m
> ${extension} ${user}
>
> /etc/postfix/main.cf
> mailbox_transport = cyrus
>
> btw: haven't been able to use other LDA methods...
> maybe we'll talk about that later...
>
>
> note:
> amavisd+postfix
> amavisd is configured to run a smtp style forwarding of
> the message, via localhost 10025, where postfix listens without
> content_filter
>
> amavisd itself works fine with postfix
> I spent 5 hours debugging it, while I thought the problem was somewhere
> there...
>
>
> Now the log...
> it's a *.* log of an incoming mail from: [EMAIL PROTECTED] to:
> [EMAIL PROTECTED] (which is user manu)
> mail gets parsed by amavisd, headers (X-Spam-Status: Yes) is added,
> message gets back to postfix which attempts first deliver
> gets a temporary fail, and enqueues the message
>
> for better reading amavisd related stuff was suppressed...
>
>
> postfix/smtpd[2206]: warning: dict_nis_init: NIS domain name not set - NIS
> lookups disabled
> postfix/smtpd[2206]: connect from unknown[192.168.1.5]
> postfix/smtpd[2206]: 122C3862C: client=unknown[192.168.1.5]
> imapd[1380]: accepted connection
> master[2211]: about to exec /usr/cyrus/bin/imapd
> imap[2211]: executed
> postfix/cleanup[2208]: 122C3862C:
> message-id=<[EMAIL PROTECTED]>
> postfix/qmgr[364]: 122C3862C: from=<[EMAIL PROTECTED]>, size=435, nrcpt=1
> (queue active)
> amavis[553]: (00553-05) FWD via SMTP: [127.0.0.1:10025]
> <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>
> postfix/smtpd[2220]: connect from localhost[127.0.0.1]
> postfix/smtpd[2220]: 6B2917C50: client=localhost[127.0.0.1]
> postfix/cleanup[2208]: 6B2917C50:
> message-id=<[EMAIL PROTECTED]>
> postfix/qmgr[364]: 6B2917C50: from=<[EMAIL PROTECTED]>, size=1053, nrcpt=1
> (queue active)
> lmtpd[2205]: accepted connection
> lmtpd[2205]: lmtp connection preauth'd as postman
> lmtpd[2205]: duplicate_check:
> <[EMAIL PROTECTED]> user.manu.spam 0
> master[2223]: about to exec /usr/cyrus/bin/lmtpd
> lmtpunix[2223]: executed
> postfix/smtpd[2220]: disconnect from localhost[127.0.0.1]
> amavis[553]: (00553-05) mail_via_smtp: 250 2.6.0 Ok, id=00553-05, from
MTA:
> 250 Ok: queued as 6B2917C50
> lmtpd[2205]: mystore: starting txn 2147484051
> lmtpd[2205]: mystore: committing txn 2147484051
> l
Re: sieve - flags : delivery failure
First of all, thanks for the attention and sorry for the lack of
informations...
I will try my best now to provide relevant data...
UPDATE WHILE WRITING (and testing)
Messages GETS delivered and correctly flagged, but deliver
returns a temporary fail, so that at the first try:
postfix enqueues the message
and later tries:
deliver says message is a duplicate,
postfix enqueues the message again
and so on...
The point is: there's some error at some point of the mail delivery process
if sieve is due to use imapflags
Sieve is installed properly (I guess) and supports imapflags
"IMPLEMENTATION" "Cyrus timsieved v2.1.12"
"SASL" "PLAIN"
"SIEVE" "fileinto reject envelope vacation imapflags notify subaddress
relational regex"
runng test program (which I learned the existence of now...) returns the
following:
filing message 'mail' into 'INBOX.spam'
with flags '\deleted'
fatal error: Virtual memory exhausted
trying ulimit -d unlimited did not help
the sieve script looks like that:
require ["imapflags", "fileinto"];
# New Rule
if header :comparator "i;ascii-casemap" :contains "X-Spam-Status"
"Yes" {
addflag "\\Deleted";
fileinto "INBOX.spam";
removeflag "\\Deleted";
stop;
}
While the message contains X-Spam-Status: Yes
software versions:
cyrus-imap-2.1.12
cyrus-sasl-2.1.5 + ldap/mysql patch
postfix 2.0.7 + mysql support
amavisd-new
software configurations:
/etc/imapd.conf
configdirectory: /var/imap
partition-default: /usr/data/spool/imap
quotawarn: 90
admins: cyrus root
srvtab: /var/imap/srvtab
allowanonymouslogin: no
pwcheck_method: auxprop
tls_cert_file: /var/imap/server.pem
tls_key_file: /var/imap/server.pem
/etc/cyrus.conf is a copy of prefork.conf
/etc/postfix/master.cf
cyrus unix - n n - - pipe
flags= user=cyrus argv=/usr/cyrus/bin/deliver -r ${sender} -m
${extension} ${user}
/etc/postfix/main.cf
mailbox_transport = cyrus
btw: haven't been able to use other LDA methods...
maybe we'll talk about that later...
note:
amavisd+postfix
amavisd is configured to run a smtp style forwarding of
the message, via localhost 10025, where postfix listens without
content_filter
amavisd itself works fine with postfix
I spent 5 hours debugging it, while I thought the problem was somewhere
there...
Now the log...
it's a *.* log of an incoming mail from: [EMAIL PROTECTED] to:
[EMAIL PROTECTED] (which is user manu)
mail gets parsed by amavisd, headers (X-Spam-Status: Yes) is added,
message gets back to postfix which attempts first deliver
gets a temporary fail, and enqueues the message
for better reading amavisd related stuff was suppressed...
postfix/smtpd[2206]: warning: dict_nis_init: NIS domain name not set - NIS
lookups disabled
postfix/smtpd[2206]: connect from unknown[192.168.1.5]
postfix/smtpd[2206]: 122C3862C: client=unknown[192.168.1.5]
imapd[1380]: accepted connection
master[2211]: about to exec /usr/cyrus/bin/imapd
imap[2211]: executed
postfix/cleanup[2208]: 122C3862C:
message-id=<[EMAIL PROTECTED]>
postfix/qmgr[364]: 122C3862C: from=<[EMAIL PROTECTED]>, size=435, nrcpt=1
(queue active)
amavis[553]: (00553-05) FWD via SMTP: [127.0.0.1:10025]
<[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>
postfix/smtpd[2220]: connect from localhost[127.0.0.1]
postfix/smtpd[2220]: 6B2917C50: client=localhost[127.0.0.1]
postfix/cleanup[2208]: 6B2917C50:
message-id=<[EMAIL PROTECTED]>
postfix/qmgr[364]: 6B2917C50: from=<[EMAIL PROTECTED]>, size=1053, nrcpt=1
(queue active)
lmtpd[2205]: accepted connection
lmtpd[2205]: lmtp connection preauth'd as postman
lmtpd[2205]: duplicate_check:
<[EMAIL PROTECTED]> user.manu.spam 0
master[2223]: about to exec /usr/cyrus/bin/lmtpd
lmtpunix[2223]: executed
postfix/smtpd[2220]: disconnect from localhost[127.0.0.1]
amavis[553]: (00553-05) mail_via_smtp: 250 2.6.0 Ok, id=00553-05, from MTA:
250 Ok: queued as 6B2917C50
lmtpd[2205]: mystore: starting txn 2147484051
lmtpd[2205]: mystore: committing txn 2147484051
lmtpd[2205]: duplicate_mark:
<[EMAIL PROTECTED]> user.manu.spam
1049361236
master[944]: process 2205 exited, status 75
here's the problem
postfix/pipe[2196]: 6B2917C50: to=<[EMAIL PROTECTED]>, relay=cyrus,
delay=1, status=deferred (temporary failure)
postfix/smtp[2216]: 122C3862C: to=<[EMAIL PROTECTED]>,
relay=127.0.0.1[127.0.0.1], delay=37, status=sent (250 2.6.0 Ok,
id=00553-05, from MTA: 250 Ok: queued as 6B2917C50)
master[944]: process 1380 exited, status 0
message is now DELIVERED, but postfix thinks not and
it keeps it in queue...
TIA guys :)
any hint appreciated
Manuele.
- Original Message -
From: "Mark Keasling" <[EMAIL PROTECTED]>
To: "Manuele" <[EMAIL PROTECTED]>
Sent: Thursday, April 03, 2003 6:54 AM
Subject: Re: sieve - flags : delivery failure
> Hi Manuele,
>
> I'm not sure I can help solve your problem with the addflag/removefl
Re: message in /var/log/messages
I m running a Red Hat Psyche 8.0
("fully updated")
i've found this :
http://asg.web.cmu.edu/cyrus/download/imapd/faq.html
Q: I'm getting messages in imapd.log like:
Sep 11 17:23:55 ogg lmtpd[773]: DBERROR db3: 16
lockers
Sep 11 17:23:55 ogg lmtpd[1409]: DBERROR db3: 17
lockers
Sep 11 17:23:56 ogg lmtpd[1508]: DBERROR db3: 9
lockers
Sep 11 17:23:56 ogg lmtpd[776]: DBERROR db3: 9 lockers
What's wrong?
A: Nothing is wrong. These messages are logged
whenever Berkeley db encounters lock contention, but
isn't necessarily a problem by themselves. This is
especially likely when you have an empty or small
duplicate delivery database and are receiving a large
volume of e-mail.
Berkeley db 4.0 has a bug where the number of lockers
isn't decremented properly, causing this number to be
unreliable.
and this :
http://www.irbs.net/internet/info-cyrus/0211/0174.html
On Wed, 13 Nov 2002, Andrei Loukinykh wrote:
> Well, now I have Cyrus installed (yet not completely
tested though)
> The only 2 things left, which are bothering me now ,
2 king of messages
> in syslog:
>
> 1:
> "lmtpd[10260]: DBERROR db4: 9 lockers"
These are usually harmless, unless they go up in a
sudden spike or are
accompanied by other problems, its ok.
> 2:
> "master: setrlimit: Unable to set file descriptors
limit to
> -1: Operation not permitted"
This is also mostly harmless, it indicates that cyrus
was unable to
unlimit its max # of file descriptors, which is
generally ok.
> But, may be there's something I can do to fix those
bugs , to live with
> clean logs...?
change the code? turn off logging? Since the setrlimit
one only occurs
at startup, it shouldn't be that big a deal. I can see
the DBERROR one
being more annoying I guess, but it would require a
change to the code.
-Rob
So i don't think this is really a problem .. ?? isn't
it ?
Best regards
--- Michael Bacon <[EMAIL PROTECTED]> wrote:
> What operating system?
>
> --On Wednesday, April 02, 2003 10:26 PM -0800
> Nicolas Gauvrit
> <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > i post this message yesterday, but i got no
> answer...
> > (is my question to stupid for you ?)
> >
> > i'd like to know what does mean those message,
> > is i do something wrong ?
> >
> > is my Cyrus Imap will work fine, even if i got
> thoses
> > Error messages ?
> >
> > i was searching several hours, but i do not found
> > anything yet...
> >
> > Apr 1 07:04:29 ilemadame master: setrlimit:
> Unable to
> > set file descriptors limit to -1: Operation not
> > permitted
> > Apr 1 07:04:29 ilemadame master: retrying with
> 1024
> > (current max)
> >
> > Apr 1 07:04:40 ilemadame lmtpd[1177]: DBERROR
> db4: 7
> > lockers
> > Apr 1 07:04:40 ilemadame pop3d[1176]: DBERROR
> db4: 8
> > lockers
> >
> > Thank you.
> >
> >
> > --- Nicolas Gauvrit <[EMAIL PROTECTED]> wrote:
> >> Hi,
> >>
> >> i had installed cyrus-imapd-2.1.11 with options :
> >>
> >> ./configure --with-auth=unix
> >> --with-sasl=/usr/lib/sasl2
> --with-cyrus-group=cyrus
> >> --with-openssl=/usr/include/openssl --no-create
> >> --no-recursion --with-mboxlist-db=skiplist
> >>
> >> I got those messages in /var/log/messages
> >>
> >> Apr 1 07:04:29 ilemadame master: setrlimit:
> Unable
> >> to
> >> set file descriptors limit to -1: Operation not
> >> permitted
> >> Apr 1 07:04:29 ilemadame master: retrying with
> 1024
> >> (current max)
> >> Apr 1 07:04:29 ilemadame master[1170]: process
> >> started
> >> Apr 1 07:04:29 ilemadame ctl_cyrusdb[1171]:
> >> recovering cyrus databases
> >> Apr 1 07:04:39 ilemadame ctl_cyrusdb[1171]: done
> >> recovering cyrus databases
> >> Apr 1 07:04:39 ilemadame master[1170]: ready for
> >> work
> >> Apr 1 07:04:39 ilemadame ctl_cyrusdb[1172]:
> >> checkpointing cyrus databases
> >> Apr 1 07:04:40 ilemadame lmtpd[1177]: DBERROR
> db4:
> >> 7
> >> lockers
> >> Apr 1 07:04:40 ilemadame pop3d[1176]: DBERROR
> db4:
> >> 8
> >> lockers
> >> Apr 1 07:05:17 ilemadame ctl_cyrusdb[1172]: done
> >> checkpointing cyrus databases
> >>
> >>
> >>
> >> What does it really mean ?
> >> is it ok ?
> >>
> >> i've seen ( here :
> >>
> >
>
http://www.irbs.net/internet/info-cyrus/0211/0174.html
> >> )
> >> that it might be not a problem, but i'd like read
> >> your
> >> advises
> >>
> >>
> >> thank you
> >>
> >>
> >>
> >> my imapd.conf :
> >> ---
> >> configdirectory: /var/imap
> >> partition-default: /home/cyrus/var/spool/imap
> >> admins: cyrus
> >> sasl_pwcheck_method: auxprop
> >> allowanonymouslogin: no
> >> timeout: 30
> >> poptimeout: 30
> >> popinpoll: 0
> >> defaultacl: lrswipcd
> >> sievedir: /usr/sieve
> >> sendmail: /usr/lib/sendmail
> >> srvtab: /var/imap/srvtab
> >> tls_cert_file: /var/imap/server.pem
> >> tls_key_file: /var/imap/server.pem
> >>
> >> my cyrus.conf :
> >> ---
> >>
> >>
> >> # standard standalone server implementation
> >>
> >> START {
> >> # do not delete this entry!
> >> recover cmd="ctl_cyrusdb -r"
> >>
> >> # this is only
Re: sieve: Too many levels of symbolic links
On Thu, 03 Apr 2003 11:16:45 +0300 Dmitry Alyabyev <[EMAIL PROTECTED]> wrote: Hello, > lrwx-- 1 cyrus cyrus 10 Apr 3 10:53 default.bc -> default.bc ^^^ > when a message delivers there is an error in cyrus log: > lmtpunix[10531]: IOERROR: fstating sieve script > /usr/local/cyrus/sieve/domain/e/example.com/u/username/default.bc: Too > many levels of symbolic links > > and sieve doesn't work according to rules of default.script > > any ideas why it happens ? Yeah, you made a recursive symlink. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk Tired of Spam? -> http://www.trustic.com pgp0.pgp Description: PGP signature
Re: sieve: Too many levels of symbolic links
Miguel Mendez wrote: > On Thu, 03 Apr 2003 11:16:45 +0300 > Dmitry Alyabyev <[EMAIL PROTECTED]> wrote: > > Hello, > >> lrwx-- 1 cyrus cyrus 10 Apr 3 10:53 default.bc -> default.bc >^^^ >> when a message delivers there is an error in cyrus log: >> lmtpunix[10531]: IOERROR: fstating sieve script >> /usr/local/cyrus/sieve/domain/e/example.com/u/username/default.bc: Too >> many levels of symbolic links >> >> and sieve doesn't work according to rules of default.script >> >> any ideas why it happens ? > > Yeah, you made a recursive symlink. I see :) but it was made not by me but by sieve, yeah ? so I'd like to know why it happened -- Dimitry
sieve: Too many levels of symbolic links
hello strange behavior - when I use websieve 0.61 (by Alain Turbide) with timsieved of cyrus 2.2 I have something like this in user sieve directory: lrwx-- 1 cyrus cyrus 10 Apr 3 10:53 default.bc -> default.bc -rw--- 1 cyrus cyrus 424 Apr 3 10:53 default.script when a message delivers there is an error in cyrus log: lmtpunix[10531]: IOERROR: fstating sieve script /usr/local/cyrus/sieve/domain/e/example.com/u/username/default.bc: Too many levels of symbolic links and sieve doesn't work according to rules of default.script any ideas why it happens ? -- Dimitry
