Ticket #26 (new defect)

Opened 3 years ago

Last modified 2 years ago

Investigate small alternative to mutt

Reported by: lunar Assigned to: lunar
Priority: normal Milestone: 1.2
Component: metche Version: 1.1
Severity: normal Keywords:
Cc:

Description

mutt is fairly heavy compared to mailx or other small mailers. Investigate the possible problem with encoding and such.

Attachments

metche-no-mutt.patch (1.0 kB) - added by anarcat on 09/18/06 20:26:49.
naive patch to get rid of mutt

Change History

08/13/06 09:19:28 changed by anarcat

What is there to investigate? Isn't "mailx" just fine?

I would just let people bite the bullet and put mutt | mailx as a dependency. metche, at runtime, should be able to detect presence of either using whereis or at installation.

Installing mutt on certain production server is a problem for me, and that is blocking the deployment of metche here.

09/16/06 11:47:38 changed by intrigeri

  • milestone changed from 1.1 to 1.2.

09/18/06 20:26:49 changed by anarcat

  • attachment metche-no-mutt.patch added.

naive patch to get rid of mutt

09/18/06 23:14:04 changed by lunar

The very first version of metche used mailx. We have switched to mutt after discovering that mailx was not able to cope with our french (iso-8859-1 encoded) changelogs.

Maybe the mailx version in Debian etch is more locale compliant and could be used instead of mailx. Tests are needed before making any changes.

09/18/06 23:23:08 changed by anarcat

I see two main things that the "mailer" should accomplish:

  1. set the proper headers
  2. encode the characters properly

I assume (1) would simply be to set a Content-Type: text/plain; charset=... where the charset would be based on the system-wide locale.

I assume that (2) would mean either: no encoding (we assume 8bit is OK) or base64 encoding.

I quote "mailer" because I think we could simply pipe through /usr/sbin/sendmail and send proper headers along the way.

10/06/06 17:23:43 changed by intrigeri

  • version changed from 1.0 to 1.1.

Even current mutt-based way has issues with charset encoding :

  • Changelog files written in a charset different from the LOCALE generate ugly metche reports
  • Thunderbird displays badly reports, even when Changelogs are encoded in the same charset as the LOCALE ; this may be due to a missing Content-Type (or similar) header.