On Monday 29 December 2003 05:37 pm, Dick Morrell wrote:
> Quoting Mike Sensney <[EMAIL PROTECTED]>:
> > Sigh. If you really want to think so then so be it. This is a developer's
> > list.
> > It is for people who actually write code to discuss problems they are
&g
At 03:42 PM 12/29/2003, [EMAIL PROTECTED] wrote:
On Monday 29 December 2003 05:32 pm, Mike Sensney wrote:
> As such I thought that thread should end.
>
Exactly what I was referring to. Thank you for making my point. It *IS*
who(m)
is talking.
Sigh. If you really want to think so then so
At 11:48 AM 12/29/2003, [EMAIL PROTECTED] wrote:
> Sorry, my mistake. I was going to make a comment, but coffee arrived,
and
> I hit the wrong button.
Just a quick comment to point out I was rather roundly trounced and then
asked
to not discuss this anymore on this dev-list the very last time su
On Tuesday 16 December 2003 09:05 pm, [EMAIL PROTECTED] wrote:
> What was bothering me, in part were two issues.
You have talked this to death. Please stop.
If you have further doubts about Mitel's compliance with the GPL I suggest you
hire yourself a lawyer and have him/her talk to Mitel's lawy
For those that are interested the author of the "Replace Exchange Server"
article is from Bynari and they have produced a commercial product based on
their research called InsightServer.
http://bynari.net
They also have some good documentation on their site
http://bynari.net/index.php?id=271
incl
Thanks Darrell,
That fixed it. Now I'm a happy camper. :-)
Thursday, August 8, 2002, 1:25:58 PM, Darrell May wrote:
DM> Mike Sensney <[EMAIL PROTECTED]> said:
>> I did a fresh install of SME 5.5 and then installed the user manager,
DM> Try 'devinfo-mitel-userma
py this from a working 5.1.2 server or are there more things broken
and this isn't a good idea? This is a production server so I don't
want to risk breaking it by experimentation
Mike Sensney
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discus
I can confirm that there seems to be a problem with Dyndns update.
This bug affects SME5 but not the previous ES 4.1.2.
Dyndns requires that you "update" your info every 30 to 35 days or they
will cancel your account, but that they don't want you updating more often
if your IP is constant. Appa
RPM Find is your friend.
Search http://www.rpmfind.net for "kernel-enterprise".
At 12:33 AM 09/30/2001 +0200, Brossin Pierrick wrote:
>Ok I only found :
>
> - kernel-enterprise-2.2.16-22.i686.rpm
> - kernel-enterprise-2.4.2-2.i686.rpm
>
>Are you sure the 2.2.19 exists ?
>if no, which one shoul
Congratulations to E-Smith/Mitel Networks. I knew you had a good product.
A friend of mine just pointed out to me this page where Compaq is offering a
ProLiant server with SME Server v5 preinstalled. SME v5 is mentioned at the
bottom of the page with a link to more info.
http://www.compaq.com
t servers."
sleep 600
done
At 02:40 PM 09/19/2001 +1000, Gordon Rowell wrote:
>On Tue, Sep 18, 2001 at 09:37:18PM -0400, Dan Brown <[EMAIL PROTECTED]> wrote:
>> Mike Sensney wrote:
>>
>> > BTW, you can produce a sorted IP list of infected servers using:
>>
What about IE5.5 and IE6? Does anybody know if they are vulnerable yet?
My guess is probably so...
(Is this a plot by Netscape to get back user share? :)
At 02:22 PM 09/18/2001 -0400, Dan York wrote:
>FYI, incidents.org now has a page up about the worm:
>
> http://www.incidents.org/alert.php
The common character string for this worm is 'c_dir'
cat /var/log/httpd/access_log |grep 'cmd.exe' | wc -l
3132
cat /var/log/httpd/access_log |grep 'root.exe' | wc -l
683
cat /var/log/httpd/access_log |grep 'c+dir' | wc -l
3815
3132 + 683 = 3815
BTW, you can produce a sorted IP
At 11:32 AM 06/26/2001 -0400, Charlie Brady wrote:
>Using:
>rpm -Uhv --nodeps apache-1.3.19-5.i386.rpm
>instead of "rpm -iv --force ..." corrects the multiple apaches problem.
I've already installed apache-1.3.19-5.i386.rpm using "rpm -iv --force ..."
as per Darrell's previous instructions.
Can
I just implemented your HowTo. Went without a hitch.
The PDFs that I reported having problems with earlier
now load without error.
At 06:27 AM 06/26/2001 +, Darrell May wrote:
>For all following this thread, I think I have the solution. If you have
>a non-production e-smith server, I wo
At 05:52 PM 06/22/2001 -0500, Timothy C Litwiller wrote:
>This has a vagly familiar sound to it. Do you know how these pdfs were
>created? or are they from completely dissimilar places? We had a
>similar
>problem with pdf coming out of an HP digital sender until we upgraded
>the
>firmware.
I just finished a nessus scan (http://www.nessus.org) of a test E-Smith
4.1.1 box. I enabled all of the nessus "plugins", including those listed as
dangerous. I also enabled nmap in scan options. Since I have yet to read
all
the directions for nessus, I very well could have something miss
conf
At 05:48 PM 03/02/2001 -0500, Charlie Brady wrote:
>So the meat of the answer is still perfectly valid - e-smith imap support
>was developed before Courier-IMAP was available, and we have yet to see
>compelling reasons to change.
What about:
http://www.securityfocus.com/frames/?content=/templates
18 matches
Mail list logo