headers
Kyle Wheeler | 1 Nov 01:20

Re: pb with pop_last


On Friday, October 31 at 10:43 PM, quoth KP Kirchdoerfer:
> I'm new to the list and new to mutt.

Welcome!

> After reading a lot of documentation and googling I still cannot 
> resolve the problem that "set pop_last" does not seem to work. I 
> understood that "set pop_last=yes" prevents my mailer to download 
> teh same mails from a popserver every time I fetch it.

Only if your server supports it. Technically, the LAST command was 
removed from the POP standard back in 1994.

In any case, I believe that if you set $mcache, you don't have to 
worry about whether your server supports LAST or not.

> I doublechecked with the same account from another machine with 
> kmail that the mailservice provider isn't the culprit.

Kmail keeps a copy of all messages, and so doesn't rely on the LAST 
command to figure out what messages it has already downloaded: it can 
just look at which ones it *has*.

~Kyle
--

-- 
Human beings are the only creatures that allow their children to come 
back home.
                                                         -- Bill Cosby
(Continue reading)

Permalink | Reply | 0 comments |
headers
giggz | 1 Nov 09:38
Picon

Pb mutt and imap.free.fr

Hi,

I'm using mutt under virtual console. I have an account under
imap.free.fr : I configure it like this under muttrc :

## imap free truc
folder-hook "imap://truc <at> imap.free.fr" 'set imap_user=truc'
folder-hook "imap://truc <at> imap.free.fr" 'set signature="~/signature"'
folder-hook "imap://truc <at> imap.free.fr" 'my_hdr From: Truc <truc <at> free.fr>'
folder-hook "imap://truc <at> imap.free.fr" 'set
folder=imap://imap.free.fr/INBOX'
## pour que qd on tape c on soit dans le compte imap
folder-hook ^imap://truc <at> imap.free.fr/?$ \
"push <change-folder>?<change-dir><kill-line>\
imap://truc <at> imap.free.fr/<Enter><exit>"
## on impose ici tout le chemin car sinon il y a conflit entre les 2
## comptes free
folder-hook "imap://truc <at> imap.free.fr" 'set
postponed=imap://truc <at> imap.free.fr/INBOX/drafts'
folder-hook "imap://truc <at> imap.free.fr" 'set
record=imap://truc <at> imap.free.fr/INBOX/sent-mail'
folder-hook "imap://truc <at> imap.free.fr" 'set crypt_autosign = yes'
folder-hook "imap://truc <at> imap.free.fr" 'set crypt_replyencrypt = yes'
folder-hook "imap://truc <at> imap.free.fr" 'set crypt_replysignencrypted = yes'

mailboxes imap://truc <at> imap.free.fr

And when I click and the mailbox and then enter the password, the
connection begins and nothing happens anymore. I have to kill mutt.
(Continue reading)

Permalink | Reply | 0 comments |
headers
bill lam | 3 Nov 06:04
Picon

mime type when adding attachment

When I attach an excel file, its mime type is automatically set to
"application/excel", while recipient has no problem (they use
outlook), my mailcap has not associate that with any spreadsheet
program, thus mutt cannot open it.  My question is how does mutt
determine mime type when adding attachment so that I could change that
for excel file to "application/vnd.ms-excel"  which seem recognised by
  both gnumeric and openoffice.

relevant portions of my /etc/mailcap

application/vnd.ms-excel; gnumeric '%s'; edit=gnumeric '%s'; description="MS Excel spreadsheet";
test=test -n "$DISPLAY"; nametemplate=%s.xls
application/x-excel; gnumeric '%s'; edit=gnumeric '%s'; description="MS Excel spreadsheet";
test=test -n "$DISPLAY"; nametemplate=%s.xls
application/x-ms-excel; gnumeric '%s'; edit=gnumeric '%s'; description="MS Excel spreadsheet";
test=test -n "$DISPLAY"; nametemplate=%s.xls
application/x-msexcel; gnumeric '%s'; edit=gnumeric '%s'; description="MS Excel spreadsheet";
test=test -n "$DISPLAY"; nametemplate=%s.xls
application/x-xls; gnumeric '%s'; edit=gnumeric '%s'; description="MS Excel spreadsheet";
test=test -n "$DISPLAY"; nametemplate=%s.xls
application/x-dos_ms_excel; gnumeric '%s'; edit=gnumeric '%s'; description="MS Excel
spreadsheet"; test=test -n "$DISPLAY"; nametemplate=%s.xls

application/vnd.ms-excel.sheet.macroEnabled.12; soffice -no-oosplash -calc '%s'; edit=soffice
-no-oosplash -calc '%s'; test=test -n "$DISPLAY"; description="Office Open XML Spreadsheet with
Macros Enabled"; nametemplate=%s.xlsm
application/vnd.ms-excel.template.macroEnabled.12; soffice -no-oosplash -calc '%s';
edit=soffice -no-oosplash -calc '%s'; test=test -n "$DISPLAY"; description="Office Open XML
Spreadsheet Template with Macros Enabled"; nametemplate=%s.xltm
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet; soffice -no-oosplash -calc
(Continue reading)

Permalink | Reply | 4 comments |
headers
Saujanya Patel | 3 Nov 06:41
Picon
Picon
Favicon

Command Line - setting the from field?

Kia ora,

I was wondering if it is possible to set the "from" value from the command line
without using the .muttrc file

Something like:

mutt -s "subject" someone <at> somewhere.com -a a.file < someText -f fromThisAddress <at> something.com

I'm going to be using it in a bash script.

Thanks and cheers,

sauj
--
ITS, The University of Auckland
Permalink | Reply | 1 comment |
headers
Christian Mongeau | 3 Nov 10:16

Re: mime type when adding attachment

On 2008-11-03, bill lam wrote:
> When I attach an excel file, its mime type is automatically set
> to
> "application/excel", while recipient has no problem (they use
> outlook), my mailcap has not associate that with any spreadsheet
> program, thus mutt cannot open it.  My question is how does mutt
> determine mime type when adding attachment so that I could
> change that
> for excel file to "application/vnd.ms-excel"  which seem
> recognised by
>   both gnumeric and openoffice.

Chapter 5 of the manual deals with MIME:
http://www.mutt.org/doc/devel/manual.html#mimesupport

In particular, "2. MIME Type configuration with mime.types"
(http://www.mutt.org/doc/devel/manual.html#mime-types) says:
"When you add an attachment to your mail message, Mutt searches
your personal mime.types file at ${HOME}/.mime.types, and then
the system mime.types file at /usr/local/share/mutt/mime.types
or /etc/mime.types

The mime.types file consist of lines containing a MIME type and
a space separated list of extensions. For example:

application/postscript          ps eps
application/pgp                 pgp
audio/x-aiff                    aif aifc aiff

[...]
(Continue reading)

Permalink | Reply | 3 comments |
headers
bill lam | 3 Nov 11:11
Picon

Re: mime type when adding attachment

On Mon, 03 Nov 2008, Christian Mongeau wrote:
> Chapter 5 of the manual deals with MIME:
> http://www.mutt.org/doc/devel/manual.html#mimesupport
> 
> In particular, "2. MIME Type configuration with mime.types"
> (http://www.mutt.org/doc/devel/manual.html#mime-types) says:
> "When you add an attachment to your mail message, Mutt searches
> your personal mime.types file at ${HOME}/.mime.types, and then
> the system mime.types file at /usr/local/share/mutt/mime.types
> or /etc/mime.types
> 
> The mime.types file consist of lines containing a MIME type and
> a space separated list of extensions. For example:
> 
> application/postscript          ps eps
> application/pgp                 pgp
> audio/x-aiff                    aif aifc aiff
> 
> [...]
> 
> You can change the MIME type that Mutt assigns to an attachment by
> using the edit-type command from the compose menu (default: ^T).
> [...]" or by modifying the mime.types file.

Thanks Christian. 

I checked again that there is no 
~/.mime.types
/usr/local/share/mutt/mime.types
/usr/share/mutt/mime.types
(Continue reading)

Permalink | Reply | 2 comments |
headers
Rado S | 3 Nov 12:30
Picon
Picon

Re: Command Line - setting the from field?

=- Saujanya Patel wrote on Mon  3.Nov'08 at 18:41:25 +1300 -=

> I was wondering if it is possible to set the "from" value from the
> command line without using the .muttrc file

Yes.

> Something like:
> mutt -s "subject" someone <at> somewhere.com -a a.file < someText -f fromThisAddress <at> something.com

No.
You have to go via '-e' and use muttrc cmds.

--

-- 
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
Permalink | Reply | 0 comments |
headers
Dave Feustel | 3 Nov 14:03
Picon

Unicode and Mutt

I saved a few messages to mutt folders that had Russian or Asian
Characters in the subject line. Now when I look at those saved messages
the Russian/Asian characters are no longer displayed. Is there any way
to make mutt work with UTF-8 so that email message text does not get
screwed up?

Thanks.
Permalink | Reply | 0 comments |
headers
Anders Karlsson | 3 Nov 14:50
Picon

Re: Unicode and Mutt

* Dave Feustel <dfeustel <at> mindspring.com> [20081103 14:03]:
> I saved a few messages to mutt folders that had Russian or Asian
> Characters in the subject line. Now when I look at those saved messages
> the Russian/Asian characters are no longer displayed. Is there any way
> to make mutt work with UTF-8 so that email message text does not get
> screwed up?
> 
> Thanks.
> 

mutt (at least the version I have) works fine with Unicode characters
as long as your terminal and LANG settings handle it. I run mutt in
urxvt, and with the font "xft:DejaVu Sans Mono-10". This does display
most kanji, chinese and cyrillic characters I have come across. LANG
is set to en_GB.utf8.

HTH,

--

-- 
Anders Karlsson <anders <at> trudheim.co.uk>
All-Round Linux Tinkerer & RHCE
Permalink | Reply | 1 comment |
headers
Dave Feustel | 3 Nov 16:14
Picon

Re: Unicode and Mutt

On Mon, Nov 03, 2008 at 02:50:40PM +0100, Anders Karlsson wrote:
> * Dave Feustel <dfeustel <at> mindspring.com> [20081103 14:03]:
> > I saved a few messages to mutt folders that had Russian or Asian
> > Characters in the subject line. Now when I look at those saved messages
> > the Russian/Asian characters are no longer displayed. Is there any way
> > to make mutt work with UTF-8 so that email message text does not get
> > screwed up?
> > 
> > Thanks.
> > 
> 
> mutt (at least the version I have) works fine with Unicode characters
> as long as your terminal and LANG settings handle it. I run mutt in
> urxvt, and with the font "xft:DejaVu Sans Mono-10". This does display
> most kanji, chinese and cyrillic characters I have come across. LANG
> is set to en_GB.utf8.
> 
> HTH,

Did you try saving the messages and verifying that the saved messages
still display properly?  Where is LANG set? I am using xterm and I wonder
if a yum update could have changed those settings.

I am currently reading the book _Unicode Explained_ by Jukka K. Korpela,
and getting Unicode to work across the desktop is more involved than I
originally thought.
Permalink | Reply | 0 comments |

Gmane