similar to: Detecting duplicate messages with sieve

Hi there, I'm using Dovecot 2.0.9-1 under Arch Linux. Currently, I have Maildir configured, and I move all my emails into dovecot by using this sequence: 1) cron starts fetchmail periodically under user manfred to collect my mails from various email accounts. 2) In ~/.fetchmailrc I have configured /usr/bin/maildrop as MDA. 3) In ~/.mailfilter (used by maildrop) I have extensive filtering in

I need some advice about replacing maildrop with the Dovecot LDA. I need to replicate a setup that uses postfix+maildrop+spamassassin. We'll be using Dovecot 1rc13. In the current setup, maildrop reads a file called .mailfilter in each user's folder, then call spamassassin according to the user's preferences. The file is simple, and looks like this -- if ( $SIZE > 20971520 ) {

Hello list, Is there a way to call a spam filter in dovecot-lda like maildrop uses the xfilter command within the .mailfilter file to do the same? Eric

I'm using maildrop to filter mail like: xfilter "/usr/bin/spamc" xfilter "/usr/bin/bogofilter -ep" I want to change to deliver (so I can use sieve) but can deliver do this?

Dear list member, does anybody have a script which can convert maildrop filter to sive filter? BR Aleks

Hi! My plea to readers: =================== Pls., people who only want strictly technical issues to read, and frown at any broader context regardless how intrinsically related, but not strictly technically related, it might be, skip all the way, all the way to, search for exact words: "strictly technical" or visually, find two lines of sole "===" characters. Thank you!

Dear Listmember. I resend this with different Subject so that the spamfilter does not drop the mail, I hope ;-) I try to migrate from my current courier-mta setup fo postfix dovecot setup. I use the following scirpt to filter to the destination mailbox. ### /var/vmail/none.at/al/.dovecot.sieve # from http://wiki.dovecot.org/LDA/Sieve require ["fileinto", "envelope",

hi all, i'm moving from a maildrop+courier setup to lda(sieve)+dovecot setup. with maildrop i had a global filter for all the users, so i could filter and archive into the spam folder spam tagged emails for users without custom filters, including them if they exist: LOGNAME=tolower($LOGNAME) `test -e $LOGNAME` if ( $RETURNCODE != 0 ) { `maildirmake $LOGNAME` `maildirmake

I'm currently using maildrop to do delivery, because I like to use it's xfilter to pipe through spamc. I don't see a similar option for dovecot's deliver. Is there something? It would be nice to use deliver, since I use dovecot for reading mail.

I'm using maildrop for delivery, because I want to filter through spamassassin before delivery. Maildrop makes that trivial. It seems deliver can pipe (one way) to a command, but what is needed is to pipe: deliver -> spamd -> deliver which is what the maildrop xfilter does.

I'd like to be able to deliver certain mail as 'read' from procmail. My procmail rules call deliver with -m to directly to inject filtered mail to maildir based directories. I like to keep copies of mail I've sent by cc'ing it to myself and using procmail to filter and store copies in the appropriate directory. I cannot seem to find a way of delivering cc'd mail from

Hi, what is the preferd way to configure/start mongrel? [ ] with Mongrel::Configurator => HttpServer [ ] @var = HttpServer.new(...) @var.run I ask because the only debug methode i have found was in Mongrel::Configurator ;-) @Zed: are you also subscribed on nitro list?! regards Alex

Greetings all, newbie to CentOS here. Also newbie to 64 bit installs. Package Manager problem: I found a yumex, which is not part of the 64 bit install, but it wants a way older version of python-2.4 whereas we have 2.6.6-something after the post install upgrade. 1st Question: Is there anything that can be done about this? Or is there something better, like a 64 bit synaptic to replace

Use the version struct in inspect_fs to hold the version of a filesystem, adapting the inspection code to that. Also, move the parts of the version parsing to helper functions of the version struct, so common bits like parsing "X.Y" or "X" version strings is done only once. --- v2 changes: - adapt to v2 changes in patch #1 src/guestfs-internal.h | 8 +-

Hello! Today I''m announcing a "soft but official" release of Mongrel 0.3.13.4 for the Unix fans in the crowd. It''s been running stable for quite some time now for many people, and should be great for nearly everyone. You can read the announce at: http://mongrel.rubyforge.org/ This release includes new versions of mongrel_upload_progress and mongrel_cluster.

I am using mongrel_cluster with mod_proxy_balancer and would like to enable compression (assuming it improves throughtput) and limit file size upload. I configured mod_deflate and LimitRequestSize in Apache, but in my trials looks like the proxied calls bypass those directives (the conf goes below). Is there a way to get this? -- fxn # Adapt this .example locally, as usual. # # To be

I''m using a cluster of mongrels behind an apache 1.3 proxy pass. I''ve been passing the request to pen, which in turn balances the cluster of mongrels. Now, I''d like to be able to use a different server to send the static files created by the rails application, so I tried to replace pen with nginx. Everything seems to work fine except the environment variable REMOTE_ADDR.

We're considering a move from Courier to Dovecot.? So far, looks like it's not too bad, but the most challenging obstacle is what to do about our local delivery.? Factors: 1. we use a lot of maildrop "features" that are impossible in sieve without piping to an external program (would rather not re-write our working maildrop scripts in another language) 2. would love to try

Hi folks, Getting much much much closer to the 1.0 release. I have some documentation to work on tonight, and I need to go through the patch queue one more time, but I''ve put up another pre-release for people to test. What this pre-release does is pull together the various patches, monkey patching, and alternatives that make Mongrel either faster or more stable. It is also the start

Hello all, turns out i'm having a bad R week. I am at my wits end with a function that I am trying to write. When I run the lines of code outside of a function, I get the desired output. When I wrap the lines of code into a function it doesn't work as expected. Not sure what is going on here. I suspected that the syntax of the if statement with the for loop was the culprit, but when I