From: Steve Youngs <sryoungs@bigpond.net.au>
Subject: Re: unix mail spool vs Exchange
Date: Fri, 10 Oct 2003 09:47:16 +1000 [thread overview]
Message-ID: <microsoft-free.87pth655yz.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <vvroewqw939.fsf@netapp.com>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
|--==> "KSV" == K S V <K> writes:
KSV> In my company I have to justify why I need a unix mail spool
KSV> (there is a Exchange server already).
KSV> Is there any compelling reason other than procmail to use
KSV> unix mail spool
Isn't _not_ using exchange server reason enough? :-P
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Ashes to ashes, dust to dust. |
| The proof of the pudding, is under the crust. |
|------------------------------<sryoungs@bigpond.net.au>---|
[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2003-10-09 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 18:37 K S V
2003-10-09 23:47 ` Steve Youngs [this message]
2003-10-10 14:10 ` Kirk Strauser
2003-10-11 3:53 ` Amos Gouaux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=microsoft-free.87pth655yz.fsf@eicq.dnsalias.org \
--to=sryoungs@bigpond.net.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).