Custom Query (332 matches)
Results (109 - 111 of 332)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #54 | fixed | Problems with email notification; in particular smtp_from | bas | r.s.hatcher@… |
| Description |
I've installed email2trac 0.13 and am using Trac 0.10.4. It exactly the utility I need and the fact it can be run from the command line is great as I'm not allowed to use mail aliases. Email notification works fine for tickets created and updated via Trac web interface. email2trac correctly enters/updates emails into the Trac system, but when it comes to emailing the notification it falls over while validating the smtp_from address specified in the trac.ini [notification] section. $ ./email2trac --project=cms < test_msg.txt
TD: Failure sending notification on creation of ticket #66: {u'f.r.user@reading.ac.uk': (550, 'Verification failed for <no-reply@reading.ac.uk>\nUnrouteable address\nSender verify failed')}
Is there a way I can stop email2trac from sending updates to the smtp_from address? The address I use is an outgoing email address only. And is a way of persuading our Helpdesk users to use the Trac interface and stop doing an email reply. Trac itself has no problems with me doing this. Alternatively, can you point me in the right direction so I might be able to modify the email2trac script to stop it trying to email the stmp_from address? I can't see where the list of email addresses is assembled. Thanks. Rosalyn |
|||
| #177 | fixed | Problem parsing Attachment Filename | bas | obwandner@… |
| Description |
After Fetching a Mail, with email2trac we have sometimes following Problem with the filename of the attachments: =?iso-8859-1?Q?Erl=E4uterung=2Epdf?= should by named as Erläuterung.pdf Mail send by MS-Outlook of Exchange to postfix the fetch by fetchmail email2trac on a Debian Machine. |
|||
| #323 | invalid | priority keyword from email subject line does not get set | bas | milki |
| Description |
Sending an email using the subject line to set the priority doesn't work for me. We have priority configured as follows: 0 Drop everything 1 Do now 2 Do next 3 Nice to have I've attempted to set any number of values for the priority in the subject line #?priority=1 #?priority=1 Do now #?priority=high #?priority="1 Do now" Whatever I try, I can't get the new trac tickets to have the priority I want. I have been able to set other properties: owner, component, type, etc. Only version fails to be set to a non-default value. Suggestions on what I'm doing wrong or if there's a bug? |
|||
