I don’t see anything at first glance that would make this .qmail-default
file particularly horrible from a security point of view. It pretty much
fully automates queue/email integration - you just make the queue and
away you go. This works with queuename-action where action defaults to
correspond if none is specified. Works for me on my debian system on
which sh->ash.
|/usr/bin/preline /import/unit/home/rt/bin/rt-mailgate --queue
${EXT%%-*} --action ${EXT2:-correspond}
Perhaps this deserves a spot in the FAQ and/or install docs, provided
there’s no glaring security holes?
Speaking of queues, I realised I could have both client and generic
queues so I did exactly that… ie:
client1
client2
accounts
sales
etc.
This seems to be working nicely so far. I expect that RT2 will
revolutionise the way we do business - keep up the good work!
Sam
Sam Johnston
Australian Online Solutions
1300 132 809
I don’t see anything at first glance that would make this .qmail-default
file particularly horrible from a security point of view. It pretty much
fully automates queue/email integration - you just make the queue and
away you go. This works with queuename-action where action defaults to
correspond if none is specified. Works for me on my debian system on
which sh->ash.
|/usr/bin/preline /import/unit/home/rt/bin/rt-mailgate --queue
${EXT%%-*} --action ${EXT2:-correspond}
Perhaps this deserves a spot in the FAQ and/or install docs, provided
there’s no glaring security holes?
I certainly don’t feel like auditing qmail to find out, but that’s
certainly poor practice. Why not use the --queue-from-extension option
to rt-mailgate (after fixing the current postfix-only code, or waiting
for me to do same)?
-Rich
Rich Lafferty --------------±----------------------------------------------
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | Save The Pacific Northwest Tree Octopus
rich@lafferty.ca -----------±----------------------------------------------