oh! - qmail-qfilter can't work with Solaris ?
Hi, I'm trying to compile qmail-qfilter on a sparc box running Solaris ver 7 and for me its problems galore - please assist. Upon compiling with default Makefile, I get an error: In file included from qmail-qfilter.c:26: fork.h:4: conflicting types for `fork' /usr/include/unistd.h:274: previous declaration of `fork' fork.h:5: conflicting types for `vfork' /usr/include/unistd.h:472: previous declaration of `vfork' Since, Solaris supports vfork, I remark the fork include file and the fork error disappears.I now remain with the errors: ./load qmail-qfilter setenv.o Undefined first referenced symbol in file unsetenvqmail-qfilter.o ld: fatal: Symbol referencing errors. No output written to qmail-qfilter collect2: ld returned 1 exit status *** Error code 1 I've tried with some Makefile variations but nothing works for meany one able to shed some light on this? Thanks, Samuel.
qmail-qfilter
Hi everyone! I want to start using qmail-qfilter, I patched qmail using QMAILQUEUE and this went ok. I then went into the qmail-qfilter directory and typed make. Then the errors started :-) ./choose cl trysetenv setenv.h1 setenv.h2 setenv.h ./compile qmail-qfilter.c In file included from qmail-qfilter.c:26: fork.h:4: conflicting types for `fork' /usr/include/unistd.h:245: previous declaration of `fork' fork.h:5: conflicting types for `vfork' /usr/include/unistd.h:461: previous declaration of `vfork' qmail-qfilter.c: In function `parse_sender': qmail-qfilter.c:92: warning: implicit declaration of function `unsetenv' qmail-qfilter.c: In function `mktmpfile': qmail-qfilter.c:218: warning: implicit declaration of function `open' *** Error code 1 make: Fatal error: Command failed for target `qmail-qfilter.o' I am running Solaris (Intel based). I searched the mailing list and could not find anything helpful. Has anyone got any ideas? Thanks, Jon
Re: qmail-qfilter logging?
On Fri, Jun 01, 2001 at 02:11:50PM -0700, Jon Rust wrote:
I've just installed a small filter using Bruce Guenter's qmail-qfilter
package. I have a print statement or 2 when i reject a message:
# from header filter(s) (sexyfun easy to spot here)
} elsif (/^From:/) {
if (/haha\@sexyfun/io) {
print mail refused, suspected Hybris (aka, Snow White) virus:;
print http://vil.nai.com/vil/virusSummary.asp?virus_k=98873\n;;
exit(31);
}
}
However, the line above doesn't show in the qmail logs anywhere, nor
does it get echoed to the sending server. Did I miss something? Any way
to log it short of using syslog calls?
Filters executed by qmail-qfilter have their standard output (where
print goes by default) connected up to either the next filter or to
qmail-queue to go into the mail spool. If you want to print an error,
print to STDERR.
BTW, the deny-filetypes catches virtually all current and future
incidences of Snow White and similar viruses.
--
Bruce Guenter [EMAIL PROTECTED] http://em.ca/~bruceg/ http://untroubled.org/
OpenPGP key: 699980E8 / D0B7 C8DD 365D A395 29DA 2E2A E96F B2DC 6999 80E8
PGP signature
reasearch: qmail-qfilter freebsd segfault
hi all- with some pointers from charles cazabon, i've stared to trace the occurance of qmail-qfilter segfaults on freebsd. here's what i've done: i set QMAILQUEUE to /var/qmail/bin/qmail-runfilters via tcpserver for all incoming mail: /etc/tcp.smtp: :allow,QMAILQUEUE=/var/qmail/bin/qmail-runfilters i'm tracing the execution of every instance of qmail-qfilter via the /var/qmail/bin/qmail-runfilters script: #!/bin/sh exec ktrace -i -f /tmp/ktrace.output`date +%H%M%S` \ /var/qmail/bin/qmail-qfilter /var/qmail/qfilter/filters/deny-filetypes /var/qmail/qfilter/filters/deny-filetypes is taken directly from the samples director that comes with qmail-qfilter-1.4. here's a sample kdump of a trace file generated by a mail that causes qmail-qfilter to segfault: 58293 qmail-qfilter RET write 1024/0x400 58293 qmail-qfilter CALL read(0,0xbfbfec68,0x1000) 58293 qmail-qfilter GIO fd 0 read 0 bytes 58293 qmail-qfilter RET read 0 58293 qmail-qfilter CALL lseek(0x5,0,0,0,0) 58293 qmail-qfilter RET lseek 0 58293 qmail-qfilter CALL read(0x1,0xbfbfec68,0x1000) 58293 qmail-qfilter GIO fd 1 read 0 bytes 58293 qmail-qfilter RET read 0 58293 qmail-qfilter PSIG SIGSEGV SIG_DFL 58293 qmail-qfilter NAMI qmail-qfilter.core i't looks like the segfault occurs after qmail-qfilter has created the temp file to hold the message, when it's trying to read the message back. in an attempt to isolate anything in particular emails that would cause the problem, i uncommented the unlink() call in qmail-qfilter.c that makes the temp files vanish. i'm attaching two text files to this email: 1. the complete temp file created bu qmail-qfilter 2. the complete trace file generated by kdumping the ktrace file generated when qmail-qfilter segfaults. if anyone has any comments on any of this, or any ideas on why the read() syscall might cause the segfault, it'd be much appreciated. thanks- dan
Re: qmail-qfilter signal 11
Daniel Kelley [EMAIL PROTECTED] wrote: i think that someone posted earlier today regarding sporadic sig 11's on freebsd 4.2-RELEASE while running qmail-qfilter. Yes, Jon Rust posted similar problems. interestingly, i just installed qmail-qfilter earlier today on the same release of freebsd, and i'm getting the same thing: [...] interestingly enough, the problem persists after removing the softlimit from /var/qmail/supervise/qmail-smtpd/run. (i'm running LWQ-style) Okay, it's not a memory limit issue then. Has anyone posted to the author's bgware mailing list? I don't recall seeing anything on that list about this. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: anyone using qmail-qfilter?
Jon Rust [EMAIL PROTECTED] wrote:
I'm getting these in my syslog:
.../kernel: pid 93400 (qmail-qfilter), uid 82: exited on signal 11
segfault? Is signal 11 a segmentation violation on your OS?
I was getting LOTS of them, and I thought it was related to my filter
attempting to reject messages with error code 31. Well my current filter
consists of:
#!/usr/bin/perl
while () {
print;
}
exit (0);
Is this happening whenever any process injects mail? Or only when qmail-smtpd
(and possibly qmail-qmtpd and qmail-qmqpd) inject mail? If the latter, are
you running with memory limits on qmail-smtpd?
Another possibility (given that you're running on PC hardware) is hardware
problems; it's worked fine for years does not mean there wasn't a latent
problem all along.
And I'm still seeing them. Bruce Guenter appears to have stopped
development of qmail-qfilter (anything related to qmail?).
No, Bruce is just a busy guy (hence the adjective prolific at qmail.org).
He's still working on qmail-related stuff; vmailmgr is undergoing active
development. If you would like Bruce to change his priorities, I'm sure that
he would be happy to move your pet projects to the top of his to-do list,
given the appropriate incentive. That's how free software consulting works.
Charles
--
---
Charles Cazabon[EMAIL PROTECTED]
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
---
Re: anyone using qmail-qfilter?
Charles Cazabon writes: Another possibility (given that you're running on PC hardware) is hardware problems; it's worked fine for years does not mean there wasn't a latent problem all along. Yep; in fact it's worked fine for years and now doesn't is probably a very good indication of a hardware failure. Have you checked your CPU fan? The qmail.org outages in December 1999, and February 2001 were due to a worn-out CPU fan. ALL of the qmail.org outages for the past five years have been due to hardware problems: o Hardware lacking AC mains power. o Hardware in wrong location. o Hardware overheating due to bad CPU fan. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | Microsoft rivets everything. 521 Pleasant Valley Rd. | +1 315 268 1925 voice | Linux has some loose screws. Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | You own a screwdriver.
Re: anyone using qmail-qfilter?
On Mon, Jun 04, 2001 at 08:36:26AM -0600, Charles Cazabon wrote: Jon Rust [EMAIL PROTECTED] wrote: I'm getting these in my syslog: .../kernel: pid 93400 (qmail-qfilter), uid 82: exited on signal 11 segfault? Is signal 11 a segmentation violation on your OS? Yes. (FreeBSD 4.2-Stable) Is this happening whenever any process injects mail? Or only when qmail-smtpd (and possibly qmail-qmtpd and qmail-qmqpd) inject mail? If the latter, are you running with memory limits on qmail-smtpd? I don't know. It doesn't happen all the time, and there is no logging available from within qmail-qfilter. :-/ I'm working on setting up a test environment to try to isolate the problem. I've got softlimit capping me usage for smtpd at 200 (2 MB). Another possibility (given that you're running on PC hardware) is hardware problems; it's worked fine for years does not mean there wasn't a latent problem all along. Okay, how about it works fine without qmail-qfilter? :-) I only recently started running q-qf. Prior to that nothing on my qmail system segfaulted. If I take q-qf outta the loop, everything is peachy again. I've searched for .core files resulting from the sig 11, but can't find any. And I'm still seeing them. Bruce Guenter appears to have stopped development of qmail-qfilter (anything related to qmail?). No, Bruce is just a busy guy (hence the adjective prolific at qmail.org). He's still working on qmail-related stuff; vmailmgr is undergoing active development. If you would like Bruce to change his priorities, I'm sure that he would be happy to move your pet projects to the top of his to-do list, given the appropriate incentive. That's how free software consulting works. Ah, bad assumption on my part. He has never responded to any mail I've sent him concerning any of the qmail how-to's or projects he has donated to our community. I just ASSuMEd he had moved on. My bad, and apologies to BG. Offering up incentive isn't an issue. I'd be more than happy to. jon
Re: anyone using qmail-qfilter?
Jon Rust [EMAIL PROTECTED] wrote: On Mon, Jun 04, 2001 at 08:36:26AM -0600, Charles Cazabon wrote: Is this happening whenever any process injects mail? Or only when qmail-smtpd (and possibly qmail-qmtpd and qmail-qmqpd) inject mail? If the latter, are you running with memory limits on qmail-smtpd? I don't know. It doesn't happen all the time, and there is no logging available from within qmail-qfilter. :-/ I'm working on setting up a test environment to try to isolate the problem. I've got softlimit capping me usage for smtpd at 200 (2 MB). Chances are that the Perl interpreter can't run in 2MB on your system; try upping that to 6MB or 8MB and try again. I bet a pint that fixes your problem. Another possibility (given that you're running on PC hardware) is hardware problems; it's worked fine for years does not mean there wasn't a latent problem all along. Okay, how about it works fine without qmail-qfilter? :-) You might not like this answer, but that's no guarantee. Hardware issues in computing can cause all sorts of seemingly unrelated problems; it's one of the reasons I wrote memtester. It worked fine before, I added foo, it doesn't work now, therefore foo is broken is an argument known as post hoc, ergo prompter hoc -- and it's a fallacy. No, Bruce is just a busy guy (hence the adjective prolific at qmail.org). He's still working on qmail-related stuff; vmailmgr is undergoing active development. If you would like Bruce to change his priorities, I'm sure that he would be happy to move your pet projects to the top of his to-do list, given the appropriate incentive. That's how free software consulting works. Ah, bad assumption on my part. He has never responded to any mail I've sent him concerning any of the qmail how-to's or projects he has donated to our community. I just ASSuMEd he had moved on. My bad, and apologies to BG. Offering up incentive isn't an issue. I'd be more than happy to. Bruce rarely responds personally to questions which fall under any of the following categories: -can be answered by the documentation -can be answered by the FAQ -can be answered by looking in mailing list archives -are only peripherally related to his software (i.e. core qmail questions) -questions sent to him personally instead of one of his mailing lists In those respects, he's a lot like djb. Unlike djb (I suspect), however, it would probably be relatively easy to get him to put your request at the top of his todo list by offering him a decent hourly rate for the work. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
qmail-qfilter signal 11
hi- i think that someone posted earlier today regarding sporadic sig 11's on freebsd 4.2-RELEASE while running qmail-qfilter. interestingly, i just installed qmail-qfilter earlier today on the same release of freebsd, and i'm getting the same thing: Jun 4 19:46:03 mx1 /kernel: pid 64541 (qmail-qfilter), uid 1003: exited on signal 11 Jun 4 19:48:39 mx1 /kernel: pid 64670 (qmail-qfilter), uid 1003: exited on signal 11 Jun 4 20:01:07 mx1 /kernel: pid 65370 (qmail-qfilter), uid 1003: exited on signal 11 Jun 4 20:04:58 mx1 /kernel: pid 65495 (qmail-qfilter), uid 1003: exited on signal 11 Jun 4 20:18:38 mx1 /kernel: pid 66276 (qmail-qfilter), uid 1003: exited on signal 11 Jun 4 20:50:45 mx1 /kernel: pid 68131 (qmail-qfilter), uid 1003: exited on signal 11 Jun 4 21:02:07 mx1 /kernel: pid 68625 (qmail-qfilter), uid 1003: exited on signal 11 Jun 4 21:52:43 mx1 /kernel: pid 70813 (qmail-qfilter), uid 1003: exited on signal 11 Jun 4 22:26:45 mx1 /kernel: pid 71658 (qmail-qfilter), uid 1003: exited on signal 11 the previous thread on this topic ended when it was suggested that the problem was running softlmit with a limit of 2 meg, which didn't give the perl interpreter enough room to get started. interestingly enough, the problem persists after removing the softlimit from /var/qmail/supervise/qmail-smtpd/run. (i'm running LWQ-style) i've checked the sig 11 FAQ (www.bitwizard.nl/sig11), but that doesn't seem to have anything relevant. has anyone else running qmail on freebsd noticed this behavior? thanks- dan
anyone using qmail-qfilter?
I'm getting these in my syslog:
.../kernel: pid 93400 (qmail-qfilter), uid 82: exited on signal 11
I was getting LOTS of them, and I thought it was related to my filter
attempting to reject messages with error code 31. Well my current filter
consists of:
#!/usr/bin/perl
while () {
print;
}
exit (0);
And I'm still seeing them. Bruce Guenter appears to have stopped
development of qmail-qfilter (anything related to qmail?). Bummer, since
this looks like the only option for filtering, and BG wrote some handy
stuff.
I'm using FreeBSD 4.2-Stable. Any suggestions are welcome.
Thanks,
jon
qmail-qfilter logging?
I've just installed a small filter using Bruce Guenter's qmail-qfilter
package. I have a print statement or 2 when i reject a message:
# from header filter(s) (sexyfun easy to spot here)
} elsif (/^From:/) {
if (/haha\@sexyfun/io) {
print mail refused, suspected Hybris (aka, Snow White) virus:;
print http://vil.nai.com/vil/virusSummary.asp?virus_k=98873\n;;
exit(31);
}
}
However, the line above doesn't show in the qmail logs anywhere, nor
does it get echoed to the sending server. Did I miss something? Any way
to log it short of using syslog calls?
Thanks,
jon
Re: qmail-qfilter question
On Mon, Feb 26, 2001 at 09:26:59AM -0500, Andy Meuse wrote: So, I have qmail-qfilter running using the deny-filetypes script included in the package. I set it up as per the README, in the smtp rules files. A.B.C.D:allow,RELAYCLIENT="",QMAILQUEUE="/usr/local/bin/(script that calls deny-filetypes" The problem is that it denies files from being sent BY my users, but it doesn't deny incoming files from the world TO my users. The relaying rules aren't being invoked I suppose. Any ideas on how I can use qmail-qfilter to screen incoming attachments another way, or how to change my relaying setup to grab them? Add a final rule to your SMTP rules file with: :allow,QMAILQUEUE="/usr/local/bin/" This will force all non-relayclient users to be filtered as well. -- Bruce Guenter [EMAIL PROTECTED] http://em.ca/~bruceg/ PGP signature
qmail-qfilter question
So, I have qmail-qfilter running using the deny-filetypes script included in the package. I set it up as per the README, in the smtp rules files. A.B.C.D:allow,RELAYCLIENT="",QMAILQUEUE="/usr/local/bin/(script that calls deny-filetypes" The problem is that it denies files from being sent BY my users, but it doesn't deny incoming files from the world TO my users. The relaying rules aren't being invoked I suppose. Any ideas on how I can use qmail-qfilter to screen incoming attachments another way, or how to change my relaying setup to grab them? Thanks, Andy
Fw: qmail-qfilter ~ Help...
I received NO responses... please help me... - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, February 22, 2001 10:25 AM Subject: qmail-qfilter ~ Help... : : : : Okay, I've tried to install qmail-filter and thought : I did everything correctly... but it's not filtering out : anything... : : Here's what I did... : : edited Makefile (added -DQMAIL_QUEUE=\"/var/qmail/bin/qmail-queue-old\" ) : so that I didn't have to install QMAILQUEUE patch : : make (looked like it worked ok) : : mv qmail-queue qmail-queue-old : : created qmail-queue with the following: : : #!/bin/sh : exec /path/to/qmai:-qfilter /var/qmail/bin/qmail-inject -n : : chmod +x qmail-queue : : restarted qmail and qmail-smtpd : : Sent test message to myself with .VBS attachment (went through ok) : : Ran (in the 'samples' directory) ./deny-filetypes : : Sent another message... Still went through... : : : What I am doing wrong??? Please help, thanks!!! : : Jesse : :
RE: qmail-qfilter problems
Thanks for the advice, here is the error Outlook Express gives me... An unknown error has occurred. Subject '', Account: 'porno.server.com', Server: 'porno.server.com', Protocol: SMTP, Server Response: '451 qq temporary problem (#4.3.0)', Port: 25, Secure(SSL): No, Server Error: 451, Error Number: 0x800CCC6A ...and from looking through the archives I found that I might need to set my softlimit value higher. I did so and that worked. Hoorah! Say goodbye to .VBS attachments on my network. Thanks again, Andy -Original Message- From: Alex Kramarov [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 21, 2001 12:02 PM To: [EMAIL PROTECTED]; Qmail List (E-mail) Subject: Re: qmail-qfilter problems Andy Meuse wrote I've installed the qmail-qfilter and cannot get it to work. After I add the "QMAILQUEUE" lines to my tcp.smtp and rebuild it, I send an email and get an email back immediately saying, "No transport provider was available for delivery to this recipient" message. 1. I suspect this error message comes from outlook - don't use it to troubleshoot smtp e-mail, you will never get a decent error message. 2. try sending a message manually (telnet host 25), or through (at least) outlook express and see what error do you recieve.
qmail-qfilter ~ Help...
Okay, I've tried to install qmail-filter and thought I did everything correctly... but it's not filtering out anything... Here's what I did... edited Makefile (added -DQMAIL_QUEUE=\"/var/qmail/bin/qmail-queue-old\" ) so that I didn't have to install QMAILQUEUE patch make (looked like it worked ok) mv qmail-queue qmail-queue-old created qmail-queue with the following: #!/bin/sh exec /path/to/qmai:-qfilter /var/qmail/bin/qmail-inject -n chmod +x qmail-queue restarted qmail and qmail-smtpd Sent test message to myself with .VBS attachment (went through ok) Ran (in the 'samples' directory) ./deny-filetypes Sent another message... Still went through... What I am doing wrong??? Please help, thanks!!! Jesse
qmail-qfilter problems
Hey All, I've installed the qmail-qfilter and cannot get it to work. After I add the "QMAILQUEUE" lines to my tcp.smtp and rebuild it, I send an email and get an email back immediately saying, "No transport provider was available for delivery to this recipient" message. There is nothing in the logs on the mail server. The TMPDIR I set in the Makefile is /var/qmail/bin/tmp. I've tried changing the ownership of the files below, and the TMPDIR to qmailq, but that didn't work either. \var\qmail\bin -rwxr-xr-x 1 qmaild qmail1753 Feb 20 15:34 deny-filetypes -rwxr-xr-x 1 qmaild qmail 74 Feb 20 16:56 qmail-qftest drwxrwxr-x 2 qmaild qmail4096 Feb 21 09:56 tmp -rwxrwxr-x 1 qmaildqmail 37931 Feb 21 09:58 qmail-qfilter tcp.smtp 172.16.3.:allow,RELAYCLIENT="",QMAILQUEUE="/var/qmail/bin/qmail-qftest" 127.:allow,RELAYCLIENT="",QMAILQUEUE="/var/qmail/bin/qmail-qftest" ---- qmail-qftest #!/bin/sh exec /var/qmail/bin/qmail-qfilter /var/qmail/bin/deny-filetypes The deny-filetypes file is straight from ~/samples in the qmail-qfilter package Processes-- root 9021 1 0 08:57 pts/100:00:00 /usr/local/bin/tcpserver -v -H -R 0 110 /var/qmail/bin/qmail-popu root 9022 1 0 08:57 pts/100:00:00 /var/qmail/bin/splogger pop3d root 9024 1 0 08:57 pts/100:00:00 svscan root 9025 9024 0 08:57 pts/100:00:00 supervise qmail-send root 9026 9024 0 08:57 pts/100:00:00 supervise log root 9027 9024 0 08:57 pts/100:00:00 supervise qmail-smtpd root 9028 9024 0 08:57 pts/100:00:00 supervise log qmails9029 9025 0 08:57 pts/100:00:00 qmail-send qmaill9030 9026 0 08:57 pts/100:00:00 /usr/local/bin/multilog t /var/log/qmail qmaill9031 9028 0 08:57 pts/100:00:00 /usr/local/bin/multilog t /var/log/qmail/smtpd qmaild9032 9027 0 08:57 pts/100:00:00 /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -c 20 -u 507 root 9037 9029 0 08:57 pts/100:00:00 qmail-lspawn ./Maildir/ qmailr9038 9029 0 08:57 pts/100:00:00 qmail-rspawn qmailq9039 9029 0 08:57 pts/100:00:00 qmail-clean Any suggestions? -Andy ALSO: In the qmail-qfilter readme it says... "Check the definitions at the top of qmail-qfilter.c, especially the value of TMPDIR. This should be set to a temporary directory that only the executor of qmail-qfilter has write access to." I can't find any TMPDIR reference in the qmail-qfilter.c file though, only in the Makefile.
Re: qmail-qfilter problems
Andy Meuse wrote I've installed the qmail-qfilter and cannot get it to work. After I add the "QMAILQUEUE" lines to my tcp.smtp and rebuild it, I send an email and get an email back immediately saying, "No transport provider was available for delivery to this recipient" message. 1. I suspect this error message comes from outlook - don't use it to troubleshoot smtp e-mail, you will never get a decent error message. 2. try sending a message manually (telnet host 25), or through (at least) outlook express and see what error do you recieve.
qmail-queue wrapper (like qmail-qfilter)
Any had implemented qmail-qfilter sucefully or any qmail-queue wrapper ? RDA.-
Re: qmail-queue wrapper (like qmail-qfilter)
On Wed, 30 Aug 2000, Ricardo Albano wrote:
Any had implemented qmail-qfilter sucefully or any qmail-queue wrapper ?
RDA.-
I have a generic qmail-queue-wrapper program. It's written in perl and
in its standard form, does nothing but add another Received header to
the message before calling the real qmail-queue. If you can program in
perl you can get it to do whatever you want. I'm using it to do header
rewrites at one site.
It should be installed with no special permissions
-rwx--x--x qmailq qmail /var/qmail/bin/qmail-queue
Program is attached.
You can also have a look at Jason Haar's scan4virus program. It too is
a perl qmail-queue-wrapper. Details at www.qmail.org.
--
Regards
Peter
--
Peter Samuel[EMAIL PROTECTED]
http://www.e-smith.org (development)http://www.e-smith.com (corporate)
Phone: +1 613 368 4398 Fax: +1 613 564 7739
e-smith, inc. 1500-150 Metcalfe St, Ottawa, ON K2P 1P1 Canada
"If you kill all your unhappy customers, you'll only have happy ones left"
#!/pkgs/bin/perl -w
#
# $Id: qmail-queue-wrapper.pl,v 1.1 2000/05/31 07:20:37 psamuel Exp $
#
# qmail-queue wrapper program.
#
# This program should be used when you wish to manipulate a mail
# message BEFORE it is placed in the queue. Possible uses include:
#
#- header rewriting
#- Firstname.Lastname replacements
#- virus scanning
#- anything else you can think of
#
# There are at least 2 ways of using this program:
#
#1) Replace the original qmail-queue with this program:
#
# mv /var/qmail/bin/qmail-queue /var/qmail/bin/qmail-queue.orig
# cp qmail-queue-wrapper /var/qmail/bin/qmail-queue
#
#Change the value of $qmailqueue below, to reflect the new name of
#the original qmail-queue program. For example
#
# my $qmailqueue = "/var/qmail/bin/qmail-queue.orig";
#
#2) Recompile qmail with Bruce Guenter's QMAILQUEUE patch. (See
#http://www.qmail.org/qmailqueue-patch). Then any program that
#needs to use this program can be called with the environment
#variable QMAILQUEUE set to /var/qmail/bin/qmail-queue-wrapper
#
# How does it work? The interface to the real qmail-queue is simple:
#
# - the body of the message is read from file descriptor 0
# - the envelope details are read from file descriptor 1.
#
# qmail-queue-wrapper also adheres to the same interface. After doing
# whatever manipulations are necessary, it calls the real qmail-queue
# and provides the message body on file descriptor 0 and the envelope
# details on file descriptor 1.
#
# Exit codes conform to those mentioned in the qmail-queue(8) manual page.
#
###
require 5;
use strict;
my $child;
my $debug = 0;
my $envelope;
my %errors;
my @months;
my $new_received_header;
my $qmailqueue = "/var/qmail/bin/qmail-queue.orig";
my @recipients;
my $sender;
###
initialise();
if ($child = fork())
{
# Parent
my $timeout = 86400;# See qmail-queue.c, line 20
alarm($timeout);
fatal(82) unless close MESSAGE_READER;
fatal(82) unless close ENVELOPE_READER;
process_message();
process_envelope();
# Wait for the child to terminate
waitpid($child, 0);
# Return with the exit status of the child
exit($? % 255);
}
elsif (defined $child)
{
# Child
fatal(82) unless close MESSAGE_WRITER;
fatal(82) unless close ENVELOPE_WRITER;
fatal(82) unless defined open(STDIN, "MESSAGE_READER");
fatal(82) unless defined open(STDOUT, "ENVELOPE_READER");
if ($debug)
{
debug_message("$$: Reading message from STDIN\n\n");
while (STDIN)
{
debug_message("$$: $_");
}
fatal(82) unless close MESSAGE_READER;
debug_message("\n$$: \n\n");
debug_message("$$: Reading envelope from STDOUT\n");
while (ENVELOPE_READER)
{
s/\0/ /g;
debug_message("$$: $_\n");
}
fatal(82) unless close ENVELOPE_READER;
exit(0);
}
else
{
unless (exec $qmailqueue)
{
# We shouldn't be here unless the exec failed
fatal(82);
}
}
}
else
{
# Unable to fork
fatal(82);
}
###
sub initialise
{
prepare_months();
prepare_error_messages();
ignore_signals();
catch_signals();
generate_new_received_header();
setup_pipes();
}
sub prepare_months
{
@months = (
"Jan", "Feb", "Mar"
qmail-qfilter
Hello, I'm trying to get qmail-qfilter running but I get thefollowing error after finishing the data command with a dot. :Connected to localhost.Escape character is '^]'.220 maxikiosco.radar.com.ar ESMTPehlo maxikisoco.rada.com.ar250-maxikiosco.radar.com.ar250-PIPELINING250 8BITMIMEmail from:[EMAIL PROTECTED]250 okrcpt to:[EMAIL PROTECTED]250 okdata354 go aheadTesting.451 qq temporary problem (#4.3.0)Here are the rights and permissions for the bin files involved :-rws--x--x 1 qmailq qmail 75 Aug 24 14:54 qmail-qftest-rws--x--x 1 qmailq qmail 12708 Aug 24 14:37 qmail-queueAny idea ? I'm using qmail-1.03 with qmail-qfilter 1.4 and the Bruce Guenter QMAILQUEUE patch. Bye and thank you.RDA.-
Re: qmail-qfilter
i had the same problem and never did find a fix : ) let me know if you find it : ) Eric On Thu, 24 Aug 2000, Ricardo Albano wrote: Hello, I'm trying to get qmail-qfilter running but I get the following error after finishing the "data command" with a dot. : Connected to localhost. Escape character is '^]'. 220 maxikiosco.radar.com.ar ESMTP ehlo maxikisoco.rada.com.ar 250-maxikiosco.radar.com.ar 250-PIPELINING 250 8BITMIME mail from:[EMAIL PROTECTED] 250 ok rcpt to:[EMAIL PROTECTED] 250 ok data 354 go aheadTesting . 451 qq temporary problem (#4.3.0) Here are the rights and permissions for the bin files involved : -rws--x--x 1 qmailq qmail 75 Aug 24 14:54 qmail-qftest -rws--x--x 1 qmailq qmail 12708 Aug 24 14:37 qmail-queue Any idea ? I'm using qmail-1.03 with qmail-qfilter 1.4 and the Bruce Guenter QMAILQUEUE patch. Bye and thank you. RDA.-
Re: qmail-qfilter
On Thu, Aug 24, 2000 at 03:17:11PM -0300, Ricardo Albano wrote: snip 354 go aheadTesting . 451 qq temporary problem (#4.3.0) What Do the Logs Say? (tm) Ben -- Ben Beuchler [EMAIL PROTECTED] MAILER-DAEMON (612) 321-9290 x101 Bitstream Underground www.bitstream.net
Re: qmail-qfilter
Hello, Bruce Guenter (the author of qmail-qfilter) say : Yes. The script MUST NOT be setuid, and MUST be readable. Only the real qmail-queue needs to be setuid. I get changed the rights to 0755 but now another error return : 451 qq internal bug (#4.3.0) Eric: Try with "chmod 0755" the qmail-qftest file and let me know the results. Bye. RDA.- -Original Message- From: Eric Peters [EMAIL PROTECTED] To: Ricardo Albano [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Thursday, August 24, 2000 3:54 PM Subject: Re: qmail-qfilter i had the same problem and never did find a fix : ) let me know if you find it : ) Eric On Thu, 24 Aug 2000, Ricardo Albano wrote: Hello, I'm trying to get qmail-qfilter running but I get the following error after finishing the "data command" with a dot. : Connected to localhost. Escape character is '^]'. 220 maxikiosco.radar.com.ar ESMTP ehlo maxikisoco.rada.com.ar 250-maxikiosco.radar.com.ar 250-PIPELINING 250 8BITMIME mail from:[EMAIL PROTECTED] 250 ok rcpt to:[EMAIL PROTECTED] 250 ok data 354 go aheadTesting . 451 qq temporary problem (#4.3.0) Here are the rights and permissions for the bin files involved : -rws--x--x 1 qmailq qmail 75 Aug 24 14:54 qmail-qftest -rws--x--x 1 qmailq qmail 12708 Aug 24 14:37 qmail-queue Any idea ? I'm using qmail-1.03 with qmail-qfilter 1.4 and the Bruce Guenter QMAILQUEUE patch. Bye and thank you. RDA.-
Re: qmail-qfilter-problem
Hi Bruce,
Bruce Guenter wrote:
On Fri, Aug 18, 2000 at 04:38:40PM +0200, Lars Pfuhl wrote:
qmail-queue -rws--x--x qmailq qmail -- this is now my shell-script
qmail-queue-old -rws--x--x qmailq qmail -- the original qmail-queue
Shell scripts must be readable by the userid that is trying to execute
them. The wrapper script also does not need to be (and should not be
for security reasons) setuid. Make qmail-queue mode 755 instead of 4711.
Thanks for helping me.
I changed it but it doesn't work.
1. Is it o.k. that the owner of the shell-script is qmailq?
Now I have:
qmail-queue -rwxr-xr-x qmailq qmail -- this is my shell-script
qmail-queue-old -rws--x--x qmailq qmail -- the original
qmail-queue
2. Is the shell-script o.k.?
I have:
#!/bin/sh
exec /var/qmail/bin/qmail-filter /var/qmail/bin/my-filter
3. Who must be the owner of my-filter, root or qmailq (I tried qmailq
and root but it doesn't work, the permissions are 755) ?
4. My error code is now (after I changed some things):
qq write error or disk full (#4.3.0)
5. I give you the perl script (it works but sometimes you don't know):
#!/usr/bin/perl -w
while () {
s/Lars/Lars Pfuhl/;
print
}
I hope anyone has an idea.
Thanks in advance!
Lars
qmail-qfilter-problem
Hi, i am using qmail-qfilter _without_ B.Guenter's QMAILQUEUE patch. When I try to send a message I get: qq temporary problem (#4.3.0) I use a perl-script and in qmail-queue is: #!/bin/sh exec /var/qmail/bin/qmail-filter /var/qmail/bin/my-filter What I have done: - in the Makefile I have written CFLAGS = -O -Wall -DQMAIL_QUEUE=\"/var/qmail/bin/qmail-queue-old\" - compile - qmail-queue -- qmail-queue-old - qmail-queue ist now the shell-script with the owner qmailq and the group qmail (chmod 755) Any ideas? Lars -- bone labs ... Secure eBusiness Try our Internet-WorkTeam platform at http://www.centerworks.de bone labs GmbH Lars Pfuhl PF 171134, D-10203 Berlin phone +49-(0)30-293475-0 email [EMAIL PROTECTED] fax +49-(0)30-293475-99 web http://www.bonelabs.com
Re: qmail-qfilter-problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18 Aug 2000, at 15:39, Lars Pfuhl wrote: When I try to send a message I get: qq temporary problem (#4.3.0) I use a perl-script and in qmail-queue is: #!/bin/sh exec /var/qmail/bin/qmail-filter /var/qmail/bin/my-filter What I have done: - in the Makefile I have written CFLAGS = -O -Wall -DQMAIL_QUEUE=\"/var/qmail/bin/qmail-queue-old\" - compile - qmail-queue -- qmail-queue-old - qmail-queue ist now the shell-script with the owner qmailq and the group qmail (chmod 755) Any ideas? The original qmail-queue is suid qmailq program. What is suid qmailq in your setup? (No other user than root or qmailq can write into the queue; qmail-smtpd should run as qmaild, and therefore can't write the queue.) -BEGIN PGP SIGNATURE- Version: PGP 6.0.2 -- QDPGP 2.60 Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBOZ0xKFMwP8g7qbw/EQK5xQCfU4WiwPKWAmyLFa1fLSX2yhODOuYAn2SO dUfxqUxvV3eEVfqenfliIeBL =TSrc -END PGP SIGNATURE- -- Petr Novotny, ANTEK CS [EMAIL PROTECTED] http://www.antek.cz PGP key ID: 0x3BA9BC3F -- Don't you know there ain't no devil there's just God when he's drunk. [Tom Waits]
Re: qmail-qfilter-problem
On Fri, Aug 18, 2000 at 04:38:40PM +0200, Lars Pfuhl wrote: qmail-queue -rws--x--x qmailq qmail -- this is now my shell-script qmail-queue-old -rws--x--x qmailq qmail -- the original qmail-queue Change qmail-queue to mode 755. I had the same problem, and I think the problem is that a shell script has to be readable in addition to executable. Chris
Re: qmail-qfilter-problem
On Fri, Aug 18, 2000 at 04:38:40PM +0200, Lars Pfuhl wrote: qmail-queue -rws--x--x qmailq qmail -- this is now my shell-script qmail-queue-old -rws--x--x qmailq qmail -- the original qmail-queue Shell scripts must be readable by the userid that is trying to execute them. The wrapper script also does not need to be (and should not be for security reasons) setuid. Make qmail-queue mode 755 instead of 4711. -- Bruce Guenter [EMAIL PROTECTED] http://em.ca/~bruceg/ PGP signature
Re: QMAILQUEUE Patch qmail-qfilter 451 qq internal bug (#4.3.0)
they are - as i said its sporadic in many ways - it works for some hosts but not others (I have servers serial mailing' into this box) this host doesn't work though Eric On Thu, 13 Jul 2000, Bruce Guenter wrote: On Thu, Jul 13, 2000 at 07:13:29PM -0700, Eric Peters wrote: First off it probably doesn't have anything at all to do with QMAILQUEUE just laying the foundation down for the implementation the qmail-smtpd.cdb is populated based upon 168.100.206.150:allow,RELAYCLIENT="",QMAILQUEUE="/usr/local/bin/qmail-filterq" and /usr/local/bin/qmail-filterq: #!/bin/sh exec /usr/local/bin/qmail-qfilter /usr/local/bin/log_sent What are the permissions on these files? Make sure they are both readable and executable by whatever user qmail-smtpd is running as. -- Bruce Guenter [EMAIL PROTECTED] http://em.ca/~bruceg/
Re: QMAILQUEUE Patch qmail-qfilter 451 qq internal bug (#4.3.0)
I have made the qmail-filterq script (the one that immediately calls the qmail-qfilter) so it doesn't actually pass onto anything (there isn't a log_sent) and it still gives that error as of yet I havn't found where there is a softlimit installed either as mentioned in a previous couple replies Any other suggestions? Eric On Fri, 14 Jul 2000 [EMAIL PROTECTED] wrote: I had similar problems at one point. Turned out to be an error buried in the script executed by qmail-qfilter. It only produced the error when it hit a certain point in the script that only ran against messages coming from a particular host. I found my problem by putting the problem message in a text file and piping it into my filtering program (like your log_sent). I immedately saw the script error on screen and was able to correct it. You may need to monkey with some environment variables to duplicate the problem environment, though. Josh Eric Peters [EMAIL PROTECTED] on 07/14/2000 09:32:12 AM To: Bruce Guenter [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject: Re: QMAILQUEUE Patch qmail-qfilter 451 qq internal bug (#4.3.0) they are - as i said its sporadic in many ways - it works for some hosts but not others (I have servers serial mailing' into this box) this host doesn't work though Eric On Thu, 13 Jul 2000, Bruce Guenter wrote: On Thu, Jul 13, 2000 at 07:13:29PM -0700, Eric Peters wrote: First off it probably doesn't have anything at all to do with QMAILQUEUE just laying the foundation down for the implementation the qmail-smtpd.cdb is populated based upon 168.100.206.150:allow,RELAYCLIENT="",QMAILQUEUE ="/usr/local/bin/qmail-filterq" and /usr/local/bin/qmail-filterq: #!/bin/sh exec /usr/local/bin/qmail-qfilter /usr/local/bin/log_sent What are the permissions on these files? Make sure they are both readable and executable by whatever user qmail-smtpd is running as. -- Bruce Guenter [EMAIL PROTECTED] http://em.ca/~bruceg/
Re: QMAILQUEUE Patch qmail-qfilter 451 qq internal bug (#4.3.0)
On Fri, Jul 14, 2000 at 07:51:34AM -0700, Eric Peters wrote: I have made the qmail-filterq script (the one that immediately calls the qmail-qfilter) so it doesn't actually pass onto anything (there isn't a log_sent) and it still gives that error as of yet I havn't found where there is a softlimit installed either as mentioned in a previous couple replies Softlimit is part of the daemontools package. Any other suggestions? You still haven't told us what your permissions are on the system on which it is failing. Or does it only fail for certain clients? What are the exact contents of your tcpcontrol rules file? -- Bruce Guenter [EMAIL PROTECTED] http://em.ca/~bruceg/ PGP signature
Re: QMAILQUEUE Patch qmail-qfilter 451 qq internal bug (#4.3.0)
permissions are 755, only certain clients, 168.100.206.150:allow,RELAYCLIENT="",QMAILQUEUE="/usr/local/bin/qmail-filterq" and i have the pasted the contents of the qmail-filterq file already too the loggin works on some hosts that connect up via serialmail to relay its only some hosts that it has issues on - (the softmail thing does sound promising ---) Eric Any other suggestions? You still haven't told us what your permissions are on the system on which it is failing. Or does it only fail for certain clients? What are the exact contents of your tcpcontrol rules file? -- Bruce Guenter [EMAIL PROTECTED] http://em.ca/~bruceg/
Re: QMAILQUEUE Patch qmail-qfilter 451 qq internal bug (#4.3.0)
For some added confusion I put the softlimit command in after the supervise and it didn't help it DEFINATELY looks to be some type of limit thing though because [root@ecamp /root]# telnet ecamp.net 25 Trying 168.100.187.53... Connected to ecamp.net. Escape character is '^]'. 220 ecamp.net ESMTP EHLO campchi.ecamp.net 250-ecamp.net 250-PIPELINING 250 8BITMIME MAIL FROM:[EMAIL PROTECTED] 250 ok RCPT TO:[EMAIL PROTECTED] 250 ok DATA 354 go ahead Received: (qmail 14800 invoked by uid 507); 7 Jul 2000 10:16:20 - Message-ID: [EMAIL PROTECTED] From: "dorine.perach" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Fri, 07 Jul 2000 10:16:20 GMT Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit hi . 250 ok 963619908 qp 9102 QUIT 221 ecamp.net queues up great - but a longer email message doesn't if [ -e $CDB ]; then supervise $DIR \ /usr/local/bin/softlimit -m 400 \ tcpserver $VERBOSE -c$CONCURRENT -x $CDB -u$USERID -g$GROUPID 0 $PORT \ sh -c ' /var/qmail/bin/qmail-smtpd cd /var/qmail/autoturn maildirsmtp /var/qmail/autoturn/$TCPREMOTEIP autoturn-$TCPREMOTEIP- $TCPREMOTEIP AutoTURN ' \ 21| setuser $LOGUSER accustamp \ | setuser $LOGUSER cyclog $LOGSIZE $LOGDIR else . is the line i use to start it root 6725 0.0 0.0 1060 328 pts/39 S20:04 0:00 supervise /var/lock/qmail-smtpd /usr/local/bin/softlimit -m 400 tcpserver -v -c40 -x /etc/tcprules.d/qmail-smtpd.cdb -u81 -g80 0 smtp sh -c ??? ?/var/qmail/bin/qmail-smtpdcd /var/qmail/autoturnmaildirsmtp /var/qmail/autoturn/$TCPREMOTEIP autoturn-$TCPREMOTEIP- $TCPREMOTEIP AutoTURN qmaill6727 0.0 0.0 1068 332 pts/39 S20:04 0:00 cyclog -s 100 /var/log/qmail-smtpd qmaild6728 0.0 0.0 1316 576 pts/39 S20:04 0:00 tcpserver -v -c40 -x /etc/tcprules.d/qmail-smtpd.cdb -u81 -g80 0 smtp sh -c ??? ?/var/qmail/bin/qmail-smtpdcd /var/qmail/autoturnmaildirsmtp /var/qmail/autoturn/$TCPREMOTEIP autoturn-$TCPREMOTEIP- $TCPREMOTEIP AutoTURN qmaild9228 0.0 0.0 1316 596 pts/39 S20:15 0:00 tcpserver -v -c40 -x /etc/tcprules.d/qmail-smtpd.cdb -u81 -g80 0 smtp sh -c ??? ?/var/qmail/bin/qmail-smtpdcd /var/qmail/autoturnmaildirsmtp /var/qmail/autoturn/$TCPREMOTEIP autoturn-$TCPREMOTEIP- $TCPREMOTEIP AutoTURN is the processes that are running Thanks, Eric On Thu, 13 Jul 2000, Eric Peters wrote: First off it probably doesn't have anything at all to do with QMAILQUEUE just laying the foundation down for the implementation this seems to only be happening on some hosts and I can't figure out what the uniqueness is and the 451 qq internal bug doesn't tell me much when i look at the qmail-smtpd.c file (where its found) here is a session that causes the error [root@ecamp /root]# telnet ecamp.net 25 Trying 168.100.187.53... Connected to ecamp.net. Escape character is '^]'. 220 ecamp.net ESMTP EHLO campchi.ecamp.net 250-ecamp.net 250-PIPELINING 250 8BITMIME MAIL FROM:[EMAIL PROTECTED] 250 ok RCPT TO:[EMAIL PROTECTED] 250 ok DATA 354 go ahead Received: (qmail 14800 invoked by uid 507); 7 Jul 2000 10:16:20 - Message-ID: [EMAIL PROTECTED] From: "dorine.perach" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Fri, 07 Jul 2000 10:16:20 GMT Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi honey. I like having two messages in my e-mail box. I wrote out all the checks for D'vrei Englit in Sept/Oct. and Elan never handed them in of course we did figure that out... I hope she didn't think we were trying to get away with something. What did you say to her? blah blahblahblah Love, Me Write right back! . 451 qq internal bug (#4.3.0) AAACK! I am lost here is the setup for the qmail shit the qmail-smtpd.cdb is populated based upon 168.100.206.150:allow,RELAYCLIENT="",QMAILQUEUE="/usr/local/bin/qmail-filterq" and /usr/local/bin/qmail-filterq: #!/bin/sh exec /usr/local/bin/qmail-qfilter /usr/local/bin/log_sent (the log_sent is the program I have that logs the data n stuff) either way if i just have /usr/local/bin/qmail-filterq: #!/bin/sh exec /usr/local/bin/qmail-qfilter (no parameters) the same error occurs Any help would be a god blessing! Thanks for your time, Eric
QMAILQUEUE Patch qmail-qfilter 451 qq internal bug (#4.3.0)
First off it probably doesn't have anything at all to do with QMAILQUEUE just laying the foundation down for the implementation this seems to only be happening on some hosts and I can't figure out what the uniqueness is and the 451 qq internal bug doesn't tell me much when i look at the qmail-smtpd.c file (where its found) here is a session that causes the error [root@ecamp /root]# telnet ecamp.net 25 Trying 168.100.187.53... Connected to ecamp.net. Escape character is '^]'. 220 ecamp.net ESMTP EHLO campchi.ecamp.net 250-ecamp.net 250-PIPELINING 250 8BITMIME MAIL FROM:[EMAIL PROTECTED] 250 ok RCPT TO:[EMAIL PROTECTED] 250 ok DATA 354 go ahead Received: (qmail 14800 invoked by uid 507); 7 Jul 2000 10:16:20 - Message-ID: [EMAIL PROTECTED] From: "dorine.perach" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Fri, 07 Jul 2000 10:16:20 GMT Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi honey. I like having two messages in my e-mail box. I wrote out all the checks for D'vrei Englit in Sept/Oct. and Elan never handed them in of course we did figure that out... I hope she didn't think we were trying to get away with something. What did you say to her? blah blahblahblah Love, Me Write right back! . 451 qq internal bug (#4.3.0) AAACK! I am lost here is the setup for the qmail shit the qmail-smtpd.cdb is populated based upon 168.100.206.150:allow,RELAYCLIENT="",QMAILQUEUE="/usr/local/bin/qmail-filterq" and /usr/local/bin/qmail-filterq: #!/bin/sh exec /usr/local/bin/qmail-qfilter /usr/local/bin/log_sent (the log_sent is the program I have that logs the data n stuff) either way if i just have /usr/local/bin/qmail-filterq: #!/bin/sh exec /usr/local/bin/qmail-qfilter (no parameters) the same error occurs Any help would be a god blessing! Thanks for your time, Eric
Re: QMAILQUEUE Patch qmail-qfilter 451 qq internal bug (#4.3.0)
On Thu, Jul 13, 2000 at 07:13:29PM -0700, Eric Peters wrote: First off it probably doesn't have anything at all to do with QMAILQUEUE just laying the foundation down for the implementation the qmail-smtpd.cdb is populated based upon 168.100.206.150:allow,RELAYCLIENT="",QMAILQUEUE="/usr/local/bin/qmail-filterq" and /usr/local/bin/qmail-filterq: #!/bin/sh exec /usr/local/bin/qmail-qfilter /usr/local/bin/log_sent What are the permissions on these files? Make sure they are both readable and executable by whatever user qmail-smtpd is running as. -- Bruce Guenter [EMAIL PROTECTED] http://em.ca/~bruceg/ PGP signature
Announcing qmail-qfilter version 1.3
Version 1.3 of qmail-qfilter is now available at: http://em.ca/~bruceg/qmail-qfilter/ See the documentation there for more details, or join the mailing list by sending an email to: [EMAIL PROTECTED] Development versions of qmail-qfilter are available via anonymous CVS. Set your CVSROOT to ":pserver:[EMAIL PROTECTED]:/CVS", login with an empty password, and check out the qmail-qfilter module. --- Changes in version 1.3 - A new environment variable, "QMAILRCPTS" is set to a newline-seperated list of the recipients. Note that if a large number of recipients are encountered (ex more than 64KB worth under Linux), this will cause execution of the filters to fail and the message will be rejected. I consider this acceptable, since 64KB worth of recipients is likely more than 1000 anyways. - Removed some GNU-specific constructs from the source and Makefile. - Included a sample MIME filename extension scanning filter. --- -- Bruce Guenter [EMAIL PROTECTED] http://em.ca/~bruceg/
Re: qmail-qfilter stangeness
On Wed, May 10, 2000 at 07:18:46PM -0400, Russell P. Sutherland wrote:
I am running with B. Guenter's QMAILQUEUE patch with his qmail-qfilter
package and have difficulty when using perl scripts in the filter
train/pipeline. E.g. with the QMAILQUEUE file containing:
exec /usr/bin/qmail-qfilter /usr/bin/perl -n -e '{print}'
Whereas if I put the equivalent constructs:
exec /usr/bin/qmail-qfilter /bin/awk '{print}'
or
exec /usr/bin/qmail-qfilter /bin/cat
There is no problem.
Any ideas why perl causes this error?
Nope. I use perl myself as a filter, so it's not just perl being wierd.
The SMTP error code ("temporary problem (#4.3.0)") indicates that qmail
queue (qmail-qfilter in this case) returned an unrecognized error code
number. qmail-qfilter returns whatever the last item in the pipe
returns, which should be 0 if your perl is working.
--
Bruce Guenter [EMAIL PROTECTED] http://em.ca/~bruceg/
qmail-qfilter stangeness
I am running with B. Guenter's QMAILQUEUE patch with his qmail-qfilter
package and have difficulty when using perl scripts in the filter
train/pipeline. E.g. with the QMAILQUEUE file containing:
exec /usr/bin/qmail-qfilter /usr/bin/perl -n -e '{print}'
The remote smtpd session sees:
$ telnet 192.168.1.11 25
Trying 192.168.1.11...
Connected to 192.168.1.11.
Escape character is '^]'.
220 raqee.clikx.com ESMTP
helo dude
250 raqee.clikx.com
mail [EMAIL PROTECTED]
250 ok
rcpt [EMAIL PROTECTED]
250 ok
data
354 go ahead
To: [EMAIL PROTECTED]
Subject: testing 3
This a test
.
451 qq temporary problem (#4.3.0)
Whereas if I put the equivalent constructs:
exec /usr/bin/qmail-qfilter /bin/awk '{print}'
or
exec /usr/bin/qmail-qfilter /bin/cat
There is no problem.
Any ideas why perl causes this error?
--
Quist ConsultingEmail: [EMAIL PROTECTED]
219 Donlea DriveVoice: +1.416.696.7600
Toronto ON M4G 2N1 Fax: +1.416.978.6620
CANADA WWW: http://www.quist.on.ca
qmail-qfilter: generic qmail-queue filter front-end
Greetings. I have just put the first release of qmail-qfilter into: http://em.ca/~bruceg/qmail-qfilter/ This is a front end for qmail-queue that can send the body of the message through one or more filters, such as qmail-inject or new-inject. See the README and man page for more details. -- Bruce Guenter [EMAIL PROTECTED] http://em.ca/~bruceg/
