ng system should accept the responsibility of
munging message ids to suit its own needs. I've
certainly seen mailing list archives on the web that
did munge the message id (but to replace @ characters,
I think).
cheers,
raf
> --
> Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID:
://datatracker.ietf.org/doc/html/rfc2156
You can define a macro that uses my_hdr for each such header.
Then each one can be a single keystroke.
cheers,
raf
t 8bit. If the DKIM
signing happens before the conversion, then subsequent DKIM
checks will fail. Work is being done in Postfix to address
this. I don't know about other MTAs. It seems unlikely that
there are any MTAs that can't accept 8bit messages, but perhaps
there are some that are misconfigured and don't advertise the
fact to other MTAs.
cheers,
raf
On Sun, Aug 20, 2023 at 06:25:57PM +0800, "Kevin J. McCarthy"
wrote:
> On Sun, Aug 20, 2023 at 03:53:09PM +1000, raf via Mutt-users wrote:
> > I don't have any "lists" commands. I do have a "subscribe" command
> > which refers to mailing lists by the
shouldn't matter.
I've fixed it with a send-hook that does "set followup_to = no"
for that address, but I don't understand why I needed to.
Can anyone think what I might have done to cause this?
Linux ook 6.1.0-11-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-4 (2023-08-08)
x86_64 GNU/Linux
mutt-2.2.9-1+b1
cheers,
raf
eat it as text/plain
and make the "print" command treat it as text/html, but I don't remember the
details on how to do this. Does anyone else remember?
cheers,
raf
quot;smtps:", mutt
still encrypts the traffic by default, because $ssl_starttls
is yes by default. But you might want to set ssl_force_tls=yes
as well.
cheers,
raf
like this?
No, but the same thing can be achieved with alternate muttrc files
and the -F option. When you run "mutt -F work" or "mutt -F floss",
the work and floss rc files can contain their specific imap settings,
and then source a common rc file with everything else.
For saving to the other account, macros would help.
If you really like your config syntax above, you could probably
write a little tool that "compiled" it into muttrc syntax.
> Best,
> Matěj
cheers,
raf
t it might match other headers.
This seems to work:
~h ^(To|Cc):.*@.+,.+@
Of course comments that contain "@" and "," will match as well,
but they should be rare.
cheers,
raf
mat conversions are
> automatic.
>
> It's here:
> <https://www.panix.com/~kh/mutt-flowed-text/>
>
> Try it, let me know how it works for you.
I'm not an emacs user, but thanks. I think it's
important to support $edit_headers for this.
I always need the option of editing headers.
cheers,
raf
ply to IPv4 (at least
for spamhaus).
Also, Microsoft once didn't like my IPv4 address so I
temporarily routed mail to there via some third party
service, but when I asked them to fix it, they did (but
they couldn't explain why they didn't like it).
Apart from that, it all seems fine (unless I'm deluded). :-)
cheers,
raf
ly easy, but that's just one editor.
Although the real reason might just be a preference
for html email.
cheers,
raf
On Sun, Sep 04, 2022 at 05:39:05PM +0200, Jan Eden via Mutt-users
wrote:
> On 2022-09-04 20:37, Cameron Simpson wrote:
> > On 04Sep2022 15:34, raf via Mutt-users wrote:
> > > On Sun, Sep 04, 2022 at 01:51:25PM +1000, Cameron Simpson
> > > wrote:
>
> > >
look quoted to my
> eye anyway, so that aside "live" space stuffing in authoring is something
> I'd find distracting.
>
> Cheers,
> Cameron Simpson
Hmm. I do "From-munging" on arrival.
I should probably read rfc3676 properly. :-)
cheers,
raf
On Sun, Sep 04, 2022 at 08:37:21PM +1000, Cameron Simpson
wrote:
> On 04Sep2022 15:34, raf via Mutt-users wrote:
> > On Sun, Sep 04, 2022 at 01:51:25PM +1000, Cameron Simpson
> > wrote:
> [...]
> > > So I've revisited the manual and found the
> > > `$send
ept that pandoc
whinges about it on stderr.
Do you have any advice for automating spaces at the end
of non-final paragraph lines for format=flowed in vim?
Perhaps I could just post-process messages with perl
in my mutt-editor wrapper script.
cheers,
raf
ourite and make a choice on behalf of their users
rather than letting their users make their own choices.
But this is speculation. I don't really know.
cheers,
raf
look into: e.g. smart_wrap
That looks good. I might add that. It wraps at word boundaries.
> Of course I can reduce the with of the frame on Notion (my window
> manager) where I run Mutt to force the wrapping, but I'd rather keep the
> size I use for everything else and have Mutt wrapping the text for me.
>
> Cheers.
> Ángel
cheers,
raf
ities to each solve a problem that could be solved
by a tiny number of (more powerful) entities. It's just
not efficient or practical or likely to work reliably.
cheers,
raf
nothing to a state of extreme poverty."
> -- groucho marx
> spamtraps: madduck.bo...@madduck.net
Perhaps notmuch's json output with threading that you mentioned
can be fed into jq which could transform it into csv.
cheers,
raf
pe with a mixture like "> >>> > >> blah"
and make it consistent like ">>>>>>> blah". And it won't add a final
space if there isn't one in the input.
I'm sure there's a better way to do it, but this'll do.
A good trick would be to follow any existing quote string. :-)
But the fact that there can be a mixture probably doesn't help.
Hmm, I might adopt the above but do the opposite, and add spaces
where they are "missing". :-)
cheers,
raf
On Mon, Jun 20, 2022 at 08:15:13AM +1000, Cameron Simpson
wrote:
> On 07Jun2022 09:56, raf wrote:
> >And I'm not sure I can do anything about it.
>
> There are many things you can do. I see you've already shifted to just
> using "bold" etc in your color d
r index"
directive per colour combination with a complicated regex
will be ugly, but it will also be much faster.
Another tip is that you can do good things setting the editor
variable to a script of your own that can perform arbitrary
modifications before and/or after invoking the real editor.
cheers,
raf
On Wed, Jun 08, 2022 at 12:23:07AM +0200, Anton Sharonov
wrote:
> raf schrieb am Di., 7. Juni 2022, 01:57:
>
> > TERM=screen.
> >
> > It's OK. screen is more important to me than bold
> > headers.
> >
>
> Don't give up. Gnu screen definitely support
On Mon, Jun 06, 2022 at 09:53:35AM -0700, "Kevin J. McCarthy"
wrote:
> On Tue, Jun 07, 2022 at 12:37:59AM +1000, raf wrote:
> > On Sun, Jun 05, 2022 at 07:02:24PM -0700, "Kevin J. McCarthy"
> > wrote:
> > > TERM=xterm-mono might work for
On Sun, Jun 05, 2022 at 07:02:24PM -0700, "Kevin J. McCarthy"
wrote:
> On Mon, Jun 06, 2022 at 10:57:47AM +1000, raf wrote:
> > And there's also the "mono" directive for terminals that
> > don't support colour, e.g.:
> >
> > mono header bold ^(Su
bject|From|To|Cc|Date):
But it doesn't work for me anymore (with TERM=xterm).
I don't know why that is. I think it must have worked in the
past. I just "ignore" the headers I don't want to see so
it's not really a problem.
And it would bold entire headers, not just their names.
cheers,
raf
On Sun, Jun 05, 2022 at 11:32:34AM +0200, Anton Sharonov
wrote:
> raf schrieb am So., 5. Juni 2022, 07:52:
>
> > On Sun, Jun 05, 2022 at 12:06:52AM -0400, Jason Franklin
> > wrote:
> >
> > > Greetings:
> > >
> > > I have two questions
l (one message at a time - see formail(1))
until you are sure that it works. And note that it doesn't
convert any uppercase to lowercase, only the other way around.
cheers,
raf
On Fri, May 20, 2022 at 05:54:55PM +1000, raf wrote:
> I'm sending a patch that adds an error check for shell
> meta-characters when $sendmail is used. It might have been
> better to check right after reading .muttrc, but this seemed
> like a more natural place to put the code (i.e.,
On Fri, May 20, 2022 at 04:20:55PM +1000, raf wrote:
> On Thu, May 19, 2022 at 12:05:59PM -0700, "Kevin J. McCarthy"
> wrote:
>
> > On Thu, May 19, 2022 at 01:12:31PM -0500, Derek Martin wrote:
> > > On Thu, May 19, 2022 at 11:06:38AM -0700, Kevin J. McCarth
ommands in a file and mutt only needs to see its name.
But users need to be told when they are required to do
that. So in addition to documenting the limitation, a
new error message when the evaluated $sendmail contains
any (non-space) shell meta-characters would be helpful.
That's a clear indication that the user is expecting
shell parsing that isn't going to happen.
cheers,
raf
e current message.
It looks like it's mutt_index_menu()'s MUTTMENU *menu's
current field but I don't think that's accessible to
eat_range().
It looks like the answer is no.
cheers,
raf
promising, though I haven't used it.
>
> Here's a Wikipedia article.
> <https://en.wikipedia.org/wiki/Message_delivery_agent>
Sieve might be another good one to look at. But I haven't
used it.
cheers,
raf
On Mon, Mar 21, 2022 at 01:28:28PM +0100, Martin Trautmann wrote:
> Am 2022-03-21 um 12:56 schrieb raf:
> > textmail can probably do at least some of what you want:
> >
> >https://raf.org/textmail
> >https://github.com/raforg/textmail
> >
> > a
he original post but...
textmail can probably do at least some of what you want:
https://raf.org/textmail
https://github.com/raforg/textmail
and it has some extensibility so you can supply external
translation programs for the bits it doesn't do.
it can operate on individual mail messages or mbox files.
check the output carefully. :-)
cheers,
raf
> --
> Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
> Public GnuPG key: http://www.unixarea.de/key.pub
So it looks like the real problem might be "You're
listed in 1 blacklist" (http://www.backscatterer.org).
Try to get removed from it. Good luck. It sounds like
the mail server you are using needs a configuration
change to stop backscatter. Perhaps you could direct
your mail server providers to that site.
cheers,
raf
On Fri, Mar 11, 2022 at 11:55:04PM +, Ken Moffat
wrote:
> On Sat, Mar 12, 2022 at 09:10:01AM +1100, raf wrote:
> > On Fri, Mar 11, 2022 at 03:12:41PM +0100, Stefan Hagen
> > wrote:
> >
> > > >
> > > > > 550-5.7.26 This message does n
ghr082f2
>
> Feel free to examine it and set your host up in a similiar way.
A good tutorial site for setting it up (at least with debian+postfix) is at
https://www.linuxbabe.com/mail-server/build-email-server-from-scratch-debian-postfix-smtp
(in 12 parts, part 4 is SPF+DKIM, part 5 is DMARC).
> Best Regards,
> Stefan
cheers,
raf
yone comes here via a search, another reason
that authentication credentials can suddenly stop
working is because someone has hacked into the email
account and changed the password (presumably via a web
interface).
cheers,
raf
://www.8t8.us/configs/80316BDA.asc.pubkey
> - the mutt website: http://www.mutt.org/keys/kevin.key
> - The keys.openpgp.org network
>
> https://keys.openpgp.org/vks/v1/by-fingerprint/8975A9B33AA37910385C5308ADEF768480316BDA
Hi Kevin!
Thanks so much for all you do.
It's sad to hear that you'll have
less time and energy for mutt now.
I hope all will be well for you.
cheers,
raf
ess (rather than just file
system access) to both sets of messages.
cheers,
raf
mtp_url just displays the current SMTP URL so you can double
> check that you called the right macro. :-)
>
> Best,
> Mihai
When I have had to do things based on the sender address,
I had to "set editor" to a script that would perform the
necessary modifications to the email before and after
invoking the real editor on the file.
cheers,
raf
t the
first time it reaches end-of-file). If you always
that behaviour, set the environment variable (e.g.) LESS=-e
cheers,
raf
urity_level = dane
For Exim, you'd need:
dns_dnssec_ok = 1
remote_smtp:
hosts_try_dane = *
cheers,
raf
On Sat, Oct 23, 2021 at 02:22:18PM -0400, Nathan Stratton Treadway
wrote:
> On Sat, Oct 23, 2021 at 09:55:12 -0400, Ofer Inbar wrote:
> > I run postfix on a cheap cloud-hosted linux instance. That does mean
>
> Thanks all (Ofer, Bastian, raf, etc.) for this suggestion -- I
postfix, dovecot, amavis,
spamassassin or rspamd, postfix-policyd-spf-perl, OpenDKIM, and
OpenDMARC will do the trick if you don't mind the hassle of setting
everything up. :-)
cheers,
raf
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
are. Although, I suspect that many
users probably wouldn't mind one way or the other.
I admit that I've never liked "FW:". "Fwd:" is better.
But I'm also OK with it how it is. I don't think I
forward emails very often, so my opinion probably
doesn't matter.
cheers,
raf
On Mon, Sep 20, 2021 at 08:31:07PM -0700, "Kevin J. McCarthy"
wrote:
> Thanks raf, I certainly can't say your opinion is due to a lack of
> experience with Mutt! However, just to be clear to everyone, my opposition
> to the "tag" interpretation is be
ight need to be delayed
until the selection process is complete (so tag-entry
makes sense). But like I said, I'm not advocating for
this. I don't even tag messages, and even if I did,
there's already a keystroke for doing that.
cheers,
raf
P.S. Thanks so much for all your work on mutt.
It's much appreciated, every single day.
e advantage of STARTTLS and
the traffic will be encrypted.
cheers,
raf
ary for localhost.
It works, but it's probably slightly slower because it
has to perform the SMTP dialogue.
If postfix can deliver mail submitted by mutt this way,
it should also be able to deliver mail submitted by
mutt the default way.
cheers,
raf
On Sat, Sep 11, 2021 at 05:24:21PM +1000, raf wrote:
> On Sat, Sep 11, 2021 at 05:31:13AM +, Globe Trotter via Mutt-users
> wrote:
>
> > Hi,
> >
> > I have an account where I need to send email through localhost
> > (with port 25). I am using postfix curr
ver to deliver mail sent from mutt, and if you have
postfix installed locally and configured OK, that will
just happen.
cheers,
raf
On Wed, Sep 08, 2021 at 03:47:00PM -0400, Jon LaBadie wrote:
> On Wed, Sep 08, 2021 at 04:31:11PM +1000, raf wrote:
> > On Wed, Sep 08, 2021 at 01:20:27AM -0400, Jon LaBadie
> > wrote:
> >
> > > I've always preferred a black letters on white background scheme.
On Mon, Sep 06, 2021 at 03:48:33PM -0700, Tom Tunguz wrote:
> Raf, amazing. Thank you. Brilliant. I mapped it to K (which is unused and
> it's now lightning fast) Ky!
>
> Thank you thank you!
That's great. I'm glad it helped.
cheers,
raf
ro index AA :!toggle-colour-scheme\n:source next-colour-scheme.muttrc\n
If you see what I mean (toggle-colour-scheme is a command
that swaps the files around).
Note: None of this is tested. It's just conjecture.
cheers,
raf
be more reliable if you used vim rather than gvim
as the editor, or make sure that your gvim window has the
same size and position as mutt's terminal emulator window.
cheers,
raf
ature (i.e. receiving an email).
That seems wierd.
cheers,
raf
eek pattern or another pattern in general, that I can use
> to make that happen or perhaps a way to make the current pattern work like
> this?
>
> Best Regards,
> IFo Hancroft
Perhaps you could use an actual date, and cron a weekly
update to your .muttrc file (and not leave mutt running
for too long).
cheers,
raf
> how can I use mutt unaware of gpg ?
>
> thanks,
I found putting this in my ~/.muttrc helpful when gpgme was
turned on in the default system-wide debian config for mutt:
set crypt_use_gpgme = no
cheers,
raf
On Wed, Aug 11, 2021 at 05:40:05PM -0400, "D.J.J. Ring, Jr."
wrote:
> I found that "man mutt" is not the whole manual.
There's also "man muttrc" for the config file syntax.
That's the most important one.
cheers,
raf
date header to my timezone.
it's attached. the local timezone is hardcoded (sorry) but
can be changed as needed.
cheers,
raf
#!/usr/bin/env perl
use warnings;
use strict;
# procmail_filter_fix_outlook_date_header.pl
#
# This is an email filter to be run by procmail as email arrives.
# It re
ne would probably have been selected
when your operating system was installed. but it can be
overridden easily.
just create a shell function like this:
mutt() { TZ=UTC /usr/bin/mutt "$@"; }
and put it in a shell startup file.
cheers,
raf
machine, move the messages to
another machine, and reply to some the messages
from there. If this variable is set, the default
From: line of the reply messages is built using
the address where you received the messages you
are replying to if that address matches your
“alternates”. If the variable is unset, or the
address that would be used doesn't match your
“alternates”, the From: line will use your address
on the current machine.
Also see the “alternates” command.
Very handy when you have hundreds of email addresses.
cheers,
raf
On Fri, Dec 18, 2020 at 11:16:23AM +0100, Josef Wolf wrote:
> Hello,
>
> I am using mutt for about twwenty years now and am happy so far.
>
> Usually, I start mutt in a screen session and let it run for a long time,
> until I need to reboot the system. This way, I can ssh to my mail host from
uld do it.
you'd need to script it in lua.
for mail delivered locally, procmail could do it.
procmail could detect the need to add the header and
then run it through a separate bespoke filter process
to add it.
cheers,
raf
ory:
mved '*oldhostname*' =newhostname=
mved =oldhostname= =newhostname=
The '=' is like '*' but you don't have to quote it from
the shell.
There are other programs that rename multiple files but
they aren't generic enough, or they require the user to
know Perl.
cheers,
raf
On Sat, Nov 21, 2020 at 04:10:24PM +1100, Cameron Simpson
wrote:
> On 21Nov2020 13:07, raf wrote:
> >On Sat, Nov 21, 2020 at 10:32:03AM +1100, Cameron Simpson
> >wrote:
> >> New ticket for amending the manual entry here:
> >> https://gitlab.com/muttmu
On Sat, Nov 21, 2020 at 10:32:03AM +1100, Cameron Simpson
wrote:
> On 19Nov2020 14:14, raf wrote:
> >Just a thought: if it needs to have a From_ mbox
> >message header (or if it needs to not have that), it
> >might be worth mentioning. Even if the mbox message
> >h
there are several variations
on the mbox file format (maybe 5?). Which ones, if any,
are supported? Nothing's ever obvious or trivial,
especially when it comes to email. :-)
cheers,
raf
for this:
> - save all the messages to a local filesystem maildir folder
> - write a short shell loop to run mutt -H for each message file in the
> maildir
>
> Cheers,
> Cameron Simpson
Another option, especially if you need to do this a
lot, is to use imapfilter if you know (or want to
learn) lua (https://github.com/lefcha/imapfilter).
cheers,
raf
't
a concern, and you probably don't have to be so
careful. But you'll need to assess the risks yourself.
Also note that mutt will coalesce multiple Cc: headers
into a single one after editing, so you don't need to
worry about creating multiple Cc: headers.
I hope that helps. If you think this approach will do
what you need, but you'd like help modifying the perl
to match your exact needs, let me know and I'll modify
it for you. I'm assuming that your environment is UNIXy
enough for all this to be possible. That might not be
the case.
cheers,
raf
On Sun, Oct 25, 2020 at 11:38:01PM +, Globe Trotter via Mutt-users
wrote:
> On Sunday, October 25, 2020, 5:53:20 PM CDT, raf wrote:
>
> On Sun, Oct 25, 2020 at 12:18:26AM +, Globe Trotter via Mutt-users
> wrote:
>
> > On Saturday, 24 October at 22
with a list of
options, and you enter your choice. That way, you could
have more that two options. If always having to select
a browser manually is too inefficient, you could
continue to invoke w3m when viewing html, and invoke
this menu-based browser chooser when "printing" html.
cheers,
raf
(the bit between the <> after a
> parse).
>
> Cheers,
> Cameron Simpson
I didn't drop procmail. I wrote a program to
generate procmail code from a set of prettier
config files. :-)
cheers,
raf
P and SMTP protocols
> whilst doing that? Is something to be feared? Surely MS cares only that
> people pay the monthly rent on Office 365?
>
> --
> Best regards,
> Ed http://www.s5h.net/
One reason is MFA. Where I work, we are often receiving
emails from the hacked email accounts of our clients.
cheers,
raf
e a lot less
effort.
But I really don't know what I'm talking about. I use
mbox.
Perhaps you can rename/move folders in a mail client
and then you don't need to look at the guts underneath.
That would be the easiest way. I know that GUI IMAP
clients can do that. Can mutt do that? I found this:
https://unix.stackexchange.com/questions/44508/mutt-rename-imap-folder
cheers,
raf
rnel would have much difficulty
sending plain text emails. but what do i know? :-)
cheers,
raf
On Tue, Aug 25, 2020 at 01:05:39PM +0100, Chris Green wrote:
> On Tue, Aug 25, 2020 at 09:15:55AM +1000, raf wrote:
> > On Mon, Aug 24, 2020 at 10:32:56AM +0100, Chris Green wrote:
> >
> > > I am on a mailing list which has two addresses, occasionally when on
it, mutt
only sees one of the addresses.
cheers,
raf
n), and then either using the
macro keystroke manually when appropriate, or creating
a send-hook to "push" the macro keystroke into the
keyboard buffer (but this will probably only work if
you can set up a pattern in the send-hook for all
recipient domains that would require the signature).
Good luck.
cheers,
raf
recipe or apply it to mbox
files.
WARNING: Please verify it carefully and make sure it's
doing what you want before deleting the original
mailboxes. Anything that transforms your email should
not be trusted until you have reason to trust it.
cheers,
raf
ould have to win. Luckily for me, that's not the case.
cheers,
raf
ould be doing by default but aren't.
cheers,
raf
ts that
are automatically translatable to text would be ideal.
Perhaps it could be called something like
auto_translate / implicit_autotranslate or auto_render
/ implicit_autorender.
cheers,
raf
r and mutt.vcard.filter by
David A Pearson, vcalendar-filter by Martyn Smith etc.
The vcalendar-filter is very useful for me these days.
In my younger, more fanatical days, I wrote a tool
(textmail) to convert everything to plain text as it
arrived to keep my mailbox small. That wouldn't help
you. :-)
cheers,
raf
Kevin J. McCarthy wrote:
> On Thu, Apr 02, 2020 at 12:01:38PM +1100, raf wrote:
> > Jens John wrote:
> >
> > > On Wed, 1 Apr 2020, at 06:22, raf wrote:
> > > > e.g. Add a CC header to f...@work.com whenever
> > > > sending/replyin
s welcome. The OP
> might adopt it and anyway the rest of us can learn from it.
>
> Cheers,
> Cameron Simpson
indeed. it looks like a great solution.
hopefully, i can work out why it isn't
being triggered for me, and get it working.
cheers,
raf
Jens John wrote:
> On Wed, 1 Apr 2020, at 06:22, raf wrote:
> > e.g. Add a CC header to f...@work.com whenever
> > sending/replying/forwarding from m...@work.com unless the
> > email is already going to f...@work.com.
>
> I think a combination of hooks or only
raf wrote:
> What's a good way to automatically add a Cc: header
> for a particular address when sending/replying/forwarding?
> But not if they're already going to receive the email.
> And only when sending from a particular address.
>
> e.g. Add a CC header to f...@work.com
was wondering if there's another way.
cheers,
raf
complaining that xterm
> was obsolete and no longer supported. (!!!)
i use it all the time.
i don't mind if it never changes again
but i'd be annoyed if it ever disappeared.
cheers,
raf
Derek Martin wrote:
> TBH most of the time, if I really need to see what's in an HTML mail,
> I just bounce it to gmail. But sometimes that doesn't work either due
> to DNS-based spam prevention.
Forwarding the email as an attachment rather than bouncing it should solve that.
cheers,
raf
anyone have any idea why this might be the case or what i can
do to make lynx work again for autoviewing html in mutt?
cheers,
raf
.
-Dave Dodge/dodo...@dododge.net
cheers,
raf
. Thus mutt is quite
happy with the following in an mbox:-
because that is correct.
the python code needs to be changed to write the From header, then the
message, then the blank line.
cheers,
raf
automatically
fetching mail as it arrives. then again,
you might not :)
raf
Jan- Hendrik Palic wrote:
On Thu, Nov 23, 2000 at 02:04:30PM +1100, raf wrote:
| I got a problem and I don't know, where the problem is.
|
| I sent yesterday a mail with several adresses in BCC- field. A friend, using
| Outlook on Windows ME (I thing Outlook 5.5) is able to see
1 - 100 of 116 matches
Mail list logo
