and here's the crunch...
This method would therefore also preclude using an SQL Server for IMail
authentication. Unless of couse, I ran TWO SQL 7 Servers...<shudder>
<sigh>
hmm, it technically possible to have the remote POP come across the WAN to your central SQL server, but practically it sounds your pipe is a little too tight to handle the SQL transactions as well as the mail.
However, having the remote POP users interact with their local Imail server rather than your main Imail server does remove some traffic from the wire (at least displace it in time). The remote users' mail pickups would be from the remote peer's disk.
Since you have to buy a 2nd mail server, "it wouldn't cost you anthing", vbg, to try the remote peer authenticating across the WAN gainst the central SQL db.
Also, since so much mail is text, make sure, for WAN links up to 256 kbits/sec, that the routers are set up for compression.
This sounds kinda convoluted, but it's a one time deal and one time Imail purchase, vs the recurrent bills for higher bandwith at $16,500 per megabit-month!!
$16.5/kilobit-month x 1000 kilobits/megabit = $16,500
Len < and quit sighing, you're depressing me !! vbg >
=========
Looks like the only really *workable* solution would be to bite the
bullet and upgrade our line capacity...and at our Telco prices of $16.50
per kb of bandwidth....
<bigger sigh>
