On 17.01.2011 15:48, Sam Varshavchik wrote:
You should have $SENDER available.
And, once again, make sure that you fully understand how all your
manufactured shell scripting needs to quote its variables. Otherwise,
you'll have an exploitable security hole on your hands.
Well, I didn't see the
On 1/18/2011 3:00 AM, Jani Ollikainen wrote:
On 17.01.2011 15:48, Sam Varshavchik wrote:
You should have $SENDER available.
And, once again, make sure that you fully understand how all your
manufactured shell scripting needs to quote its variables. Otherwise,
you'll have an exploitable
On 15.01.2011 03:40, Sam Varshavchik wrote:
# cat testmail.txt | /usr/lib/courier/bin/mailbot -T forward -c UTF-8
-t reply.txt -A 'From: u...@example.org' -s 'Test'
511 Headers specify no receipients.
sendmail: Unable to submit message.
But without -T parameters it works
# cat testmail.txt
Jani Ollikainen writes:
On 15.01.2011 03:40, Sam Varshavchik wrote:
# cat testmail.txt | /usr/lib/courier/bin/mailbot -T forward -c UTF-8
-t reply.txt -A 'From: u...@example.org' -s 'Test'
511 Headers specify no receipients.
sendmail: Unable to submit message.
But without -T parameters it
Hi,
Noticed that there's -T in mailbot and I think that those sounds better
to have the original message as attachment than directly reply to it.
As if the original message is long, reader might not notice the
reply text.
Did some testing:
# cat testmail.txt | /usr/lib/courier/bin/mailbot -T
Jani Ollikainen writes:
Hi,
Noticed that there's -T in mailbot and I think that those sounds better
to have the original message as attachment than directly reply to it.
As if the original message is long, reader might not notice the
reply text.
Did some testing:
# cat testmail.txt |
