Greetings from a happy new qmail user (first post),
** qmail 1.03
** linux-2.2.16-:i386-:-:pentium-:-
As part of a ritualistic adventure to the edges of qmail sanity, I
brazenly created a fifo to be read by a perl "daemon".
Using a .qmail file in a real-user's home dir that read:
./inmail.pipe
(BTW - I'm also using fastforward, but this is an actual user account
without aliasing)
Long story short -- qmail wrote to the pipe just fine but justifiably
barfs at the end. (Uhh, stat call or something?)
<error>
Jul 20 10:43:03 mn qmail: 964089783.401047 delivery 3225: deferral:
Unable_to_write_./inmail.pipe:_invalid_argument._(#4.3.0)/
</error>
So .. I proceeded to create a writer.sh:
#!/bin/sh
cat > ./inmail.pipe
and modified .qmail:
| ./writer.sh
This appears to work fine, as I had hoped.
Why would I do such a crazy thing in the first place?
I've compiled with QUEUE_EXTRA and plan to use it to mangle
incoming/outgoing messages for [EMAIL PROTECTED] & [EMAIL PROTECTED]
More precisely, I plan to attach ticket # headers, update the "bug
reports" database, and route incoming replies to the sales/support
person who was first to respond. Blah blah blah .. using Perl.
I switched to qmail 1) specifically for QUEUE_EXTRA, 2) security,
security, security, and 3) out of desperation and displeasure with
sendmail (Sorry sendmail hackers).
So why the FIFO? I'm concerned about spawning many-a-Perl at 2.5MB
each on my lowly P75 DNS/Firewall/qmail box. So the idea of a single
reader is attractive ..
Is that crazy? Suggestions? (Other than "Pentium II's are cheap") :-)
-Jay J
p.s. Many thanks for qmail & friends
