Ken wrote:
> Although, if you're grep'ing for something, you'd think you'd
> still find it in text/html (if it wasn't base64-encoded).
Might as well go to text/plain along with decoding.
Even Q-P is bothersome, esp. for replying.
> Perhaps we should think about extending pick to decoding
> base6
>Seriously, I would love to have the thing you're proposing, especially
>if it works with repl. I'm getting increasing amounts of mail which I
>can't conveniently reply to becuase it doesn't get decoded.
Just a gentle plug for replyfilter ...
It should handle text/html fine by using w3m to conver
>Minor fcc bug or mis-feature: Can't send a message with fcc's but no
>recipients.
Why would you want to? I'm just trying to think of the use case here.
send/post are designed to transmit mail to the Internet; seems like you
could replicate Fcc's functionality with refile (or use one of David
Lev
>So that's why the deluge stopped when I stopped postfix and didn't
>restart when I started postfix. Apparently, when I rebooted, postfix
>wasn't gone long enough to interrupt the loop.
You know, the more I think about it, I have to wonder ... why did stopping
postfix stop it permamently? Unless
Failing out would be nice, as would be an option to edit.
I often mistype an Fcc, and then hqve go trolling through
drafts for the message to mv
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
I'm thinking that maybe whom should have an option to include fcc headers. If
that option is chosen and there is a -check , then whom should check that the
directories exist and are writable.
Norman Shapiro
798 Barron Avenue
Palo Alto CA 94306-3109
(650) 565-8215
n...@dad.o
It seems to me that if a message has an Fcc header with a directory that does
not exist, and the user declines an invitation to create the directory, then
the message should not be sent, just as in the case when one of the addressees
loses.
Norman Shapiro
_
david wrote:
> I've been getting text emails with only a text/html
> Content-Type, with no alternative text/plain part.
> Microsoft Exchange and Outlook have settings to do that:
>
> http://technet.microsoft.com/en-us/library/aa998896(v=exchg.65).aspx
> http://support.microsoft.com/kb/32
Thus spake David Levine:
> I've been getting text emails with only a text/html
> Content-Type, with no alternative text/plain part.
> Microsoft Exchange and Outlook have settings to do that:
>
> http://technet.microsoft.com/en-us/library/aa998896(v=exchg.65).aspx
> http://support.microsoft.com
Hi David,
> * decode base64 and Q-P parts
I'd like 8-bit UTF-8, i.e. change the charset too, for most usefulness
at the command line.
Cheers, Ralph.
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-wo
I've been getting text emails with only a text/html
Content-Type, with no alternative text/plain part.
Microsoft Exchange and Outlook have settings to do that:
http://technet.microsoft.com/en-us/library/aa998896(v=exchg.65).aspx
http://support.microsoft.com/kb/323195
This is so annoying (/rud
Norm wrote:
> Minor fcc bug or mis-feature: Can't send a message with fcc's but no
> recipients.
You can now (after nmh 1.5) with this mis-feature:
Bcc: /dev/null
What now? send -mts sendmail/pipe
David
___
Nmh-workers mailing list
Nmh-workers
Mail directed to dad.org, goes to adzone.com, which forwards it to my Internet
Provider, rawbw.com.
I use "cc: norm.org:L instead of fcc for a kind of neuritic reason. That way,
I know that my message has made its way out in the world -- indeed has crossed
the Tehachapi Mountains twice :-), s
Ken Hornstein writes:
>I think the reason it didn't show up was that every three minutes the
>message was making it "around the loop" to the various mailer hosts
>in your ISP, and it would only show up if you happened to run those
>commands while the message was local. There's a misconfiguration
14 matches
Mail list logo
