I have mutt compiled and running under os 10.4. When i go to print an email,
it works fine. My question is, my printer, an HP printer, supports duplex
printing. What do i have to do to get the email that is printed to utilized
this function?
Thanks,
Russ
On Wed, 13 Oct 2010 at 10:41AM +0900, Dan Drake wrote:
> I'm wondering if there's any way to get Mutt to decode the filenames of
> attachments. Here's a bit from an attachment I received today:
Whoops...I just looked in the archives for this list, and noticed that just
yesterday there was a messag
Hello,
I'm wondering if there's any way to get Mutt to decode the filenames of
attachments. Here's a bit from an attachment I received today:
Content-Type: application/octet-stream;
name="=?EUC-KR?B?MjAxMbq9ILCzvLOxs7D6uPEoRSkueGxz?="
Content-Transfer-Encoding: base64
Content
On 12Oct2010 11:19, Todd Hesla wrote:
| [...] Of course, technically, the "."
| character would, I imagine, be interpreted as a special character which
| stands for _any_ character, so I suppose I should be single-quoting these
| regexp's, but there's really no other character (than an actual "."
On Tue, Oct 12, 2010 at 11:19:56AM -0500, Todd Hesla wrote:
Thanks a lot for your reply. Yes, I am using exactly the same regexp for
the account-hook's, and they are working correctly (because I'm able to get
into the INBOX's of those accounts!).
Here, in more detail, is my experimental .muttrc
Michael,
Thanks a lot for your reply. Yes, I am using exactly the same regexp for
the account-hook's, and they are working correctly (because I'm able to get
into the INBOX's of those accounts!).
Here, in more detail, is my experimental .muttrc file:
set mark_old=no
folder-hook . "set fol
Hello,
IIRC this will help (put it in .miuttrc):
set rfc2047_parameters=yes
On Tue, Oct 12, 2010 at 10:35:49AM +0300,
Cristopher Thomas wrote:
> =?utf-8?B?SU1HMDA1MTItMjAxMDEwMTEtMTcwMS5qcGc=?=
--
With best regards,
xrgtn (+380501102966/+380636177128/xr...@jabber.kiev.ua)
It seems that mutt is not correctly parsing some attachment names that
other mail readers don't seem to have a problem with. I've confirmed
that the filenames are *technically* correct by comparing the name as
displayed by mutt and the full headers version in Gmail, but I'd really
like mutt to sho
