Re: not to set message id in outgoing email
On 16Feb2021 09:37, Shehu Dikko wrote: >* Cameron Simpson [20210216 09:02:36]: >>On 15Feb2021 21:53, Shehu Dikko wrote: >>>* Peng Yu [20210203 20:23:18]: >>>>I want the first MTA add one, instead of using the one generated by >>>>mutt. >>> >>>One way to get what you want is to use esmtp: >>> >>># muttrc >>>set sendmail="/usr/bin/esmtp" >>> >>># esmtprc >>> [...] >>> message_id = disabled >>> [...] >> >>Does that actually strip the one from mutt, or just prevent esmtp from >>_adding on if missing_. Peng Yu is trying to stop mutt adding a message >>id. [...] > >As you can see from the User-Agent and Message-ID strings of this >message, it does indeed strip the one from mutt. Aha. Thank you. - Cameron Simpson
Re: Marking as unread when moving mail to another folder
On 16Feb2021 11:31, Sam Kuper wrote: >On Thu, Jul 16, 2020 at 10:57:13AM +0200, Kai Weber wrote: >> I have a save-hook defined to move all mail into a certain folder. >> >> save-hook "~A" +personal/Archive >> >> Very often I want to move the mail into the archive without opening the >> mail at all but then the mail ends up as unread in the archive. >> >> I want to mark the mail as "read" when moving. How could I achieve this? >> I guess a macro could do it? Should I get rid of the save-hook? Does it matter if its unread in the archive? I guess to you it does. Do you want to mark _everything_ in the archive as unread? Maybe it would be quicker with a folder-hook which matches your archive folder and marks everything unread as read on entry to the folder. >This macro may do what you want. It marks mail as "read" and moves it >to the $record file. > >Note that it makes use of `<`, which is Mutt's built-in shortcut for the >$record file. Note: I missed this remark, thought it was a typo :-) So the OP might want that replaced with +personal/Archive. ># Unlike index mode, pager mode does not accept this macro without ># an initial ``. So we need two variants of this macro, one ># for each mode. >macro index ss"set > auto_tag=yesnauto_tag=noy" >macro pager ss "set > auto_tag=yesn auto_tag=noy" > >If anyone reading this knows of a better solution, please share it. Remarks: I usually spell the pager macro like this: macro pager ss "ss" which avoids a lot of repetition. I rarely end macros with , it shows things down and I like to only sync when intended, via the $ keystroke. I wouldn't fiddle with auto_tag, I'd just preceed things with , since you seem to have made this conditional on beging tagged anyway. In principle, fiddling an option requires unfiddling it at the end of the macro with the usual cumbersome set $my_option=$option set option=whatever ... do stuff set option=$my_option shuffle embedded in the macro. If you set wait_key=no during the macro you can drop the "y" you have embedded after the save. Cheers, Cameron Simpson
Re: Marking as unread when moving mail to another folder
On Thu, Jul 16, 2020 at 10:57:13AM +0200, Kai Weber wrote: > I have a save-hook defined to move all mail into a certain folder. > > save-hook "~A" +personal/Archive > > Very often I want to move the mail into the archive without opening the > mail at all but then the mail ends up as unread in the archive. > > I want to mark the mail as "read" when moving. How could I achieve this? > I guess a macro could do it? Should I get rid of the save-hook? This macro may do what you want. It marks mail as "read" and moves it to the $record file. Note that it makes use of `<`, which is Mutt's built-in shortcut for the $record file. # Unlike index mode, pager mode does not accept this macro without # an initial ``. So we need two variants of this macro, one # for each mode. macro index ss"set auto_tag=yesn
Mailman strips subject from DMARC messages (was: Re: Fwd:)
On Sat, Oct 24, 2020 at 12:49:12PM -0700, Kevin J. McCarthy wrote: > On Sat, Oct 24, 2020 at 12:24:23PM -0700, Kevin J. McCarthy wrote: >> On Sat, Oct 24, 2020 at 02:04:11PM -0400, Remco Rijnders wrote: >>> Unfortunately, the subject of such messages seems to get cleared. I >>> don't think this is something under our control but of the generous >>> people who host the mutt-users mailing list for the project. Kevin, >>> do you know if this is anything that can be changed / fixed? >> >> Whoops, I missed the fact that the wrapper removes the Subject line >> too. That's not convenient at all. Let me see if there is anything >> I can do about that. > > I didn't see any options regarding the wrapper Subject header, so I've > changed the action to munge the From address instead. Mailman's failure to retain the Subject: header when wrapping a DMARC message was a bug, and the Mailman maintainer has issued a patch: https://mail.python.org/archives/list/mailman-us...@python.org/thread/ZVM6I4UTDKHY4EKNLIBIWE4JNC2PYLIS/ -- A: When it messes up the order in which people normally read text. Q: When is top-posting a bad thing? () ASCII ribbon campaign. Please avoid HTML emails & proprietary /\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
Re: simple formatting possibilities
On Mon, Aug 31, 2020 at 01:06:48PM -0400, Mark H. Wood wrote: > Things like HTML and PDF are designed for finalized documents. PDF, yes. But historically, TimBL very much designed HTML for revisable documents. (Sadly, as was already pointed out earlier in the thread, many people are unwilling to learn how to edit HTML. TimBL accounted for numerous stumbling blocks the Web might face, but is I think still taken aback by the many regrettable vagaries of human psychology.) -- A: When it messes up the order in which people normally read text. Q: When is top-posting a bad thing? () ASCII ribbon campaign. Please avoid HTML emails & proprietary /\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
Re: not to set message id in outgoing email
* Cameron Simpson [20210216 09:02:36]: >On 15Feb2021 21:53, Shehu Dikko wrote: >>* Peng Yu [20210203 20:23:18]: >>>I want the first MTA add one, instead of using the one generated by >>>mutt. >> >>One way to get what you want is to use esmtp: >> >># muttrc >>set sendmail="/usr/bin/esmtp" >> >># esmtprc >> [...] >> message_id = disabled >> [...] > >Does that actually strip the one from mutt, or just prevent esmtp from >_adding on if missing_. Peng Yu is trying to stop mutt adding a message >id. [...] As you can see from the User-Agent and Message-ID strings of this message, it does indeed strip the one from mutt. regards, s h e h u
