That's kind of conflicting, isnt it? Saying it's the way to go, but then it has weird, unidentifiable problems with large volumes of mail. :)

I'm not sure how you define large volumes, the Imail server in question will move over 2Mbps sustained of mail at some points of the day. That's quite a bit, considering it's mostly text.

Is there a compelling reason to go with win2k3?

Jonathan

At 12:12 PM 12/19/2003, you wrote:
For the majority, W2K3 is the way to go if you are able to. Ipswitch does
support running Imail on W2K3.

There are some possible issues.

1. Running MS DSN service on W2K3 WITH Imail Anti-Spam DNS tests is a
problem.

2. Some issues have been reported on the Imail list when the server
processes a high volume of messages per day. Nothing seems to be conclusive
as far as I know to date, and from the posts, I have not seen a definite
pattern.

John Tolmachoff
Engineer/Consultant/Owner
eServices For You


> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- > [EMAIL PROTECTED] On Behalf Of Jonathan > Sent: Thursday, December 18, 2003 10:44 PM > To: [EMAIL PROTECTED] > Subject: RE: [Declude.JunkMail] Windows Server 2003 > > So I haven't heard anything else back on this .. are you guys all staying > away from Windows 2003 and Imail? I'm having a hard time trying to justify > the risk of running new servers on 2k3 when 2k works just fine .. but then > again, 2k3 seems more stable over time .... but not if Imail doesn't > support it well yet. > > grrrr > > Thoughts? > > Jonathan > > At 05:04 PM 12/4/2003, you wrote: > >The issues seem to appear at high volumes. > > > >Besides, I am more than willing to use those licenses for you. ;) > > > >John Tolmachoff > >Engineer/Consultant/Owner > >eServices For You > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- > > > [EMAIL PROTECTED] On Behalf Of Jonathan > > > Sent: Thursday, December 04, 2003 2:43 PM > > > To: [EMAIL PROTECTED] > > > Subject: [Declude.JunkMail] Windows Server 2003 > > > > > > So, what's the scoop with current Imail 8, declude, sniffer, etc on > > > Windows > > > 2003 Server? We're thinking about moving it to some new iron > internally, > > > and Ive got some 2k3 licenses just burning a hole in my pocket. :) > > > > > > I heard some stability issues, saw some imail patches/etc .. things > stable > > > (and *robust*) now? Relatively high volumes of email .. > > > > > > Jonathan > > > > > > --- > > > [This E-mail was scanned for viruses by Declude Virus > > > (http://www.declude.com)] > > > > > > --- > > > This E-mail came from the Declude.JunkMail mailing list. To > > > unsubscribe, just send an E-mail to [EMAIL PROTECTED], and > > > type "unsubscribe Declude.JunkMail". The archives can be found > > > at http://www.mail-archive.com. > > > >--- > >[This E-mail was scanned for viruses by Declude Virus > >(http://www.declude.com)] > > > >--- > >This E-mail came from the Declude.JunkMail mailing list. To > >unsubscribe, just send an E-mail to [EMAIL PROTECTED], and > >type "unsubscribe Declude.JunkMail". The archives can be found > >at http://www.mail-archive.com. > > --- > [This E-mail was scanned for viruses by Declude Virus > (http://www.declude.com)] > > --- > This E-mail came from the Declude.JunkMail mailing list. To > unsubscribe, just send an E-mail to [EMAIL PROTECTED], and > type "unsubscribe Declude.JunkMail". The archives can be found > at http://www.mail-archive.com.

---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]


---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.

--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.

Reply via email to