Custom Query (332 matches)


Show under each result:

Results (94 - 96 of 332)

Ticket Resolution Summary Owner Reporter
#354 fixed qmail configuration example bas ttt@…

I would like to contribute with a full working example of qmail setup
for a multi Trac environment, making use of the parentdir configuration
option of email2trac.

You can add it all or in parts to the instructions page if you like.

Note that I could get the --virtualenv option to work for me and I had
to explicitly run the script with the Python from the desired
VirtualEnv. Maybe there is some bug in the VirtualEnv setting in
email2trac or wrong usage by me, I did not have enough time to find the
root cause and I could work around the problem.

Thank you for your effort developing and supporting this valuable
integration point between email system and Trac.

Best regards.

= qmail Configuration

This configuration was based on the following references:
 * man qmail-users

Configuration changes:

 * To accept emails for the new domain:
root@server:/etc/qmail# echo >> rcpthosts

 * To declare the new domain as a virtual domain, to ensure namespace
separation of local usernames:
root@server:/etc/qmail# echo >>

 * Add a rule to match all possible users of the new virtual domain to a
directory where per-user .qmail files determine further processing of
messages, running as www-data user:
root@server:/etc/qmail# sed -i

 * Make changes take effect:
root@server:/etc/qmail# qmail-newu
root@server:/etc/qmail# /etc/init.d/qmail restart

 * Put per-user .qmail files in place, making messages go to the
email2trac script:
root@server:/servers/trac/email2trac# echo '|/usr/bin/preline
/servers/trac/email2trac/bin/email2trac --project=one' > .qmail-one
root@server:/servers/trac/email2trac# echo '|/usr/bin/preline
/servers/trac/email2trac/bin/email2trac --project=two' > .qmail-two
root@server:/servers/trac/email2trac# echo '|/usr/bin/preline
/servers/trac/email2trac/bin/email2trac --project=three' > .qmail-three
#96 fixed QMail can't use sudo method in documentation bas sweeney@…

I'm running email2trac 0.9.40 with Qmail. I've built the application as an rpm package and installed it. My web user is apache and my QMail user is nobody. I've tested the app using the local command line method and it works:

/usr/bin/email2trac --project=info < msg.txt

However, I tried the first method of setting up Qmail and it didn't work. It fails with a return message:

preline: fatal: unable to run /usr/bin/run_email2trac --project=info: file does not exist

I'm assuming that this is the failure noted in the documentation under the Qmail heading:

And so, I try the optional method. I've added an entry to sudoers:

nobody ALL = (apache)NOPASSWORD: /usr/bin/run_email2trac

and I change the execute command in the mail user's .qmail file to the following:

|PYTHON_EGG_CACHE=/var/trac/tracenv/attachments /var/qmail/bin/preline /usr/bin/sudo -u apache /usr/bin/run_email2trac --project=info

This produces an error:

sudo: sorry, you must have a tty to run sudo

Very frustrating. What am I doing wrong?

#26 fixed Q: Able to collaborate internally on tickets before mailing a response anonymous anonymous

From a customer support perspective can ticket items be collaborated on internally (as they are currently with Trac) and then only at the end a reply specified to the original sender?

If not please consider this a feature request.


Note: See TracQuery for help on using queries.