Re: Qmail and Procmail
* Alexander Meis [EMAIL PROTECTED] [010406 12:21]: i Try to setup qmail with maildirs and Procmail Mailfiltering. Ok Qmail works. How do i enable the filtering to of Procmail to the ariving Mails ? I found nothing in the manual. Tip 1: Don't start new threads by replying to unrelated messages. Tip 2: If possible, use maildrop instead of procmail. www.courier-mta.org Tip 3: Put the following into your .qmail file |preline procmail -t .procmailrc (assuming that you already have a .procmailrc) -Johan -- Johan Almqvist http://www.almqvist.net/johan/qmail/ Emanuel.exe
Virus found in message Re: Qmail and Procmail
Ett virus upptäcktes i e-post som var adresserad till dig. Vi har stoppat det infekterade brevet för att din dator inte ska bli smittad. A virus was discovered in an e-mail addressed to you. We have rejected the infected mail so your computer will not be infected. The header from the infected e-mail: RCPT TO:[EMAIL PROTECTED] From: jessica [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject:Re: Qmail and Procmail Message-ID: 015901c0cbfe$f0de8320$0300a8c0@acer345t Date: Mon, 23 Apr 2001 22:05:43 +0800
Re: Virus found in message Re: Qmail and Procmail
From: System Anti-Virus Administrator [EMAIL PROTECTED] To: [EMAIL PROTECTED] A virus was discovered in an e-mail addressed to you. We have rejected the infected mail so your computer will not be infected. Thank you. However, - a message from the list to me doesn't go through your computers. - you have now revealed that andreas2 is subscribed to the list. What about sending such warning messages to the envelope sender address? Or what about just dropping the infected messages silently? A simple 'grep ... exit 99' quietly stopped it for me. Sitting here with no virus but lots of warning messages it occurs to me that the latter is at least as disturbing as the first. Please consider doing something with your AV-software. Mads
Re: Virus found in message Re: Qmail and Procmail
On Mon, Apr 23, 2001 at 07:01:57PM +0200, Mads E Eilertsen wrote: From: System Anti-Virus Administrator [EMAIL PROTECTED] To: [EMAIL PROTECTED] A virus was discovered in an e-mail addressed to you. We have rejected the infected mail so your computer will not be infected. Sitting here with no virus but lots of warning messages it occurs to me that the latter is at least as disturbing as the first. Please consider doing something with your AV-software. A better statement to say would be: don't dick with your AV-software, the author knew what he was doing!!! That's *MY* Qmail-Scanner software that generated that message. Unfortunately that site has *REWRITTEN IT* so that it doesn't act as I intended. I went through a *LOT* of effort to stop Qmail-Scanner being like all those bl**dy commercial scanners that spam mailing-lists when they find viruses - mine specifically doesn't send AV messages to mailing-lists. I have vented by displeasure at the site owner. I am not happy. [one of the drawbacks of Open Source of course. Each user can rewrite it as they please] So now in an attempt to make a silk purse from a sow's ear; for those interested in a Email AV solution that won't spam mailing-lists with such messages, take a look at http://qmail-scanner.sourceforge.net/ ;-) -- Cheers Jason Haar Unix/Special Projects, Trimble NZ Phone: +64 3 9635 377 Fax: +64 3 9635 417
Re: Qmail and Procmail
* Alexander Meis [EMAIL PROTECTED] [010406 12:21]: i Try to setup qmail with maildirs and Procmail Mailfiltering. Ok Qmail works. How do i enable the filtering to of Procmail to the ariving Mails ? I found nothing in the manual. Tip 1: Don't start new threads by replying to unrelated messages. Tip 2: If possible, use maildrop instead of procmail. www.courier-mta.org Tip 3: Put the following into your .qmail file |preline procmail -t .procmailrc (assuming that you already have a .procmailrc) -Johan -- Johan Almqvist http://www.almqvist.net/johan/qmail/ Emanuel.exe
Re: Qmail and Procmail
Ok Qmail works. How do i enable the filtering to of Procmail to the ariving Mails ? I found nothing in the manual. man qmail-command
Re: Qmail and Procmail
* Alexander Meis [EMAIL PROTECTED] [010406 12:21]: i Try to setup qmail with maildirs and Procmail Mailfiltering. Ok Qmail works. How do i enable the filtering to of Procmail to the ariving Mails ? I found nothing in the manual. Tip 1: Don't start new threads by replying to unrelated messages. Tip 2: If possible, use maildrop instead of procmail. www.courier-mta.org Tip 3: Put the following into your .qmail file |preline procmail -t .procmailrc (assuming that you already have a .procmailrc) -Johan -- Johan Almqvist http://www.almqvist.net/johan/qmail/ PGP signature
Re: qmail and procmail
Hi Johan, I stumbled onto this thread because of your earlier message in which you heartily recommended using qmail-queue, procmail -m, and spambouncer. I didn't see any replies to this message. Did you end up resolving the procmail log file problem? In light of that problem, do you still recommend this approach to spam-tagging? (I've been trying to decide whether to go back to rblsmtpd alone, or to go for the kinder, gentler approach of tagging suspected spam rather than rejecting it. I was all set to start using your recommended setup until I read your later message about it.) -c At 12:56 PM +0200 9/17/00, Johan Almqvist wrote: Hi! I've hade quite some success using qmail and procmail together, especially using spambouncer (http://www.spambouncer.org/), and, even more, |bouncesaying formail -D 8000 .foo.msgid.file [That's really neat...] However, my procmail logs are filled to the level of unusability with the following lines: procmail: Extraneous deliver-head flag ignored How can I make them go away (and go back to tail -f .procmail-log for biff)? -Johan -- Johan Almqvist At 12:45 AM +0200 7/26/00, Johan Almqvist wrote: On Tue, Jul 25, 2000 at 05:27:28PM -0400, Michael T. Babcock wrote: I would like to offer an option similar to pobox.com's [spam: 84%] "Subject:" munging for incoming messages from RBL or RSS listed sites. Instead of actually bouncing the message as RBLSMTPD does, allow the message but add [spam - rbl] or [spam - rss] or the like to the Subject: field of the messages in question. I'm wondering if anyone else has done this before I go making a completely modified version of rblsmtpd to do so. I think the way to go is SpamBouncer (http://www.spambouncer.org/), procmail -m and the qmail-queue patch (Let spambouncer look at all incoming messages.) rblsmtpd basically runs INSTEAD of smtpd, and denies accepting the message. Okay, s/the way/one way/. -Johan -- Johan Almqvist Chris Thorman (413) 473-0853 e-fax
Re: qmail/maildir/procmail ?
[EMAIL PROTECTED] wrote: Has anyone setup procmail to work with qmail and maildir ? If so, are there any resources I should look to for ideas on how to do this ? Check out: http://Web.InfoAve.Net/~dsill/lwq.html#safecat -Dave
Re: qmail/maildir/procmail ?
On Tue, Nov 16, 1999 at 09:13:42AM -0500, Dave Sill mentioned: Has anyone setup procmail to work with qmail and maildir ? If so, are there any resources I should look to for ideas on how to do this ? Check out: http://Web.InfoAve.Net/~dsill/lwq.html#safecat Nice one. I also had a look at: http://Web.InfoAve.Net/~dsill/lwq.html#procmail Smeg, but this is going to be an evil one to get working. Seems I have to install the qmail-procmail error number, translation software, safecat, and then add a line to .qmail. Oh, and procmail has to be recompiled, with a patch so it doesn't dump temporary files into /var/spool/mail, instead of ~/Maildir. Aaaarg. Kate -- Microsoft. The best reason in the world to drink beer. http://www.redbrick.dcu.ie/~valen
Re: qmail/maildir/procmail ?
On Tue, 16 Nov 1999 15:59:27 + "John P . Looney" wrote: Nice one. I also had a look at: http://Web.InfoAve.Net/~dsill/lwq.html#procmail Smeg, but this is going to be an evil one to get working. Seems I have to install the qmail-procmail error number, translation software, safecat, and then add a line to .qmail. Oh, and procmail has to be recompiled, with a patch so it doesn't dump temporary files into /var/spool/mail, instead of ~/Maildir. Aaaarg. You're wanting to use procmail, and you care about ugly?? Bemused, Giles
Re: qmail and procmail
[EMAIL PROTECTED] wrote: Im fishing for suggestions for my qmail box at home. I'm trying to get rid of spam and have installed the rblsmtp program to help.. What I'd like to also do is learn how to filter stuff thats not specifically addressed to me with procmail. Looking at Dave Sill's excellent "Life with Qmail" document, it seems that procmail needs some tweaking to work with qmail. Should I try to get procmail to work or would maildrop be a lot easier? If you don't already know procmail, maildrop is probably the way to go. And if maildrop would be the preferred method, does anyone have any rules for for blocking things not specifically addressed to the local user (i.e. http://www.css.tayloru.edu/~bbell/spam-filter/) Can't help you there, but watch your use of "filter" and "block". In antispam circles these mean different things. Filtering is passing messages through a pattern matching tool and filing/munging/ignoring/ bouncing messages that match various patterns. Blocking is rejecting SMTP connections from known/suspected/likely spammers. Bouncing can occur in two places: during the SMTP dialogue and after the message has been accepted by the MTA, but before delivery. On the case of spam, bouncing during the SMTP dialogue is preferable since spam often has invalid return paths and the initial SMTP session is the only contact you'll have with the spammer. -Dave
Re: qmail and procmail
On Wed, 4 Aug 1999 12:49:56 -0400, [EMAIL PROTECTED] said: J What I'd like to also do is learn how to filter stuff thats not J specifically addressed to me with procmail. I've included a small .procmailrc file which does that below. You can add additional checks, and then make your final disposition decision based on how many "X-Spam" headers you end up with. Good spam and procmail information can be found here: http://www.best.com/~ariel/nospam/ http://www.hrweb.org/spambouncer/spambnc.tar.Z http://www-new.hrweb.org/spambouncer/proctut.shtml J ... it seems that procmail needs some tweaking to work with qmail. I've never had a problem using qmail with procmail, delivering to a regular mailbox. My ~/.qmail file looks like this: | preline /usr/local/bin/procmail If I want a copy of an outgoing message, I include the header "Bcc: vogelke-bcc" which makes use of the ~/.qmail-bcc file: | (preline /bin/cat; echo) $HOME/mail/sentmail This way, I see the actual message as created by qmail. I also like to keep track of messages I've sent recently (even if I don't need a copy of the whole thing), so I include the header "Bcc: vogelke-header" which makes use of the ~/.qmail-header file: | (preline formail -XFrom: -XSubject: -XDate: -XTo: -XMessage-ID: ; echo) $HOME/mail/SENT.`/bin/date +%Yw%W` All on one line, of course. -- Karl Vogel ASC/YCOA, Wright-Patterson AFB, OH 45433, USA [EMAIL PROTECTED] or [EMAIL PROTECTED] The Uniform Commercial Code protects the innocent purchaser, but it is not a shield for the sly conniver, the blindly naive, or the hopelessly gullible. --Ruling in Atlas Auto Rental Corp. v. Weisberg, N.Y. City Civ. Ct. 1967 --- # Search path. PATH=/bin:/usr/bin:/usr/local/bin # Current directory while procmail is executing. All pathnames are # relative to this directory. MAILDIR=$HOME/mail # File containing error messages or diagnostics. If this file does not # exist, then said messages will be bounced back to the message sender. #LOGFILE=$MAILDIR/MAILLOG # If yes, keep an abstract of the From and Subject lines of each delivered # message, the folder it was delivered to, and the size of the message. # If no, skip this abstract. #LOGABSTRACT=yes # If on, describe actions of procmail in detail. #VERBOSE=on # Number of seconds before procmail zaps a lockfile by force. LOCKTIMEOUT=1 # Default shell and umask value. SHELL=/bin/sh UMASK=022 #-- # Flag anything not addressed to me. :0 f * !^TO_.*vogelke | formail -A "X-Spam: not addressed to me" # other rules here...
Re: qmail and procmail
[EMAIL PROTECTED] writes:
Should I try to get procmail to work or would maildrop be a lot easier? And if
maildrop would be the preferred method, does anyone have any rules for for
blocking things not specifically addressed to the local user (i.e.
http://www.css.tayloru.edu/~bbell/spam-filter/)
I believe that Im using the maildir format.. :)
If you're using maildir, you will need to patch procmail, as it doesn't
deliver to to maildirs. As far as Bcc-s go,
if ( !hasaddr("foo@bar") )
{
exit
}
This will discard all your blind-carbon-copied mail.
--
Sam
Re: qmail + Maildir + procmail
"Mark E. Drummond" [EMAIL PROTECTED] wrote: I now have mail being forwarded to my machine from our hub. However it is being spooled on /var/spool/mail/mark. Here is my /var/qmail/rc: exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start ./Mailbox sh -c 'accustamp | cyclog -s 50 -n 10 /var/log/qmail' Which would normally deliver to ~/Mailbox only my ~/.qmail: |preline /usr/local/bin/procmail runs it through procmail. My procmail is the Maildir capable version and my ~/.procmailrc is (shorted for clarity): PATH=/bin:/usr/bin:/usr/local/bin MAILDIR=$HOME/Maildir LOGFILE=$MAILDIR/log/log.`date +%y-%m-%d` SHELL=/bin/sh :0: * ^(From|Cc|To).*mutt.*@mutt.org mutt/ Try adding: LOGFILE = $MAILDIR/from LOGABSTRACT=all VERBOSE=on then examine $MAILDIR/from after a delivery. So mail from the mutt list(s) should get dumped into ~/Maildir/mutt/, a Maildir format mail box which should be created by procmail as needed no? I doubt it, but I don't know "the Maildir capable version" of procmail. Mail still being spooled on /var/spool/mail/mark. Wasn't there something about procmail delivering to there regardless of the .procmailrc? You need a catch-all recipe like: :0: $HOME/Mailbox at the bottom of your .procmailrc to prevent /var/spool/mail deliveries. Would I be better off just going to maildrop? No doubt. Also, see: http://Web.InfoAve.Net/~dsill/lwq.html#procmail for more qmail/procmail tips, although it's still not 100% complete. -Dave
Re: qmail + Maildir + procmail
Dave Sill [EMAIL PROTECTED] wrote on Tue, 22 Jun 1999: You need a catch-all recipe like: :0: $HOME/Mailbox at the bottom of your .procmailrc to prevent /var/spool/mail deliveries. Actually, setting DEFAULT=$HOME/Mailbox ... should work just as well, even if there's nothing wrong with setting a catch-all recipe. And procmail might also be smart enough to use the contents of the MAIL environment variable if that's been properly when procmail is run defined, though I'm not sure about this. -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / Support bacteria -- it's the only culture some people have.
Re: qmail + Maildir + procmail
"Mark E. Drummond" [EMAIL PROTECTED] writes: I just finished DLing and installing procmail with the necessary patches and tested it out. Part way there ... The incoming message _was_ picked out by procmail but a) it was dumped into a file called ~/Maildir/trash instead of a directory ~/Maildir/trash/... It's not clear what you want, here. Maildir delivery doesn't involve any directory called "trash", unless you created a directory confusingly "Maildir" which isn't one, but which contains a maildir called "trash", having subdirectories "cur", "new", and "tmp". What recipe did you try in your procmailrc? What is ~/Maildir/trash? What did you desire to accomplish? and b) it was _also_ delivered to ~/Maildir/new/. As you deduced, that was probably because of the "./Maildir/" line in your .qmail file. By the way, you can also get the job done using normal procmail, and my "safecat" utility. The recipe in your procmailrc should look like: :0w criteria here | safecat $HOME/Maildir/trash/tmp $HOME/Maildir/trash/new That assumes, of course, that ~/Maildir/trash is a maildir into which you want your messages delivered. Otherwise, delete the text "/trash" globally from the above example. You can find safecat at http://www.pobox.com/~lbudney/linux/software/safeact.html. Len. -- The king's heart is in the hand of the LORD, as the rivers of water: he turneth it whithersoever he will. --Proverbs 21:1
Re: qmail + Maildir + procmail
It's not clear what you want, here. Maildir delivery doesn't involve I'll explain my goal in detail. We run a NIS+ environment here but my machine (Linux box) is standalone. I make it as autonomous as possible like running a secondary DNS server etc. No I want to move my mail off of our hub and onto my machine. I am running qmail 1.03 and want to use Maildir. The idea is this: My mail gets forwarded from the hub to my local machine. procmail filters my mail into various mail boxes (two words so I don't lead anyone to believe I am referring to a particular format) like inbox (mail that doesn't fit any other category), linux, mutt, qmail, security etc (various mailing lists). When I start up mutt I want it to go straight to the "inbox". I also want to use Maildir which means (to me) that _each_ of the above mentioned mail boxes will be a Maildir with a cur new and tmp subdir, like so: ~/Mail /inbox /cur /new /tmp /linux /cur /new /tmp /security /cur /new /tmp Finally, if possible, I want deleted messages moved to a trash mail box. Here are some of my configs: /var/qmail/rc: exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start ./Mailbox sh -c 'accustamp | \ cyclog -s 50 -n 10 /var/log/qmail' ~/.qmail: |preline /usr/local/bin/procmail ~/.procmailrc: PATH=/bin:/usr/bin:/usr/local/bin MAILDIR=$HOME/Mail LOGFILE=$MAILDIR/log/log.`date +%y-%m-%d` SHELL=/bin/sh :0: * ^(From|Cc|To).*mutt.*@mutt.org mutt/ :0: * ^(Subject).*test test/ ~/.muttrc: set folder=~/Mail set mbox=+inbox/ set mbox_type=Maildir set spoolfile=~/Maildir I have been screwing around so much now that my configs are probably all screwed up. Right now, if I send mail to myself, it gets delivered to ~/Mail/mark/ (a Maildir) _and_ /var/spool/mail/mark. If I attempt to use a procmail recipe like the one for a Subject of "test", it does not work. The message still gets delivered to ~/Mail/mark/. -- ___ Mark E DrummondRoyal Military College of Canada [EMAIL PROTECTED]Computing Services Linux Uber Allesperl || die ...there are two types of command interfaces in the world of computing: good interfaces and user interfaces. - Dan Bernstein, Author of qmail PGP Fingerprint = 503D A72D AF41 2AD1 D433 C514 98D9 9A39 B25A 2405
Re: qmail + Maildir + procmail
More strangeness I now have mail being forwarded to my machine from our hub. However it is being spooled on /var/spool/mail/mark. Here is my /var/qmail/rc: exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start ./Mailbox sh -c 'accustamp | cyclog -s 50 -n 10 /var/log/qmail' Which would normally deliver to ~/Mailbox only my ~/.qmail: |preline /usr/local/bin/procmail runs it through procmail. My procmail is the Maildir capable version and my ~/.procmailrc is (shorted for clarity): PATH=/bin:/usr/bin:/usr/local/bin MAILDIR=$HOME/Maildir LOGFILE=$MAILDIR/log/log.`date +%y-%m-%d` SHELL=/bin/sh :0: * ^(From|Cc|To).*mutt.*@mutt.org mutt/ So mail from the mutt list(s) should get dumped into ~/Maildir/mutt/, a Maildir format mail box which should be created by procmail as needed no? No joy so I created the mailbox myself and what now? here is a listing of ~/Maildir/mutt/: signals:~/Maildir$ ls -l mutt total 11 drwx-- 2 mark users1024 Jun 16 15:00 cur/ -rw--- 1 mark users3633 Jun 16 15:03 msg.ZA4B -rw--- 1 mark users3989 Jun 16 15:10 msg.aA4B drwx-- 2 mark users1024 Jun 16 15:00 new/ drwx-- 2 mark users1024 Jun 16 15:00 tmp/ signals:~/Maildir$ ls -l mutt/new/ total 0 Those 2 funny looking files are messages from the mutt mailing list, presumably dumped there by procmail. I am all $@^ed up. Mail still being spooled on /var/spool/mail/mark. Wasn't there something about procmail delivering to there regardless of the .procmailrc? Would I be better off just going to maildrop? -- ___ Mark E DrummondRoyal Military College of Canada [EMAIL PROTECTED]Computing Services Linux Uber Allesperl || die ...there are two types of command interfaces in the world of computing: good interfaces and user interfaces. - Dan Bernstein, Author of qmail PGP Fingerprint = 503D A72D AF41 2AD1 D433 C514 98D9 9A39 B25A 2405
Re: qmail-uce procmail-fromfilter stderr
On Sun, 4 Apr 1999 14:44:43 -0400 (EDT), Sam wrote: On Sun, 4 Apr 1999, Roland Schneider wrote: Instead of sending this string back to the remote side, it just gets logged in the procmail.log: == Obviously procmail's doing that. You'll need to check procmail's doc. Try sending the error message to stdout. Procmails up to 3.11pre7 discarded stdout, and only left stderr alone. I haven't looked at procmail in a long time, but perhaps the current version handles stderr differently. Thanks Sam, I always used procmail 3.11pre7 and it worked once... They also found new buffer-overflows in Bugtraq yesterday in all versions up to 3.12 (upgrade to 3.13 recommended). Now I replaced procmail with your maildrop and everything works again as expected without any troubles. Roland
