posting news with mutt
I have a, possibly, unusual question. I find it convenient to fetch news from a remote server in large batches and store them as mbox folders, for reading with mutt. Threading works fine, so why not? Now, the question is, can I use mutt's reply to compose a good followup message? Obviously I don't expect mutt to post it -- I'll pipe it to a posting program with 'set sendmail' or something like that -- but I need it to preserve/generate the needed headers. The Newsgroups: header is less of a problem, I can generate it automatically or even manually, but I wonder if there are additional Xref- or other news-related fields that mutt will or won't be able to create. Does anyone have any advice to offer on this? -- Anatoly Vorobey, [EMAIL PROTECTED] http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton
Re: procmail rules
You, [EMAIL PROTECTED], were spotted writing this on Mon, May 29, 2000 at 07:51:56PM -0300: I've got procmail sorting my messages into folders, so that each mailing list goes to a separate folder. eg: :0: * ^[EMAIL PROTECTED] IN.mutt-users However, when someone sends a message TO: the list with a CC: to me, or the opposite, both copies end up in the list's folder. I'd like to have one copy in my inbox, and the other in the list's folder. Anyone knows how to solve this? Thanks Almost every mailing list adds a unique header when it processes the messag; you need to filter on that header. Almost always it will be Sender: however, recently Mailing-List: became popular which is even better. Thus, for mutt-users: :0: * ^Sender: [EMAIL PROTECTED] IN.mutt-users -- Anatoly Vorobey, [EMAIL PROTECTED] http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton
Sender: vs From:
LISTSERV appears to prefer Sender: to From: (incorrectly?). My From: is always set to [EMAIL PROTECTED] (a forwarding service) and Sender: varies as I send mail from different machines. As a result, I can't seem to subscribe myself ([EMAIL PROTECTED]) to a LISTSERV mailing list (moreover, if I succeeded, I suspect LISTSERV would not accept my messages to the list for the same reason) - LISTSERV subscribes mellon@[specific machine] instead. It appears that mutt, rather than sendmail, is inserting Sender: lines -- messages sent with mail(1) do not exhibit them. When I try to hardcode Sender: [EMAIL PROTECTED] via my_hdr command, mutt appears to ignore it. Help? I find it unlikely that I would be the first to stumble upon this problem, and so I apologize if this is a known question answered elsewhere. -- Anatoly Vorobey, [EMAIL PROTECTED] http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton
Charsets translation
Hello, I have a problem with mutt's insistent translating between charsets when I view messages in Russian. Such messages typically belong to the 'koi8-r' charset, yet there are three types of messages: a) With charset=iso-8859-1 incorrectely written in Content-Type: header b) With charset=koi8-r correctly written in Content-Type: header Now if my .muttrc has 'set charset=iso-8859-1' then I will see messages of type a) correctly, but messages of type b) will have ?'s instead of Russian letters. If I 'set charset=koi8-r', I will lose messages a) and will see messages b). Seems like I can't win here! Can anyone help? Thanks, Anatoly. -- Anatoly Vorobey, [EMAIL PROTECTED] http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton
