Re: Creating sieve script with image attachements
Hi,
you need
require [fileinto, body]
and Cyrus 2.3.0 or greater
Quoting Adam D [EMAIL PROTECTED]:
Michael Menge wrote:
Hi,
Content-Type filtering is done by the sieve body extenssion
http://www.ietf.org/internet-drafts/draft-ietf-sieve-body-04.txt
You want to have a look at the examples unter 4.2
---
if body :content audio/mp3 :contains {
fileinto jukebox;
}
--
OK, I am understanding that the Content-Type is not a header; it is
part of the body (MIME) in which sieve can not work with. So, that
makes sense with the above script when it uses 'body' than 'header'.
Now, knowing and understanding better that it is a MIME part
message can sieve still put out the content-type of 'image/gif' from
the body?
When creating the script and since I use websieve to make managing
scripts for sieve a bit easier this is the custom rule set where I
can put my raw script but when I deviate from using 'header' to
'body' and 'contains' to 'content' it gives me this error:
Updatesieve Error: Cant' update script...
Returned Error: Putting script: script errors: line 21: syntax
error, unexpected $undefined
You can click on your browser's Back button to go back and try your
entry again.
With this script:
if body :content image/gif {
fileinto system.2-mail.missed-spam;
}
I have gone in to the default script and changed it manually in the
sieve directory but when I do it throws all the other scripts off
created by websieve. Before I used websieve I used to write all the
scripts out by hand and but this way is much easier if the scripts
work. I don't know if this turns out to be a websieve issue and
should be addressed on that mailing list or can I continue with the
thread on this list?
Much thanks from everyone,
-Adam
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
M.Menge Tel.: (49) 7071/29-70316
Universitaet Tuebingen Fax.: (49) 7071/29-5912
Zentrum fuer Datenverarbeitung mail:
[EMAIL PROTECTED]
Waechterstrasse 76
72074 Tuebingen
smime.p7s
Description: S/MIME krytographische Unterschrift
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Message contains invalid header
Hello, from time to time we are getting this message in our exim logs: LMTP error after end of data: 554 5.6.0 Message contains invalid header I have also experienced this error while I'm syncing emails from an old server to our new cyrus mailserver. I have munge8bit: false in my imapd.conf and reject8bit is set to false by default. Which headers is cyrus complaining about? I cannot change this world where clients like Notus Notes are sending invalid emails, but simply refusing these mails is a bad choice. And we also have a lot of emails we received in the old setup and I wouldn't know how to explain to our users, that they cannot access these messages any more. How can I make cyrus less strict? Regards Marten Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Message contains invalid header
Marten Lehmann wrote:
Hello,
from time to time we are getting this message in our exim logs:
LMTP error after end of data: 554 5.6.0 Message contains invalid header
I have also experienced this error while I'm syncing emails from an
old server to our new cyrus mailserver. I have
munge8bit: false
in my imapd.conf and reject8bit is set to false by default. Which
headers is cyrus complaining about? I cannot change this world where
clients like Notus Notes are sending invalid emails, but simply
refusing these mails is a bad choice. And we also have a lot of emails
we received in the old setup and I wouldn't know how to explain to our
users, that they cannot access these messages any more.
How can I make cyrus less strict?
If it's mails from the broken Lotus Notes client that's the problem (and
they're the only ones we saw here), it's caused by a null Message-ID
header; just have your SMTP server remove those. LMTP will generate a
new, valid message-id when the message is delivered.
in Exim:
headers_remove = ${if match{$h_Message-ID:}{\N^\s*$\N} {Message-ID} {} }
cheers,
Adam.
--
Adam Stephens
Network Specialist - Email DNS
[EMAIL PROTECTED]
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Message contains invalid header
Marten Lehmann wrote:
Hello,
from time to time we are getting this message in our exim logs:
LMTP error after end of data: 554 5.6.0 Message contains invalid header
I have also experienced this error while I'm syncing emails from an
old server to our new cyrus mailserver. I have
munge8bit: false
in my imapd.conf and reject8bit is set to false by default. Which
headers is cyrus complaining about? I cannot change this world where
clients like Notus Notes are sending invalid emails, but simply
refusing these mails is a bad choice. And we also have a lot of emails
we received in the old setup and I wouldn't know how to explain to our
users, that they cannot access these messages any more.
How can I make cyrus less strict?
If it's mails from the broken Lotus Notes client that's the problem (and
they're the only ones we saw here), it's caused by a null Message-ID
header; just have your SMTP server remove those. LMTP will generate a
new, valid message-id when the message is delivered.
in Exim:
headers_remove = ${if match{$h_Message-ID:}{\N^\s*$\N} {Message-ID} {} }
and with postfix you can try this in header_checks:
# Remove empty Message-ID headers from broken Notes implementation
/^Message-ID:[[:space:]]*$/ IGNORE
Simon
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Message contains invalid header
Hello, sorry, but I'm not looking for a way to change anything in an email, I am looking for a way so that Cyrus doesn't check for such errors and simply ignores them. Even if I would remove the according message ids in new messages, I still have to migrate the old mailboxes and IMAP is giving me the same error on APPEND. So what should I do with all those existing messages? Why does cyrus have a problem with an empty message-id header? Or there other cases in which cyrus throws this error (like 8bit in headers)? Regards Marten Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
question on poptimeout
Hello, some of our users are grumping that they get the pop3 error: -ERR [IN-USE] Unable to lock maildrop: Mailbox is locked by POP server I know where it comes from and I understand that there must be a sort of locking for pop3. But sometimes users seem to get an authentication error and are asked by their mail clients to enter the password again. Then, when they retype they get the error. I don't know what makes the login failing in the first try (it only happens every now and then). We are using sasldb2 which doesn't do more than looking up a user in a file. I don't know what can go wrong with that, but obviously it happens from time to time. It set poptimeout: 1 but it didn't solve the problem. Is it possible to set a lower timeout? Regards Marten Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: cyradm auth failure with krb admin instances
Jukka Salmi -- info-cyrus (2006-10-24 18:46:52 +0200): Jukka Salmi -- info-cyrus (2006-10-22 16:32:58 +0200): Jukka Salmi -- info-cyrus (2006-10-22 16:23:30 +0200): Hi, I'm using Cyrus IMAP4 v2.2.13. I haven't used cyradm for some time, but today I noticed I can't log in as admin anymore because GSSAPI authentication fails. My imapd.conf contains `admins: jukka/admin'; I successfully require a TGT for jukka/admin, but authentication fails: $ cyradm --user jukka/admin --authz jukka/admin host cyradm: cannot authenticate to server with as jukka/admin The following is logged: imap[15512]: accepted connection imap[15512]: badlogin: [...] GSSAPI [SASL(-13): authentication failure: bad userid authenticated] Using a principal without a admin instance as a cyrus admin works fine. This used to work some time ago, but I can't remember when exactly... This is badly worded. I tried to say that using an /admin instance of a Kerberos principal as a cyrus admin user id used to work, but right now only non-admin instances seem to work. Any hints what could have cause this regression? Or even better how to fix it? ;-) This regression was introduced with Cyrus IMAPd v2.2.13: I just failed to reproduce the problem with v2.2.12, i.e. 2.2.12 works fine. I found the problem: for some reason I don't understand (or is it just a bug?) HAVE_GSSAPI_H is only defined if .../gssapi.h is found, but _not_ if .../gssapi/gssapi.h is found: $ ./configure [...] [...] checking gssapi.h usability... no checking gssapi.h presence... no checking for gssapi.h... no checking gssapi/gssapi.h usability... yes checking gssapi/gssapi.h presence... yes checking for gssapi/gssapi.h... yes [...] checking for gss_unwrap in -lgssapi... yes checking GSSAPI... with implementation heimdal [...] $ grep HAVE_GSSAPI_H config.h #undef HAVE_GSSAPI_H Defining HAVE_GSSAPI_H and rebuilding fixed the problem: using a principal's /admin instance as a cyrus admin now works again. I had a glance at the latest Cyrus IMAPd 2.3 sources and the problem seems to be still there. Any comments? Regards, Jukka -- bashian roulette: $ ((RANDOM%6)) || rm -rf ~ Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Too slow
Hello, I turned the mail partition now to xfs and it's terribly fast. WOW!!! did you use an ext3 partition with dir_index before? I'm just asking because we are at a similar point and need to make a decision. All benchmarks I know of don't show that XFS actually performs faster than a modern ext3. Actually, with many concurrent reads and writes, ext3 seem to perform better, but only according to benchmarks. I cannot tell from an own installation. A switch from ext3 to XFS would be a big step for us, because we have to take care for about 13,000 mailboxes. So I want to be really sure if it is the right step. Regards Marten Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: CREATE INBOX/attention: NO Invalid mailbox name
Hello, Why? If the problem is that Dovecot uses the folders below inbox, then do the migration and *THEN* enable altnamespace. Simple! :-) the problem is, that dovecot allows both: at the same level of INBOX and subfolders of INBOX. Cyrus only supports on of both at the same time. So I choosed to rename folders and it worked fine. I guess users will find their folders without problems. Regards Marten Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Too slow
On Wednesday 25 October 2006 20:20, Marten Lehmann wrote: did you use an ext3 partition with dir_index before? I'm just asking because we are at a similar point and need to make a decision. All benchmarks I know of don't show that XFS actually performs faster than a modern ext3. Actually, with many concurrent reads and writes, ext3 seem to perform better, but only according to benchmarks. I cannot tell from an own installation. A switch from ext3 to XFS would be a big step for us, because we have to take care for about 13,000 mailboxes. So I want to be really sure if it is the right step. XFS may be faster _until_ it craps out. I have had two (not one) instances of a '.' directory entry being removed from a particular directory and fsck.xfs not being able to repair it caused the need for reinstallation. Doing anything in the directory caused the FS to be unmounted due to detecting an inconsistency in the FS. This happened to my /var partition on both occasions. Granted, it happened on a laptop during a suspend resume both times, but it does not instill confidence that it is not robust enough to stand up to this, not to mention unexpected power offs and the like. Also, the XFS developers are no longer paid by SGI to do XFS from what I understand, so that's another strike. Ciao, wt -- Warren Turkal Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Too slow
I turned the mail partition now to xfs and it's terribly fast. WOW!!! did you use an ext3 partition with dir_index before? I'm just asking We've just had some experience with filesystems ourselves. Previously we've used reiserfs exclusively for the last 5 years. All up, it's been really good to us. There are two really, really important things with reiserfs though: 1. You MUST have hardware that doesn't lie about it's write cache. When the filesystem tells the device driver to sync to disk, and the disk says it's done, it must be done (http://community.livejournal.com/lj_dev/670215.html - see the Disk cache issues) 2. Your hardware must be IO reliable, it must never report any write or read IO errors at the sector level Both of these issues are really to do with your hardware and device driver. If you've got good hardware and drivers, you should never see either. I believe that every report out there with people saying reiserfs screwed my partition totally is because of one of these 2 things. In the 5 years we've been using it, we've had dozens of different kernel crashes, power lost, etc, and not one corruption due to any of it. The only corruptions we've had are due to IO errors on the external RAID device itself (RAID 6, two simultaneous failed drives, and a third drive started reporting errors which were returned as IO errors to the kernel). In this respect, IBM seem to really have gotten their SCSI hardware right. Recently, a number of new machines we got we decided to try out ext3 again with dir_index. The results have been horrible with huge server loads. Using a spare partition, we're juggling users back to reiserfs partitions. The result is significantly lower loads for the exact same user set. I'd rate the general pros/cons of *linux* filesystems as: * ext3 pros: most widely used; excellent recovery tools; full data journaling available; best in the face of flakey hardware or disk caches that lie cons: performance just isn't that good in a large active user base * reiserfs pros: performs well with large active user base configuration, full data journaling available cons: recovery tools generally work, but have been known to crash and can be slow on large partitions; large mount time (will be fixed in 2.6.19), apparently some concurrecny issues with taking the BKL * xfs pros: fast on large files, good concurrency cons: no data journaling, only meta-data; not really stable when bugs like this occur that even a xfs_repair wouldn't fix! (http://oss.sgi.com/projects/xfs/faq.html#dir2) All the other filesystems I'd label as less used, which means that it's more likely bugs to appear and wouldn't recommend for a production environment. What about zfs? It's solaris only, and I believe there's still horrible performance in the face of fsync() calls, which cyrus does a LOT of. My 2 cents. Rob Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
