After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 610263 - Evolution: It seems not to be possi...
Evolution: It seems not to be possi...
Status: RESOLVED DUPLICATE of bug 568311
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.28.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-02-17 14:25 UTC by sp1
Modified: 2010-02-18 16:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description sp1 2010-02-17 14:25:22 UTC 
It seems not to be possible to send Html-Mails with a special font (e.g. Sans Sarif, Helvetica, Arial). Setting up fonts in Evolution-settings effects only, how Html-mails are *displayed* in that single Evolution-installation. It has absolutely no effect on how the message is displayed at the receipients mail client. In fact it seems, that Evolution even deletes all font-face- and font-size-tags in outgoing e-mails (Means: If you receive a html-mail written in Arial and you reply to this mail, all font-face=Arial-tags are removed!)

To conlcude: It seems that it is not possible to send a Html-Mail with Arial/Helvetica-text. 

This is a very big DISADVANTAGE when using evolution for commercial issues! In other mail-clients Html-mails without font-face are displayed in TimesNewRoman, what makes them look very old fashioned!

Maybe someone can fix this bug?


Distribution: openSUSE 11.2 (x86_64)
Gnome Release: 2.28.2 (null) (SUSE)
BugBuddy Version: 2.28.0
Comment 1 André Klapper 2010-02-18 16:04:11 UTC 
Same as bug 568311, hence marking as duplicate. Please do not add any comments
to bug 568311 that do not add any additional technical value - "I have this
problem too" comments only create bugmail noise. Thanks a lot!

*** This bug has been marked as a duplicate of bug 568311 ***