Actually, we have tried both but have not found the culprit(s)
yet. Although my partner believes he saw a spike in traffic coming in as a
Telenet session from an unexpected origin -
rrcs-74-39-200-122.nys.biz.rr.com which on searching with google appears
not too uncommon - that is hacks, spam
Orin Wells wrote on Thursday, September 08, 2005 1:15 AM:
Regarding telnet - apparently there is a problem with windows 2003
and iMail. If my source is correct one can telnet into a Windows
2003 system running iMail (pick a version) on port 25 and get by the
authentication. Again, my
One other thing to add to this. Ipswitch in their brilliance, decided
to make a default password of "password" for any newly created account
including root. One must take great care to change these otherwise
they can become susceptible to AUTH hacking with a great deal of ease,
and you then
Orin Wells wrote:
OK, I see it. The question is how do you KILL the stuff that has
gotten into the server? We shut down the IMAP yesterday primarily
because we really don't have anyone we are aware of who does not use
POP3. But the problem persists and seems to avoid every attempt to
find
: Russ Lists [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Thursday, September 08, 2005 9:24 AM
Subject: Re: [Declude.JunkMail] OT - iMail 7.x and Windows 2003
Orin Wells wrote:
OK, I see it. The question is how do you KILL the stuff that has gotten
into the server? We shut down
I don't see that as a big issue.
They can't Auth when 'Account Access Disabled' is checked in the user
gui.
If the user has a POP box, uncheck 'Account Access Disabled' and use
their unique password.
If the user is for forwarding, then make sure that 'Account Access
Disabled' is checked. They
We are about to build a new server using Windows 2003. The reason is that
we were apparently attacked through the iMail IMAPI exploit. The last of
whatever got in seems to be running in a very effective stealth mode
because nothing seems to be able to find it and kill it. As a consequence,
We have been running iMail 7.07 under windows 2000. We had some input
that
there may be some problems in this environment. We are not keen on
upgrading to 8.x since IPSwitch is walking away from iMail the product.
Ipswitch is not walking away from Imail. It is still alive and well, and in
I think that the exploit is in imail 7.07 and not in your server do a
google on
imail 7.07 exploit.
So you most likely would need to upgrade to 8.2 series. Tho the exploit
isn't in 8.15 I don't believe. BTW they do seem to have some interesting
pricing going on if you google imail deals depending
At 01:43 PM 9/7/2005, Ncl Admin wrote:
I think that the exploit is in imail 7.07 and not in your server do a
google on
imail 7.07 exploit.
OK, I see it. The question is how do you KILL the stuff that has gotten
into the server? We shut down the IMAP yesterday primarily because we
really
and remove it.
Kevin Bilbee
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Orin Wells
Sent: Wednesday, September 07, 2005 3:32 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] OT - iMail 7.x and Windows 2003
At 01:43 PM 9/7/2005
11 matches
Mail list logo
