From: Amos Gouaux <amos+lists.ding@utdallas.edu>
Subject: Re: unix mail spool vs Exchange
Date: Fri, 10 Oct 2003 22:53:03 -0500 [thread overview]
Message-ID: <m2he2gv3a8.fsf@gilgamesh.local> (raw)
In-Reply-To: <vvroewqw939.fsf@netapp.com> (K. S. V.'s message of "Fri, 10 Oct 2003 00:07:46 +0530")
>>>>> On Fri, 10 Oct 2003 00:07:46 +0530,
>>>>> K S V <venky@netapp.com> (ksv) writes:
ksv> Hi,
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
Tell them: how do they expect prospective UNIX customers to take
them seriously if they don't even use UNIX themselves....
--
Amos
prev parent reply other threads:[~2003-10-11 3:53 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
2003-10-10 14:10 ` Kirk Strauser
2003-10-11 3:53 ` Amos Gouaux [this message]
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=m2he2gv3a8.fsf@gilgamesh.local \
--to=amos+lists.ding@utdallas.edu \
/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).