access-type support in Mutt for remote documents?

2001-01-21 Thread msquared

One of the mailing lists that I am on occasionally has MIME attachments
that -refer- to some file on an FTP site and/or mail server.  ('Refer' as
opposed to 'contain'.)

For example, the MIME portion pertaining to the remote file might look
like this:

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
access-type="mail-server";
server="[EMAIL PROTECTED]"

Content-Type: text/plain
Content-ID: [EMAIL PROTECTED]

ENCODING mime
FILE /somewhere/bar.txt

--OtherAccess
Content-Type: Message/External-body;
name="bar.txt";
site="ftp.foo.org";
access-type="anon-ftp";
directory="internet-drafts"

Content-Type: text/plain
Content-ID: [EMAIL PROTECTED]

--OtherAccess--


Mutt happily displays this as an attachment, but says that the access
method "anon-ftp" is unknown.

How do I configure Mutt to recognise the access type and to retrieve the
appropriate document/attachment?


 2
Regards, /|/|
/   |



Re: Moving mail to another mailbox

2001-01-21 Thread Conor Daly

On Sat, Jan 20, 2001 at 05:08:24PM +0300 or so it is rumoured hereabouts, 
Vitaly A. Repin thought:
 On Sat, Jan 20, 2001 at 03:03:31PM +0100, Jeroen Valcke wrote:
 
  very simple obvious task. How can I move messages to another folder. I
  read something of a copy command (C) but nothing of a move command. By
  tagging the messages I would be able to move a bunch of msgs to another
  mailbox, right?
 
 Yes.  You should tag the messags you like, press ";" key, and after this press "s" 
key.   It seems to me, this is what you need.
 
 Also, you can use the "d" command to delete message from the mailbox.
 You can do this command with ";" prefix too.  
 
 -- 
 WBR  WBW, Vitaly.
Interestingly, I don't seem to need the ";" when using 'd', 'C', 'N' on
tagged messages.  It happens automatically.  I'm using 

[cdaly@Hobbiton cdaly]$ mutt -v
Mutt 1.0.1i (2000-01-18)
Copyright (C) 1996-2000 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 2.2.14-5.0 [using slang 10202]
Compile options:
-DOMAIN
-HOMESPOOL  -USE_SETGID  -USE_DOTLOCK  +USE_FCNTL  -USE_FLOCK
+USE_IMAP  +USE_GSS  +USE_POP  +HAVE_REGCOMP  -USE_GNU_REGEX  +HAVE_COLOR  
+HAVE_GPG  -BUFFY_SIZE 
-EXACT_ADDRESS  +ENABLE_NLS
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/spool/mail"
SHAREDIR="/var/tmp/mutt-root/etc"
SYSCONFDIR="/var/tmp/mutt-root/etc"
-ISPELL
_PGPPATH="/usr/bin/gpg"
_PGPGPGPATH="/usr/bin/gpg"
To contact the developers, please mail to [EMAIL PROTECTED].


-- 
Conor Daly [EMAIL PROTECTED]

Domestic Sysadmin :-)
-
faenor.cod.ie
  9:05pm  up 89 days,  3:33,  0 users,  load average: 0.08, 0.02, 0.02

Hobbiton.cod.ie
  9:02pm  up 4 days, 21:21,  1 user,  load average: 0.00, 0.00, 0.00



Re: Encrypting attachments with GnuPG so that Eudora can see it... SOLUTION

2001-01-21 Thread msquared

On Fri, Jan 19, 2001 at 05:08:34PM +0100, Sven Guckes wrote:

 This is a problem of Eudora, right?

As it happens, yes you're right.  :)  At the time I didn't know who was at
fault, I merely found out how to solve the incompatibility with a bit of a
hack.  :)

  Tell the Eudora developers!

I'm going to try...  I'm poking around www.eudora.com to see if there's an
appropriate email addres to submit bug reports to...

 Adding workarounds to mutt for other broken software is WRONG!

Oh, I agree 100%.  I just identified a workaround that allows me to do
what I want right now, and thought I'd pass it on.


I dug into the mutt-dev archives for more information, in case it had
already been discussed there, and it seems it has.  Apparently, the code
that does wrongful things by Eudora was actually a kludge to make Mutt
work with Outlook.  Figures...

 2
Regards, /|/|
/   |



Re: alias question

2001-01-21 Thread Eugene Lee

On Sat, Jan 20, 2001 at 06:57:19AM -0800, Dale Morris wrote:
: 
: I want to be able to add a little information about some of my aliases, such
: as who the person is or maybe their phone number, or whatever. Can I just
: add the information, comment it out with ##, or is there a better way?
: I'm not the greatest with Unix scripts..

Mutt scripts, including the aliases files, can be commented out by
putting a # as the first character on the line.  So you can do things
like so:

alias eugene "Eugene Lee" [EMAIL PROTECTED]
# home phone is 987-654-3210
# work phone is 123-456-7890
# note: he is really freaky!


-- 
Eugene Lee
[EMAIL PROTECTED]



Re: Moving mail to another mailbox

2001-01-21 Thread Vitaly A. Repin

On Sat, Jan 20, 2001 at 09:04:30PM +, Conor Daly wrote:

 Interestingly, I don't seem to need the ";" when using 'd', 'C', 'N' on
 tagged messages.  It happens automatically.  I'm using 

It seems to me, the cause is the "auto_tag" variable in muttrc set to "yes".
Quotation from "man muttrc":
auto_tag
  Type: boolean
  Default: no

  When set, functions in the index menu which  affect
  a  message  will  be applied to all tagged messages
  (if there are any).  When unset, you must first use
  the  tag-prefix function (default: ";") to make the
  next function apply to all tagged messages.

 [cdaly@Hobbiton cdaly]$ mutt -v
 Mutt 1.0.1i (2000-01-18)

By the way, I am using Mutt 1.2.5i (2000-07-28).
It is newer than yours, as I can guess from the version number.
May be you should be intresting to upgrade your mutt.

-- 
WBR  WBW, Vitaly.




Several quesions about mutt customizing

2001-01-21 Thread Vitaly A. Repin

Hello, All!

I have several questions related to mutt customizing.
I hope, you'll help me.

The questions are:
1) How can I redefine the keys used to scroll message by 1 line?
I am about "backspace" and "enter" keys.  
I want to use keys "up" and "down" to do this case.

2) I am russian, that's why  I am using localized mutt.  
I like russian letters in menu and help, but it is very uncomfortable for me
to use russian letters when replying to mutt questions.  I'd like to use
letters "y"/"n" for this purpose, not the russian letters.
Can I fix this problem?

-- 
WBR  WBW, Vitaly.




Re: alias question

2001-01-21 Thread Dale Morris

thanks Eugene, that makes mutt even more useful..
Eugene Lee [[EMAIL PROTECTED]] wrote:
 On Sat, Jan 20, 2001 at 06:57:19AM -0800, Dale Morris wrote:
 : 
 : I want to be able to add a little information about some of my aliases, such
 : as who the person is or maybe their phone number, or whatever. Can I just
 : add the information, comment it out with ##, or is there a better way?
 : I'm not the greatest with Unix scripts..
 
 Mutt scripts, including the aliases files, can be commented out by
 putting a # as the first character on the line.  So you can do things
 like so:
 
   alias eugene "Eugene Lee" [EMAIL PROTECTED]
   # home phone is 987-654-3210
   # work phone is 123-456-7890
   # note: he is really freaky!
 
 
 -- 
 Eugene Lee
 [EMAIL PROTECTED]

-- 
"You are entitled to your actions...not the results"
 --Bhagavad Gita



Re: Several quesions about mutt customizing

2001-01-21 Thread Michael Tatge

Vitaly A. Repin muttered:
 1) How can I redefine the keys used to scroll message by 1 line?
 I am about "backspace" and "enter" keys.  
 I want to use keys "up" and "down" to do this case.

bind pager down next-line
bind pager up previous-line

 2) I am russian, that's why  I am using localized mutt.  
 I like russian letters in menu and help, but it is very uncomfortable for me
 to use russian letters when replying to mutt questions.  I'd like to use
 letters "y"/"n" for this purpose, not the russian letters.
 Can I fix this problem?

You need to rebind most default keys. Look at the bind and functions
sections of the manual.

HTH,

Michael
-- 
"Oh, I've seen copies [of Linux Journal] around the terminal room at The
Labs."
(By Dennis Ritchie)

PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key



Re: Default mailbox display?

2001-01-21 Thread Heinrich Langos

On Sun, Jan 21, 2001 at 04:23:53PM +0100, Martin Schweizer wrote:
 Hello Heinrich
 
 On Fri, Jan 19, 2001 at 12:24:40PM +0100 Heinrich Langos wrote:
One thing that I think would help not only me, but tons of others is
something like this:

mailbox 1   3 new messages
mailbox 2  12 new messages
mailbox 3   8 new messages
  
  how about this ? 
  
  Mail/mutt-users  [Msgs:413   New:18   1.1M]
  Mail/sf/vuln-dev [Msgs:141478K]
  Mail/nymip   [Msgs:54 368K]
 
 The above is nice! But how you do you set the 'index_format=' variable for 
 this view?

you can't ... thats what this whole thread is about. ;-)

i was just making up something to stirr up those who are content with
something that is not good enough. something that could be done better
but isn't.

-heinrich



Re: Default mailbox display?

2001-01-21 Thread Dave Pearson

On Sat, Jan 20, 2001 at 05:40:03PM +0100, Heinrich Langos wrote:
 On Fri, Jan 19, 2001 at 12:05:01PM +, Dave Pearson wrote:
  On Fri, Jan 19, 2001 at 12:24:40PM +0100, Heinrich Langos wrote:
 
   the problem with "-y" is that it simply doesn't work reliably.
  
  Yes it does.
 
 No it doesn't. Been there, tried it. 

Then your experience is different from mine. I've been using mutt since
before the mailboxes feature was added and, apart from the documented issues
(which you quoted) it has always worked reliably. That's why I'm saying it
does work reliably. The only things I've ever seen that can affect it are
those that are documented.

 We talk about multiple incoming mboxes that are fed by procmail, don't we?

Correct.

 I can asure you that I often find new mail in these mailboxes eventhough
 "mutt -y" doesn't tell so. That may be because wo do backup our system.
 And from time to time I allow myself to grep my mail directory for some
 phonenumber or other information.

There you go then. The reason that the mailboxes appear to have not been
updated since you last read them is because they've not been updated since
you last "read" them. I do backups here too and I don't have a problem,
that's because I ensure that my backup solution preserves timestamps.

  That quote is informing you that if you allow other tools to modify the
  timestamps. It doesn't say that mutt's detection of mailboxes with new mail
  is unreliable.
 
 Yes it does. Or what else does this note say? 

The quote is informing you that external processes might change the
timestamp behaviour.

 So please stop defending mutt's weakness in this area and lets try to
 think of a way to improve mutt. I love mutt and I want it to suck even
 less! :-)

Please don't suggest that I'm defending a weakness, I'm not. I am pointing
out that it does what it says in the documentation. It points out it's own
weakness and that other than the documented issues it's reliable.

 or is there a _reasonable_ opposition against saving status information
 that i don't see?

Saving such information won't help you work out how many new mails there
are, or if there is new mail at all. It would let you know if the mailbox
had been modified in some way, which is pretty much what mutt does right
now.

-- 
Dave Pearson:  | mutt.octet.filter - autoview octet-streams
http://www.davep.org/  | mutt.vcard.filter - autoview simple vcards
Mutt:  | muttrc2html   - muttrc - HTML utility
http://www.davep.org/mutt/ | muttrc.sl - Jed muttrc mode



Re: Default mailbox display?

2001-01-21 Thread Heinrich Langos

On Sun, Jan 21, 2001 at 03:59:22PM +, Dave Pearson wrote:
 On Sat, Jan 20, 2001 at 05:40:03PM +0100, Heinrich Langos wrote:
  On Fri, Jan 19, 2001 at 12:05:01PM +, Dave Pearson wrote:
   On Fri, Jan 19, 2001 at 12:24:40PM +0100, Heinrich Langos wrote:
  
the problem with "-y" is that it simply doesn't work reliably.
   
   Yes it does.
  
  No it doesn't. Been there, tried it. 
 
 Then your experience is different from mine. I've been using mutt since
 before the mailboxes feature was added and, apart from the documented issues
 (which you quoted) it has always worked reliably. That's why I'm saying it
 does work reliably. The only things I've ever seen that can affect it are
 those that are documented.
 
[...]
 
 The quote is informing you that external processes might change the
 timestamp behaviour.

leading to non-detection of new mail ... i don't want mutt to tell me
if i or some programms have accessed the mailbox. i want it to tell me
if there is new mail in there.

BTW: pointing your finger at evil software that doesn't conform to
standards will not solve the problem. if that was enough, nobody at the
samba development team would have to care about yet another
microsoft-"extention" of standards.

  So please stop defending mutt's weakness in this area and lets try to
  think of a way to improve mutt. I love mutt and I want it to suck even
  less! :-)
 
 Please don't suggest that I'm defending a weakness, I'm not. I am pointing
 out that it does what it says in the documentation. It points out it's own
 weakness and that other than the documented issues it's reliable.

sorry, but the documented issues is what i am ranting about and what i
proposed a solution for. documenting an issue may be enough for M$ or
IBM. working to resolve the documented issue is what open source is
about, isn't it?

  or is there a _reasonable_ opposition against saving status information
  that i don't see?
 
 Saving such information won't help you work out how many new mails there
 are, or if there is new mail at all. It would let you know if the mailbox
 had been modified in some way, which is pretty much what mutt does right
 now.

nope ... right now mutt only shows that the mailbox has been accessed.
not if it has been modified. 

right now a simple grep will screw up new mail detection.

try this: 
$ echo blah | mail yourself@localhost
$ grep something /var/spool/mail/yourself
$ mutt -y
and you see no "N" ... pretty sad, isn't it?

if mutt would realy show modification i would instantly shut up.

i'm not saying that mutt should constantly scan the whole mailboxes or
anything like that. i just say it could do so on request. or on
startup. but it seems that i am the only one with that problem. so i
guess i'll have to roll my own mutt. i guess the code that is needed
is already in there... it just needs some tweaking. 

-heinrich

ps: sorry for my uppish tone ... but i have recently had an overdose
of "it's free. quit moaning!"-attitude. :)

-- 
Heinrich Langos [EMAIL PROTECTED]
 pgp: http://wh9.tu-dresden.de/~heinrich/pub_pgp_key.asc
 _
|o| The reason we come up with new versions is not to fix bugs. |o|
|o| It's absolutely not. It's the stupidest reason to buy a new |o|
|o| version I ever heard. -- Bill Gates,  Microsoft Corporation |o|
 ~



Re: Default mailbox display?

2001-01-21 Thread Axel Bichler

Hi Heinrich!

On Fri, 19 Jan 2001, Heinrich Langos wrote:

 how about this ? 
 
 Mail/mutt-users  [Msgs:413   New:18   1.1M]
 Mail/sf/vuln-dev [Msgs:141478K]
 Mail/nymip   [Msgs:54 368K]
 
 now wouldn't that be nice ?

There's a patch available on Brandon Long's "mutt insanity"
site (linked from mutt.org). 

quote

Folder Count This patch causes mutt to count the number of
messages and new messages in a folder when you are using the
mutt Folder Mode (dirlist.c). This has a lot of overhead,
and is slow (especially over NFS), but if you have cycles to
spare, or few mail folders, this is for you. 

First Version Patched: 0.47
Author: Brandon Long 
PGP Effects: None

/quote

The patch is targeted at an older version of mutt (1.0 or
so, IIRC), but it shouldn't be too hard to adopt it for a
current version.

If you try it, I would like to know how it works.

Another approach I've seen on one of the linked mutt pages
is a script, which uses procmail's log to determine the
number of new messages.

Regards,
Axel



Keeping the [...]

2001-01-21 Thread Brian Foley


Hello All,
  Does anybody know if there is a way to keep the lines such as:

[-- Type: text/plain, Encoding: 7bit, Size: 1 --]

when you are printing or replying to a mail?  This would be useful for
text attachments that are autoviewed, so that you can see where one
attachment finishes and the other begins in a print-out of the mail.
  Brian.


-- 
Brian Foley -- [EMAIL PROTECTED] -- www.maths.tcd.ie/~brianf

A little inaccuracy sometimes saves tons of explanation.
-- H. H. Munroe



thread date question

2001-01-21 Thread Ken Weingold

I'm sorry, but I have looked all over my muttrc and the mutt manual,
but can't find this anymore.  What variable is it that pushed a thead
to the top of the index if there is new mail in it?

Thanks.


-Ken

-- 
[EMAIL PROTECTED]AIM: ScopusFest



Re: thread date question

2001-01-21 Thread Heinrich Langos

On Sun, Jan 21, 2001 at 02:42:24PM -0500, Ken Weingold wrote:
 I'm sorry, but I have looked all over my muttrc and the mutt manual,
 but can't find this anymore.  What variable is it that pushed a thead
 to the top of the index if there is new mail in it?
 

set sort_aux=last-date  # date of the last message in thread


-heinrich



Re: thread date question

2001-01-21 Thread Josh Huber

On Sun, Jan 21, 2001 at 02:42:24PM -0500, Ken Weingold wrote:
 I'm sorry, but I have looked all over my muttrc and the mutt manual,
 but can't find this anymore.  What variable is it that pushed a thead
 to the top of the index if there is new mail in it?

I think you're looking for sort_aux.  f. ex:
set sort_aux=date-received

-- 
Josh Huber | [EMAIL PROTECTED] |
1024D/6B21489A 61F0 6138 BE7B FEBF A223  E9D1 BFE1 2065 6B21 489A

 PGP signature


Re: Default mailbox display?

2001-01-21 Thread Daniel Freedman

On Fri, Jan 19, 2001, Dave Pearson wrote:
 Yes it does.
 
  to quote the docs:
  ---
  Note: new mail is detected by comparing the last modification time to
  the last access time. Utilities like biff or frm or any other program
  which accesses the mailbox might cause Mutt to never detect new mail
  for that mailbox if they do not properly reset the access time. Backup
  tools are another common reason for updated access times.
  ---
 
 That quote is informing you that if you allow other tools to modify the
 timestamps. It doesn't say that mutt's detection of mailboxes with new mail
 is unreliable.

Hi,

I'd like to follow up this conversation with a concrete question about
this new mail detection that has been bothering me for a bit:

I've never been able to have mutt inform me of new mail in my
mailboxes, which are filtered by procmail after being retreived from
the dept. mailhub by fetchmail (even though they're listed properly
with the mailbox command in my muttrc).  I'm mentioning this as I
don't think I'm encountering any of the noted access issues above as I
don't grep my mailbox files or otherwise touch them outside mutt and
the only backup script that the sysadmin tells us about runs at 5am
everyday (and I still can't see new mail at any time of the day).  My
only guess might be that I'm running on AFS, which doesn't seem to be
as extensively tested and I've encountered a few other mail
difficulties with AFS.

My mutt is now at 1.0.1i, and I'll try to convince the sysadmin to
upgrade to 1.25.  Could this version difference affect my not seeing
new mail marked, or maybe it's still present in the current release?
Am i correct to guess AFS?  Any other suggestions are much
appreciated.

Thanks so much,

Daniel


-- 
Daniel A. Freedman
Laboratory for Atomic and Solid State Physics
Department of Physics
Cornell University



Re: Default mailbox display?

2001-01-21 Thread Axel Bichler

Hi Dave!

On Sun, 21 Jan 2001, Dave Pearson wrote:
 
 Obviously the best method of dealing with this is to implement a solution,

Ack. But before reinventing something, it seems always
advisible to check if there's alreay a solution. Finally,
this can be accomplished by a discussing the problem here...

 that's more constructive than a self-confessed "uppish tone". It would seem
 you've decided to do that so I don't really see a problem or a need for such
 a tone.

On the other hand, meticulously insisting on an "It does what
it says" point of view could be perceived as an "uppish
tone", too.

I would also like to see the discussed feature, so I'm
thinking about my contribution to an appropriate solution.

Regards,
Axel