Summary | Vacation messages don't declare encoding |
Queue | Ingo |
Queue Version | 1.0.1 |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | jan (at) horde (dot) org |
Requester | alex (at) segv (dot) de |
Created | 06/13/2006 (6939 days ago) |
Due | |
Updated | 02/28/2007 (6679 days ago) |
Assigned | 06/21/2006 (6931 days ago) |
Resolved | 02/28/2007 (6679 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
Assigned to Jan Schneider
Taken from
State ⇒ Resolved
still uses the vacation program from unix.
still uses the vacation program from unix.
doesn't build a valid mime message.
can't encode it any differently there. If it's possible to embed a
mime message into .vacation.msg let me know and I'll rewrite my patch.
this isn't a patch against ingo, but one against vacation-h3. Which
still uses the vacation program from unix.
doesn't build a valid mime message.
New Attachment: forwards.diff
encoding is not a good idea. And your patch hardcodes utf-8, it
should use NLS::getCharset() instead.
UTF-8 site, plus latin1 requirement for a .vacation.msg... bad when
people try to use french characters for example.
Fix is easy enough
Assigned to
State ⇒ Assigned
encoding is not a good idea. And your patch hardcodes utf-8, it should
use NLS::getCharset() instead.
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Vacation messages don't declare encoding
Queue ⇒ Ingo
New Attachment: vacation_encoding.patch
State ⇒ Unconfirmed
vacation messages doesn't declare the encoding of the mail.
E.g. if you use german umlaute in the vacation mail, it is sent
encoded in unicode but not declared as such. Some mailers like mutt
assume the mail is encoded in ISO-8859-1 and will print garbage.
Suggested fix:
Add the headers:
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
To the formail code.
The attached patch does that.