bad-formatted e-mail notification

[anonymous]

I just updated from Trunk… You can see that top part of e-mail is not looking goood. Below is example of bad-formatted e-mail notification:

---

#926: Rx Ring desing and implementation——————————————————-+——————————————————— Id: 926 | Status: new Component: HAL | Modified: Fri May 21 09:51:05 2004 Severity: normal | Milestone: 2.0 Priority: P1 | Version: 1.0 Owner: dmitry@xxxx | Reporter: dmitry@xxxxx——————————————————-+———————————————————As above

keys:

• port steering
• optimized locking
• include smart pool-based memory management
• incapsulation into HAL channel abstraction
• Ring statistics
• MSI if available

---

Dmitry

[Jonas Borgström]

Can you submit the example again and this time inside a code block like this:

{{{
In here
}}}

Or as a screenshot?

[anonymous]

Here it is:

#926: Rx Ring desing and implementation-------------------------------------+--------------------------------------       Id:  926                      |      Status:  new                     Component:  HAL                      |    Modified:  Fri May 21 09:51:05 2004 Severity:  normal                   |   Milestone:  2.0                      Priority:  P1                       |     Version:  1.0                         Owner:  dmitry@xxxx  |    Reporter:  dmitry@xxxx -------------------------------------+--------------------------------------As above

keys:

    * port steering
    * optimized locking
    * include smart pool-based memory management
    * incapsulation into HAL channel abstraction
    * Ring statistics 
    * MSI if available



-- Ticket URL: <http://10.16.16.227/cgi-bin/trac.cgi/ticket/926>xxx <http://trac.edgewall.com/>

[daniel]

I'm unable to reproduce this. However, notification now uses os.linesep instead of '\n' in emails. Possibly, this will fix your problem.

Fixed in [668].

[anonymous]

still the same behavior with 0.7.1 environment: RedHat 9.0/sendmail

[daniel]

[740] changes emails so all lines are terminated by CRLF rather than os.linesep.

This ought to fix the problem.

If not, please attach a sample problematic email to this ticket.