Bug 174715 - [patch] calendar(1): define Content-Type / charset when sending periodic mails
Summary: [patch] calendar(1): define Content-Type / charset when sending periodic mails
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 9.1-PRERELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-26 14:40 UTC by Thierry Thomas
Modified: 2017-12-31 22:29 UTC (History)
0 users

See Also:


Attachments
io.c.diff (2.84 KB, patch)
2012-12-26 14:40 UTC, Thierry Thomas
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Thierry Thomas freebsd_committer 2012-12-26 14:40:00 UTC
	When daily_calendar_enable is set (periodic.conf), `calenidar -a'
	is run, and sends mails with the content of calendar files.
	These calendar files may be encoded with non-ASCII character
	sets, defined by the variable LANG.
	Unfortunately, calendar always sends mails without defining any
	charset.

	If your MUA is set for the same default charset that the one
	used by your calendar files, it may seem working, and you won't
	notice anything strange. Else, the non-ASCII strings won't be
	displayed correctly.

Fix: Please check the hereunder patch. I'm not sure that this is the
	best way to do it, but you got the idea - and it works for me!
How-To-Repeat: 	- include some non-ASCII calendar files in your ~/calendar
	  (e.g. #include <calendar.french>)
	- set your MUA to a different default charset
	  (e.g. for mutt: set charset="utf-8")
	- run `calendar -a' or wait for periodic.
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:54 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped