Custom Query (330 matches)


Show under each result:

Results (52 - 54 of 330)

Ticket Resolution Summary Owner Reporter
#335 wontfix Couple config questions for email2trac bas adrya.stembridge@…

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  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 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>


project: /www/virtualhosts/trac
debug: 0
black_list: MAILER-DAEMON@
drop_spam : 1
drop_alternative_html_version: 1
email_quote: >
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
#265 wontfix Crash bas support@…

Hello email2trac. I observed a crash with email2trac, which I think happens when no Subject-header is given, although I'm only speculating

2011-08-03T08:02:08.975852+02:00 email2trac: Traceback (most recent call last):
2011-08-03T08:02:08.979852+02:00 email2trac:   File "/usr/bin/email2trac", line 1642, in <module>     tktparser.parse(sys.stdin)
2011-08-03T08:02:08.979852+02:00 email2trac:   File "/usr/bin/email2trac", line 961, in parse m.replace_header('Subject', m['Subject'].replace('\r', '').replace('\n', ''))
2011-08-03T08:02:08.979852+02:00 email2trac: AttributeError: 'NoneType' object has no attribute 'replace'

This is the standard package from Debian lenny. Not sure which version number that is.

#63 fixed Crash when parsing X-Spam-Score headers with no score bas email2trac@…

Given a non-spam email, i.e. the X-Spam-Score header is present, but has no value, the script will crash with:

Traceback (most recent call last):
  File "/usr/bin/email2trac", line 1137, in ?     tktparser.parse(sys.stdin)
  File "/usr/bin/email2trac", line 710, in parse     component =  self.spam(m)
  File "/usr/bin/email2trac", line 245, in spam     number = spam_l[0].count('*')
IndexError: list index out of range

Patch as follows:

--- email2trac.orig     2008-05-29 15:02:15.000000000 -0700
+++ email2trac  2008-05-29 15:04:09.000000000 -0700
@@ -242,7 +242,10 @@
                spam = False
                if message.has_key('X-Spam-Score'):
                        spam_l = string.split(message['X-Spam-Score'])
-                       number = spam_l[0].count('*')
+                       if len(spam_l) == 0:
+                               number = 0
+                       else:
+                               number = spam_l[0].count('*')
                        if number >= self.SPAM_LEVEL:
                                spam = True
Note: See TracQuery for help on using queries.