Thank you. The only reason we're concerned is we're using Netscape Mail
Server which can NOT handle the traffic it's getting. Granted, it's
5-year-old unsupported software, but it's all we had in an emergency
situation. Now that we have time to roll out a product properly, we
want to make sure we do it right. We have no problems at all with
bandwidth. We have our primary DNS server internally, and our secondary
is hosted out. Also, all mail is routed through our email virus
firewall. I would imagine the majority of our customers send standard
"Hi mom" messages, although we do have a reasonable number that do send
pictures and files. Thanks for the input!
Jeff Underwood
WestCoastNet
(541)996-9700
[EMAIL PROTECTED]
-----Original Message-----
From: Len Conrad [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 18, 2000 11:42 AM
To: [EMAIL PROTECTED]
Subject: Re: [IMail Forum] Requirements
>mail server is on. Our company currently has about 2,000 users, 30,000
That's only .7 msgs/sec for a 12-day. Almost any mail server can handle
that.
2000 accounts is tiny. Imail has servers of 10's of 1000's.
>mail messages per day, and we have a dual-Pentium Pro 200 with 128 meg
>of RAM. Will this be sufficient?
Sounds reasonable. What speed is your link to Internet?
Do you run your own DNS on the same LAN segment as Imail?
Receiving msgs to Imail is very fast, but sending msgs requires Imail to
do
a DNS lookup (want a sufficiently available and fast DNS server),
intiatiate contact with the remote server, shake hands, send the mail.
If the address is wrong or the other server is down or unreachable,
Imail
will then go into its queue-it-and-retry loop, eating up Imail
throughput.
If your 2000 users are in the habit of sending mutli-megabyte files,
then
that eats up your backbone link real fast compared to 30,000 text msgs.
Len
================
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
