Re: Logs filling with strange error
> On 07 Jul 2003 18:17:29 -0700, > Scott Bronson <[EMAIL PROTECTED]> (sb) writes: sb> As long as they don't indicate something amiss, I can live with them. sb> Thanks. Incidentally, they're gone in 2.1.14. -- Amos
Re: sieve script not running?
> On Mon, 7 Jul 2003 21:34:37 -0400 (EDT), > Igor Brezac <[EMAIL PROTECTED]> (ib) writes: >> > gcc -L/usr/local/lib -R/usr/local/lib -L/usr/local/BerkeleyDB.4.0/lib >> > -R/usr/local/BerkeleyDB.4.0/lib -L/usr/local/lib -R/usr/local/lib >> > -L/usr/local/lib -L/usr/local/lib -o test \ >> > test.o libsieve.a ../et/libcom_err.a ../lib/libcyrus.a >> > Undefined first referenced >> > symbol in file >> > shutdown../lib/libcyrus.a(util.o) >> > ld: fatal: Symbol referencing errors. No output written to test >> > collect2: ld returned 1 exit status >> > gmake: *** [test] Error 1 >> > ib> You are missing -lsocket -lnsl in your link statement. Maybe that library changed between 2.1.12 and 2.1.13 to require those libraries? I notice the compile line is the same for both, but since 2.1.13 the error above appears. Yeah, as you say, adding those two fixes link problem. Looks like configure.in is missing something that the others have. -- Amos
Re: sieve script not running?
> On Mon, 07 Jul 2003 21:13:22 -0400, > Ken Murchison <[EMAIL PROTECTED]> (km) writes: km> Which version of Cyrus gives the problem below? Reviewing my logs from my build script, it appears to have started with 2.1.13. Yeah, 2.1.12 compiled just fine. Sorry for not mentioning it sooner. Kinda forgot about it. -- Amos
Re: sieve script not running?
On Mon, 7 Jul 2003, Ken Murchison wrote: > > > Amos Gouaux wrote: > >>On Mon, 07 Jul 2003 15:56:17 -0400, > >>Ken Murchison <[EMAIL PROTECTED]> (km) writes: > > > > > > km> Test your script/message combo by running the them through the > > km> sieve/test.c program in the distro. > > > > Oh, that reminds me of something. I generally try to compile that > > because it's handy for manually testing scripts (will this work > > with 2.2?). > > If you're asking if the test program will work with 2.2 (bytecode), the > answer is yes, provided you compile the script with sievec first. > > Which version of Cyrus gives the problem below? > > > However, last time I tried, got this: > > > > + cd sieve > > + gmake test > > gcc -c -I. -I.. -I. -I./../lib -I./../et -I/usr/local/BerkeleyDB.4.0/include > > -I/usr/local/include -I/usr/local/include -I/usr/local/include -DHAVE_CONFIG_H -I. > > -I. -Wall -g -O2 \ > > test.c > > test.c: In function `hashheader': > > test.c:70: warning: subscript has type `char' > > test.c: In function `parseheader': > > test.c:108: warning: subscript has type `char' > > test.c:121: warning: subscript has type `char' > > gcc -L/usr/local/lib -R/usr/local/lib -L/usr/local/BerkeleyDB.4.0/lib > > -R/usr/local/BerkeleyDB.4.0/lib -L/usr/local/lib -R/usr/local/lib > > -L/usr/local/lib -L/usr/local/lib -o test \ > > test.o libsieve.a ../et/libcom_err.a ../lib/libcyrus.a > > Undefined first referenced > > symbol in file > > shutdown../lib/libcyrus.a(util.o) > > ld: fatal: Symbol referencing errors. No output written to test > > collect2: ld returned 1 exit status > > gmake: *** [test] Error 1 > > You are missing -lsocket -lnsl in your link statement. -- Igor
Re: sieve script not running?
Amos Gouaux wrote: On Mon, 07 Jul 2003 15:56:17 -0400, Ken Murchison <[EMAIL PROTECTED]> (km) writes: km> Test your script/message combo by running the them through the km> sieve/test.c program in the distro. Oh, that reminds me of something. I generally try to compile that because it's handy for manually testing scripts (will this work with 2.2?). If you're asking if the test program will work with 2.2 (bytecode), the answer is yes, provided you compile the script with sievec first. Which version of Cyrus gives the problem below? > However, last time I tried, got this: + cd sieve + gmake test gcc -c -I. -I.. -I. -I./../lib -I./../et -I/usr/local/BerkeleyDB.4.0/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -DHAVE_CONFIG_H -I. -I. -Wall -g -O2 \ test.c test.c: In function `hashheader': test.c:70: warning: subscript has type `char' test.c: In function `parseheader': test.c:108: warning: subscript has type `char' test.c:121: warning: subscript has type `char' gcc -L/usr/local/lib -R/usr/local/lib -L/usr/local/BerkeleyDB.4.0/lib -R/usr/local/BerkeleyDB.4.0/lib -L/usr/local/lib -R/usr/local/lib -L/usr/local/lib -L/usr/local/lib -o test \ test.o libsieve.a ../et/libcom_err.a ../lib/libcyrus.a Undefined first referenced symbol in file shutdown../lib/libcyrus.a(util.o) ld: fatal: Symbol referencing errors. No output written to test collect2: ld returned 1 exit status gmake: *** [test] Error 1 This is on Solaris 8 with gcc-3.2.3. -- 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: Logs filling with strange error
As long as they don't indicate something amiss, I can live with them. Thanks. - Scott On Mon, 2003-07-07 at 12:54, Ken Murchison wrote: > These are harmless (I could give you a technical reason if you care). > Reduce you logging level from DEBUG down to something like INFO or > NOTICE and these will disappear. > > > Scott Bronson wrote: > > > Can anyone tell me why my logs are filling with messages > > like these? > > > > Jul 5 17:41:08 eden cyrus/lmtpd[28993]: Could not shut down > > filedescriptor 0: Bad file descriptor > > Jul 5 17:41:08 eden cyrus/lmtpd[28993]: Could not shut down > > filedescriptor 1: Bad file descriptor > > Jul 5 17:41:08 eden cyrus/lmtpd[28993]: Could not shut down > > filedescriptor 2: Bad file descriptor > > Jul 5 17:41:09 eden cyrus/imapd[28983]: Could not shut down > > filedescriptor 0: Bad file descriptor > > Jul 5 17:41:09 eden cyrus/imapd[28983]: Could not shut down > > filedescriptor 1: Bad file descriptor > > Jul 5 17:41:09 eden cyrus/imapd[28983]: Could not shut down > > filedescriptor 2: Bad file descriptor > > > > Why would cyrus even TRY to shut down STDIN, STDOUT, and > > STDERR? > > > > - Scott > > > > > > > >
Re: quota warning problem - Is it a bug of cyrus imap?
Quoting Joe Rhett <[EMAIL PROTECTED]>: > I doubt (I may be wrong) that the idea was to round everything -- just the > actual quota. So calculate each message normally and then round the total > to k to compare against the quota. > > Since the error of margin could be 1/2 k, with 1 million users you could > possibly end up using 500mb more space than you intended if they were all > overquota and at the top of the margin of error. I doubt this counts as a > significant problem. Currently there are two numbers stored -- the amount of the quota and the current usage. If you store the current usage rounded to kB, then your error is as much as +-512 bytes per message. Multiply by millions of messages processed, and you have a serious problem, especially if it happens that most of your messages are of similar size. Also, the quota is incrementally updated, so when a message is deleted the size is subtracted from the amount used. If you don't round the current total, then you haven't accomplished anything since the number doesn't fit in 32 bits. The easiest solution is also the clearly correct one -- just use more bits to store the quota and current usage per quota root. -- John A. Tamplin Unix System Administrator
Re: quota warning problem - Is it a bug of cyrus imap?
> >Or do you really need to give some users 5,121,133 byte quotas? Do you > >really manage your quotas down to less than 1 kilobyte, when you are giving > >the users 50 megabyte boundaries on the low side? > >Or am I missing your point entirely? > > > The problem is if you keep only the count of kBytes in a mailbox, what > do you do when you receive a message of 512 bytes? Do you not count it > at all, or do you count it as 1kB? If you keep actual bytes, you still > have the problem of it fitting in a 32-bit number, and if you round it > either way the quota will eventually be so wrong it is useless. I doubt (I may be wrong) that the idea was to round everything -- just the actual quota. So calculate each message normally and then round the total to k to compare against the quota. Since the error of margin could be 1/2 k, with 1 million users you could possibly end up using 500mb more space than you intended if they were all overquota and at the top of the margin of error. I doubt this counts as a significant problem. -- Joe Rhett Chief Geek [EMAIL PROTECTED] Isite Services, Inc.
Re: sieve script not running?
> On Mon, 07 Jul 2003 15:56:17 -0400, > Ken Murchison <[EMAIL PROTECTED]> (km) writes: km> Test your script/message combo by running the them through the km> sieve/test.c program in the distro. Oh, that reminds me of something. I generally try to compile that because it's handy for manually testing scripts (will this work with 2.2?). However, last time I tried, got this: + cd sieve + gmake test gcc -c -I. -I.. -I. -I./../lib -I./../et -I/usr/local/BerkeleyDB.4.0/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -DHAVE_CONFIG_H -I. -I. -Wall -g -O2 \ test.c test.c: In function `hashheader': test.c:70: warning: subscript has type `char' test.c: In function `parseheader': test.c:108: warning: subscript has type `char' test.c:121: warning: subscript has type `char' gcc -L/usr/local/lib -R/usr/local/lib -L/usr/local/BerkeleyDB.4.0/lib -R/usr/local/BerkeleyDB.4.0/lib -L/usr/local/lib -R/usr/local/lib -L/usr/local/lib -L/usr/local/lib -o test \ test.o libsieve.a ../et/libcom_err.a ../lib/libcyrus.a Undefined first referenced symbol in file shutdown../lib/libcyrus.a(util.o) ld: fatal: Symbol referencing errors. No output written to test collect2: ld returned 1 exit status gmake: *** [test] Error 1 This is on Solaris 8 with gcc-3.2.3. -- Amos
Re: Quota.
> > How about just "over quota in " where xxx is the quota root? Since > > this matches the mailbox name they are over quota in, it will make sense to > > the user and still be specific for debugging. > > This isn't perfect either since it is really the entire mailbox hierarchy under the > quota root that is over quota.For example, if you set a quota root on the inbox > and then the user fills up a subfolder of inbox, they may be over quota with no > messages in their inbox at all. If the error message reported is "over quota in > user.joesmith" or "over quota in INBOX", they are still going to call the help > desk.Maybe it should be something like, "over quota in INBOX or a subfolder" Most people will get the idea that subfolders could be the culprit. That's going to generate less helpdesk problems than a word someone doesn't know. ...Having had to fix many error messages of my own that confused me, even though I wrote them to be specific about the problem. I ended up giving up and using ID#s so that people just reported the ID# and didn't write us confused about the text. -- Joe Rhett Chief Geek [EMAIL PROTECTED] Isite Services, Inc.
Re: Sieve with Spamassassin && virus checking mechanisms?
James Pattie <[EMAIL PROTECTED]> writes:
> foobar wrote:
>> Hi,
>>
>> Is this (see subject) possible in anyway per account basis in sieve? ( I
>> don't remember if there was any proper plugin-support in sieve (haven't
>> investigated the code too much ).
>>
>> Thing what I done was when I didn't invent anything else and was lazy to
>> read the code:
>>
>> MTA lmtp-> sa_lmtpd (pre-loaded spamassassin-instance which can be re-used
>> (better than that idiotic pipe-wrapper) lmtp-> MDA.
>>
>> by tweakin transports, there is sa.foo.bar which destination is
>> lmtp:where_sa_lmtpd_is and every user which wants sa-processed mail
>> inserts forward [EMAIL PROTECTED] and it goes thru sa_lmtpd to cyrus's
>> lmtpd. That sa_lmtpd is my written perl-daemon which re-uses
>> checker-instances.
>>
>> So,
>> Is there any better way to do this?
>>
>> ++Titus
>>
>
> Check out MailScanner (http://www.mailscanner.info) for a Virus/Spam mail
> filtering product that plugs into the sendmail/exim/whatever flow and uses
> SpamAssassin for it's main spam checking/marking.
If you're using postfix, amavisd-new is quite nice. It does single
spam scan per message, regardless of numberrecipients and allows for
SQL-based storage of SA preferences.
> I use it to deliver to my cyrus server and just wrote a sieve rule to move any
> emails where the subject starts with {SPAM?} (the default in MailScanner) to my
> SPAM folder. There are lots of other stuff you can do with it also. ;)
We have a web interface that allows for the simple installation of
predefined rules for filter and delete spam. For advanced stuff, we
use standard Sieve scripts.
--
Ted Cabeen http://www.pobox.com/~secabeen[EMAIL PROTECTED]
Check Website or Keyserver for PGP/GPG Key BA0349D2 [EMAIL PROTECTED]
"I have taken all knowledge to be my province." -F. Bacon [EMAIL PROTECTED]
"Human kind cannot bear very much reality."-T.S.Eliot[EMAIL PROTECTED]
Re: Quota.
Joe Rhett wrote:
> > > a quota warning message from the Trash mailbox.Since the IMAP alert does
> > > not specify the mailbox that the quota warning applies to, the user assumes
> > > that it is the inbox and continues to try and delete messages until they go
> .. ..
> > Ok, so maybe it makes sense to change the message to "over quota in
> > quotaroot x." This is definately a reasonable change.
> .. ..
> > I'll file a bug on amending the quota warnings to include the mailbox name
> > (of course, this only helps if they ever select the mailbox).
>
> Um, can we not use "quotaroot" in the message. Guaranteed to get helpdesk
> calls on a word that no standard user knows.
>
> How about just "over quota in " where xxx is the quota root? Since
> this matches the mailbox name they are over quota in, it will make sense to
> the user and still be specific for debugging.
>
This isn't perfect either since it is really the entire mailbox hierarchy under the
quota root that is over quota.For example, if you set a quota root on the inbox
and then the user fills up a subfolder of inbox, they may be over quota with no
messages in their inbox at all. If the error message reported is "over quota in
user.joesmith" or "over quota in INBOX", they are still going to call the help
desk.Maybe it should be something like, "over quota in INBOX or a subfolder"
For my own personal quota problems, I finally gave up and against Rob's better
judgement, I removed the quota enforcement on COPY to any mailbox whose name
contains ".Trash". I put a separate cron script in place to email me if it finds
any users who are at more than 200% of there quota to catch any malicious users.
This seems to be working well so far, although it is a kluge with security risks.
diff index.c index.c.org
1220,1228c1220
< /* next lines changed to allow copy to Trash when usr over quota */
< /* jwidera jwade 6/27/03 lets users "move to Trash" when over quota */
<
< if ( strstr(name,".Trash") ) {
r = append_setup(&append_mailbox, name, MAILBOX_FORMAT_NORMAL,
1230d1221
< }
Enjoy,
John
Re: sieve vacation problems
Not sure if this applies, but we received similar problem in 2.0.16 with qmail until we modified lmtp.c to replace all instances of smbuf[2] = "<>"; with something like smbuf[2] = "[EMAIL PROTECTED]"; qmail's sendmail replacement really did not like the <> as a "From" address. Hope this helps, John Alexander Brill wrote: > I am having some problems related to sieve and its vacation module. It > just won't send out to the right recipient, but it tries to send it to > [EMAIL PROTECTED] This is what I get in my logs: > > Jul 3 10:48:25 tarkan postfix/smtpd[13027]: 15CEB3FA05: client=localhost[127.0.0.1] > Jul 3 10:48:25 tarkan postfix/cleanup[13046]: 15CEB3FA05: message-id=<[EMAIL > PROTECTED]> > Jul 3 10:48:25 tarkan postfix/smtpd[13027]: disconnect from localhost[127.0.0.1] > Jul 3 10:48:25 tarkan postfix/qmgr[14206]: 15CEB3FA05: from=<>, size=1436, nrcpt=1 > (queue active) > Jul 3 10:48:25 tarkan amavis[12936]: (12936-01) Passed, (?) -> <[EMAIL PROTECTED]>, > Message-I > D: <[EMAIL PROTECTED]> > Jul 3 10:48:25 tarkan postfix/smtp[13022]: 9215E3FB50: to=<[EMAIL PROTECTED]>, > orig_to= @unspecified-domain>, relay=127.0.0.1[127.0.0.1], delay=1, status=sent (250 2.6.0 > Ok, id=12936-01, from MTA: 250 Ok > : queued as 15CEB3FA05) > Jul 3 10:48:26 tarkan postfix/smtp[13050]: 15CEB3FA05: to=<[EMAIL PROTECTED]>, > relay=mail.onl > ine.no[148.122.161.36], delay=1, status=sent (250 KAA05768 Message accepted for > delivery) > > -- > Alexander Brill <[EMAIL PROTECTED]> > http://www.project23.no > PGP-key: http://www.nettstudio.no/pgp/alexander.brill.asc > > >Name: signature.asc >signature.asc Type: application/pgp-signature > Description: This is a digitally signed message part
Re: quota warning problem - Is it a bug of cyrus imap?
Joe Rhett wrote: On Wed, Jul 02, 2003 at 12:29:41PM -0500, Paul M Fleming wrote: Rounding error would present a problem for us and our users. My 2 cents .. quotas > 4GB are fairly rare. I know with a large student user base with 50-75Mb quotas rounding to the nearest K wouldn't be desirable. Okay, color me confused. Say your mailbox quota is 50mb. Isn't that exactly 51200k? Or do you really need to give some users 5,121,133 byte quotas? Do you really manage your quotas down to less than 1 kilobyte, when you are giving the users 50 megabyte boundaries on the low side? Or am I missing your point entirely? The problem is if you keep only the count of kBytes in a mailbox, what do you do when you receive a message of 512 bytes? Do you not count it at all, or do you count it as 1kB? If you keep actual bytes, you still have the problem of it fitting in a 32-bit number, and if you round it either way the quota will eventually be so wrong it is useless. -- John A. Tamplin Unix System Administrator Emory University, School of Public Health +1 404/727-9931
Re: quota warning problem - Is it a bug of cyrus imap?
On Wed, Jul 02, 2003 at 12:29:41PM -0500, Paul M Fleming wrote: > Rounding error would present a problem for us and our users. My 2 cents > .. quotas > 4GB are fairly rare. I know with a large student user base > with 50-75Mb quotas rounding to the nearest K wouldn't be desirable. Okay, color me confused. Say your mailbox quota is 50mb. Isn't that exactly 51200k? Or do you really need to give some users 5,121,133 byte quotas? Do you really manage your quotas down to less than 1 kilobyte, when you are giving the users 50 megabyte boundaries on the low side? Or am I missing your point entirely? -- Joe Rhett Chief Geek [EMAIL PROTECTED] Isite Services, Inc.
Re: Quota.
> > a quota warning message from the Trash mailbox.Since the IMAP alert does > > not specify the mailbox that the quota warning applies to, the user assumes > > that it is the inbox and continues to try and delete messages until they go .. .. > Ok, so maybe it makes sense to change the message to "over quota in > quotaroot x." This is definately a reasonable change. .. .. > I'll file a bug on amending the quota warnings to include the mailbox name > (of course, this only helps if they ever select the mailbox). Um, can we not use "quotaroot" in the message. Guaranteed to get helpdesk calls on a word that no standard user knows. How about just "over quota in " where xxx is the quota root? Since this matches the mailbox name they are over quota in, it will make sense to the user and still be specific for debugging. -- Joe Rhett Chief Geek [EMAIL PROTECTED] Isite Services, Inc.
Re: sieve script not running?
Test your script/message combo by running the them through the
sieve/test.c program in the distro. Once it works there, then you can
work on lmtpd/timsieved problems.
Hank Beatty wrote:
I'm working with the 2.2 version and have this sieve script:
require ["fileinto"];
if header :contains "X-Spam-Flag" "YES" {
fileinto "Junk Mail";
}
The "Junk Mail" folder does exist:
user//INBOX.Drafts@.net (\HasNoChildren)
user//INBOX.Sent@.net (\HasNoChildren)
user//INBOX.Trash@.net (\HasNoChildren)
user//mail/Drafts@.net (\HasNoChildren)
user//mail/Family@.net (\HasNoChildren)
user//mail/Junk Mail@.net (\HasNoChildren)
user//mail/Sent@.net (\HasNoChildren)
user//mail/Trash@.net (\HasNoChildren)
user/@.net (\HasChildren)
I can use sieveshell to upload and activate the script.
list
phpscript
test <- active script
imapd.conf
##
# Global info's
##
configdirectory: /var/imap
partition-default: /var/spool/imap
unixhierarchysep: yes
altnamespace: yes
imapidresponse: no
##
# Autentification & User rights
##
admins: cyrus murderbackend murderproxy
sasl_pwcheck_method: saslauthd
allowanonymouslogin: no
##
# Quota & Message size limit
##
quotawarn: 90
autocreatequota: 10240
lmtp_overquota_perm_failure: yes
defaultacl: anyone lrs
##
# Virtual Domain Support
##
virtdomains: yes
singleinstancestore: yes
duplicatesuppression: yes
foolstupidclients: yes
hashimapspool: yes
sievedir: /usr/sieve
sieveusehomedir: no
The sieve script was created in:
ls /usr/sieve/domain/R/.net/W//
default.bc phpscript.bc phpscript.script test.bc test.script
The script isn't moving any of the mail that has the spam flag set. Does
anyone have any ideas?
--
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: Logs filling with strange error
These are harmless (I could give you a technical reason if you care). Reduce you logging level from DEBUG down to something like INFO or NOTICE and these will disappear. Scott Bronson wrote: Can anyone tell me why my logs are filling with messages like these? Jul 5 17:41:08 eden cyrus/lmtpd[28993]: Could not shut down filedescriptor 0: Bad file descriptor Jul 5 17:41:08 eden cyrus/lmtpd[28993]: Could not shut down filedescriptor 1: Bad file descriptor Jul 5 17:41:08 eden cyrus/lmtpd[28993]: Could not shut down filedescriptor 2: Bad file descriptor Jul 5 17:41:09 eden cyrus/imapd[28983]: Could not shut down filedescriptor 0: Bad file descriptor Jul 5 17:41:09 eden cyrus/imapd[28983]: Could not shut down filedescriptor 1: Bad file descriptor Jul 5 17:41:09 eden cyrus/imapd[28983]: Could not shut down filedescriptor 2: Bad file descriptor Why would cyrus even TRY to shut down STDIN, STDOUT, and STDERR? - Scott -- 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
Logs filling with strange error
Can anyone tell me why my logs are filling with messages like these? Jul 5 17:41:08 eden cyrus/lmtpd[28993]: Could not shut down filedescriptor 0: Bad file descriptor Jul 5 17:41:08 eden cyrus/lmtpd[28993]: Could not shut down filedescriptor 1: Bad file descriptor Jul 5 17:41:08 eden cyrus/lmtpd[28993]: Could not shut down filedescriptor 2: Bad file descriptor Jul 5 17:41:09 eden cyrus/imapd[28983]: Could not shut down filedescriptor 0: Bad file descriptor Jul 5 17:41:09 eden cyrus/imapd[28983]: Could not shut down filedescriptor 1: Bad file descriptor Jul 5 17:41:09 eden cyrus/imapd[28983]: Could not shut down filedescriptor 2: Bad file descriptor Why would cyrus even TRY to shut down STDIN, STDOUT, and STDERR? - Scott
sieve script not running?
I'm working with the 2.2 version and have this sieve script:
require ["fileinto"];
if header :contains "X-Spam-Flag" "YES" {
fileinto "Junk Mail";
}
The "Junk Mail" folder does exist:
user//INBOX.Drafts@.net (\HasNoChildren)
user//INBOX.Sent@.net (\HasNoChildren)
user//INBOX.Trash@.net (\HasNoChildren)
user//mail/Drafts@.net (\HasNoChildren)
user//mail/Family@.net (\HasNoChildren)
user//mail/Junk Mail@.net (\HasNoChildren)
user//mail/Sent@.net (\HasNoChildren)
user//mail/Trash@.net (\HasNoChildren)
user/@.net (\HasChildren)
I can use sieveshell to upload and activate the script.
> list
phpscript
test <- active script
imapd.conf
##
# Global info's
##
configdirectory: /var/imap
partition-default: /var/spool/imap
unixhierarchysep: yes
altnamespace: yes
imapidresponse: no
##
# Autentification & User rights
##
admins: cyrus murderbackend murderproxy
sasl_pwcheck_method: saslauthd
allowanonymouslogin: no
##
# Quota & Message size limit
##
quotawarn: 90
autocreatequota: 10240
lmtp_overquota_perm_failure: yes
defaultacl: anyone lrs
##
# Virtual Domain Support
##
virtdomains: yes
singleinstancestore: yes
duplicatesuppression: yes
foolstupidclients: yes
hashimapspool: yes
sievedir: /usr/sieve
sieveusehomedir: no
The sieve script was created in:
ls /usr/sieve/domain/R/.net/W//
default.bc phpscript.bc phpscript.script test.bc test.script
The script isn't moving any of the mail that has the spam flag set. Does
anyone have any ideas?
--
Hank Beatty <[EMAIL PROTECTED]>
Re: APPEND vs RFC2822 vs STD0011
Edward Reid wrote: The mail provider (MX) for my domain, fastmail.fm, runs cyrus. I use Eudora (for Mac, v5.2), mostly in POP mode, but I use some IMAP features too. In particular, some of my filters copy incoming (POP) messages to an IMAP mailbox at fastmail.fm. That's where the problems start. Some of these incoming messages contain NULs or bare CR or LF. Yes, the sender is broken as far as RFC2822 is concerned, but the messages get through anyway. And the messages are valid RFC822/STD0011 format. When Eudora tries to copy these (APPEND them) to the IMAP mailbox, cyrus (at fastmail.fm) returns an error. I could live with an occasional copy failure, but the worst part is that when Eudora gets the server error, it thinks it's a terrible problem and throws up a dialog box and ceases all processing. Since I (like many people) depend on Eudora cleaning up my mailbox and doing other things with incoming mail automatically when I'm not at my desk, this gets to be a serious problem. That's what sieve is for -- do it in the server and you won't have to rely on a particular client doing it for you. So I started reading RFC3501 to find the reason. I assumed that I'd find a good reason that I could quote to Eudora support, telling them why Eudora has to clean up the message before storing it in an IMAP mailbox. But I didn't find that. What I found -- under the APPEND command (section 6.3.11) -- is : The APPEND command appends the literal argument as a new message : to the end of the specified destination mailbox. This argument SHOULD : be in the format of an [RFC-2822] message. Note well: that's "SHOULD", not "MUST". This is important. RFC2119 gives the meaning of SHOULD: : This word [...] mean[s] that there may exist valid reasons in : particular circumstances to ignore a particular item [...] So based on my reading of the RFC, it's the client's choice: it should normally append RFC2822 messages, but if it has a valid reason, it's allowed to append something that's not RFC2822. Now, IMAP mailboxes are intended for email -- "Internet message format" or "Internet text messages" in the RFC language -- and so it would be hard to make a case for storing anything that's not such a message. But RFC822 messages are still rampant on the Internet. In fact, as I understand it, although RFC2822 has obsoleted RFC822, STD0011 (which is identical to RFC822) is still a standard and has not yet been superseded. And it certainly seems to me that making a copy of an existing message is a "valid reason" for copying it intact, without the modifications needed to force it to conform to the stricter format of RFC2822. Since RFC3501 leaves this decision up to the client, it follows that cyrus is broken when it refuses the message. If RFC3501 said "MUST", then I'd say it's Eudora's responsibility to fix the message before attempting an APPEND. But the RFC says "SHOULD". Is there any good argument for cyrus' action? If there is, I'd be happy to take it to Eudora and push them to fix Eudora. Eudora's not exactly known for its stellar IMAP support, and I'd like them to improve this. I've shoved the RFCs in their face plenty of times in the past. But in this case, my reading of the RFCs is that Eudora's APPEND action is defensible and cyrus' action is incorrect. I disagree - it sounds like it would be defensible if Cyrus supported storing such messages even though it is clearly recommended against by the standard. If Eudora insists on storing such messages, it should be prepared to deal with a server that is unwilling to do so. If you allow the IMAP server to store arbitrary data, it makes the other functions much more difficult -- if it can't assume there is a message-id that is globally unique, it has to create its own unique key for a message. Searching based on header fields is more problematic since you can't assume there is even a header or that if there is one that it's value corresponds to anything you might expect (ie, character set, line length, and other issues). Allowing null characters in particular is problematic for any code that uses null-terminated strings for messages or parts of messages, and would require changing the code everywhere to use and pass the length of all the strings instead. I don't know if there is a technical reason behind not supporting bare newlines or not. As far as STD0011 not being obsoleted, there are plenty of RFCs etc. that are not obsoleted by something but are still not best current practice. Clearly if the RFC it has been based on has been obsoleted, the STD should be updated as well. -- John A. Tamplin Unix System Administrator Emory University, School of Public Health +1 404/727-9931
Re: vdac - web administartion tool for Postfix+Cyrus
I would like to take the part of your code that allows editing of user preferences for amavisd and modify it to work as a plugin for SquirrelMail (http://www.squirrelmail.org) webmail program. As an ISP, we are content, so far, with the mod_perl-based account administration software, freeside (http://www.sisd.com/freeside), because it conveniently lets us modify a user's other account settings (personal web space, ftp access, dial-up permissions, etc.) at the same time that we make any changes to their email account. -- Scott Langley [EMAIL PROTECTED] Systems Administrator Rural Network Services Manuele writes: Hello you all, this mail is to inform those intrested that I've started a new project - so far named 'vdac' - intended to become a web based administration tool for Postfix+Cyrus. The project is still in early stage, but already working for my mailserver. It currently supports and follows the criteria below: - Mainly it supposes a postfix/Cyrus installation, both with mysql support. - Two types of users: administrator, domain master. Administators have full right on the whole thing; domain masters have full rights on assigned domains, they can create cyrus users, build virtual tables. - Domain masters limits are based on the amount of (cyrus-)users they can create and on the amount of external aliases they can put in the virtual table. Quotas they can assign can be limited as well. - It fully supports Cyrus and Amavisd(with per user preferences) so far. Very next step will be support for IMP (expecially cyrus-user preferences) Next - very soon - steps are: support for secondary MX administration, integrity and sanity checks, ghost domains and canonical tables (for Administrators only). The whole thing is written - so far - in only php, but things may change. I'm writing this mail in order to get - eventual - feedbacks and requests, mainly, but I am also trying to see if someone is intrested in helping me out. Specifically to this list: I am searching someone that might want to give me a hand to cope with the differences between releases of cyrus, as I am only using 2.1.x versions so far and will need some help to make the thinh work with 2.2.x The whole thing WILL be open source in a next future, but the first releases - if someone will want to download them and try them :) - will be given out in 'zend-compiled' form. The whole idea came out, of course, from Webcyradm, even thou this has already become something very different. Screenshots are available at: http://vdac.cappelleri.net/shots/ Access to the system can be given upon request, if intrested in this early stage developement. No demo accounts exist, since the only copy of it is running live with my domains on :) Thank you for your attention. - This mail sent through IMP: http://horde.org/imp/
APPEND vs RFC2822 vs STD0011
The mail provider (MX) for my domain, fastmail.fm, runs cyrus. I use Eudora (for Mac, v5.2), mostly in POP mode, but I use some IMAP features too. In particular, some of my filters copy incoming (POP) messages to an IMAP mailbox at fastmail.fm. That's where the problems start. Some of these incoming messages contain NULs or bare CR or LF. Yes, the sender is broken as far as RFC2822 is concerned, but the messages get through anyway. And the messages are valid RFC822/STD0011 format. When Eudora tries to copy these (APPEND them) to the IMAP mailbox, cyrus (at fastmail.fm) returns an error. I could live with an occasional copy failure, but the worst part is that when Eudora gets the server error, it thinks it's a terrible problem and throws up a dialog box and ceases all processing. Since I (like many people) depend on Eudora cleaning up my mailbox and doing other things with incoming mail automatically when I'm not at my desk, this gets to be a serious problem. So I started reading RFC3501 to find the reason. I assumed that I'd find a good reason that I could quote to Eudora support, telling them why Eudora has to clean up the message before storing it in an IMAP mailbox. But I didn't find that. What I found -- under the APPEND command (section 6.3.11) -- is : The APPEND command appends the literal argument as a new message : to the end of the specified destination mailbox. This argument SHOULD : be in the format of an [RFC-2822] message. Note well: that's "SHOULD", not "MUST". This is important. RFC2119 gives the meaning of SHOULD: : This word [...] mean[s] that there may exist valid reasons in : particular circumstances to ignore a particular item [...] So based on my reading of the RFC, it's the client's choice: it should normally append RFC2822 messages, but if it has a valid reason, it's allowed to append something that's not RFC2822. Now, IMAP mailboxes are intended for email -- "Internet message format" or "Internet text messages" in the RFC language -- and so it would be hard to make a case for storing anything that's not such a message. But RFC822 messages are still rampant on the Internet. In fact, as I understand it, although RFC2822 has obsoleted RFC822, STD0011 (which is identical to RFC822) is still a standard and has not yet been superseded. And it certainly seems to me that making a copy of an existing message is a "valid reason" for copying it intact, without the modifications needed to force it to conform to the stricter format of RFC2822. Since RFC3501 leaves this decision up to the client, it follows that cyrus is broken when it refuses the message. If RFC3501 said "MUST", then I'd say it's Eudora's responsibility to fix the message before attempting an APPEND. But the RFC says "SHOULD". Is there any good argument for cyrus' action? If there is, I'd be happy to take it to Eudora and push them to fix Eudora. Eudora's not exactly known for its stellar IMAP support, and I'd like them to improve this. I've shoved the RFCs in their face plenty of times in the past. But in this case, my reading of the RFCs is that Eudora's APPEND action is defensible and cyrus' action is incorrect. I'm very interested in hearing the cases for both sides. Edward
[no subject]
Hello you all, this mail is to inform those intrested that I've started a new project - so far named 'vdac' - intended to become a web based administration tool for Postfix+Cyrus. The project is still in early stage, but already working for my mailserver. It currently supports and follows the criteria below: - Mainly it supposes a postfix/Cyrus installation, both with mysql support. - Two types of users: administrator, domain master. Administators have full right on the whole thing; domain masters have full rights on assigned domains, they can create cyrus users, build virtual tables. - Domain masters limits are based on the amount of (cyrus-)users they can create and on the amount of external aliases they can put in the virtual table. Quotas they can assign can be limited as well. - It fully supports Cyrus and Amavisd(with per user preferences) so far. Very next step will be support for IMP (expecially cyrus-user preferences) Next - very soon - steps are: support for secondary MX administration, integrity and sanity checks, ghost domains and canonical tables (for Administrators only). The whole thing is written - so far - in only php, but things may change. I'm writing this mail in order to get - eventual - feedbacks and requests, mainly, but I am also trying to see if someone is intrested in helping me out. Specifically to this list: I am searching someone that might want to give me a hand to cope with the differences between releases of cyrus, as I am only using 2.1.x versions so far and will need some help to make the thinh work with 2.2.x The whole thing WILL be open source in a next future, but the first releases - if someone will want to download them and try them :) - will be given out in 'zend-compiled' form. The whole idea came out, of course, from Webcyradm, even thou this has already become something very different. Screenshots are available at: http://vdac.cappelleri.net/shots/ Access to the system can be given upon request, if intrested in this early stage developement. No demo accounts exist, since the only copy of it is running live with my domains on :) Thank you for your attention. - This mail sent through IMP: http://horde.org/imp/
Re: Sharing Folders in Mozilla Mail
Hi, Wouldn't the correct thing to do here be to vote for a Mozilla bug? http://bugzilla.mozilla.org/show_bug.cgi?id=207628 I actually think that 207628 should die as a duplicate of 135977 ;-) (opened a whole year before) http://bugzilla.mozilla.org/show_bug.cgi?id=135977 No problem! I wrote the email before I saw someone else make the same comment later in the thread (I've been on holiday). But: Everybody please vote! If someone has the time, the same bug should be filed against kmail,balsa and evolution as well. Tarjei Bye
Re: Sharing Folders in Mozilla Mail
Tarjei Huse wrote: Wouldn't the correct thing to do here be to vote for a Mozilla bug? http://bugzilla.mozilla.org/show_bug.cgi?id=207628 I actually think that 207628 should die as a duplicate of 135977 ;-) (opened a whole year before) http://bugzilla.mozilla.org/show_bug.cgi?id=135977 Bye -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 Fax +34 93 5883007
