Custom Query (332 matches)
Results (226 - 228 of 332)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#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) }}} |
|||
#100 | fixed | problems with ticket follow-up | bas | zygis@… |
Description |
im having problems posting follow-ups to tickets from emails. email2trac works to create new tickets from email, so i dont think there's a problem there, however the follow-ups just never appear. any ideas where i can look for more clues? email2trac is working with fetchmail on a single project. here's my email2trac.conf [DEFAULT] project: /d/trac/darqenv debug: 2 umask: 022 reply_all : 1 mailto_link: 0 email_comment: > email_header: 0 trac_version: 0.11 enable_syslog : 1 alternate_notify_template: 0 verbatim_format: 0 strip_signature: 1 use_textwrap: 70 ticket_update: 1 output of fetchmail fetchmail: 1 message for trac@example.com at mail.example.com. .TD: saving email to /tmp/msg.txt TD: part1: Content-Type: text/plain TD: part1: filename: None TD: this part is not multipart TD: writing part1 (/tmp/part1) TD: saving email to /tmp/tmpEuThG_.email2trac fetchmail: reading message trac@example.com@mail.example.com:1 of 1 (1392 header octets) (149 body octets) flushed read:errno=0 |
|||
#207 | fixed | Problems with unicode-attachments in 1.4.5 | bas | hju@… |
Description |
Emails with attachments containing unicode-charcters in filename are not handled in a usable way. (see attached screenshots) the attachments could not be opened No handler matched request to /attachment/ticket/451/=?utf-8?Q?Budget_2010_-_Ger=C3=A4teliste_-_Danz?= =?utf-8?Q?ig.xls?= Excample-Filename: Budget 2010 - Geräteliste - Warschau.xls |