On Tue, Apr 20, 2010 at 11:07:13AM -0700, Michael Elkins wrote:
On Tue, Apr 20, 2010 at 07:46:23PM +0200, Gary wrote:
If you can produce a test muttrc and a test email message that exhibit the
problem
Well, it applies to outgoing email, so the latter doesn't really apply,
but I can send my
* Gary on Sunday, May 02, 2010 at 16:28:59 +0200
On Tue, Apr 20, 2010 at 11:07:13AM -0700, Michael Elkins wrote:
The idea is to create a rc file and set of actions that demonstrate the
problem. It could be just a bogus mailing list address if you prefer.
Okay. I have cut it down as much as
Christian Ebert writes:
* Gary on Sunday, May 02, 2010 at 16:28:59 +0200
On Tue, Apr 20, 2010 at 11:07:13AM -0700, Michael Elkins wrote:
The idea is to create a rc file and set of actions that demonstrate the
problem. It could be just a bogus mailing list address if you prefer.
Okay. I
On Mon, Apr 19, 2010 at 08:42:58PM +0200, Gary wrote:
I may be wrong, but despite set followup_to=yes in my config file, and
lists + subscribe entries, mutt doesn't seem to be generating this
header correctly. I've got some extra ones being created by my_hdr, but
I don't think that could be
On Mon, Apr 19, 2010 at 11:14:35PM +0200, Gary wrote:
Please let me know what you want and I will try to.
If you can produce a test muttrc and a test email message that exhibit the
problem, that would be helping for debugging. Typically you want something
standalone, so you will invoke it
