Custom Query (332 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (13 - 15 of 332)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Resolution Summary Owner Reporter
#362 fixed Case for "mail delivery failed" bas kshetriamrit@…
Description

I have a case where there are multiple recipient for a mail. But one of the email is returning "mail delivery failed" email which is again used to comment on the ticket.

And this process is going in a loop.

Do we have any mechanism to control this? I searched but found nothing.

Thanks

#354 fixed qmail configuration example bas ttt@…
Description
Hello!


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



= qmail Configuration

This configuration was based on the following references:
 * man qmail-users
 * http://www.lifewithqmail.org/lwq.html#virtual-domains
 * http://www.lifewithqmail.org/lwq.html#dot-qmail-files
 * https://oss.trac.surfsara.nl/email2trac/wiki/Email2tracMta#QmailSetup

Configuration changes:

 * To accept emails for the new domain:
{{{
root@server:/etc/qmail# echo trac.server.net >> rcpthosts
}}}

 * To declare the new domain as a virtual domain, to ensure namespace
separation of local usernames:
{{{
root@server:/etc/qmail# echo trac.server.net:trac-server-net >>
virtualdomains
}}}

 * 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
's|^\.$|+trac-server-net-:www-data:33:33:/servers/trac/email2trac:-::\n.|'
users/assign
}}}

 * 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/virtualenv/bin/python
/servers/trac/email2trac/bin/email2trac --project=one' > .qmail-one
root@server:/servers/trac/email2trac# echo '|/usr/bin/preline
/servers/trac/virtualenv/bin/python
/servers/trac/email2trac/bin/email2trac --project=two' > .qmail-two
root@server:/servers/trac/email2trac# echo '|/usr/bin/preline
/servers/trac/virtualenv/bin/python
/servers/trac/email2trac/bin/email2trac --project=three' > .qmail-three
}}}
#346 fixed too eager subject parsing in ticket update bas thomas.moschny@…
Description

For this example subject

[hic] #1529?owner=bas,priority=medium: Re: LRZ

the fields part is parsed as:

owner=bas,priority=medium: Re

so in the end, the ticket field priority would be set to

medium: Re

This can be easily fixed:

  • email2trac.py.in

     
    18591859        #
    18601860        ticket_regex = r'''
    18611861            (?P<new_fields>[#][?].*)
    1862             |(?P<reply>(?P<id>[#][\d]+)(?P<fields>\?.*)?:)
     1862            |(?P<reply>(?P<id>[#][\d]+)(?P<fields>\?[^:]*)?:)
    18631863            '''
    18641864
    18651865        ## Check if  FullBlogPlugin is installed
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note: See TracQuery for help on using queries.