Walter Truitt | 10 May 2004 18:30
Picon

masquerade mmailid and pop

After a moderate period away from nmh, I have come back. :)

Previously, I have used a different masquerade option to fix my from
address.  Today, I decided that I prefer not to have custom components
and replcomps files.  I like that I can put the mail id in the passwd
file and set the localhost.  This works well (except that sometimes it
breaks other mail programs).  It works well for sending mail, but when
I want to retreive mail, it sort of hacks the username globally.  It
was originally noticeable when I found I had to set the Maildrop in my
mh_profile.  Then when I changed to pop, I didn't have a way of
setting my pop username to wtruitt and my email address to
walter.truitt, except by passing the -user on the inc command-line.

When using any wrapper around MH, this is not simple.  I was curious
if anyone else has similar interests in getting this to work in a new
way.  My current fix, was to modify the sources to add a popuser line
to the mh_profile.  I patched inc to use this if it is set, and
otherwise call the getusername function.  I realize now writing this,
that I didn't change anything for the maildrop.  I think the mmailid
is great for sending, but it isn't something that should be used in
other parts of the system.

I would be willing to make changes and post them to the list if that
is the preferred method.  Otherwise, if the maintainer likes to make
changes consistent with the design, that is fine.

 -walter

_______________________________________________
Nmh-workers mailing list
(Continue reading)

Nathan Bailey | 21 May 2004 02:06
Favicon

Forwarding MIME messages?

I'm a long-time mh user (10+ years?) but possibly a fairly basic one
(i.e. I don't necessarily know all the options available in its many
features).  I have found that the only way Windows users can easily
see my attachments is doing them this way:

	#application/msword; name="whattheusersees.doc" whatthefileiscalled.doc

which means I need to type 'mime' (i.e. automime doesn't work with this,
IIRC).  But that's not the problem I'm writing about :-)

When people send me an attachment, I often need to forward it to others.
I have taken to using 'dist' for this purpose, since it happily forwards
the attachment validly, although it drives the recipients nuts, because:
	a) They don't know how they got it (although they guess it was me
	   from past experience :-)
	b) They don't know why they got it (because no covering note)

Using forward (e.g. forw -format) means I have to clean up the message
by hand and re-attach any attachments -- a lot of work.  I could write
a MIME parser reasonably easily in perl, but before I do, I wanted to
check if:
	a) There isn't already some secure option supporting this (e.g.
	   fancy repl.filters or similar)
	b) The new nmh release candidate doesn't already support it
	   (I'm currently running nmh-1.1-RC1)

If I do write something in perl, is that still useful as part of the
nmh package, or do we want all tools to be written in C for cross
platform compatability/consistency?

(Continue reading)

Neil W Rickert | 21 May 2004 02:58
Favicon

Re: Forwarding MIME messages?

Nathan Bailey <Nathan.Bailey <at> its.monash.edu> wrote on May 21, 2004:

>Using forward (e.g. forw -format) means I have to clean up the message
>by hand and re-attach any attachments -- a lot of work.  I could write

You can use

	forw -mime

to attach the original message as an rfc822 attachment.

 -NWR

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
http://mail.nongnu.org/mailman/listinfo/nmh-workers

Jerry Peek | 21 May 2004 05:19
X-Face
Gravatar

Re: Forwarding MIME messages?

On 21 May 2004 at 10:06, Nathan Bailey <Nathan.Bailey <at> its.monash.edu> wrote:
> Using forward (e.g. forw -format) means I have to clean up the message
> by hand and re-attach any attachments -- a lot of work.

I either use "forw -mime" (as Neil mentioned), or I put a #forw
directive in the message body (which is what "forw -mime" does)...
or I copy the message into the drafts folder and then edit it to
look the way I want, like:

	cp `mhpath cur` `mhpath new +drafts`
	comp -use -e vi last

When I edit someone else's message, I take out most of the
header fields (Received:, etc.) and change the "From:" and
"To:" fields.  I might edit the message body some -- maybe
removing an attachment or cleaning up some particularly ugly
HTML -- or else I just send it as-is.

Jerry
--

-- 
Jerry Peek, jpeek <at> jpeek.com, http://www.jpeek.com/

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
http://mail.nongnu.org/mailman/listinfo/nmh-workers

Nathan Bailey | 21 May 2004 03:43
Favicon

Re: Forwarding MIME messages?

Neil W Rickert <rickert+nmh <at> cs.niu.edu> wrote:
>Nathan Bailey <Nathan.Bailey <at> its.monash.edu> wrote on May 21, 2004:
>	forw -mime
>to attach the original message as an rfc822 attachment.

That does 90% of what I want, the only other bit is that occasionally
I edit (gasp!) the messages to highlight the relevant bit of text, but
in that rarer case I'm probably happy to hand-edit it for now.

Thanks for saving me an extra 5-10 minutes a day folks! :-)

Next dev requests/ideas:
	* IMAP support (looks like it is happening?)
	* LDAP support for addressing (I use a perl script with a vim
	  macro, it'd be nice if 'post' supported LDAP lookups in a
	  similar fashion to lib/aliases)
	* S/MIME certificate support (decrypting or verifying
	  signatures in show/mhl, encrypting in whatnow/post)

Is there a roadmap for nmh where we can propose these things and slot
them in to a proposed release?

regards,
Nathan
PS: Jon Steinhart, my reply to your message spam-bounced?
--

-- 
Nathan Bailey                        * Email: Nathan.Bailey <at> its.monash.edu
Manager, Flexible Learning and Teaching Program, Application Services,
Information Technology Services      * Phone: +61 3 990 54741
Monash University 3800     Australia * Fax: +61 3 990 53024
(Continue reading)

Ralph Corderoy | 21 May 2004 11:46
Picon

Re: Forwarding MIME messages?


Hi Nathan,

> >	forw -mime
> > to attach the original message as an rfc822 attachment.
> 
> That does 90% of what I want, the only other bit is that occasionally
> I edit (gasp!) the messages to highlight the relevant bit of text, but
> in that rarer case I'm probably happy to hand-edit it for now.

Try

    comp -- use `#forw <msg sequence>' in the draft
    mime -- at the what now prompt
    edit -- at the what now prompt and tinker with what it has embedded
    send

Cheers,

Ralph.

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
http://mail.nongnu.org/mailman/listinfo/nmh-workers

Mike O'Dell | 21 May 2004 14:32
Favicon

Re: Forwarding MIME messages?


my solution to this general problem is somewhat unorthodox but
seems to be mostly workable.

I run the UW-IMAP4 server on my FreeBSD machine where my MH
account lives. the cool part is that UW-IMAP4 understands
#mh as a user-local namespace for IMAP folders, and 
IT DOES THE RIGHT THING.

so over on MacOS X, i created an account that uses the IMAP
server and the #mh namespace, and PRESTO!!!! all my MH folders
appear and all the MIME tomfoolery can be done with Mail.app,
or even better, Mozilla Thunderbird.  Mail.app's IMAP support
is, as the Brits would say, "dodgy at best". (ie, PROFOUNDLY BUGGY!)
T-Bird, on the other hand, is fast at IMAP things and hasn't
yet puked its brains out like Mail.app.

and the net result is that i can go back and forth - doing some
things with MH, especially when i'm coming in remote via SSH
from some dial-up hell and just wanna blow through the mail
(frequently using emacs mhe for single-keystroke-kills).
but then when i get home, i can peruse the MIME comic book
stuff with a nice vidiot interface.

are there nits and warts, yes, occassionaly in abundance, but
for the most part, it's the best of both worlds at a cost
i find more than acceptable.

thanks for all the great work, guys.

(Continue reading)

Paul Fox | 21 May 2004 16:14
Picon
Favicon

Re: Forwarding MIME messages?


 > my solution to this general problem is somewhat unorthodox but
 > seems to be mostly workable.
 > 
 > I run the UW-IMAP4 server on my FreeBSD machine where my MH
 > account lives. the cool part is that UW-IMAP4 understands
 > #mh as a user-local namespace for IMAP folders, and 
 > IT DOES THE RIGHT THING.

does this handle sequences?  at the least, does it maintain the
"unseen" sequence?

paul
=---------------------
 paul fox, pgf <at> foxharp.boston.ma.us (arlington, ma, where it's 65.5 degrees)

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
http://mail.nongnu.org/mailman/listinfo/nmh-workers

mort | 21 May 2004 13:18
Picon
Picon

Preferences for MIME transport encoding?

Hi.

I've been looking for a way to tell nmh that I'd prefer if it used
8bit encoding instead of quoted-printable for mails with eightbit
characters in them. Sofar, I've come up with nothing.

My outgoing mailserver has no problem with 8BITMIME from other
mailers.

Anyone have a clue as to where I should look? I've even tried the
source, but my C-skills are...well, not that great. :-)

//Christer

--

-- 
| Sys admin  <at>  MEDIC              WWW: http://www.dtek.chalmers.se/            |
| Email: mort <at> dtek.chalmers.se   Phone: (0)31 772 5431, (0)707 53 57 57	      |
"I fought the loa and the loa won, I fought the loa and the loa won..."
        -- Dave Aronsson, a.s.r.

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
http://mail.nongnu.org/mailman/listinfo/nmh-workers

Mike O'Dell | 21 May 2004 17:20
Favicon

Re: Forwarding MIME messages?

hmmm - not sure about sequences
i don't use those very much except with "pick"
(ie, "picked") 

	-mo

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
http://mail.nongnu.org/mailman/listinfo/nmh-workers


Gmane