<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.mail.mh-e.user">
    <title>gmane.mail.mh-e.user</title>
    <link>http://blog.gmane.org/gmane.mail.mh-e.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2689"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2688"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2687"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2686"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2685"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2684"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2683"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2682"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2681"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2680"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2679"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2678"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2677"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2675"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2674"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2673"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2672"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2671"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2670"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.mail.mh-e.user/2669"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2689">
    <title>Re: mh-refile-msg vs mh-thread-refile</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2689</link>
    <description>&lt;pre&gt;Thanks for the patch, Henrique!

Henrique Martins &amp;lt;mh-e-users-2009&amp;lt; at &amp;gt;martins.cc&amp;gt; wrote:


&lt;/pre&gt;</description>
    <dc:creator>Bill Wohler</dc:creator>
    <dc:date>2013-05-13T04:44:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2688">
    <title>Re: mh-refile-msg vs mh-thread-refile</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2688</link>
    <description>&lt;pre&gt;
Re mh-thread-refile doesn't set mh-last-destination and
mh-last-destination-folder.

Looks like copying a few lines from mh-refile-msg to
mh-thread-refile, and adding an optional argument to
mh-thread-refile, like the one in mh-refile-msg does the
trick.

Patch below.  I'll attach it to
  https://sourceforge.net/p/mh-e/bugs/473/
as well.

&lt;/pre&gt;</description>
    <dc:creator>Henrique Martins</dc:creator>
    <dc:date>2013-05-11T16:31:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2687">
    <title>Re: mh-refile-msg vs mh-thread-refile</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2687</link>
    <description>&lt;pre&gt;I'm not familiar with mh-thread-refile (!), but from your description, I
would have to agree.

Please submit a bug report. I encourage others to vote on it (and other
bugs for that matter now that we have that feature) who have been
affected.

Henrique Martins &amp;lt;mh-e-users-2009&amp;lt; at &amp;gt;martins.cc&amp;gt; wrote:


&lt;/pre&gt;</description>
    <dc:creator>Bill Wohler</dc:creator>
    <dc:date>2013-05-10T04:20:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2686">
    <title>mh-refile-msg vs mh-thread-refile</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2686</link>
    <description>&lt;pre&gt;
Seems that
  mh-refile-msg
sets the variables
  mh-last-destination
and
  mh-last-destination-folder
to be used in future refiles, but
  mh-thread-refile
does not sets those thus things can get a bit confusing if
one does a few of each in succession.

Shouldn't the behavior be identical?

&lt;/pre&gt;</description>
    <dc:creator>Henrique Martins</dc:creator>
    <dc:date>2013-05-10T01:48:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2685">
    <title>Re: /etc/nmh/components not parsed</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2685</link>
    <description>&lt;pre&gt;

F18 comes with nmh-1.5-3, but that has been the case for
while with Fedora. It was only recently when I decided to
clean and/or remove my different comps files that I bumped
into this.


I don't have Emacs installed but downloaded the latest
emacs-el rpm from the repos and it seems to contain 8.3.1.


I'll wait for Bill to get to it then ...

&lt;/pre&gt;</description>
    <dc:creator>Henrique Martins</dc:creator>
    <dc:date>2013-05-07T02:07:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2684">
    <title>Re: /etc/nmh/components not parsed</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2684</link>
    <description>&lt;pre&gt;

That is the next ticket on my list, as soon as I am able.


&lt;/pre&gt;</description>
    <dc:creator>Bill Wohler</dc:creator>
    <dc:date>2013-05-07T02:33:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2683">
    <title>Re: /etc/nmh/components not parsed</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2683</link>
    <description>&lt;pre&gt;

Let me guess: F18 includes nmh 1.5...?  I can reproduce the problem with
Debian 7rc1 (which has nmh 1.5) and Emacs 23.4.

There's a ticket open for support for nmh 1.5[1]; this appears to be a
known issue.  One of the notes in the ticket says

    - comp, forw, and dist now process all drafts through mh-format(5)
      and now suport new command line arguments -from, -to, -cc, -fcc,
      and -subject.


According to the ticket, support for nmh 1.5 is targeted for MH-E 8.6.

Does F18 ship MH-E 7.4.2 just for XEmacs, or for both Emacs and XEmacs?

mike

Footnotes: 
[1]  http://sourceforge.net/p/mh-e/bugs/468/

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
&lt;/pre&gt;</description>
    <dc:creator>Mike Kupfer</dc:creator>
    <dc:date>2013-05-07T01:09:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2682">
    <title>/etc/nmh/components not parsed</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2682</link>
    <description>&lt;pre&gt;
I created a brand new user on my system (Fedora 18), no
customization files whatsoever.

Logged on as that user, ran install-mh, accepted the defaults.

Ran "xemacs -nw -vanilla" and once in xemacs invoked "M-x
mh-smail".

The resulting draft is a copy /etc/nmh/components, not expanded
at all, which would be a bit puzzling to a new user, to say the
least.

Read the manual through the mh-smail invocation and if I was a
new user I wouldn't know what to do then, which is?

&lt;/pre&gt;</description>
    <dc:creator>Henrique Martins</dc:creator>
    <dc:date>2013-04-24T03:49:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2681">
    <title>face for messages for which i'm on the cc list</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2681</link>
    <description>&lt;pre&gt;hi.  i've always been curious/slightly miffed that i get a visual
notification (a blue versus a black face (?) in my +inbox folder
listing) when i'm on the To: list of a received e-mail, but not when i'm
on the cc: list.

this has recently gotten more urgent (as the amount of spam i'm dealing
with has increased greatly over the past few weeks).  tonight i looked
at this.  it seems that the language mh-format provides requires one to
enter the query for cc: more than once.

if mh-scan-format-nmh has the following format:

      (concat
       "%4(msg)"
       "%&amp;lt;(cur)+%| %&amp;gt;"
       "%&amp;lt;{replied}-"
       "%?(nonnull(comp{to}))%&amp;lt;(mymbox{to})t"
 ; my addition (after splitting the above line)
       "%?(nonnull(comp{cc}))%&amp;lt;(mymbox{cc})c%&amp;gt;"
       "%&amp;gt;"
       "%?(nonnull(comp{cc}))%&amp;lt;(mymbox{cc})c%&amp;gt;"
       "%?(nonnull(comp{bcc}))%&amp;lt;(mymbox{bcc})b%&amp;gt;"
       "%?(nonnull(comp{newsgroups}))n%&amp;gt;"
       "%&amp;lt;(zero) %&amp;gt;"
       "%02(mon{date})/%02(mday{date})%&amp;lt;{date} %|*%&amp;gt;"
       "%&amp;lt;(mymbox{from})%&amp;lt;{to}To:%14(decode(friendly{to}))%&amp;gt;%&amp;gt;"
       "%&amp;lt;(zero)%17(decode(friendly{from}))%&amp;gt;  "
       "%(decode{subject})%&amp;lt;{body}&amp;lt;&amp;lt;%{body}%&amp;gt;")

one sees a "c" in the right place.  (otherwise, i think one wouldn't see
a "c" unless there were *no* To: header at all *and* one's e-mail
address appeared in the cc: field.)

cheers, Greg
----

ps -- mh-scan-format-nmh is defined in mh-scan.el with the following:
----
(defvar mh-scan-format-nmh
  (concat
   "%4(msg)"
   "%&amp;lt;(cur)+%| %&amp;gt;"
   "%&amp;lt;{replied}-"
   "%?(nonnull(comp{to}))%&amp;lt;(mymbox{to})t%&amp;gt;"
   "%?(nonnull(comp{cc}))%&amp;lt;(mymbox{cc})c%&amp;gt;"
   "%?(nonnull(comp{bcc}))%&amp;lt;(mymbox{bcc})b%&amp;gt;"
   "%?(nonnull(comp{newsgroups}))n%&amp;gt;"
   "%&amp;lt;(zero) %&amp;gt;"
   "%02(mon{date})/%02(mday{date})%&amp;lt;{date} %|*%&amp;gt;"
   "%&amp;lt;(mymbox{from})%&amp;lt;{to}To:%14(decode(friendly{to}))%&amp;gt;%&amp;gt;"
   "%&amp;lt;(zero)%17(decode(friendly{from}))%&amp;gt;  "
   "%(decode{subject})%&amp;lt;{body}&amp;lt;&amp;lt;%{body}%&amp;gt;")
  "*Scan format string for nmh.
This string is passed to the scan program via the -format arg.
This format is identical to the default except that additional
hints for fontification have been added to the fifth
column (remember that in Emacs, the first column is 0).

The values of the fifth column, in priority order, are: \"-\" if
the message has been replied to, t if an address on the To: field
matches one of the mailboxes of the current user, \"c\" if the Cc:
field matches, \"b\" if the Bcc: field matches, and \"n\" if a
non-empty Newsgroups: field is present.")
----

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis &amp;amp; visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
&lt;/pre&gt;</description>
    <dc:creator>Greg Minshall</dc:creator>
    <dc:date>2013-04-18T00:43:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2680">
    <title>Re: method of autosaving sent mail</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2680</link>
    <description>&lt;pre&gt;
To all who helped me get the outgoing mail save.   Thank you.
It was so easy.  That shows how good MH-E is. 
Also the idea that outboxes could be different for different identities is a very good.

I can translate from Japanese to English.  I recall a request to get a summarized translation of some Japanese module, but I forgot what and where it was and don't know if it's still needed.  I believe it had something to do with, collecting mail and notification of mail received?  Let me know, if that is still needed.  I could do a simple translation of it's function summary and usage.

Darel

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis &amp;amp; visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
&lt;/pre&gt;</description>
    <dc:creator>d.henman</dc:creator>
    <dc:date>2013-04-17T00:45:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2679">
    <title>Re: method of autosaving sent mail</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2679</link>
    <description>&lt;pre&gt;
    Bill&amp;gt; I use "Fcc: +outbox" in my various component files as
    Bill&amp;gt; well. That seems 

Me too.

    Bill&amp;gt; If you already use identities, you may consider using them instead of or
    Bill&amp;gt; in addition to updating your components files to emit an Fcc header
    Bill&amp;gt; field. Please see:

    Bill&amp;gt; http://mh-e.sourceforge.net/manual/html/Identities.html

And I customize this field with MH-E's identities, so that when I change
my From:, I also change the FCC.

&lt;/pre&gt;</description>
    <dc:creator>Michael Richardson</dc:creator>
    <dc:date>2013-04-08T17:12:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2678">
    <title>Re: method of autosaving sent mail</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2678</link>
    <description>&lt;pre&gt;Hi Darel,

I use "Fcc: +outbox" in my various component files as well. That seems
like a more effective way to save a copy. The copy goes directly to the
desired folder rather than taking a circuitous route of going through an
MTA and procmail which also necessitates additional work to configure.

If you already use identities, you may consider using them instead of or
in addition to updating your components files to emit an Fcc header
field. Please see:

  http://mh-e.sourceforge.net/manual/html/Identities.html

d.henman &amp;lt;dhenman&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:


&lt;/pre&gt;</description>
    <dc:creator>Bill Wohler</dc:creator>
    <dc:date>2013-04-07T00:35:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2677">
    <title>Re: spam filtering -- false positives</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2677</link>
    <description>&lt;pre&gt;

This link doesn't seem to be valid any more. At any rate, the current
version of the book is at SourceForge:

http://rand-mh.sourceforge.net/book/

The script is described in:

http://rand-mh.sourceforge.net/book/mh/rem.html#BetWay
http://rand-mh.sourceforge.net/book/mh/e-rmmer.html

and found in:

http://rand-mh.sourceforge.net/book/examples/mh/bin/rmmer


&lt;/pre&gt;</description>
    <dc:creator>Bill Wohler</dc:creator>
    <dc:date>2013-04-07T00:29:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2675">
    <title>method of autosaving sent mail</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2675</link>
    <description>&lt;pre&gt;
What is the current recommended method for setting up MH-E for automatically save 
a copy of outgoing mail?

I found the below, but I recal seeing another method  to accoplish this but can't find it yet.  If someone would give me a reference or actual example I'd appreciate


darel
 --

What I did fid was:
     a.) this proposal to use the dcc header field.
         (defcustom mh-insert-dcc-address nil 
                        "Append this string as a dcc field to the header.
                         t means insert the output from function `user-login-name'."
 :type '(choice (const :tag "Don't insert dcc" nil)
 (const :tag "Use user-login-name" t)
 (string :tag "dcc address"))group 'mh-compose)


      (defun mh-insert-dcc () "Insert dcc field if `mh-insert-dcc-address' is non-nil."
      (save-excursion   (when (and mh-insert-dcc-address
      (not (mh-goto-header-field "dcc:")))   (mh-goto-header-end 0)
      (if (stringp mh-insert-dcc-address)    (insert "dcc: " mh-insert-dcc-address "\n")
      (insert "dcc: " (user-login-name) "\n")))))

   # And edit 'mh-compose-and-send-mail , adding  "(pop-to-buffer draft):" after
   (if mh-insert-dcc-address (mh-insert-dcc))

OR manually for each send one would have to use C-c C-f C-d  to use the dcc field.



--------------------------------

A note should be given to indicate that the other way to do this
would be for the user to put a line like:

Dcc: %(putstr(me))

into their `mhpath +`/replcomps or `mhpath +`/replgroupcomps
files.



------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
&lt;/pre&gt;</description>
    <dc:creator>d.henman</dc:creator>
    <dc:date>2013-04-05T09:17:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2674">
    <title>Re: method of autosaving sent mail</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2674</link>
    <description>&lt;pre&gt;Darel,

i use Fcc.  it shows up in various places:
----
% grep -iw fcc ~/Mail/* 2&amp;gt;&amp;amp;1 | grep -v "Is a directory"
~/Mail/components:Fcc: outbox
~/Mail/replcomps:%&amp;lt;{fcc}Fcc: %{fcc}\n%&amp;gt;\
~/Mail/replcomps:Fcc: outbox\n\
~/Mail/replgroupcomps:%&amp;lt;{fcc}Fcc: %{fcc}\n%&amp;gt;\
~/Mail/replgroupcomps:Fcc: outbox\n\
----
(it doesn't show up in my forwcomps, for some reason, so i don't
automatically save forwarded e-mail.)

my components file is:
----
From: blah blah blah
To:
cc:
Subject:
Fcc: outbox
--------
----

while my replcomps is:
----
From: blah blah blah
%(lit)%(formataddr %&amp;lt;{reply-to}%?{from}%?{sender}%?{return-path}%&amp;gt;)\
%&amp;lt;(nonnull)%(void(width))%(putaddr To: )\n%&amp;gt;\
%(lit)%(formataddr{to})%(formataddr{cc})%(formataddr(me))\
%&amp;lt;(nonnull)%(void(width))%(putaddr cc: )\n%&amp;gt;\
%&amp;lt;{fcc}Fcc: %{fcc}\n%&amp;gt;\
%&amp;lt;{subject}Subject: Re: %{subject}\n%&amp;gt;\
%&amp;lt;{date}In-reply-to: Your message of "\
%&amp;lt;(nodate{date})%{date}%|%(pretty{date})%&amp;gt;."%&amp;lt;{message-id}
             %{message-id}%&amp;gt;\n%&amp;gt;\
Fcc: outbox\n\
--------
----

hope that helps.

cheers, Greg

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
&lt;/pre&gt;</description>
    <dc:creator>Greg Minshall</dc:creator>
    <dc:date>2013-04-05T10:45:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2673">
    <title>Re: method of autosaving sent mail</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2673</link>
    <description>&lt;pre&gt;Darel,

you're welcome.


i'm not sure what *else* the Fcc field might be used for, so i guess i
can't really give much of an answer.

cheers, Greg

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
&lt;/pre&gt;</description>
    <dc:creator>Greg Minshall</dc:creator>
    <dc:date>2013-04-05T22:17:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2672">
    <title>Re: method of autosaving sent mail</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2672</link>
    <description>&lt;pre&gt;
Greg,
  thanks for the data.  I appreciate the real case example and MH format strings used.  Wouldn't the obscure and probably never else dcc field be better than the fcc field?  Or maybe its too obscure to for mta?  

Darel

Greg Minshall &amp;lt;minshall&amp;lt; at &amp;gt;umich.edu&amp;gt; wrote:

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
&lt;/pre&gt;</description>
    <dc:creator>d.henman</dc:creator>
    <dc:date>2013-04-05T12:55:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2671">
    <title>Re: method of autosaving sent mail</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2671</link>
    <description>&lt;pre&gt;

Or, specify it in your identity, like this:

  (custom-set-variables
   '(mh-identity-list
     ;; ~/.emacs sets mh-identity-default to one of these:
     (quote (("Home" (("From" . "Kevin Layer &amp;lt;layer&amp;lt; at &amp;gt;known.net&amp;gt;")
      ("Fcc" . "+outbox")))
     ("Work" (("From" . "Kevin Layer &amp;lt;layer&amp;lt; at &amp;gt;franz.com&amp;gt;")
      ;;("Organization" . "Franz, Inc.")
      ("Fcc" . "+outbox"))))))

then somewhere you need to do

 (custom-set-variables '(mh-identity-default "Home"))
or
 (custom-set-variables '(mh-identity-default "Work"))


------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
&lt;/pre&gt;</description>
    <dc:creator>Kevin Layer</dc:creator>
    <dc:date>2013-04-05T13:48:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2670">
    <title>Re: spam filtering -- false positives</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2670</link>
    <description>&lt;pre&gt;awesome --- thanks, Mark!

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
&lt;/pre&gt;</description>
    <dc:creator>Greg Minshall</dc:creator>
    <dc:date>2013-04-03T22:53:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2669">
    <title>Re: spam filtering -- false positives</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2669</link>
    <description>&lt;pre&gt;Hi Greg,

Greg Minshall &amp;lt;minshall&amp;lt; at &amp;gt;umich.edu&amp;gt; wrote:


I normally have my delete operations move messages into a +DELETE
folder. I do this at the nmh level with the specification of rmmproc

My .mh_profile has the following lines related to rmmproc

refile: -rmmproc /bin/rm
rmmproc:rmmer.one_fdr

and my rmmer.one_fdr script borrowed from the very nice book O'Reilly &amp;amp;
Associates book "MH &amp;amp; xmh" book by Jerry Peek. See
http://oreilly.com/openbook/mh/e-rmmer.htm for more information on
rmmer as well as http://orielly.com/openbook/mh/ for the online copy
of the book.

A copy of the script I use is after my .signature ...

-- Mark

----------%&amp;lt;----------%&amp;lt;----------%&amp;lt;----------%&amp;lt;----------%&amp;lt;----------
#! /bin/sh
# $Header: /u3/acs/jdpeek/.bin/RCS/rmmer,v 3.4 90/11/21 06:52:02 jdpeek Exp $
###rmmer - move mail to &amp;lt; at &amp;gt;DELETE for "find" to clean up
###Usage in .mh_profile:    rmmproc: rmmer
###rmmer.one_fdr - move mail to +DELETE for "find" to clean up
###Usage in .mh_profile:    rmmproc: rmmer.one_fdr
##
##rmmer IS DESIGNED TO BE USED WITH THE MH MAIL rmm COMMAND.
##INSTEAD OF JUST ADDING A COMMA (,) TO THE MESSAGE NAME, LIKE
##STANDARD rmm DOES, rmmer MOVES THE MESSAGE INTO A SUB-FOLDER
##NAMED "DELETE".  A SYSTEM PROGRAM SHOULD CLEAN OUT THAT FOLDER
##EVERY SO OFTEN (YOU MAY HAVE TO SET THAT UP, TOO).  ANYHOW,
##THE IDEA IS THAT MESSAGES IN A "DELETE" SUB-FOLDER ARE EASY TO
##RECOVER IF YOU REMOVED ONE BY ACCIDENT.
##
##FOR EXAMPLE, LET'S SAY YOU JUST DELETED A MESSAGE BY ACCIDENT.
##TO GET IT BACK, YOU GO TO THE SUB-FOLDER.  YOUR MESSAGE WILL
##BE THE LAST ONE IN THE SUB-FOLDER BECAUSE YOU JUST REMOVED IT.
##TO RECOVER THE DELETED MESSAGE, MOVE IT BACK TO THE PARENT FOLDER
##(WHERE IT WAS BEFORE) WITH refile.  AFTER YOU RECOVER IT, IT'LL
##BE THE LAST MESSAGE IN THE FOLDER.  HERE GOES:
##% rmm
##% show last &amp;lt; at &amp;gt;DELETE
##(Message inbox/DELETE:25)
##(message appears -- this is the one you "deleted")
##% refile &amp;lt; at &amp;gt;..
##% show last &amp;lt; at &amp;gt;..
##(Message inbox:54)
##(same message appears -- now it's back in the parent folder)
##
##IF YOU DON'T WANT rmmer TO USE A SUB-FOLDER--AND, INSTEAD, PUT
##ALL THE MESSAGES IN A CENTRAL "DELETE" FOLDER--YOU CAN CALL THE
##PROGRAM WITH THE NAME rmmer.one_fdr AND THAT'LL DO IT.

# TABSTOPS ARE SET AT 4 IN THIS CODE

moveto=DELETE# NAME OF FOLDER FOR DELETED MESSAGES
mvdir=/bin# DIRECTORY WHERE mv COMMAND LIVES

awk=/usr/bin/awk  mkdir=/bin/mkdir  touch=/bin/touch  tr=/usr/bin/tr

mhpath=mhpath
if [ -x /usr/bin/mh/mhpath ]; then mhpath=/usr/bin/mh/mhpath; fi

# USE PROGRAM NAME TO SET PATH TO DESTINATION FOLDER:
case "$0" in
*rmmer) destfol="&amp;lt; at &amp;gt;$moveto" ;;
*rmmer.one_fdr) destfol="+$moveto" ;;
*)echo "$0 aborting: can't find my name." 1&amp;gt;&amp;amp;2; exit 1 ;;
esac

trap 'echo "$0: Interrupt!  $* may not be removed." 1&amp;gt;&amp;amp;2; exit' 1 2 15

# rmm SETS CURRENT DIRECTORY TO FOLDER, SO IT'S EASY TO MAKE
# NEW SUB-FOLDER.  (LET USER MAKE THEIR OWN "+DELETE" ONCE.)
if [ "$destfol" = "&amp;lt; at &amp;gt;$moveto" -a ! -d "$moveto" ]
then $mkdir $moveto || exit
fi

# rmm PUTS SINGLE MESSAGE NUMBERS INTO $* (LIKE 12 13 14).
# UPDATE LAST-MOD TIME SO find -mtime WON'T DELETE TOO SOON:
$touch $* &amp;gt;/dev/null 2&amp;gt;&amp;amp;1

# IF &amp;lt;= 7 MESSAGES, REFILE EACH WITH mv AND mhpath new.
# OTHERWISE, SAVE TIME BY GETTING FIRST UNUSED MESSAGE NUMBER
# IN $destfol AND USING PLAIN mv COMMANDS IN A LOOP:
case $# in
[1-7])
for m
do $mvdir/mv $m `$mhpath new $destfol` || exit
done
;;
*)newpath="`$mhpath new $destfol`" || exit# FIRST MSG.
PATH=${mvdir}:$PATH; export PATH# GET THE RIGHT mv
# GIVE awk NUMBERS LIKE 23 24, SPLIT ONTO SEPARATE LINES
# BY TURNING SPACES INTO NEWLINES.  OUTPUT mv COMMANDS
# THAT THE SHELL READS (BY eval) AND RUNS, LIKE THIS:
#mv ,23 /xxx/Mail/inbox/DELETE/99;
#mv ,24 /xxx/Mail/inbox/DELETE/100;
# **HUGE** MESSAGE LISTS MAY CAUSE LONG-LINE PROBLEMS.
eval `
echo $* | $tr ' ' '\012' | $awk '
BEGIN {
# SPLIT PATH OF FIRST UNUSED MESSAGE INTO part ARRAY:
np = split("'$newpath'", part, "/")
# BUILD ALL BUT THE LAST PIECE INTO DIRECTORY NAME:
for (i = 2; i &amp;lt; np; i++)
dir = dir "/" part[i]
# LAST part IS FIRST NEW MESSAGE NUMBER; PUT IN new.
# MAKE SURE awk TREATS AS INTEGER BY ADDING ZERO:
new = part[np] + 0
}
{
# READ MESSAGE NUMBERS, OUTPUT COMMANDS:
printf "mv %d %s/%d;", $1, dir, new++
}'`
;;
esac

exit
----------%&amp;lt;----------%&amp;lt;----------%&amp;lt;----------%&amp;lt;----------%&amp;lt;----------

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
&lt;/pre&gt;</description>
    <dc:creator>Mark D. Baushke</dc:creator>
    <dc:date>2013-04-03T22:43:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.mail.mh-e.user/2668">
    <title>spam filtering -- false positives</title>
    <link>http://permalink.gmane.org/gmane.mail.mh-e.user/2668</link>
    <description>&lt;pre&gt;hi, all.

i'm my own spam filter.  (there's nothing between me and the internet;
it's pretty interesting to see new spam "technologies"/"techniques" pop
up, play out, die off.)

up till now, i delete spam messages (using "d" or "k").

but, i occasionally kill the wrong message.

so, since the amount of storage consumed by spam is fairly small, i'd
like to remap "d" and "k" to do refiles to a "+spam" folder instead.

what would be nice would be something that allowed me to continue to see
the same (emacs calls this) "face" for "d"/"k" messages versus "o"/"^"
messages.

is there any obvious way of approaching this?

cheers, Greg

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
&lt;/pre&gt;</description>
    <dc:creator>Greg Minshall</dc:creator>
    <dc:date>2013-04-03T22:14:40</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.mail.mh-e.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.mail.mh-e.user</link>
  </textinput>
</rdf:RDF>
