Custom Query (332 matches)
Results (277 - 279 of 332)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#305 | fixed | email2trac raises exception for ticket update when agilo is installed | bas | smcclure@… |
Description |
I have trac version 0.12.0 and agilo 0.9.5. When I ran email2trac to update a ticket I had a traceback. I fixed it with this patch: $ diff email2trac email2trac.orig 982,987d981 < # Agilo specific modifications < from agilo.utils.config import AgiloConfig < if AgiloConfig(self.env).is_agilo_enabled: < from agilo.ticket.model import AgiloTicket < tkt = AgiloTicket(self.env, self.id, self.db) < 1217,1222d1210 < # Agilo specific modifications < from agilo.utils.config import AgiloConfig < if AgiloConfig(self.env).is_agilo_enabled: < from agilo.ticket.model import AgiloTicket < tkt = AgiloTicket(self.env) < |
|||
#308 | fixed | Problems with run_email2trac and no logging possible | bas | kmartinka@… |
Description |
Hello, I'm trying to figure out how to configure email2trac with fetchmail, but I'm unable to get it working if the .fetchmailrc is set to : mda "/usr/local/bin/run_email2trac" but it works, if I have set the following line : mda "/usr/local/bin/email2trac" Unfortunately it imports all emails in to TRAC :(, even from unathorised users or previously deleted users (removed from permissions, but it seems, that since they are still in DB the email2trac resolves it)
It does not log(!) and it does ignore any permissions in TRAC.. It imports every email and it does not create the log file. The fetchmail is being run under the account which has the permissions to the home directory.. (trac) Please help me with the three installation issues :
(Trac version 0.12.2) }}} |
|||
#309 | fixed | Test | bas | bas@… |