timsieved error message
Hello all, I'd like to make a small suggestion: I just spent several hours tracking down an error with someone trying to upload a sieve script using the avelsieve squirrelmail plugin. The error message, as reported by timsieved file parser.c line 308 was "Did not specify script data", when in fact the problem is (and could only be at that point in the file) "Did not specify script length, or script is too big". Of course, the reason ended up being that the script exceeded the default 32k limit which I upped and resolved the issue. But really, that error text should be made more clear IMNSHO :) Thanks! Dave --- Home Page: http://asg.web.cmu.edu/cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: interesting limitation
2 level hashing would work, but I don't know if Cyrus supports that. It would most likely be trivial to implement. eg spool/s/sm/user/smith On Sat, 29 Mar 2003, Jure Pecar wrote: > > Hi all, > > Recently i was testing a 2.2 branch on linux with Veritas vxfs. I wanted to > create 20 users in the form of userN, where n is 1..20. I soon found > out that vxfs won't let me create more than 32k subdirs in one dir. > > This is clearly a limitation of the filesystem. How does other filesystems > handle this? > > The solution here is full dir hash. But, the next limit is at 26*32k users. > Is anyone actually nearing this number of users on a single box? Probably > not, but who knows what the future may bring ... > > > -- > > Jure Pecar > > >
RE: deliver problems
One thing you can try is to log what procmail does with a directive like this: LOGFILE=/var/log/mail/procmail.log which might give you some useful information. You could also try delivering the mail to a standard mbox file and examining it to see if theres any other bogus headers that might be causing cyrus to choke. Good luck. Dave On Thu, 20 Feb 2003, James Miller wrote: > Thank you for the suggestion. I added the formail line to the .procmailrc, > but I still am not getting an of the messages delivered to the mailbox. I'm > not even seeing procmail even calling /usr/cyrus/deliver in my mail logs (we > use procmail for alot of other things -- mainly spam checking). I'm sure > I'm missing something stupid. Is there anything else that I could be > missing? > > > Thanks again =) > Jim > > > -Original Message- > From: Dave O [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 20, 2003 4:22 PM > To: James Miller > Subject: Re: deliver problems > > > > Hi, I just answered another guy a few days ago with the same exact > problem. Put this at the top of your procmailrc: > > :0hfw > | /usr/bin/formail -I 'From ' > > the problem is the "From ..." header added by your MTA. > > Dave > > On Thu, 20 Feb 2003, James Miller wrote: > > > Hi all, > > > > I'm having trouble using /usr/cyrus/deliver for delivering mail to > > mailstore.And am hoping someone else has run into this problem before. > > I'm sure it's something stupid on my part. While testing, I'm using > > procmail to deliver new messages. Here's the .procmailrc receipt I'm > using: > > -- > > LOGNAME = $1 > > EXTENSION = $2 > > > > :0 w > > * EXTENSION ?? . > > | /usr/cyrus/bin/deliver -a "$LOGNAME" -e -q -m "$EXTENSTION" -- > "$LOGNAME" > > > > # If no Extension we try this > > :0 wE > > | /usr/cyrus/bin/deliver -a "$LOGNAME" -e -q -- "$LOGNAME" > > > > # Whichever one we tried, failed > > EXITCODE = $? > > HOST > > --- > > > > When I send a message it gets bounced back with the following errors: > > > > The original message was received at Thu, 20 Feb 2003 11:44:13 -0600 > > from NTAdmin.simutronics.com [198.83.204.82] > > > >- The following addresses had permanent fatal errors - > > "|/usr/cyrus/bin/deliver -m user.admin admin" > > (reason: Data format error) > > (expanded from: <[EMAIL PROTECTED]>) > > > >- Transcript of session follows - > > admin+user.admin: Message contains invalid header > > 501 5.6.0 Data format error > > > > The original message was received at Thu, 20 Feb 2003 11:40:21 -0600 > > from NTAdmin.simutronics.com [198.83.204.82] > > > >- The following addresses had permanent fatal errors - > > "|/usr/cyrus/bin/deliver -m user.admin admin > > (reason: Data format error) > > (expanded from: <[EMAIL PROTECTED]>) > > > >- Transcript of session follows - > > 553 5.0.0 "|/usr/cyrus/bin/deliver -m user.admin admin... Unbalanced '"' > > admin+user.admin: Message contains invalid header > > 501 5.6.0 Data format error > > > > > > > > > > > > >
Re: EXITCODE=65 from deliver called thru procmail?
Chances are, this error is caused by the "From ..." line added by your MTA. You can either configure the MTA not to add this line, or you can add this to the top of your procmailrc: :0hfw | /usr/bin/formail -I "From " hope that helps :) On Mon, 17 Feb 2003, Louis LeBlanc wrote: > Hey all. I'm having some trouble with delivery using a new > sendmail/procmail/deliver scheme. > > Everything seems to go fine up to the call to deliver. procmail is > executing as the recipient uid (running in explicit delivery mode) and > calling deliver at the end of processing. > > This is how deliver is being called from ~/.procmailrc: > > :0 w > * FOLDER ?? . > | /usr/local/cyrus/bin/deliver -q -m "$FOLDER" -- "$LOGNAME" > > # Only if there was no extension do we try this > :0 wE > | /usr/local/cyrus/bin/deliver -q -- "$LOGNAME" > > # Whichever one we tried, failed > EXITCODE = $? > HOST > > > This is what shows up in the procmail log: > > procmail: Executing "/usr/local/cyrus/bin/deliver,-q,--,leblanc" > procmail: Program failure (65) of "/usr/local/cyrus/bin/deliver" > procmail: Assigning "LASTFOLDER=/usr/local/cyrus/bin/deliver -q -- leblanc" > procmail: Assigning "EXITCODE=65" > procmail: Assigning "HOST" > > > I vaguely remember seeing exitcode discussed here, but I'm not sure. > It isn't discussed in the deliver manpage at all either. > > I don't think it can have anything to do with being called as the > recipient, because I've run tests where I save a message to a flat > file then pipe it directly into the call as above. No problems. > > Anyone have any ideas? > > TIA > Lou > -- > Louis LeBlanc [EMAIL PROTECTED] > Fully Funded Hobbyist, KeySlapper Extrordinaire :) > http://www.keyslapper.org ԿԬ > > Reisner's Rule of Conceptual Inertia: > If you think big enough, you'll never have to do it. > > >
Re: Impossible to move messages to trash when overquota
On Thu, 2 Jan 2003, Scott Russell wrote: > On Thu, Jan 02, 2003 at 10:17:28AM -, [EMAIL PROTECTED] wrote: > > > This has come up before. The move command is actually a two step > > > operation where the file is first copied to the 'Trash' folder and then > > > deleted from the source directory. The copy operation fails > > > because the user is over quota. > > > > > > > Since the mailbox is all on the same filesystem, why not use hard links to > > move the file when the move command is used, like sendmail does, instead > > of copy and delete ? It would give better performance, and take care of > > the overquota problem. > > There is no 'move' command in the IMAP RFC iirc. A 'move' operation is > just client side semantics for 'copy and then delete'. > Then why not use the hard links (essentially the same as SIS delivery) for IMAP copy?
Re: Sieve not processing
Note that if you use a -m with the deliver program (as invoked from sendmail, procmail, etc), it appears to bypass Sieve. Hope that helps.. On Tue, 12 Nov 2002 [EMAIL PROTECTED] wrote: > I used the smartsieve application from source forge to create a vacation script, > only nothing happens. :( I don't see anything in the logs, etc >
Re: sieveshell says "sasl mech list empty"
I can't say I know enough about SASL to know why, but I needed the "LOGIN" mech to make sieve work on my system. HTH Dave On Mon, 14 Oct 2002, Nick Fisher wrote: > Hello people, > I'm having a problem with sieveshell. When I run 'sieveshell localhost' > I get: > connecting to localhost > unable to connect to server: sasl mech list empty at /usr/bin/sieveshell > line 175. [...] > > sasl_mech_list: PLAIN >
