Custom Query (332 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (328 - 330 of 332)

Ticket Resolution Summary Owner Reporter
#282 Installation question bas akou@…
Description
Hello,

I am currently evaluating email2trac to use with our current trac setup. Our
current trac setup uses virtualenv and we would like to keep any python
packages installed within and use pip as our primary install mechanism.
After looking at the installation, it seems that I can write a standard
python setup.py file to do the installation for me. I was wondering if there
was any reason/dependencies for using make and packages that I am not aware
was and am
I correct in assuming I can write a setup.py to do the work? Any help is
appreciated

Thank you so much for your help!

- Andrew
#335 wontfix Couple config questions for email2trac bas adrya.stembridge@…
Description
Hi,

I have postfix and dovetail installed and working.  I can send a message
from a remote system to the mail server, and I receive the message as
expected.   My trac installation is at /www/virtualhosts/trac.

I installed email2trac using the Install guide (made an RPM and used yum
https://oss.trac.surfsara.nl/email2trac/wiki/Email2tracInstallation).  No
errors on install - everything looks clean.   My config file is included at
the bottom of this message.


*First question.*

The example *project* option in email2trac.conf shows "/data/trac/jouvin".
  If I put "/www/virtualhosts/trac" I get an error when testing email2trac:

[tmp]# email2trac --project trac < msg.txt
Not a valid project name: trac, valid names are: []
or set parentdir in the [DEFAULT] section


What should I have for *project*?


*Second question.*
I'm a little unclear on setting up Postfix to work with email2trac.

In the mail server documentation there is this hint under Postfix:  "Please
note that postfix seemingly runs commands from the alias definition file as
user "nobody", even if the rest of it is running as user "postfix".  *So
please assure that the MTA_USER is set to nobody, not to postfix!*"

In the Install documentation, I see this:
"*Pay attention to the MTA_USER and TRAC_USER, they are not something you
can ignore! The default are for MTA (postfix) and TRAC_USER (apache2)*"

And that's how I set up configure.in prior to building/installing.

*What should MTA_USER be, if not postfix *(my mail server)*? *



*Third question*
Do you have a working postfix/email2trac install, and if so could you copy
one of your trac alias lines?  I'm not sure what user should go here.

tracproj: "|/usr/bin/email2trac <see command line options>







/etc/email2trac.conf


[DEFAULT]
project: /www/virtualhosts/trac
debug: 0
black_list: MAILER-DAEMON@
drop_spam : 1
drop_alternative_html_version: 1
email_quote: >
html2text_cmd:
ignore_trac_user_settings: 0
inline_properties: 1
reply_all : 0
spam_level: 5
strip_quotes: 0
strip_signature: 0
ticket_update: 1
ticket_update_by_subject: 1
umask: 022
verbatim_format: 1
reply_all: 1
#117 fixed propagate fail to calling environment bas admin-egon@…
Description

given a setup where fetchmail uses mda "...run_email2trac" the mda should give a non-zero return code on failure...

Note: See TracQuery for help on using queries.