Custom Query (330 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (34 - 36 of 330)

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Ticket Resolution Summary Owner Reporter
#38 fixed integrityerror bas bastiaans@…
Description
This email is sent by logcheck. If you wish to no-longer receive it,
you can either deinstall the logcheck package or modify its
configuration file (/etc/logcheck/logcheck.conf).

System Events
=-=-=-=-=-=-=
Dec 14 15:45:41 subtrac email2trac: etype = _sqlite.IntegrityError, evalue = columns ticket, time, field are not unique
Dec 14 15:45:41 subtrac email2trac: Traceback (most recent call last):
Dec 14 15:45:41 subtrac email2trac:   File "/usr/bin/email2trac", line 1071, in ?     tktparser.parse(sys.stdin)
Dec 14 15:45:41 subtrac email2trac:   File "/usr/bin/email2trac", line 671, in parse     if self.ticket_update(m):
Dec 14 15:45:41 subtrac email2trac:   File "/usr/bin/email2trac", line 542, in ticket_update     tkt.save_changes(self.author, body_text, when)
Dec 14 15:45:41 subtrac email2trac:   File "/usr/lib/python2.3/site-packages/trac/ticket/model.py", line 250, in save_changes     (self.id, when, author, cnum, comment))
Dec 14 15:45:41 subtrac email2trac:   File "/usr/lib/python2.3/site-packages/trac/db/util.py", line 50, in execute     return self.cursor.execute(sql_escape_percent(sql), args)
Dec 14 15:45:41 subtrac email2trac:   File "/usr/lib/python2.3/site-packages/sqlite/main.py", line 255, in execute     self.rs = self.con.db.execute(SQL % parms)
Dec 14 15:45:41 subtrac email2trac: IntegrityError: columns ticket, time, field are not unique

_______________________________________________
Rc_root mailing list
Rc_root@mailman.rc.sara.nl
http://mailman.rc.sara.nl/cgi-bin/mailman/listinfo/rc_root
#39 fixed blacklisting, check for case insensitive mailer-daemon@ bas jodok@…
Description

not all mailer-daemons specify ther e-mail adress in uppercase letters. re.IGNORECASE should be included.

        def blacklisted_from(self):
                FROM_RE = re.compile(r"""
                    MAILER-DAEMON@
                    """, re.VERBOSE|re.IGNORECASE)
                result =  FROM_RE.search(self.email_addr)
                if result:
                        return True
                else:
                        return False

                 """, re.VERBOSE|re.IGNORECASE)
#40 fixed Lost in config - emails not arriving at trac bas Johan
Description

I've read and reread the docs, but I'm obviously missing something. I can't get email2trac setup properly.

running email2trac --project=alarmsystem < msg.txt produces the message TD: saving email to /tmp/tmp6TmF-f.email2trac - I don't have write access to /var/lib/trac/alarmsystem/db/, fair enough. If I run the command as root it works, and I get the new ticket in trac.

It's after this I'm lost, when trying to send an email to create the ticket.

What address does it get sent to? Should that address be a user on the system? An existing user? A new user?

As far as I understand it, I have fetchmail fetching mail from the server, and postfix delivers it. Should I use:

bugs: | "/usr/local/bin/run_email2trac --project=alarmsystem" - for postfix

or

mda "/usr/local/bin/run_email2trac" - for fetchmail

The mta_user needs to be configured for each one, and I've checked that that's set correctly when I try this.

So far I've tried creating a new email - bugs@.org.uk, and a new user - bugs - who recieves the email. This works, it's simple enough for me to handle!

I add the alias in postfix, and nothing actually happens. The user bugs still recieves the emails without them appearing in trac. If I change the alias to do something else with the emails, such as forward them to someone else, that works as anticipated. So postfix is doing its job, I think.

What step have I missed? What am I not understanding?

Ubuntu feisty trac 0.10.3-1 email2trac 0.10

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Note: See TracQuery for help on using queries.