Custom Query (332 matches)
Results (214 - 216 of 332)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#225 | fixed | Attribute Error(s) | bas | anonymous |
Description |
I am receiving the following after running python email2trac.py < C:\Inetpub\mailroot\Drop\msg.eml from the command prompt: Traceback (most recent call last):
active)
t
ect_unixsocket
AttributeError?: 'module' object has no attribute 'AF_UNIX' Error in atexit._run_exitfuncs: Traceback (most recent call last):
run_exitfuncs
down
AttributeError?: SysLogHandler? instance has no attribute 'socket' Error in sys.exitfunc: Traceback (most recent call last):
run_exitfuncs
down
AttributeError?: SysLogHandler? instance has no attribute 'socket' Here's my environment: Trac running on Windows Server 2003, SP 2, x86 That server is not running Exchange, so I installed the built-in SMTP server. I followed the directions at https://subtrac.sara.nl/oss/email2trac/wiki/Email2tracInstallation/Windows (downloaded the three files, renamed them, put them in C:\Program Files\BitNami? Trac Stack\python\, and changed #configfile = '@email2trac_conf@' to configfile = 'email2trac.conf') My overall goal is to be able to send emails to an email address, and have those emails generate a ticket within Trac. I am able to see that my email made it to C:\Inetpub\mailroot\Drop\, but it looks like the email is not being processed. My guess is that there is an issue with the configuration of a few files, but I'm at a loss as to a fix, as I am a complete noob. Does anyone have any thoughts? |
|||
#226 | fixed | More versatile workflow : compatibility with AdvancedTicketWorkflowPlugin | bas | Frédéric DUARTE <f.duarte@…> |
Description |
It would be useful to get email2trac aware of the 'workflow' entry of trac.ini's [ticket] section. It would help to trigger custom workflow operations that are not handled by Trac's ConfigurableTicketWorkflow. |
|||
#227 | fixed | [patch] allow '_' in inline properties | bas | thomas.moschny@… |
Description |
The subject already says it. Is there a reason to not allow some more characters, especially '_' for the name of inline properties? We have custom fields which contain them, and I want people to be able to set these fields via mail. |