Custom Query (332 matches)
Results (310 - 312 of 332)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #329 | fixed | initial import of threaded mbox to ticket, and subsequent upgrades | bas | pinto@… |
| Description |
Hi there, I'm in the initial stages of educating myself on what can be expected from email2trac. I'd like to do a bulk import of the whole support mailbox, and have the tickets threads recognized and build from the threads in the mailbox, using this syntax: email2trac < ~/mail/support However the whole mailbox is being imported as a single new ticket, including the raw attachments. Subsequently I'd like to run the same above command every couple of minutes (via a crontab), and have the utility update trac only with the new emails or replies. However the whole mailbox is being imported as a single new ticket again. Reflecting back, the suggested installation exercise kept creating a new ticket every time I ran it again, and that was completely unexpected. email2trac < msg.txt Am I expecting too much? Thanks Jaime |
|||
| #330 | fixed | Agilo detection does not work patch | bas | sebastian@… |
| Description |
Hey, the Agilo support detction does not work with the current agilo trac plugin. They changed Ticket to AgiloTicket?. I think therefore the detction code has to be changed to import AgiloTicket? instead. Greeting Sebastian |
|||
| #333 | fixed | replying email not working | bas | kshetriamrit@… |
| Description |
After replying email sent from trac, no comment is seen. Also I see a lot of *trac.email2trac* files in my /tmp folder that contains message replied to notification mail. |
|||
