On Sun 14 at 08:06 PM -0700, Kevin J. McCarthy ke...@8t8.us wrote:
I'm not super familiar with the details of send-hook but I suspect
multiple commands may not be allowed. Try breaking the last line into
two parts and see if that helps:
I think I wasn't quite clear: I do *not* have the
On Sat 06/21/08 at 10:11 AM -0400, Sahil Tandon [EMAIL PROTECTED] wrote:
Why not place all email addressed to mutt-users@ (regardless of the domain
name) in your mutt mailbox?
Great idea, and I think this is my preferred solution. Thanks for the tip.
--
// [EMAIL
On Sat 06/21/08 at 02:12 AM -0500, David Champion [EMAIL PROTECTED] wrote:
If it is not, I'd like to remove the following from my .procmailrc:
:0
* ^Delivered-To:[EMAIL PROTECTED]
$HOME/Mail/m/
Just use a List-* header instead:
List-Post: mailto:mutt-users@mutt.org
It's too bad
A few years ago messages to the mutt-users list (from Germany?) were
occasionally ending up in my inbox because they had been sent to what was
apparently some sort of alternative address for the list:
[EMAIL PROTECTED]
Is anyone aware if this address is still in any way active for the list?
If
A few years ago messages to the mutt-users list (from Germany?) were
occasionally ending up in my inbox because they had been sent to what was
apparently some sort of alternative address for the list:
[EMAIL PROTECTED]
Is anyone aware if this address is still in any way active for the list?
If
On Sat 06/21/08 at 12:37 AM -0400, Sahil Tandon [EMAIL PROTECTED] wrote:
It is no longer active. Users who send email to that address are asked,
via a bounce, to direct email to [EMAIL PROTECTED]
Thank you muchly, sorry for the dupe.
--
// [EMAIL PROTECTED] //
On Tue 06/17/08 at 02:30 AM -0500, Kyle Wheeler [EMAIL PROTECTED] wrote:
Use whatever works for you; I just recommend using a tighter pattern
when possible. Your original pattern of just two lowercase letters
seems to be just begging to match things you don't intend.
I've never actually once
IMPORTANT: This email remains the property of the Australian Defence
Organisation and is subject to the jurisdiction of section 70 of the
CRIMES ACT 1914. If you have received this email in error, you are
requested to contact the sender and delete the email.
I find these hysterics hysterical
On Mon 06/16/08 at 02:30 PM -0500,
Kyle Wheeler [EMAIL PROTECTED] wrote:
Hmmm... so it's not matching? Interesting. Try deconstructing it, to
see what's breaking the match. For example, remove the $ off the end,
and see if that helps.
I originally had this:
|cv|dm
and you suggested
On Mon 06/16/08 at 09:38 PM +0200,
Christian Brabandt [EMAIL PROTECTED] wrote:
Have you tried something like the following format: (%?l?%4l%4c?)
This will display the line number if available otherwise it will print
the byte size.
This is perfect. It's amazing how mutt has a solution for
On Sun 06/15/08 at 09:40 PM -0500,
Kyle Wheeler [EMAIL PROTECTED] wrote:
[...] that you use something more like this:
folder-hook '(|=cv|=dm)$' 'set index_format=whatever'
The only problem I'm having with this:
'(|=cv|=dm)$'
instead of this:
'|cv|dm'
in this:
On Sun 06/15/08 at 10:39 AM -0500, Kyle Wheeler [EMAIL PROTECTED] wrote:
Probably a folder-hook that sets your sorting order whenever you enter
the INBOX.
Well, I have what's below, but I've these forever:
folder-hook . set sort=threads
folder-hook .'set
On Sun 06/15/08 at 02:50 PM -0500, Kyle Wheeler [EMAIL PROTECTED] wrote:
Think of it this way:
mutt reads your muttrc (sort=date)
mutt opens your inbox (hook triggered, sort=threads)
you tell mutt to re-read the muttrc (sort=date)
you tell mutt to re-open your inbox (hook
On Sun 06/15/08 at 07:22 PM -0500,
Kyle Wheeler [EMAIL PROTECTED] wrote:
[that I wrote]
folder-hook |sent|cv|dm|fabio'set index_format= etc
^^^
. . . duplication of sent-folder names.
Well, not necessarily. Remember, you're providing a *pattern*, so that
pattern
On Sun 06/15/08 at 09:40 PM -0500,
Kyle Wheeler [EMAIL PROTECTED] wrote:
[...] that sent string in the original pattern will also match folders
named abSENT and SENTimental and esSENTial. So it was entirely
possible that the sent string was not redundant, and was actually
intentional.
Ah.
On Sun 06/15/08 at 11:15 PM -0400, Russell Hoover [EMAIL PROTECTED] wrote:
Absolutely. Though I'm partial to the plus-sign, so I used that
instead of =.
folder-hook '(|+cv|+dm)$''set index_format=whatever'
^ ^
Looks like I'm better off with the equal-sign
Suddenly I've discovered that when I try to re-load my .muttrc with the
:source ~/.muttrc command, the last message in my index (number 920), is
re-positioned as number 576. Other messages are also moved around.
If I change folders out of the inbox and then back into it, the
message-order is
On Mon 06/09/08 at 09:37 AM -0500, Kyle Wheeler [EMAIL PROTECTED] wrote:
Just thought I would point out... You can compress that into a single
macro by putting a comma between index and pager::
macro index,pager F enter-commandset
mime_forward=yesenterforward-message
Wow. This
I want to see *some* X-headers, like people's interesting and funny custom
my_hdrs (even though there doesn't seem to be as many of them these days).
But of course I don't want to see all X-headers.
So I have a very long list of boring and irrelevant X-headers in my
ignore list.
And I have an
Fixed. I had asterisks where I shouldn't have had them in the ignore list.
Sorry for the false alarm.
--
// [EMAIL PROTECTED] //
On Sat 11/03/07 at 12:30 AM -0700,
Gary Johnson [EMAIL PROTECTED] wrote:
There's been no deliberate change to this behavior that I know of.
What is your 'editor' variable set to?
set editor=/usr/local/bin/vim.new +/^$# Puts vim's cursor at the second
On Sat 11/03/07 at 04:50 AM -0400,
I, Russell Hoover [EMAIL PROTECTED] wrote:
set editor=/usr/local/bin/vim.new +/^$
The fix was to change vim.new to vim in the line above, as there is
currently no vim.new on the system. I had to see it posted before
I could recognize what was wrong
On Sat 11/03/07 at 01:04 AM -0400,
I, Russell Hoover [EMAIL PROTECTED] wrote:
In mutt-1.4.2.3 (used on a different ISP than where I use mutt-1.5.10),
if I edit a message, the lines header is lost, leaving the lines
number in the index at zero.
Same thing occurs with mutt-1.5.10i
On Sat 11/03/07 at 01:04 AM -0400,
Russell Hoover [EMAIL PROTECTED] wrote:
How can I edit a message and keep a (now changed) lines header?
Maybe this question should be put this way: How can I have an updated
Lines: header automatically created immediately after I edit a message
In mutt 1.5.10 when from either mutt's index or pager I press e to
edit a message, the screen blinks and I see the error message Message
not modified!
What do I need to do to be able to be put into my editor to edit
a message (as always happened before) ?
--
// [EMAIL
In mutt-1.4.2.3 (used on a different ISP than where I use mutt-1.5.10),
if I edit a message, the lines header is lost, leaving the lines
number in the index at zero.
I do have the following in 1.4.2.3's .procmailrc file:
# Generate a Lines: header (needed for maildir mailbox
# format) using
When I am in mutt and I press 'm' to compose a new mail, and I'm then
dropped into my editor (vim), I'd like to have it so that I'll always
be automatically already in vim's insert mode.
Right now, once mutt puts me into vim after I press 'm',
and I am in vim's 'normal mode' ready to compose a
Is there an easy way to save mutt's help
screens to a file, without doing a cut paste?
--
// [EMAIL PROTECTED] //
I am amazed that this list gets absolutely no spam.
How is this accomplished?
Perhaps some tricks cam be passed on to zsh-users,
which isn't nearly as air-tight when it comes to
spam-infestation.
--
// [EMAIL PROTECTED] //
Hey mutt users, I'm putting this question to the list for a friend.
(Let me know if any more info is needed for help
with answers/suggestions):
How can I configure mutt to communicate directly with a POP server
and SMTP server outside of my local network. I'm running Linux
behind a firewall and
Is there any way of telling mutt to execute an interactive command (e.g.
collapse-all) in .muttrc short of using push?
--
// [EMAIL PROTECTED] //
There are no differences but differences of degree
between different degrees of
On Fri 01/25/02 at 05:27 PM -0600,
Jeremy Blosser [EMAIL PROTECTED] wrote:
From: Jeremy Blosser [EMAIL PROTECTED]
Date: Fri, 25 Jan 2002 17:27:19 -0600
Subject: Re: \223 and \224
To: [EMAIL PROTECTED]
Cc: Christopher S. Swingley [EMAIL PROTECTED],
On Tue 01/01/02 at 09:40 PM +0100, Thomas Roessler
[EMAIL PROTECTED] wrote:
mutt-1.2.5.1 and mutt-1.3.25 have just been released.
These releases both fix a security hole which can be remotely
exploited. ^
^^
I'm not sure what that
On Tue 01/01/02 at 09:40 PM +0100, Thomas Roessler
[EMAIL PROTECTED] wrote:
mutt-1.2.5.1 and mutt-1.3.25 have just been released.
These releases both fix a security hole which can be remotely
exploited.
May we be told the nature (if not the details) of the vulnerability?
--
On Tue 12/25/01 at 02:18 AM -0500,
Philip Mak [EMAIL PROTECTED] wrote:
I think this is the easiest solution to the Maildir lines problem,
assuming that the user doesn't mind seeing bytes instead.
But if you do want to see the number of lines
rather than bytes, put this in your .procmailrc :
On Sun 10/28/01 at 02:59 AM -0700, Rob 'Feztaa' Park [EMAIL PROTECTED]
wrote:
So when the development branch gets all fixed up real nice-like, they'll
make it 1.4.0.
I don't want to be prescriptive, by any means, because I'm not a developer,
but it would seem that the overall project runs
On Sun 10/28/01 at 08:47 AM -0800, Eugene Lee [EMAIL PROTECTED] wrote:
I wonder if Russell is thinking of something more akin to the FreeBSD
development cycle where there are two branches: [snip]
However, I don't know if Mutt or the Mutt community is large enough to
warrant this
It has now been -- to the day -- exactly one year and three months since
a stable-branch, general-release version of mutt has appeared.
While the developer-branch continues to evolve (and is now at version
1.3.23i), the stable branch stagnates at 1.2.5i.
Maybe there is, in fact, a good reason
I use mutt 1.2.5i and the maildir mailbox format. Pressing 'h' shows
the full list of headers. There is never a From line visible.
But, when I press 'e' to edit the message, once I am in vim, I see a new
header as the top line,
From [EMAIL PROTECTED] Mon Aug 6 11:29:56 2001
I know
I noticed I hadn't been seeing my (zsh) shell's You have new mail notification
for awhile, so I sent myself a few mails from another ISP account and discovered
that mail notification is definitely not happening.
But it does work if I *edit an existing message* in my inbox. (since, In mutt,
if
On Thu 06/28/01 at 06:33 PM +0800, Greg Matheson [EMAIL PROTECTED] wrote:
Yes, I only tried it on mbox folders. I wonder if a patch to readmsg for
maildir folders was what Sven Guckes was talking about?!
Probably not, but I sometimes use mbox, and know others who do. It would
still help if
On Thu 06/28/01 at 06:54 AM +0800, Greg Matheson
[EMAIL PROTECTED] wrote:
Why not use readmsg itself? It may be on your machine. It's on
mine, a Red Hat derivative, with elm. You still have to specify
what number message it is you are looking for, however.
Trying it from within vim from
Can a message be put into the body of an outgoing message in mutt?
'A' inserts one as an attachment, yes, but can it be done not as an
attachment?
If not, is there anything like a 'readmsg' patch for mutt? This is
one of the very few instances where elm does something better than
mutt
What's the best way to insert one or two of the mail-messages that I have
sitting in my inbox -- the current folder -- (and, say, one from another
mail-folder) into an outgoing message that I'm composing (from within vim)
in mutt? Is there more than one way?
This is very simple to do with
:51:37 2001) --]
gpg: Signature made Tue Jan 02 06:26:09 2001 EST using DSA key ID my-public-key-ID
gpg: Good signature from "Russell Hoover [EMAIL PROTECTED]"
[-- End of PGP output --]
This is with:
set pgp_sign_as=my-secret-key-ID
in my gpg.rc.
But when I put in
On Tue 01/02/01 at 08:24 AM -0500, Russell Hoover [EMAIL PROTECTED] wrote:
When I sign a mail with GPG I get the following error-message:
gpg: skipped `my-secret-key-ID': this is a PGP generated ElGamal key which is not
secure for signatures! Press any key to continue...
I commented-out
On Fri 12/22/00 at 02:54 PM -0800, Mike E [EMAIL PROTECTED] wrote:
I find myself having to constantly recenter the cursor while I'm
going through emails...
Although you can always use 'H' to put the index indicator-bar (or arrow)
at the top message of your screen, 'M' to put it in the middle,
A question about mutt forwarded from an elm user:
I'd like to be able to incorporate into the message I'm composing
an arbitrary message from the current folder, whatever it is,
without first having to tag that message and without having to
incorporate it as an attachment.
Secondarily, it would
On Sun 10/08/00 at 08:07 PM -0400, Russell Hoover [EMAIL PROTECTED] wrote:
Does anyone know why this error messages appears whenever I try to
mail my key with ESC-k in the compose menu?
[-- Attachment #2: PGP Key 0xFC5C7370. --]
[-- Type: application/pgp-keys, Encoding: 7bit, Size: 0K
On Fri 10/06/00 at 12:40 PM +0200, Mark Weinem
[EMAIL PROTECTED] wrote:
maildir is not correct: use Maildir.
set mbox_type ="Maildir"
I beg to differ. I've had:
set mbox_type=maildir# Which of the 4 mailbox formats I use.
in my .muttrc for quite some time and it's
Does anyone know why this error messages appears whenever I try to
mail my key with ESC-k in the compose menu?
[-- Attachment #2: PGP Key 0xFC5C7370. --]
[-- Type: application/pgp-keys, Encoding: 7bit, Size: 0K --]
[-- Error: could not find beginning of PGP message! --]
--
I'm having some trouble GPG-signing my outgoing messages.
For example if I __'s'ign__ from the PGP options menu, these headers
appear (these appear to be the defaults right now):
sign as: Russell HooverMIC algorithm: pgp-sha1
I then hit RETURN, enter my passphrase, and I get
On Mon 10/02/00 at 06:50 PM +0530,
Suresh Ramasubramanian [EMAIL PROTECTED] wrote:
[-- Type: text/sgml, Encoding: 7bit, Size: 10K --]
What is a preferable mailcap entry for text/sgml? I have:
text/sgml; lynx -dump %s; needsterminal; copiousoutput
but this produces one long monolithic block
On Mon 10/02/00 at 04:28 PM -0500,
Jeremy Blosser [EMAIL PROTECTED] wrote:
What do you have set for $pgp_sign_as? This should be a key id
(0xFC5C7370), not your name (Russell Hoover).
That's it -- it *was* set to my name. Why did I think it should be? Was
this the case at some time
On Wed 09/20/00 at 08:05 PM +0930,
Brian Salter-Duke [EMAIL PROTECTED] wrote:
However hard one tries to customorize mutt or slrn to
be the same there are irritating small differences.
Yes !!! And this is one big plus in favor of the NNTP patch.
--
// [EMAIL
e ID of my GPG public key and press RETURN.
3) This puts me in the PGP menu where I see my public and private key IDs
listed thus:
1 + 1024/0xFC5C7370 DSA -s Russell Hoover [EMAIL PROTECTED]
2 + /XxXXXX XXX e- Russell Hoover [EMAIL PROTECTED]
4) I press RETURN and get th
and press RETURN.
3) This puts me in the PGP menu where I see my public and private key IDs
listed thus:
1 + 1024/0xFC5C7370 DSA -s Russell Hoover [EMAIL PROTECTED]
2 + /XxXXXX XXX e- Russell Hoover [EMAIL PROTECTED]
4) I press RETURN and get this message at the bottom of
On Mon 07/24/00 at 03:56 PM -0400, yours truly, [EMAIL PROTECTED] wrote:
What if you want to see *all* X- headers (including ones you don't know)
except a specific few that you *are* able to specify? As I noted above,
I tried using a second "ignore" line after the "unignore" line, and that
I thought I wanted to see all "X-" headers that came my way, so I set:
ignore * # This means "ignore all header lines by default."
unignore From: Date Subject To Cc Organization Organisation User-Agent \
X-Mailer X-
But there are some I don't want to see, such as:
On Mon 07/24/00 at 01:47 AM -0700, Anton Graham
[EMAIL PROTECTED] wrote:
Your muttrc file is read from the top down, so
you can put another ignore line after the unignore:
ignore X-Priority X-MSmail-Priority
That was the first thing I did, and it had no effect.
Does that really work for you?
On Mon 07/24/00 at 02:31 PM +0530,
Suresh Ramasubramanian [EMAIL PROTECTED] wrote:
Here's part of my .muttrc -
ignore *
unignore From To Cc Subject Date Reply-To Organization X-Mailer
Whichever X-Foo headers you want to see get explicitly unignored.
In your example (if I understand you
On Mon 07/24/00 at 01:13 PM -0700, Anton Graham [EMAIL PROTECTED] wrote:
Yes :) As an example, these are the ignore / unignore lines I
normailly use:
ignore lines precedence status nntp-posting-host path old-return-path
[...]
ignore X-eGroups-From x-sequence resent- from
unignore from:
I've just gotten mutt to work on a new (backup) ISP. (And at least until I
persuade the sysadmin to upgrade, it's mutt 0.95.7i). It took me the
*longest* time to be able to send any mail. Then I finally realized I had
to disable "dsn_notify" and "dsn_return" in my .muttrc in order for any
mail
.
In other words, the index goes from looking like this:
20 r T 05/ 9 [EMAIL PROTECTED] ( 50) Re: Receipt for payment
21 s 05/ 9 Thomas Roessler ( 85) [Announce] mutt-1.2 is out.
22 r + 05/ 9 Teddi Longardt ( 10) Thank you!
23 F 05/ 9 Russell Hoover ( 21
On Sun 05/21/00 at 09:12 PM +0300, Mikko Hänninen
[EMAIL PROTECTED] wrote:
Sounds like you have different settings for the $index_format in a
stand-alone "set index_format" command and in folder-hooks.
This was indeed the problem. Thanks.
// [EMAIL
test
--
// [EMAIL PROTECTED] //
Since procmail 3.14 supports the maildir mailbox format, I would assume that
means, using it with mutt, that I can get rid of the maildir.c delivery program
I've been using for the last couple of years,
and that I can change my procmail recipes from one like this:
:0
*
On Sun 05/07/00 at 11:40 PM -0500, "Corey G." [EMAIL PROTECTED] wrote:
I am looking for what I would call a nice color scheme for Mutt. I
currently use the scheme listed below but I would like to see what other
people have come up with.
From my .muttrc:
color hdrdefault brightwhite
On Mon 05/08/00 at 01:34 AM -0500, Kelly Scroggins
[EMAIL PROTECTED] wrote:
Is there a default address book for mutt?
I don't think there is. But the way you create it is this.
Put these lines in your .muttrc:
set alias_file=~/.mutt_aliases# Where I keep my aliases.
source
On Mon 05/08/00 at 06:12 AM -0500, Kelly Scroggins [EMAIL PROTECTED] wrote:
How do I get one of the addresses into a message I'm composing?
After you strike "m" to compose a message, you'll be at the "To:" prompt. When
you are there, strike TAB, and all your aliases will be visible. You can
Would anyone care to hazard a realistic estimate (or even an
unrealistic one) as to when we might see the release of mutt 1.2?
--
// [EMAIL PROTECTED] //
If I have this in my .mailcap file:
application/pgp; cat; copiousoutput
application/pgp-keys; pgp -f %s ; copiousoutput
application/pgp-signature; cat ; copiousoutput
and this in my .mime-typs file:
application/pgppgp
On Fri 05/05/00 at 02:07 PM -0400, Russell Hoover [EMAIL PROTECTED] wrote:
why have I begun to see this at the end of mail messages in mutt:
[-- application/pgp-signature is unsupported (use 'v' to view this part)
along with the warning:
mailcap entry for type application/pgp
On Mon 02/14/00 at 01:20 AM -0500, Russell Hoover [EMAIL PROTECTED] wrote:
Could someone explain where or how the BUFFY_SIZE option got its name?
Still hoping for an answer here. Does no one the list know why BUFFY_SIZE
or xbuffy were given that name? Who wrote the xbuffy patch?
I mean
On Tue 02/15/00 at 10:29 PM -0500, Russell Hoover [EMAIL PROTECTED] wrote:
there isn't a DRAGON option is there?
I mean a --VAMPIRES option . . .
--
// [EMAIL PROTECTED] //
I could swear I read on this list not too long ago that the command "subscribe"
would replace the "lists" command in the muttrc to define what mailing lists
mutt should recognize the user as being subscribed to.
I thought this change was going to take place in version 1.0.1, but AFAKCT it
Could someone explain where or how the BUFFY_SIZE option got its name?
And does it cycle through incoming mailboxes only at the 'c' (change-folder)
prompt? And is that it's only function?
--
// [EMAIL PROTECTED] //
On Tue 01/18/00 at 10:00 AM -0500, David T-G [EMAIL PROTECTED] wrote:
Since you reference lines 2/3 you are probably not using edit_headers and
wouldn't be interested in setting your editor variable to something like
set editor="vim +/^$"
to put the cursor at the first blank line. But it
When I go to send a new mail with the 'm' command, how can I make it (by
creating a macro or otherwise) so that I am instantly put into vim in insert
mode, and with the sigdashes on line 3 instead of line 2?
--
// [EMAIL PROTECTED] //
On Mon 11/29/99 at 09:26 AM +, Chris Green [EMAIL PROTECTED] wrote:
So, for example, the following macros in my .muttrc file *don't*
work (though they all appear OK on the help screen):-
macro generic ,s "s{mailandnews.co.uk}"
macro generic ,c "c{mailandnews.co.uk}"
macro generic ^X
On Mon 11/29/99 at 08:14 AM -0500, Subba Rao [EMAIL PROTECTED] wrote:
Where do you set mbox_type="Maildir"? In .muttrc?
Where? Well, I put it alphabetically, just after "set mbox..." and just
before "set mime_forward..." Maybe I'm not understanding the question. You
can put it anywhere you
Since the "User-Agent" header is now the RFC-defined standard (and not just
"window-dressing"), could we please finally have it replace the "X-Mailer"
header by default in the next stable, publicly-released version of mutt?
"User-Agent" appears to have replaced "X-Mailer" in the last several
Every so often on mutt-users, someone asks for slrn-style header-coloration
(where the name of the header -- everything to the left of the colon -- can
be defined as one color, and the value of the header -- to the right of the
colon -- as another color).
But this still has not been made
On Sun 10/24/99 at 11:18 PM +0100, John Poltorak [EMAIL PROTECTED] wrote:
I would like to change the colours of headers so that part of the line
up to ':' is one colour and the rest a different colour.
So would I, and a bunch of other folks, I'd suspect. (Anyone?) Like in
slrn. This
On Sat 09/04/99 at 07:30 PM -0400, erik [EMAIL PROTECTED] wrote:
Why when i try to forward a message with an attqchment, it doesnt
include it with the message. is there a way to make mutt do this?
From the mutt manual:
6.3.40. forward_decode
Type: boolean
Default: set
Controls the
From the 1.0pre2i manual:
6.3.19. bounce_delivered
Type boolean
Default: set
When this variable is set, mutt will include Delivered-To headers
when bouncing messages. Postfix users may wish to unset this
variable.
Why unset for
What determines which of these two headers is displayed automatically?
("automatically" as opposed to being displayed because you've created
one or the other as a user-defined "my_hdr" in the muttrc.)
On Fri 09/03/99 at 02:14 PM +0200, Ralf Hildebrandt [EMAIL PROTECTED] wrote:
What are you talking about?
The sender uses "my_hdr" or "edit_hdrs" to add/edit arbitrary headers.
The recipient can use "ignore" and "unignore" to hide/display the headers.
Yes. Of course. I probably shouldn't
Has anyone else noticed that the cursor jumps wildly around the screen upon
opening version 0.95.6?
(0.95.5 didn't do this)
--
// [EMAIL PROTECTED] //
We know the halls of the eye like welcome visitors but we live in our mouth.
On Wed 11/03/99 at 10:08 PM -0500, I [EMAIL PROTECTED] wrote:
Every so often on mutt-users, someone asks for slrn-style header-coloration
(where the name of the header -- everything to the left of the colon --
can be defined as one color, and the value of the header -- to the right
of the
90 matches
Mail list logo
