Re: why is mutt better?

[Jeremy Blosser]

Eugene Lee [[EMAIL PROTECTED]] wrote:
> Having said this, I saw one feature in TheBat that I'd like to see Mutt
> have someday: the ability to create and use templates for new messages,
> replies, forwarded messages, etc.

This should be possible now...

1) create the templates you want, using your editor of choice
2) create macros that change the value of 'editor' to call a script/etc.
that processes the reply+template and calls your editor, then set 'editor'
back to the default, eg:

macro index r :set editor=replyscript:set editor=default

With forms of this method the "template" isn't even limited to a text-based
construct, it can really be anything at all.

-- 
Jeremy Blosser   |   [EMAIL PROTECTED]   |   http://jblosser.firinn.org/

 PGP signature

Re: why is mutt better?

[Ralf Hildebrandt]

> Having said this, I saw one feature in TheBat that I'd like to see Mutt
> have someday: the ability to create and use templates for new messages,
> replies, forwarded messages, etc.

Definitely. Especially for my administrative mail like: "Your mailserver is
an open relay", etc.

-- 
Ralf Hildebrandt <[EMAIL PROTECTED]> www.stahl.bau.tu-bs.de/~hildeb
"My other computer is an abacus ... which is still better than a mac."
  -- Anonymous


 PGP signature

Re: signature send-hook problem

[Byrial Jensen]

On Thu, Mar 09, 2000 at 23:52:30 +0200, Mikko Hänninen wrote:
> And, incidentally, the best (or recommended) way of writing a pattern
> that matches everything is with a single dot, "."

Well, I would say the canonical way to match everything is the ~Ã
pattern. In fact "." is internally converted to "~A" to aviod using
time parsing it as the regular expression it really is.

-- 
Byrial

Re: why is mutt better?

[Marius Gedminas]

On Thu, Mar 09, 2000 at 06:39:45PM +, J McKitrick wrote:
> I just got in a debate over email clients, and my windows friend
> argues anything i can do in mutt, he can do in TheBat! just as easily.
> I checked the feature list, and it is extensive.  Most of what mutt
> offers, thebat offers.  Why is the advantage of mutt, or any
> text-based email client?

I use The Bat! at work.  It is good, but Mutt is much better (for me, at
least).  I miss hooks, macros, patterns, mailing list support, replying
to multiple e-mails with one message, the  command, etc.  The
Bat! does have a couple of features that Mutt lacks, but those are the
features that I do not need.  Maybe others do.

Unfortunatelly, I cannot use Mutt under Windows NT: it dumps core in the
pager.  I've posted stack backtrace on mutt-dev, but nobody seems to
have noticed it (and I don't blame the developers -- they are busy
finishing Mutt 1.2 under Unix).

Marius Gedminas
-- 
Microsoft does have a Year 2000 problem. We're it.

Re: why is mutt better?

[Ralf Hildebrandt]

On Fri, Mar 10, 2000 at 11:28:59AM +0200, Marius Gedminas wrote:

> Bat! does have a couple of features that Mutt lacks, but those are the
> features that I do not need.  Maybe others do.

What features does it have?
 
> Unfortunatelly, I cannot use Mutt under Windows NT: it dumps core in the
> pager.  I've posted stack backtrace on mutt-dev, but nobody seems to

can't you use an external pager?

-- 
Ralf Hildebrandt <[EMAIL PROTECTED]> www.stahl.bau.tu-bs.de/~hildeb
What about the four lusers of the apocalypse? 
I nominate: "advertising", "can't log in", "power switch" and "what backup?" 


 PGP signature

Re: why is mutt better?

[Edmund GRIMLEY EVANS]

I suppose my main reason for using mutt is that it runs on Linux and
(my version of) it can handle Unicode. I think the only other options
for a Unicode MUA on Linux are Mozilla and a suitably patched
bleeding-edge Emacs. (On Windows there's Outlook, of course, which
apparently handles charsets rather well.)

Having switched to mutt from rmail in Emacs there are some other
things I now appreciate, such as its speed, threads, MIME-handling,
and PGP. You could probably get those things in Emacs, apart from the
speed. I still use Emacs as my editor with mutt. Perhaps I should make
jed do Unicode so I have an alternative ...

Edmund

Re: why is mutt better?

[Stefan `Sec` Zehl]

On Fri, Mar 10, 2000 at 09:38:22AM +0100, Ralf Hildebrandt wrote:
> > Having said this, I saw one feature in TheBat that I'd like to see Mutt
> > have someday: the ability to create and use templates for new messages,
> > replies, forwarded messages, etc.
> 
> Definitely. Especially for my administrative mail like: "Your mailserver is
> an open relay", etc.

I personally think this is better done in your editor. I have all my
templates put into ~/.dau/ and use the attached macro set. It's started
with ,dau and opens a window with an ls -l. Wander around with hjkl and
select the appropriate file with .

CU,
Sec
-- 
"Computers make very fast, very accurate, mistakes."


" The File-Browser&Reader. Very handsome.

map ,dau o~/.dau/"dddu__filelist

" start the file reader. Directory in register d.
map __filelist :split .
!!ls -l d 
__LN-__mm
nn __LN- /[0-9] \K..  \=[0-9]3E2l
" crate mapping for enter
noremap __mm :map  __rm0__LN-mai:r d`a"ay$:q!
@a

" remove mapping
noremap __rm :unmap 

 PGP signature

Re: why is mutt better?

[Thomas Roessler]

On 2000-03-10 10:07:11 +, Edmund GRIMLEY EVANS wrote:

> Perhaps I should make jed do Unicode so I have an
> alternative ...

This sounds like a great idea. ;-)

-- 
http://www.guug.de/~roessler/

Re: why is mutt better?

[Eugene Lee]

On Fri, Mar 10, 2000 at 02:20:27AM -0600, Jeremy Blosser wrote:
:Eugene Lee [[EMAIL PROTECTED]] wrote:
:> 
:> Having said this, I saw one feature in TheBat that I'd like to see Mutt
:> have someday: the ability to create and use templates for new messages,
:> replies, forwarded messages, etc.
:
:This should be possible now...
:
:1) create the templates you want, using your editor of choice
:2) create macros that change the value of 'editor' to call a script/etc.
:that processes the reply+template and calls your editor, then set 'editor'
:back to the default, eg:
:
:macro index r :set editor=replyscript:set editor=default
:
:With forms of this method the "template" isn't even limited to a text-based
:construct, it can really be anything at all.

In this aspect, Mutt is far more configurable because of its ability to
call external programs to do things.  However, it's not possible to
insert information --- that Mutt already knows --- into a template
without writing another email parser.  For example, let's say I have a
template for replying to messages from a particular mailing list.  My
template might look like this:

Hullo, %%%FROM%%%!

I have a comment about your message about "%%%SUBJECT%%%" on %%%DATE%%%.

- begin original message -
%%%BODY%%%
- end original message -

%%%SIGNATURE%%%

As you can see, there is information about the email that I'd like to
insert in place of the "%%%" strings.  Mutt already knows what this
stuff is.  But there's no mechanism to pass this information onto an
external script.  Such a script has to figure this information out by
itself by parsing the headers, checking for RFC compliancy, fixing
special ISO-8859 characters, handling MIME attachments, etc.

Maybe Mutt could pass this information along as environment variables to
an external script to handle.  Or maybe when Mutt creates a temp file,
it can read in a template and substitute all the information first,
before passing the temp file onto the user's editor.


-- 
Eugene Lee
[EMAIL PROTECTED]

Re: why is mutt better?

[Thomas Roessler]

On 2000-03-10 02:57:41 -0800, Eugene Lee wrote:

>   Hullo, %%%FROM%%%!

>   I have a comment about your message about "%%%SUBJECT%%%" on %%%DATE%%%.

set attribution="Hullo, %F!\n\nI have a comment about\
your message about \"%s\" on %d.\n\n\
- begin original message -"

>   - end original message -

set post_indent_string="- end original message "


-- 
http://www.guug.de/~roessler/

Re: attachments appear as NoName

[Stefan Bender]

Hi,

On Thu, Mar 09 2000 14:11:46 -0500 wrote David T-G
with subject "Re: attachments appear as NoName":

> I've lost track of whether [the argument is that] mutt should put a
> 'name="*"' parameter on the Content-Type: header or [the complaint is
> that] mutt expects such a parameter.  It seems to me that either can be
> fixed with scripts.

Maybe I misstated my argument a little bit. I don't think mutt expects
a `name' parameter but some other mail clients may do, but I'm not
sure, I don't have dtmail. At least mutt does not create it but other
mail clients do (at least Outlook and kmail).

> 1) If we want mutt to provide the parameter, change $sendmail to a script
> that automatically adds the name= data to the Content-Type: line and then
> feeds everything on to sendmail.

The rfc doesn't say that it is necessary to behave that way, but my
_guess_ was that dtmail looks for it and if it doesn't find it, it
marks attachments as `NoName'. In this case writing some wrappers for
sendmail would fix the problem.

> This doesn't mean, of course, that I know anything about MIME or even
> general email RFCs :-)  If "everyone" out there expects a name= parameter,
> maybe we could just hack mutt to spit out Content-Type: headers that way
> with a leading X-Content-Type-Explanation: "for stupid mail clients like
> dtmail" so that everyone knows we know why we're doing it ;-)

Good suggestion ... :-)

Regards, Stefan.

-- 
Mark's Dental-Chair Discovery:
Dentists are incapable of asking questions that require a
simple yes or no answer.

Re: why is mutt better?

[Eugene Lee]

On Fri, Mar 10, 2000 at 12:04:42PM +0100, Thomas Roessler wrote:
:On 2000-03-10 02:57:41 -0800, Eugene Lee wrote:
:
:set attribution="Hullo, %F!\n\nI have a comment about\
:   your message about \"%s\" on %d.\n\n\
:   - begin original message -"

:set post_indent_string="- end original message "

I was wrong saying that there wasn't a way in Mutt to pass this info
onto an external script.  I stand corrected.  Excuse me while I RTFM.
Yet again.  :)

But setting a separate set of attribute/post_indent_string values for
each send-hook could get ugly with the escapes needed for extra quotes.


-- 
Eugene Lee
[EMAIL PROTECTED]

Re: [Announce] mutt-1.1.8 is out

[Stephan Seitz]

Hi!

On Sam, Mär 04, 2000 at 02:19:36 +0100, Thomas Roessler wrote
> Mutt-1.1.8 is out.  This is another BETA version.  Changes

I would like to know, which patches for 1.0 are part of the new
version.
I am using the save_alias-patch and the compressed_folder-patch.

The manual for 1.1.8 doesn't mention it, but maybe the patches
will be part of the 1.2-release? They are really useful.

How does mutt handle text/plain with difficult charsets (like
japanese) now? In 1.0 mutt thinks, it can handle text/plain by its
own, but that doesn't work always.

A long time ago, there was a patch for 0.9x, so that I could write the
line
auto_view text/plain;charset=!(us-ascii|iso-8859-1)
in my muttrc and
text/plain; showtext %{charset}; copiousoutput
in my mailcap.

Can I do such specifications now in the official release?

Shade and sweet water!

Stephan

-- 
| Stephan SeitzE-Mail: [EMAIL PROTECTED] |
|  WWW: http://fsing.fs.uni-sb.de/~stse/|
| PGP Public Keys: http://fsing.fs.uni-sb.de/~stse/pgp.html |

 PGP signature

Re: why is mutt better?

[Vincent Lefevre]

On Thu, Mar 09, 2000 at 13:57:08 -0600, David DeSimone wrote:
> If TheBat! does everything that he wants it to, then he should use it.

No

I received several messages sent by TheBat, and they weren't really
RFC-compliant! It was breaking threads or something like that.
Perhaps this has been fixed. And the sig separator was incorrect.

-- 
Vincent Lefèvre <[EMAIL PROTECTED]> - Web:  - 100%
validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des
Jeux Mathématiques et Logiques, TETRHEX, etc.
Computer science / computer arithmetic / Arénaire project at LIP, ENS-Lyon

test (n/t)

[J McKitrick]

-- 
-jm

'from' data in headers

[J McKitrick]

In the pager, i see two different 'from' lines.  One is the send, the
other is the real sender.  For example, on email from this list, i see
the name of the sender, and above that is 'mutt-list-owner', or
something similar.  How can i get rid of that unnecessary line with
'mutt-list-owner'?

-- 
-jm

Re: 'from' data in headers

[Michael Elkins]

On Fri, Mar 10, 2000 at 05:12:07PM +, J McKitrick wrote:
> In the pager, i see two different 'from' lines.  One is the send, the
> other is the real sender.  For example, on email from this list, i see
> the name of the sender, and above that is 'mutt-list-owner', or
> something similar.  How can i get rid of that unnecessary line with
> 'mutt-list-owner'?

ignore 'from '

note the space after the word from, it's important.

me
-- 
pgp key available from http://www.cs.hmc.edu/~me/elkins-pgp-key.asc

 PGP signature

Re: %N in $folder_format

[Drew Bloechl]

On Thu, Mar 09, 2000 at 11:26:49PM -0500, David T-G wrote:
> Is your shell, perhaps, checking for new mail as well?  Anything
> that accesses the folder, as I recall, will reset the new function.
> Thus, --enable-buffy-size might just be the ticket after all.

I have a few things checking for mail.  I did recompile with 
--enable-buffy-size and verified that it was in there with mutt -v, 
but that %N is still blank.  Is there something else I have to do to 
get it to work?  I assume the check is automatic on entering "browser" 
mode.  

-- 
Drew Bloechl
[EMAIL PROTECTED]

Re: 'from' data in headers

[J McKitrick]

On Fri, Mar 10, 2000 at 09:20:03AM -0800, Michael Elkins wrote:
> On Fri, Mar 10, 2000 at 05:12:07PM +, J McKitrick wrote:
> > In the pager, i see two different 'from' lines.  One is the send, the
> > other is the real sender.  For example, on email from this list, i see
> > the name of the sender, and above that is 'mutt-list-owner', or
> > something similar.  How can i get rid of that unnecessary line with
> > 'mutt-list-owner'?
> 
> ignore 'from '
> 
> note the space after the word from, it's important.
I have:
ignore *
unignore subject from to cc

adding:
ignore 'from'

doesn't change anything
> 
> me
> -- 
> pgp key available from http://www.cs.hmc.edu/~me/elkins-pgp-key.asc



-- 
-jm

Re: 'from' data in headers

[Drew Bloechl]

On Fri, Mar 10, 2000 at 05:38:08PM +, J McKitrick wrote:
> I have:
> ignore *
> unignore subject from to cc
> 
> adding:
> ignore 'from'

Try:

ignore *
unignore subject: from: to: cc:

Note the colons.  

-- 
Drew Bloechl
[EMAIL PROTECTED]

Re: %N in $folder_format

[Mikko Hänninen]

Drew Bloechl <[EMAIL PROTECTED]> wrote on Fri, 10 Mar 2000:
> I have a few things checking for mail.  I did recompile with 
> --enable-buffy-size and verified that it was in there with mutt -v, 
> but that %N is still blank. 

A couple of other things to check that I can think of:

1) When you enter these folders which are supposed to have new mail,
does Mutt actually show any messages as new?  Is it just the file
browser or also the folder index too?

2) Are you actually using the right $folder_format setting?  Use

  :set ?folder_format

... to display the current value, when in Mutt.

3) You could try to use a different folder format for testing, eg.
Maildir.  Maildirs aren't as sensitive as mbox folders and it's easy
to also manipulate them from the shell to have a desired "new-ness
state" (ie. by moving a message file under the "new" subdir).


> Is there something else I have to do to 
> get it to work?  I assume the check is automatic on entering "browser" 
> mode.  

It should be automatic, yes, and not require any special actions.


Mikko
-- 
// Mikko Hänninen, aka. Wizzu  //  [EMAIL PROTECTED]  //  http://www.iki.fi/wiz/
// The Corrs list maintainer  //   net.freak  //   DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
Time was invented by an Irish guy named O'Clock.

Re: 'from' data in headers

[Mikko Hänninen]

J McKitrick <[EMAIL PROTECTED]> wrote on Fri, 10 Mar 2000:
> On Fri, Mar 10, 2000 at 09:20:03AM -0800, Michael Elkins wrote:
> > ignore 'from '
> > 
> > note the space after the word from, it's important.

> adding:
> ignore 'from'
> 
> doesn't change anything

Right, it wouldn't.  Try the following line EXACTLY (copy/paste it if
necessary):

ignore 'from '


There MUST be a space included after the word "from" for it to work.
Like Michael already told you...


Mikko
-- 
// Mikko Hänninen, aka. Wizzu  //  [EMAIL PROTECTED]  //  http://www.iki.fi/wiz/
// The Corrs list maintainer  //   net.freak  //   DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
Classified signature.  Please enter password to continue: _

Re: signature send-hook problem

[David DeSimone]

Byrial Jensen <[EMAIL PROTECTED]> wrote:
>
> Well, I would say the canonical way to match everything is the ~A
> pattern.

When referring to message patterns, ~A is the "true" way to match all
messages, but other hooks refer to text strings, or pathnames, such as
folder-hooks.  For those, ~A matches the home directory of user "A".  :)

-- 
David DeSimone   | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED]   |  that there is no man really clever who has not
Hewlett-Packard  |  found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D  AB A6 15 F1 BB BE 8C 44

jump settings when viewing mail

[Stephen Kaluzny]

I am just starting to use mutt and I would like it to not jump to a new
mail message when I delete or save a message.  I have searched through
the online manuals and many of the various .muttrc files posted on the
web and I cannot find the settings to control this.

Thanks in advance,
 Stephen Kaluzny
 [EMAIL PROTECTED]

Re: %N in $folder_format

[Drew Bloechl]

On Fri, Mar 10, 2000 at 07:53:48PM +0200, Mikko H?nninen wrote:
> A couple of other things to check that I can think of:
> 
> 1) When you enter these folders which are supposed to have new mail,
> does Mutt actually show any messages as new?  Is it just the file
> browser or also the folder index too?

Yes, in the index there are messages marked as new.  That part of it 
has always worked.  

> 2) Are you actually using the right $folder_format setting?  Use

folder_format="%3C %N %-32.32f %-16.16d %s"

> 3) You could try to use a different folder format for testing, eg.
> Maildir.  Maildirs aren't as sensitive as mbox folders and it's easy
> to also manipulate them from the shell to have a desired "new-ness
> state" (ie. by moving a message file under the "new" subdir).

Well, I'd prefer not to.  I'd rather keep mbox format with no "N" in 
the browser than have to switch over to Maildir.  

-- 
Drew Bloechl
[EMAIL PROTECTED]

send-hook From: change

[J McKitrick]

I'm having a problem getting pattern matching to work for send-hook.
i want to change my From: address when i send mail to any list on
freebsd.org.  Here's what i have:

send-hook . "my_hdr From: [EMAIL PROTECTED]"
send-hook (freebsd-*@freebsd.org) \
"my_hdr From: [EMAIL PROTECTED]"

The lists i refer to are freebsd-@freebsd.org

What am i doing wrong?
-- 
-jm

[j_mckitrick@bigfoot.com: send-hook From: change]

[J McKitrick]

I'm having a problem getting pattern matching to work for send-hook.
i want to change my From: address when i send mail to any list on
freebsd.org.  Here's what i have:

send-hook . "my_hdr From: [EMAIL PROTECTED]"
send-hook (freebsd-*@freebsd.org) \
"my_hdr From: [EMAIL PROTECTED]"

The lists i refer to are freebsd-@freebsd.org

What am i doing wrong?
-- 
-jm

Re: 'from' data in headers

[J McKitrick]

What is the name of the other From field?
Maybe i'll try that one and compare.
-- 
-jm

Re: jump settings when viewing mail

[Mikko Hänninen]

Stephen Kaluzny <[EMAIL PROTECTED]> wrote on Fri, 10 Mar 2000:
> I am just starting to use mutt and I would like it to not jump to a new
> mail message when I delete or save a message.  I have searched through
> the online manuals and many of the various .muttrc files posted on the
> web and I cannot find the settings to control this.

The relevant configuration option is $resolve.
Include this in your .muttrc:

  unset resolve


Regards,
Mikko
-- 
// Mikko Hänninen, aka. Wizzu  //  [EMAIL PROTECTED]  //  http://www.iki.fi/wiz/
// The Corrs list maintainer  //   net.freak  //   DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
I'm a shareware signature!  Send $2 if you use me, $10 for a manual.

Re: signature send-hook problem

[J McKitrick]

How does mutt *do* all of these things with only 300K?  I'm stunned by
the amount of pattern matching and on-the-fly processing the prog must
do, and yet it is SO fast!  And totally configurable!
-- 
-jm

Re: %N in $folder_format

[Mikko Hänninen]

Drew Bloechl <[EMAIL PROTECTED]> wrote on Fri, 10 Mar 2000:
> Well, I'd prefer not to.  I'd rather keep mbox format with no "N" in 
> the browser than have to switch over to Maildir.  

Well, I meant only for testing, trying out to see that you can get the
N displayed at all.

Are these folders where there is new mail but which aren't shown with
newly created with new mail, ie. they didn't exist before new mail was
added to them by whatever delivery program?  I remember once finding
that that new mail recognition didn't work unless I set $keep_empty,
especially with the --enable-buffy-size option.


Mikko
-- 
// Mikko Hänninen, aka. Wizzu  //  [EMAIL PROTECTED]  //  http://www.iki.fi/wiz/
// The Corrs list maintainer  //   net.freak  //   DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
Time is what keeps everything from happening at once.

Re: %N in $folder_format

[Mikko Hänninen]

Mikko Hänninen <[EMAIL PROTECTED]> wrote on Fri, 10 Mar 2000:
> that that new mail recognition didn't work unless I set $keep_empty,

... that should, of course, be $save_empty, not $keep_empty.


Mikko
-- 
// Mikko Hänninen, aka. Wizzu  //  [EMAIL PROTECTED]  //  http://www.iki.fi/wiz/
// The Corrs list maintainer  //   net.freak  //   DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
Change is inevitable, except from a vending machine.

Re: %N in $folder_format

[David DeSimone]

Drew Bloechl <[EMAIL PROTECTED]> wrote:
>
> Yes, in the index there are messages marked as new.  That part of it
> has always worked. 

When reading the folder, Mutt can tell which messages are new, by
reading the Status: headers.  However, that's only done when opening a
folder; when you just want to know if a folder has new mail in it, it's
much faster to simply check the time-stamp on the file, for mbox
folders.

So, Mutt checks the time to determine if it should put an 'N' for that
folder.  You can check this yourself to see what the system has stored
as a time-stamp on the file:

ls -l /path/to/folder   ==> This gives you the "modified" time.
ls -lu /path/to/folder  ==> This gives you the "accessed" time.

If the folder was modified at a later time than it was accessed, the
folder is assumed to have new mail in it.  Try this yourself on some
folders that have had new mail delivered to them, and see if you can
figure out why they aren't being set the way Mutt thinks they should be.

If the times are showing up as equal, you can use a script like this to
print out the exact times:

perl -e '@stat = stat("/path/to/mfolder"); print "Mod = $stat[9], Acc = 
$stat[8]\n";'

This prints the exact times, to the second, which you can compare.  This
is what Mutt actually does.

Using this technique, perhaps you can determine what the problem is.

-- 
David DeSimone   | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED]   |  that there is no man really clever who has not
Hewlett-Packard  |  found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D  AB A6 15 F1 BB BE 8C 44

Re: %N in $folder_format

[Drew Bloechl]

On Fri, Mar 10, 2000 at 01:17:12PM -0600, David DeSimone wrote:
> If the folder was modified at a later time than it was accessed, the
> folder is assumed to have new mail in it.  Try this yourself on some
> folders that have had new mail delivered to them, and see if you can
> figure out why they aren't being set the way Mutt thinks they should be.

$ ls -l Mail/livid-dev ; ls -lu Mail/livid-dev 
-rw---1 drew drew  3219213 Mar 10 02:23 Mail/livid-dev
-rw---1 drew drew  3219213 Mar  8 12:05 Mail/livid-dev

This particular folder has an mtime greater than its atime, but mutt 
doesn't seem to realize that with or without BUFFY_SIZE.  

-- 
Drew Bloechl
[EMAIL PROTECTED]

Re: [j_mckitrick@bigfoot.com: send-hook From: change]

[Lars Hecking]

J McKitrick writes:
> 
> I'm having a problem getting pattern matching to work for send-hook.
> i want to change my From: address when i send mail to any list on
> freebsd.org.  Here's what i have:
> 
> send-hook . "my_hdr From: [EMAIL PROTECTED]"
> send-hook (freebsd-*@freebsd.org) \
 ^

> "my_hdr From: [EMAIL PROTECTED]"
> 
> The lists i refer to are freebsd-@freebsd.org
> 
> What am i doing wrong?

 '*' is a regexp modifier, not a DOS style wildcard. Your regexp
 will be interpreted as

 "freebsd" plus zero or more of "-" plus "@freebsd.org"

 So, you want to use freebsd-.*@freebsd.org instead:

 "freebsd-" plus zero or more of "any character" plus "@freebsd.org".

 And you don't need the parentheses. I'd rewrite this hook as

 send-hook '~C freebsd-.*@freebsd.org' my_hdr From: [EMAIL PROTECTED]

 The "~C" stands for "To: or Cc:".

Re: send-hook From: change

[Mikko Hänninen]

J McKitrick <[EMAIL PROTECTED]> wrote on Fri, 10 Mar 2000:
> send-hook . "my_hdr From: [EMAIL PROTECTED]"
> send-hook (freebsd-*@freebsd.org) \
> "my_hdr From: [EMAIL PROTECTED]"

> What am i doing wrong?

Use "freebsd-.*@freebsd.org" as the pattern.  The wildcards are standard
regexp style, not shell-expansion style.


Regards,
Mikko
-- 
// Mikko Hänninen, aka. Wizzu  //  [EMAIL PROTECTED]  //  http://www.iki.fi/wiz/
// The Corrs list maintainer  //   net.freak  //   DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
What if there were no hypothetical situations?

cursor location in index

[J McKitrick]

How does mutt decide where to put the cursor in the index when
changing mailboxes?  It would seem the last accessed message would
make sense, but i've noticed that isn't always the case.
-- 
-jm

Re: jump settings when viewing mail

[J McKitrick]

Try 'set resolve'
or 'unset'
i'm not sure which...
-- 
-jm

Re: %N in $folder_format

[Mikko Hänninen]

Drew Bloechl <[EMAIL PROTECTED]> wrote on Fri, 10 Mar 2000:
> This particular folder has an mtime greater than its atime, but mutt 

... I'm at a loss to explain that, but...

> doesn't seem to realize that with or without BUFFY_SIZE.

If you use BUFFY_SIZE, it makes Mutt ignore the access/modification
times and only compares folder sizes to detect new mail.  (IIRC)


Mikko
-- 
// Mikko Hänninen, aka. Wizzu  //  [EMAIL PROTECTED]  //  http://www.iki.fi/wiz/
// The Corrs list maintainer  //   net.freak  //   DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
Bumper sticker: I brake for no apparent reason.

Strange header fields

[Christian R Molls]

Hi everybody,

I am using GMX (a German freemail service) to collect e-mail from
various accounts. Mails that have been collected with GMX have the
following header lines (the example is a mail to this list):

>From [EMAIL PROTECTED]  Fri Mar 10 23:43:44 2000
Return-Path: <[EMAIL PROTECTED]>

Who is responsible for the garbled "From " and "Return-Path:" headers
(as I don't think these are correct)? Is it GMX or is it my MTA? If
the latter, how can I educate my sendmail? Right now I am using
formail to do the job, but that is more cosmetics than a solution.

And at last: what is the purpose of a "From " header (it doesn't even
conform to RFC822, does it?)

Christian

-- 
christian molls
student of laws
univ of cologne

Re: %N in $folder_format

[Drew Bloechl]

On Fri, Mar 10, 2000 at 09:10:46PM +0200, Mikko H?nninen wrote:
> Are these folders where there is new mail but which aren't shown with
> newly created with new mail, ie. they didn't exist before new mail was
> added to them by whatever delivery program?  I remember once finding
> that that new mail recognition didn't work unless I set $keep_empty,
> especially with the --enable-buffy-size option.

No, these are fairly old (and large) folders.  

-- 
Drew Bloechl
[EMAIL PROTECTED]

Re: cursor location in index

[Mikko Hänninen]

J McKitrick <[EMAIL PROTECTED]> wrote on Fri, 10 Mar 2000:
> How does mutt decide where to put the cursor in the index when
> changing mailboxes?  It would seem the last accessed message would
> make sense, but i've noticed that isn't always the case.

The logic goes something like this:

- position at oldest new message
- if there are no new messages, position at oldest unread (old) message
- if there no unread messages, position at newest message

... or somethin like that.  This is just from personal observation, not
any detailed knowledge of what the code does. :-)


Mikko
-- 
// Mikko Hänninen, aka. Wizzu  //  [EMAIL PROTECTED]  //  http://www.iki.fi/wiz/
// The Corrs list maintainer  //   net.freak  //   DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
The 5 year plan: In 5 years we'll make up a new plan. Or just re-use this one.

Re: Strange header fields

[Mikko Hänninen]

Christian R Molls <[EMAIL PROTECTED]> wrote on Sat, 11 Mar 2000:
> From [EMAIL PROTECTED]  Fri Mar 10 23:43:44 2000
> Return-Path: <[EMAIL PROTECTED]>
> 
> Who is responsible for the garbled "From " and "Return-Path:" headers
> (as I don't think these are correct)? Is it GMX or is it my MTA?

It's impossible for us to say.  You'd need to look at the email headers
at your ISP, before they reach your box, to be able to to answer that.

> If the latter, how can I educate my sendmail?

rm -rf /usr/{lib,sbin}/sendmail and install a proper MTA instead? ;-)
Sorry, the question is a bit outside of my knowledge (and outside of the
scope of this list too...), try asking on a sendmail list.

> And at last: what is the purpose of a "From " header (it doesn't even
> conform to RFC822, does it?)

In mbox folders, "From " is used as the message separator.  The same
line also contains the envelope sender information (return path).  It
is not a real header, no -- it should be considered more to be part
of the mbox structure.  When sent, emails don't actually contain this
line.  For you, apparently some MTA long the way (or your MDA) also
stores the evelope sender info in a real Return-Path: header, so you
see the information in both.

If you want my guess, I think your ISP changes the envelope sender and
adds the Return-Path: header with that info, and the "From " line gets
added by your local MDA (mail delivery agent).


Regards,
Mikko
-- 
// Mikko Hänninen, aka. Wizzu  //  [EMAIL PROTECTED]  //  http://www.iki.fi/wiz/
// The Corrs list maintainer  //   net.freak  //   DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
The reason computer chips are so small is that computers don't eat much.

Re: Strange header fields

[Aaron Schrab]

At 01:24 +0100 11 Mar 2000, Christian R Molls <[EMAIL PROTECTED]> wrote:
> From [EMAIL PROTECTED]  Fri Mar 10 23:43:44 2000
> Return-Path: <[EMAIL PROTECTED]>
> 
> Who is responsible for the garbled "From " and "Return-Path:" headers

Nobody, since they're not garbled.  The list server is using VERP
(variable envelope return path, ), so
the address that you have subscribed to the list is encoded in the
return path.

This way when the list software receives a bounce message it's almost
guaranteed that it will have enough information to figure out which
subscribed address is having problems, even when dealing with forwarded
mail and/or broken MTAs (although there are a few MTAs broken enough to
still cause problems.  The problem with VERP, though, is that it only
allows one recipient per outgoing message.

-- 
Aaron Schrab [EMAIL PROTECTED]  http://www.execpc.com/~aarons/
 "Been there, done that, didnt like it threw it out"   -- Alan Cox

Re: Strange header fields

[Lars Hecking]

 
> >From [EMAIL PROTECTED]  Fri Mar 10 23:43:44 2000
> Return-Path: <[EMAIL PROTECTED]>
> 
> Who is responsible for the garbled "From " and "Return-Path:" headers
> (as I don't think these are correct)? Is it GMX or is it my MTA? If
> the latter, how can I educate my sendmail? Right now I am using
> formail to do the job, but that is more cosmetics than a solution.

 It's gbnet, the generous site hosting mutt-users (hi steve :) and more.
 I'm not commenting on the use of qmail here ;-p

 Query your nearest search engine for VERP. This is some sort of intentional
 header mangling (not garbling), so to speak.

> And at last: what is the purpose of a "From " header (it doesn't even
> conform to RFC822, does it?)

 It's an mbox separator. There's more than just RFC822 to email, btw.
 Don't take $200, go back to RFC821 and read up on "envelope".

Re: Strange header fields

[Lars Hecking]

> It's impossible for us to say.  You'd need to look at the email headers
> at your ISP, before they reach your box, to be able to to answer that.
> 
> > If the latter, how can I educate my sendmail?
> 
> rm -rf /usr/{lib,sbin}/sendmail and install a proper MTA instead? ;-)

 Now, that's a bit harsh. Considering that sendmail is more or less The
 Standard, I wouldn't exactly \em{recommend} an alternative MTA. It's more
 like pointing towards alternatives that get the job done just as well
 or better ...

[jcm@dogma.freebsd-uk.eu.org: word wrap]

[J McKitrick]

Subject: word wrap

i realize this is a bit off subject because it is somewhat of an editor problem, but 
it applies to mutt as well.  I
started using xterm with a smaller font, so more words fit per line.  I got complaints 
about my word wrap.  I have word
wrap margin set to 10 in vi, but that isn't helping, i guess.  Is there a better way?
-- 
-jm

- End forwarded message -

-- 
-jm

macros messing up browser under screen

[Greg Matheson]

I have started using screen so that I can launch lynx sessions in
another window. The problem is that this has messed up the
display of the mutt browser. There are error messages and
reverse-video bars placed in the wrong place when I scroll
through my mailboxes, whereas before it was just like scrolling
through the index. The index has not been affected under screen.

I have narrowed the problem down to the macros I have to make the
browser act more like the index and pager. [They write a file
with a count of the mailbox I am viewing at the moment, so I am
placed on it each time I return to the mailbox screen from the
index.] 

Under screen, when I comment out these macros in my .muttrc, the
browser is fine, as before. When I define them again, the display gets
screwed up again.

It is a redrawing problem. Perhaps because the macros take too
long to execute? When I type  the display is refreshed
and everything looks good. 

But when I type  , the screen command to refresh
the screen, the display is not refreshed. This leads me to the
conclusion that this is not just a screen problem, but a problem
due to the interaction between mutt and screen.  is a
mutt command, and that is what redraws the screen. 

For what it's worth here is (one of the macros):

macro browser j ':macro browser \cBJ `$HOME/.jayplus`'\n\cBJ

where in $HOME/.jayplus there is:


#!/bin/bash

#test if last-entry has been reached. If not, add another.
#.
#I have 33 mailboxes including spool, so 32  are needed.
#There is something wrong with the test. I get an error message
#but it still seems to work.

touch $HOME/.jay
JAY=`cat $HOME/.jay`
if [ $JAY = 
""
 ] 
then 
exit
else
echo -n "" >> $HOME/.jay
fi

#$HOME/.jay contains strings of form <..


What advice do you have?

-- 
Greg Matheson   "Vent the pent:"
Chinmin College, Taiwan Samuel Beckett
[EMAIL PROTECTED]