On Mon, Oct 25, 2021 at 08:13:15PM -0400, John Hawkinson wrote:
> Derek Martin wrote on Mon, 25 Oct 2021
> at 19:00:12 EDT in <20211025230012.gc9...@bladeshadow.org>:
>
> > Cost? I see no cost, other than the time needed to physically check
>
> My Oct. 7 email, to which you replied, enumerated
Derek Martin wrote on Mon, 25 Oct 2021
at 19:00:12 EDT in <20211025230012.gc9...@bladeshadow.org>:
> Cost? I see no cost, other than the time needed to physically check
My Oct. 7 email, to which you replied, enumerated several costs that I
perceived.
That you go on to state that you perceive n
On Thu, Oct 07, 2021 at 11:52:02PM -0400, John Hawkinson wrote:
> ಚಿರಾಗ್ ನಟರಾಜ್ wrote on Thu, 7 Oct 2021
> at 23:32:00 EDT in :
>
> > Any email client (including mobile email clients) worth its salt is
> > going to wrap the subject line (at least in the email view, if not
> > in the index view),
On Fri, Oct 08, 2021 at 06:50:24PM +1100, raf wrote:
> My advice is, don't worry about the default.
> If you don't like it, just change it.
>
> "man muttrc" and look for "forward_format".
>
> I think you want something like this in your ~/.muttrc:
>
> set forward_format = "Fwd: %s"
>
> or:
My advice is, don't worry about the default.
If you don't like it, just change it.
"man muttrc" and look for "forward_format".
I think you want something like this in your ~/.muttrc:
set forward_format = "Fwd: %s"
or:
set forward_format = "FW: %s"
They are both common patterns.
And they
So, in my opinion, communication is most effective if the recipient easily
comprehends what is conveyed to him/her. I suspect most recipients of our
e-mails do not know much about mutt except that you likely get it from a place
other than a breeder.
So, [mutt-users@mutt.org: Email Subject] make
12021/06/39 09:94.47 ನಲ್ಲಿ, John Hawkinson ಬರೆದರು:
> ಚಿರಾಗ್ ನಟರಾಜ್ wrote on Thu, 7 Oct 2021
> at 23:32:00 EDT in :
>
> > Any email client (including mobile email clients) worth its salt is
> > going to wrap the subject line (at least in the email view, if not
> > in the index view), so that sho
ಚಿರಾಗ್ ನಟರಾಜ್ wrote on Thu, 7 Oct 2021
at 23:32:00 EDT in :
> Any email client (including mobile email clients) worth its salt is
> going to wrap the subject line (at least in the email view, if not
> in the index view), so that shouldn't really be an issue, right?
My principal concern is with
12021/06/39 09:52.97 ನಲ್ಲಿ, John Hawkinson ಬರೆದರು:
> I'd object to the proposal to add the "FW: " characters to the default. Space
> is at a premium in modern Subject lines, especially with the prevalence of
> mobile devices that have limited screen real estate, and cutting out 3
> characters i
I'd object to the proposal to add the "FW: " characters to the default.
Space is at a premium in modern Subject lines, especially with the
prevalence of mobile devices that have limited screen real estate, and
cutting out 3 characters is very undesirable. I think it's pretty clear
from context that
12021/06/39 09:27.23 ನಲ್ಲಿ, Globe Trotter via Mutt-users
ಬರೆದರು:
> When I foward my mutt-composed email, I have something like the following,
> which I believe is the default behaviour:
>
> [mutt-users@mutt.org: Email subject]
>
> which I think is very nice because it gives the recipient an id
When I foward my mutt-composed email, I have something like the following,
which I believe is the default behaviour:
[mutt-users@mutt.org: Email subject]
which I think is very nice because it gives the recipient an idea of whether
the originator of this email is someone s/he should even bother
ally.
I found when I was doing this that invoking the filter manually was
too slow when I want to move on to the next message. I saved it to a
mailbox and let a cron job eat the mailbox periodically.
> If I were using Spamassassin, I'd more then likely use this
> suggestion.
There&#x
Here's what I've simply settled on:
# Remap S to move spam to the spam folder
macro index S "unset wait_key\nbogofilter
-s\nset wait_key\ns=.Spam\n"
macro pager S "unset wait_key\nbogofilter
-s\nset wait_key\ns=.Spam\n"
ven though Bogofilter only brings
in at most one dependency, it seems to be bogus at catching spam. :-/
I guess instead of using a Bash script to call bogofilter to scan the spam
maildir, I could simply create a hook to call it. But I tend to try to do most
things manually.
(... explains why I'm no using Mutt ;-)
If I were using Spamassassin, I'd more then likely use this suggestion.
* On 21 Jul 2010, Roger wrote:
> >> Since I'm always saving/moving email to $HOME/.maildir/.Spam... you
> >> would think Mutt would catch-on after the 10th email. ;-)
> >
> >I attach the following macros to the z key in my .muttrc
> >
> > macro index z "s=mutt/spam\n" "move message to spam"
> > ma
On Wed, Jul 21, 2010 at 10:12:34PM +0100, Steve Searle wrote:
>Around 07:56pm on Wednesday, July 21, 2010 (UK time), Roger scrawled:
>
>> Since I'm always saving/moving email to $HOME/.maildir/.Spam... you
>> would think Mutt would catch-on after the 10th email. ;-)
>
>I attach the following macros
Around 07:56pm on Wednesday, July 21, 2010 (UK time), Roger scrawled:
> Since I'm always saving/moving email to $HOME/.maildir/.Spam... you
> would think Mutt would catch-on after the 10th email. ;-)
I attach the following macros to the z key in my .muttrc
macro index z "s=mutt/spam\n" "move me
On Wed, Jul 21, 2010 at 06:50:12PM +0200, Rado S wrote:
>=- Christoph Kluenter wrote on Wed 21.Jul'10 at 10:30:34 +0200 -=
>
>> Thank you very much. save-hooks is exactly what I want.
>
>There are some vars controlling save-location, if you want to make
>it constant.
force_name & save_name?
) to be.
> A likely more appropriate suggestion would be to have Mutt use the last
> "save to folder name" used as a suggestion (along with the usual "?" to list
> folder names).
there is a *default* save-hook location, even mentioned in the fine
documentation.
> Since I&#x
esn't even exist from the idea of the sender's
email address!
A likely more appropriate suggestion would be to have Mutt use the last
"save to folder name" used as a suggestion (along with the usual "?" to list
folder names).
Since I'm always saving/moving email
=- Christoph Kluenter wrote on Wed 21.Jul'10 at 10:30:34 +0200 -=
> Thank you very much. save-hooks is exactly what I want.
There are some vars controlling save-location, if you want to make
it constant.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least t
* Am Wed, Jul 21, 2010 at 10:02:08AM +0200 , schrieb Joost Kremers:
> On Wed, Jul 21, 2010 at 09:36:54AM +0200, Christoph Kluenter wrote:
> > when I press "s" to save a mail to another folder, mutt suggest the
> > foldername.
> > But mutt is mostly always wrong :-)
> > So I thought it would be nic
On Wed, Jul 21, 2010 at 09:36:54AM +0200, Christoph Kluenter wrote:
> when I press "s" to save a mail to another folder, mutt suggest the
> foldername.
> But mutt is mostly always wrong :-)
> So I thought it would be nice if I could write my own script which would
> parse the mail
> and suggest a
Hi all,
when I press "s" to save a mail to another folder, mutt suggest the foldername.
But mutt is mostly always wrong :-)
So I thought it would be nice if I could write my own script which would parse
the mail
and suggest a folder. Is something like this possible or feasable ?
Alternatively I w
Hi,
* Edd Barrett wrote:
> What do you think of a progress indication when you close a large
> mailbox. I use mutt with gmail and frequently when I close a mailing
> list folder it takes a while. User feedback would be nice :)
I have a patch in my queue at bitbucket that does this:
http://bit
Not gmail. thought you are asking in general.
Best,
Paul
-Original Message-
From: Edd Barrett [mailto:vex...@gmail.com]
Sent: Thursday, August 13, 2009 12:16 PM
To: Paul Grinberg
Cc: mutt-users@mutt.org
Subject: Re: Quick suggestion
On Thu, Aug 13, 2009 at 4:56 PM, Paul Grinberg
On Thu, Aug 13, 2009 at 4:56 PM, Paul Grinberg wrote:
> 16000 emails. 395M. -> 10 seconds.
Is that a gmail account?
--
Best Regards
Edd Barrett
(Freelance software developer / technical writer / open-source developer)
http://students.dec.bournemouth.ac.uk/ebarrett
16000 emails. 395M. -> 10 seconds.
Best,
Paul
-Original Message-
From: owner-mutt-us...@mutt.org [mailto:owner-mutt-us...@mutt.org] On Behalf Of
Edd Barrett
Sent: Thursday, August 13, 2009 11:53 AM
To: mutt-users@mutt.org
Subject: Quick suggestion
Hi Guys,
What do you think o
Hi Guys,
What do you think of a progress indication when you close a large
mailbox. I use mutt with gmail and frequently when I close a mailing
list folder it takes a while. User feedback would be nice :)
--
Best Regards
Edd Barrett
(Freelance software developer / technical writer / open-source
I think it's a good idea to have a facility like shell expansion when
adding attachments to mail.
For example, I have files named 1.zip 2.zip and so on. I want adding all
of them to a mail as attachments when composing the mail. It will be
good to specify things like *.zip when pressing the 'a' ke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thus spake Nicolas Rachinsky ([EMAIL PROTECTED]):
> > 3. When I get clearer with gpg, I try to make my 'uid' more informative
> >for others. But I found gpg doesn't provide good maintaining method
> >to update them. You can not update uid exc
Hi, all --
Since I'm a definite contributor, though I hope not terribly often, I
probably ought to chime in...
...and then Derek D. Martin said...
%
% At some point hitherto, Roman Neuhauser hath spake thusly:
..
% > mutt-chat, so that those who feel the urge to send non-technical, OT
% >
> > I guess that quite a few of the subscribers are just devoted to
> > flooding this list with chitchat. I would suggest creating
> > mutt-chat, so that those who feel the urge to send non-technical, OT
> > stuff to mutt-users would have a place to go.
>
> Yeah, but the problem i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Derek D. Martin hath spake thusly:
[SNIP]
> discussions almost always result directly from discussions that
> originally WERE on-topic, and are unavoidable. Humans have a penchant
> for going off on tangents, and you can not p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Roman Neuhauser hath spake thusly:
> I guess that quite a few of the subscribers are just devoted to
> flooding this list with chitchat. I would suggest creating
> mutt-chat, so that those who feel the urge to send
> As Tom Gilbert has it in his sample .muttrc:
> set indent_str="> " # change this and I'll kill you! ;-)
I have have this:
set indent_string="> " # Dont' be a moron. Leave it as is.
igor
--
Uptime : 31 days, 28 min
Rob 'Feztaa' Park <[EMAIL PROTECTED]> [11 Jan 2002 16:37 -0700]:
> > 9o)
>
> BTW, what the heck is that thing?
He has a big nose and a monocle, obviously.
--
http://www.epic.org - Electronic Privacy Information Center
msg22976/pgp0.pgp
Description: PGP signature
Alas! Knute spake thus:
> This is quoted text: - End forwarded message -
>
> So what do you think?
> (I think I need to put on my asbestos long john's!)
You die. You die and go to hell!
Just kidding ;)
> 9o)
BTW, what the heck is that thing?
--
Rob 'Feztaa' Park
[EMAIL PROTECTED]
-
Alas! Roman Neuhauser spake thus:
> I guess that quite a few of the subscribers are just devoted to
> flooding this list with chitchat. I would suggest creating
> mutt-chat, so that those who feel the urge to send non-technical, OT
> stuff to mutt-users would have a place to go.
I
On Fri, Jan 11, 2002 at 06:24:47PM +, Benjamin Smith wrote:
> Yeah, but the problem is that when 'chitchat' spins off from another
> thread, it rarely (in my experience) ends up getting moved. Although if
> people think that it will actually get used, I would support it
We had the "chitchat
On Fri, Jan 11, 2002 at 06:37:52PM +0100, Roman Neuhauser wrote:
> I guess that quite a few of the subscribers are just devoted to
> flooding this list with chitchat. I would suggest creating
> mutt-chat, so that those who feel the urge to send non-technical, OT
> stuff to mutt-use
> Date: Fri, 11 Jan 2002 08:27:47 -0800
> From: "J. Scott Dorr" <[EMAIL PROTECTED]>
> To: Anh Lai <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: Re: Suggestion for List Etiquette
>
> Nah. :) He coulda just highlighted the appropriate lines (via
On Fri, Jan 11, 2002 at 07:46:15AM -0600, Anh Lai wrote:
>
> ... On 01/10/02, Knute decided to write ...
>
> > On Fri, 11 Jan 2002, Nick Croft wrote:
> >
> > This is quoted text:
> > This is quoted text:
> > This is quoted text: * Imre Vida ([EMAIL PROTECTED]) wrote:
> > This is quoted text:
On Fri, 11 Jan 2002, Anh Lai wrote:
>
>
> ... On 01/10/02, Knute decided to write ...
>
> > On Fri, 11 Jan 2002, Nick Croft wrote:
> >
> > This is quoted text:
> > This is quoted text:
> > This is quoted text: * Imre Vida ([EMAIL PROTECTED]) wrote:
> > This is quoted text: > somewhat diffe
Agree with you, too. Your post showed one well-tailored. :-)
best,
charlie
On Thu, Jan 10, 2002 at 08:55:24AM +0100, Volker Moell wrote:
> Charles Jie wrote:
> > I Agree. For an hacker, his message should be as well tailored as his
> > programs.
>
> But please: Don't snip *everything*! Just rea
... On 01/10/02, Knute decided to write ...
> On Fri, 11 Jan 2002, Nick Croft wrote:
>
> This is quoted text:
> This is quoted text:
> This is quoted text: * Imre Vida ([EMAIL PROTECTED]) wrote:
> This is quoted text: > somewhat different but related:
> This is quoted text: >
> This is quot
On Fri, Jan 11, 2002 at 12:24:17PM +0800, Charles Jie <[EMAIL PROTECTED]> wrote:
>user id (short form, 8 hex digits) - an key ID for your convenience
> to specify a key for gpg, not guaranteed to be unique (non-ambiguous)
>user id (long form, 16 hex digits) - better ID but who'll use
Nick Croft wrote:
> As Tom Gilbert has it in his sample .muttrc:
> set indent_str="> " # change this and I'll kill you! ;-)
i also like the bit from the muttrc man page:
You are strongly encouraged not to change this
value, as it tends to agitate the more fanatica
On Fri, 11 Jan 2002, Nick Croft wrote:
This is quoted text:
This is quoted text:
This is quoted text: * Imre Vida ([EMAIL PROTECTED]) wrote:
This is quoted text: > somewhat different but related:
This is quoted text: >
This is quoted text: > wouldn't it be better to use > as a quote-marker ch
On Thu, 10 Jan 2002, Rob 'Feztaa' Park wrote:
> Alas! Imre Vida spake thus:
> > wouldn't it be better to use > as a quote-marker char consistently?
> > some of the alternatives like "%" i realy dislike
>
> This point has come up before. Although I personally like to use '>'
> just because I thin
Thank you, Justin. I've just gone thru your tutorial. It's helpful.
However, I would suggest some more info to be included, which I've tried
hard (with 'man gpg' and google search) but can not yet get a clear
picture of pgp.
Don't blame me posting this in mutt mail listing, and asking your
tutor
* Imre Vida ([EMAIL PROTECTED]) wrote:
> somewhat different but related:
>
> wouldn't it be better to use > as a quote-marker char
> consistently?
> some of the alternatives like "%" i realy dislike
>
> imre
>
As Tom Gilbert has it in his sample .muttrc:
set indent_str="> " # change this and
Alas! Imre Vida spake thus:
> wouldn't it be better to use > as a quote-marker char consistently?
> some of the alternatives like "%" i realy dislike
This point has come up before. Although I personally like to use '>'
just because I think it's a good character for quoting (it looks like an
arrow
somewhat different but related:
wouldn't it be better to use > as a quote-marker char
consistently?
some of the alternatives like "%" i realy dislike
imre
Charles Jie wrote:
> I Agree. For an hacker, his message should be as well tailored as his
> programs.
But please: Don't snip *everything*! Just reading the answer or comment
(to an unknown question, because I deleted the original posting in the
meantime) ist more painful than ignoring superfluou
I Agree. For an hacker, his message should be as well tailored as his
programs.
charlie
I would like to suggest that people judiciously edit the text to which they are
replying and remove unnecessary sentences. I'm seeing a lot of messages
which I have to scroll down a ways on my 80x24 term before I can see the
text of the message, and its quite annoying. If you are going to inline
* Ken Weingold <[EMAIL PROTECTED]> [011207 19:38]:
> I think it would be really cool in the manual to see
> at what version of mutt each config variable came in.
"me, too!" That's why I started writing my own manual
with exactly that in mind - but unfortunately this
was never included with the m
Daniel --
...and then Daniel Eisenbud said...
%
% On Tue, Dec 11, 2001 at 08:16:08PM -0500, David T-G
<[EMAIL PROTECTED]> wrote:
% >
% > ...and then Ken Weingold said...
% > %
...
% > % Instead of something like -?-?-?-?- , maybe things like -?4?-> or the
...
% >
% > That sounds pretty cool.
On Tue, Dec 11, 2001 at 08:16:08PM -0500, David T-G
<[EMAIL PROTECTED]> wrote:
> Ken --
>
> ...and then Ken Weingold said...
> %
> % The more I run 1.3.24, the more I am appreciating the multiple '?'s in
> ...
> % Instead of something like -?-?-?-?- , maybe things like -?4?-> or the
> % like, r
Ken --
...and then Ken Weingold said...
%
% The more I run 1.3.24, the more I am appreciating the multiple '?'s in
...
% Instead of something like -?-?-?-?- , maybe things like -?4?-> or the
% like, replacing all the '?'s with a number representing them? Seems
% like a happy medium.
That sound
The more I run 1.3.24, the more I am appreciating the multiple '?'s in
long threads, where some messages have been deleted, so I know which
messages are on equal levels and such. But, I wonder if this could be
done, which might have the same effect, but make the threads narrower.
Instead of somet
I think it would be really cool in the manual to see at what version
of mutt each config variable came in.
-Ken
On 2001.08.03, in <[EMAIL PROTECTED]>,
"John Wright" <[EMAIL PROTECTED]> wrote:
> Just talking to someone about mutt flagging mail with + when it's to
> you and T when it's to you and other, etc, and we were just wondering if
> mutt either does or could have a flag for emails which are fro
* fman <[EMAIL PROTECTED]>:
> Is there plans to make enable mutt to read the news from a news server?
I don't know, but I doubt it.
See some of the nntp patches though:
http://www.mutt.org/links.html#patch
Juan --
...and then fman said...
% Is there plans to make enable mutt to read the news from a news server?
Plans for official development: no
Plans for unofficial support: yes, discussed a few times in the past.
Take a wander through the mail archives for more info, including at least
one or to
On Wed, Jun 28, 2000, fman wrote:
> Is there plans to make enable mutt to read the news from a news server?
Yeah, it already can. Hit 'qtin' or 'qslrn'. Works great. ;-)
-Ken
--
[EMAIL PROTECTED]AIM: ScopusFest
On Tue, Jun 27, 2000 at 09:25:10PM -0700, Shawn D. McPeek wrote:
>
> And mention that a 32 line sig on a 3 line message is a bit excessive :)
>
> Shawn
I hadn't realized how big it was, becuase I was reading it through an xterm
window. Should be ok now
fman proclaimed on mutt-users that:
>Is there plans to make enable mutt to read the news from a news server?
>
>-juan
See http://www.mutt.org - there is an NNTP patch. Read the archives -
this (and other alternatives such as newsfetch) were discussed a few weeks
back.
--
Suresh Ramasubramania
Is there plans to make enable mutt to read the news from a news server?
-juan
--
PGP signature
On Wed, Jun 28, 2000, Sven Guckes wrote:
> * fman <[EMAIL PROTECTED]> [000628 04:16]:
> > The muttfaq says to send suggestions to this list.
> > I suggest someone write a book on how to use mutt.
> > Maybe a small book like those o'reilly pocket references.
> > Mutt is popular enought to deserve o
On 06/27 21:12 -0700, fman wrote:
> The muttfaq says to send suggestions to this list. I suggest someone write a
> book on how to use mutt. Maybe a small book like those o'reilly pocket
> references. Mutt is popular enought to deserve one, no?
but then clueless people would start using it...
-
On 2000-06-28 14:20:02 +0200, Gerhard den Hollander wrote:
> (note, this does involve some more or less complicated (c) issues with
> contributors to the online docs ...
Not necessarily; Open Content with restrictions on printing is
always an option (this is how "The Cathedral and the Bazar" work
* Sven Guckes <[EMAIL PROTECTED]> (Wed, Jun 28, 2000 at 01:19:20PM +0200)
> * fman <[EMAIL PROTECTED]> [000628 04:16]:
>> The muttfaq says to send suggestions to this list.
>> I suggest someone write a book on how to use mutt.
>> Maybe a small book like those o'reilly pocket references.
>> Mutt is
On Tue, Jun 27, 2000 at 09:25:10PM -0700, Shawn D. McPeek wrote:
> And mention that a 32 line sig on a 3 line message is a bit excessive :)
Quoting style should get some attention too... ;)
Marius Gedminas
--
Science is to computer science as hydrodynamics is to plumbing.
* fman <[EMAIL PROTECTED]> [000628 04:16]:
> The muttfaq says to send suggestions to this list.
> I suggest someone write a book on how to use mutt.
> Maybe a small book like those o'reilly pocket references.
> Mutt is popular enought to deserve one, no?
I had suggested this to O'Reilly two years
Shawn D. McPeek muttered:
>
> And mention that a 32 line sig on a 3 line message is a bit excessive :)
[full quote deleted]
The same goes to full quoting of cause :-)
And - to whom it may concern - quoting sigs!
HTH,
Michael
--
Prof:So the American government went to IBM to come up with
And mention that a 32 line sig on a 3 line message is a bit excessive :)
Shawn
Previously, fman wrote:
% The muttfaq says to send suggestions to this list. I suggest someone write a
% book on how to use mutt. Maybe a small book like those o'reilly pocket
% references. Mutt is popular enought
The muttfaq says to send suggestions to this list. I suggest someone write a
book on how to use mutt. Maybe a small book like those o'reilly pocket
references. Mutt is popular enought to deserve one, no?
--
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info
Daniel --
...and then Daniel González Gasull said...
% Hi! :-)
%
% Myself wrote To Mutt users:
%
% > list to ask it, but, are there any standard email
% > headers to say something like this?:
This was the important part of your first post, we note.
% >
% > X-PGP-Advocacy: Hey, I prefer to r
Daniel --
My, I'm busy this morning :-)
...and then Daniel González Gasull said...
% Hi! :-)
%
% David T-G <[EMAIL PROTECTED]> wrote To Mutt users:
%
% > You may find everything you wanted for the
% > pgpmimeuser setting in v1.2 and up (currently
% > 1.2.2 AFAIK), since there is now a clearsig
Hi again :-)
I just thought of a simpler and potentially easier answer to this whole
thing. Since you've already stepped up to the work of configuring *your*
environment (the aliases file) for these folks who can't get it together,
why not just configure your procmail setup to recognize any of t
y readdress any email for
% > [EMAIL PROTECTED] to [EMAIL PROTECTED]?
%
% Yes. But something more. I have improved my
Hokay. Got that so far.
% suggestion. The command would be something like
%
% aka {alias} {regexp}
%
% It will rewrite any address that match regexp with
% the one
Dave --
...and then Dave Pearson said...
% On Thu, Jun 22, 2000 at 07:59:55AM -0400, David T-G wrote:
% >
% > What a cool idea. Care to share it?
%
% My pleasure, on the understanding that installing and using glimpse is left
% as an exercise for the reader.
No problem. All I have to do is
On Thu, Jun 22, 2000 at 07:59:55AM -0400, David T-G wrote:
> Dave --
>
> % grepmail wrapper that does all this for you. I've got something similar that
> % I use with glimpse. It does the search and, if something was found, it fires
> % up mutt with all the found messages in a folder. It ever wri
Dave --
...and then Dave Pearson said...
% On Wed, Jun 21, 2000 at 04:03:34PM -0400, [EMAIL PROTECTED] wrote:
%
% > grepmail > /tmp/mutt-11241
% >
% > and then loads /tmp/mutt-11241 or whatever as the current box.
...
%
% grepmail wrapper that does all this for you. I've got something simila
On Wed, Jun 21, 2000 at 04:03:34PM -0400, [EMAIL PROTECTED] wrote:
> I just had a suggestion for what might be a nice feature for Mutt. The
> grepmail program is nice since it greps for e-mails containing something
> and spits them out in standard mail format. We could add a se
Marius Gedminas <[EMAIL PROTECTED]> wrote on Wed, 21 Jun 2000:
> My understanding was that *replying* to a mail from [EMAIL PROTECTED] would
> address the reply to [EMAIL PROTECTED]
> I can find uses for this too. Some mailing lists around here can be
> reached via multiple aliases -- [EMAIL PRO
On Wed, Jun 21, 2000 at 01:00:47AM -0400, David T-G wrote:
> I, for one, had trouble following your aka proposal. Do I understand
> that a configuration like
>
> aka [EMAIL PROTECTED] [EMAIL PROTECTED]
>
> would automatically readdress any email for [EMAIL PROTECTED] to [EMAIL PROTECTED]?
My
On Wed, Jun 21, 2000 at 04:03:34PM -0400, [EMAIL PROTECTED] wrote:
> We could add a search mail function that does:
>
> grepmail > /tmp/mutt-11241
>
> and then loads /tmp/mutt-11241 or whatever as the current box.
Mutt already has that feature.
l ~b
will limit the messages displayed
I just had a suggestion for what might be a nice feature for Mutt.
The grepmail program is nice since it greps for e-mails containing something
and spits them out in standard mail format. We could add a search mail
function that does:
grepmail > /tmp/mutt-11241
and then loads /tmp/mutt-11
Stan Ryckman <[EMAIL PROTECTED]> wrote on Wed, 21 Jun 2000:
> This is sort of a guess as well, since I'm going from memory, but
> what I think was asked.
My understanding was that he wanted to specify the "display name" for
several mail addresses, in the mail folder view. This is what
$reverse_a
At 10:35 AM 6/21/00 +0100, Telsa Gwynne wrote:
>On Wed, Jun 21, 2000 at 01:00:47AM -0400 or thereabouts, David T-G wrote:
>> Daniel --
>>
>> I, for one, had trouble following your aka proposal.
>
>I did, also. I know this sounds silly, but was Daniel actually looking
>for the 'alias' setting?
On Wed, Jun 21, 2000 at 01:00:47AM -0400 or thereabouts, David T-G wrote:
> Daniel --
>
> I, for one, had trouble following your aka proposal.
I did, also. I know this sounds silly, but was Daniel actually looking
for the 'alias' setting?
I am so used to the term 'alias' because I've always
Daniel --
You may find everything you wanted for the pgpmimeuser setting in v1.2
and up (currently 1.2.2 AFAIK), since there is now a clearsign mode.
With a [few] send-hook[s], you should be able to define whatever settings
you wish for whatever recipients you have. You shouldn't have ever had
t
Daniel --
I, for one, had trouble following your aka proposal. Do I understand
that a configuration like
aka [EMAIL PROTECTED] [EMAIL PROTECTED]
would automatically readdress any email for [EMAIL PROTECTED] to [EMAIL PROTECTED]?
If that's correct, I don't see why that's needed; just send you
> [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > My idea is to use Mutt to encode the attachments and produce the
> > headers.
>
> This is not a bad idea, but Mutt is really designed more for interactive
> use, and thus, there may be other tools better suited. Have you looked
> at the "m
> [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > My idea is to use Mutt to encode the attachments and produce the
> > headers.
>
> This is not a bad idea, but Mutt is really designed more for interactive
> use, and thus, there may be other tools better suited. Have you looked
> at the "m
> [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > My idea is to use Mutt to encode the attachments and produce the
> > headers.
>
> This is not a bad idea, but Mutt is really designed more for interactive
> use, and thus, there may be other tools better suited. Have you looked
> at the "m
1 - 100 of 128 matches
Mail list logo
