Custom Query (332 matches)
Results (43 - 45 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) }}} |
|||
#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) < |
|||
#304 | fixed | None and None-1 encoding problem | bas | szybalski@… |
Description |
Hello, While using email2trac ve been running a email2trac plugin for a while, and this is a first time I'm having trouble with trac not being able to decoded the attachment properly. One of the users is using 3rd party web application to send an attachment. In trac it shows up as None-1 (236.7kb), but if I cc myself on the email "thunderbird" opens it without any problems. When I open the none-1 it looks like text/binary version of a pdf. Here is a part of the email from thunderbird. Is anybody familiar with email content types to tell me what could be wrong with it? Is this a email2trac issue or formatting issue on the person that sends it. Note that if I forward the same email using Thunderbird it attaches just fine.: ..... ..email headers... Date: 3 Oct 2012 15:32:14 -0500 Content-Type: multipart/mixed; boundary=--boundary_4_cc760ab8-c89d-410d-9943-8117bbe33377 Message-ID: <AMC1IDk4JdxVHYEuZFk0000109b@…> X-OriginalArrivalTime?: 03 Oct 2012 20:32:21.0891 (UTC) FILETIME=[30CBAD30:01CDA1A6] Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable <html><body style=3D"font-family : arial, tahoma, sans-serif; fon= t-size : 10pt"></body></html> Content-Type: application/octet-stream; name=CompanyApp?.pdf Content-Transfer-Encoding: base64 Content-Disposition: attachment JVBERi0xLjYNCg0KODggMCBvYmoNCjw8DQovRSA2NjI2OQ0KL0ggWyA2NzQzIDQy NCBdDQovTCAyNDIzODQNCi9MaW5lYXJpemVkIDENCi9OIDENCi9PIDkyDQovVCAy NDA1NzMNCj4+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KZW5kb2JqDQoNCnhyZWYNCjg4 ....... ...... MCBuDQowMDAwMjM5ODE1IDAwMDAwIG4NCjAwMDAyNDAxODkgMDAwMDAg bg0KdHJhaWxlcg0KPDwNCi9TaXplIDg4DQo+Pg0Kc3RhcnR4cmVmDQoxODQNCiUl RU9GDQo= And in trac the "comapnyapp.pdf" is called none-1 and when opened it shows: %PDF-1.6 2 3 88 0 obj 4 << 5 /E 66269 6 /H [ 6743 424 ] 7 /L 242384 8 /Linearized 1 9 /N 1 10 /O 92 11 /T 240573 12 >> 13 endobj 14 15 xref 16 88 206 17 0000000012 00000 n ........ original header file that does not work. <html><body style=3D"font-family : arial, tahoma, sans-serif; fon= t-size : 10pt"></body></html> Content-Type: application/octet-stream; name=CompanyApp?.pdf Content-Transfer-Encoding: base64 Content-Disposition: attachment header files from Thunderbird after I forward the email to truck from Thunderbird. This will be encoded correctly. Content-Type: multipart/mixed;
This is a multi-part message in MIME format. Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Type: application/octet-stream;
Content-Transfer-Encoding: base64 Content-Disposition: attachment;
|