Re: script filter before qmail-local .. solved
Ok, just in case anybody else will fight with it too, I found this: seekablepipe http://www.skarnet.org/software/qmail-local-mda/ -- jozef :-)
Announce: change-attachement-ext
Yet another anti-worm/virus solution: don't virus-scan, only change the attachement extensions so that the users can clickrun it. If you're interested, have a look: http://hico.fphil.uniba.sk/ht-wormfilter.html -- jozef :-)
script filter before qmail-local
Hi, I'm quite sure this is near FAQ, but I didn't succeed trying guessing it myself, nor looking through archives, so pls forgive my asking here - What I'm trying to do, is put a perl filter just before qmail-local puts its hands on mail. I moved qmail-local to qmail-local-orig and put in a script named qmail-local, which calls the filter first. Could you please tell me if it is possible to do this with a sh or perl script? If yes, any hint will be highly appreciated, an example of script which just does nothing and forwards mail to qmail-local-orig would be great. I know I could write qmail-local replacement in C (qmail-lspawn.c qmail-local.c as inspiration), but I'd prefer the script solution now, if possible. The resulting flow would be like this: qmail-lspawn --origmsg- qmail-local --filteredmsg- qmail-local-orig The filter itself is simple one-pass always-success script, which just scans attachements for .exe, .vbs, .. and adds .VIRUS extension, so that nobody can simply click through the worms (yes I have such users here). Yes, I'll make the script available (BSD) after some more testing. Thanks, -- jozef :-)
ANN: Filtering out already delivered mail
Here's a little tool I made to get rid of unwanted mail already delivered to ~/Maildir/ on the system (most of my 2000+ mail users _aren't_ the smart ones when it comes to computers). The logic is quite simple: You notice you're hit by a worm or chain letter or anything. So you set up filtering, you kill copies already in ~/Maildir/new, you're done. I'm sure someone did this before, but couldn't find it somehow. Well, here's my $.02. It's a #!/bin/sh script. You can [1] scan all ~/Maildir/new, see the list of files with matches and choose whether delete them (the -n option) [2] scan all ~/Maildir/new, then see each message which matched, and decide whether delete it, leave it in /new or move it to /cur so you won't see it during next search. It's not meant to replace on-delivery mail filtering, but to supplement it. Use with care. It works for me. If it works for you, great. If not, you may hack it as you wish. If you loose your mails, don't blame me, you've been warned. ftp://158.195.33.220/pub/qmail/check-mail-src -- jozef :-)
Patching pine 4.20
Sorry! The patches didn't work. My fault, should be fixed now: ftp://158.195.33.220/pub/pine/pine-4.20-maildir_2.patch ftp://158.195.33.220/pub/pine/pine-4.20-maildir_2.howto It is _not_ inclusive (as I said before), just plain Maildir patch. Works fine for me. -- jozef :-)
Re: Pine and Maildir support
Try ftp://158.195.33.220/pub/pine/, the pine-4.20-maildir.patch should be the one. The rest are older patches included in this one. Don't use the -sk.patch, it translates most of pine texts into Slovak, wouldn't be of much use I'd say. -- jozef :-) Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
Maildir Pine 4.20
I'm working on a linux/qmail with ~/Maildir/ delivery for cca 1500 users. The problem is that we'd like to use pine as the client. I've found patches for 4.10, but .. What's current situations in maildir support for pine - anything new with 4.20? If you are using such a setup, what problems should I prepare for? Pine folder collection (sent-mail, saved-msg etc) will be in Maildir or mbox format? Thanx for any comments on this. -- jozef :-) Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
