[xmail] XMail on FC4

2006-03-12 Thread Dale Qualls

Any horror stories about running xmail on FC4?

I've given up on running it on Open Suse 10, it just doesn't like the
hardware I guess (it's a strong running Dell but OpenSuse just drags
on it.  Stopping xmail takes forever, and eventually the processes are
stopped but the /etc/init.d/xmail stop command never finishes, this
along with other issues including my filter error -97 woes

Never had an issue like this on our RH8 box so I guess sticking with
RH in some form is the way to go.

We're either going to go with the FC4 or just rebuild the box on RH8
with larger drives.  Might have to just stick with RH8 since we know
it works pretty darned good.

Thx!



-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: XMail on FC4

2006-03-12 Thread Jeffrey Laramie

On Sunday 12 March 2006 08:02, Dale Qualls wrote:
 Any horror stories about running xmail on FC4?

 I've given up on running it on Open Suse 10, it just doesn't like the
 hardware I guess (it's a strong running Dell but OpenSuse just drags
 on it.  Stopping xmail takes forever, and eventually the processes are
 stopped but the /etc/init.d/xmail stop command never finishes, this
 along with other issues including my filter error -97 woes

I've had XMail running on openSUSE 10 for a couple months now and haven't had 
any of those issues, but I have a very low volume server. Maybe XMail prefers 
AMD chips...   ;-)

Jeff
-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: XMail on FC4

2006-03-12 Thread Dale Qualls

Hmmm.  On this box it starts up fine but doesn't stop easily.  It is
an Intel chip.

Also, for some reason it's very sluggish.  Running in debug mode
showed approximately 8-10 seconds to connect via POP3 and SMTP from
the client (and both were on a 100mb switch with nobody else on).


-- 
later,
 Dale
 mailto:[EMAIL PROTECTED]  


Sunday, March 12, 2006, 8:13:34 AM, you wrote:


 On Sunday 12 March 2006 08:02, Dale Qualls wrote:
 Any horror stories about running xmail on FC4?

 I've given up on running it on Open Suse 10, it just doesn't like the
 hardware I guess (it's a strong running Dell but OpenSuse just drags
 on it.  Stopping xmail takes forever, and eventually the processes are
 stopped but the /etc/init.d/xmail stop command never finishes, this
 along with other issues including my filter error -97 woes

 I've had XMail running on openSUSE 10 for a couple months now and haven't had
 any of those issues, but I have a very low volume server. Maybe XMail prefers
 AMD chips...   ;-)

 Jeff
 -
 To unsubscribe from this list: send the line unsubscribe xmail in
 the body of a message to [EMAIL PROTECTED]
 For general help: send the line help in the body of a message to
 [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: Unable to compile Xmail on NetBSD 3.0

2006-03-12 Thread David Lord
On 11 Mar 2006, at 8:37, Davide Libenzi wrote:

 
 On Tue, 7 Mar 2006, David Lord wrote:
 
  Well it was quite a while back (Jan 17).
 
  g++  -O2 -I. -D__UNIX__ -D__BSD__ -D__NETBSD__ -D_REENTRANT=1
  -D_THREAD_SAFE=1 -DHAS_SYSMACHINE -c SysDep.cpp
  In file included from SysDep.cpp:40:
  SysDepBSD.cpp: In function `int SysGetDiskSpace(const char*,
  SYS_INT64*,  SYS_INT64*)':
  SysDepBSD.cpp:2429: error: aggregate `statfs SFS' has incomplete
  type and cannot be defined SysDepBSD.cpp:2431: error: invalid use of
  undefined type `struct statfs' SysDepBSD.cpp:2429: error: forward
  declaration of `struct statfs' gmake: *** [SysDep.o] Error 1
 
  It didn't get very far. I can post full output 4.5k but that was
  first error encountered.
 
  I've not had any other unexplained problem during setting up this
  server.
 
  xmail-1.21 compiled ok on the k6-400 with NetBSD 2.0 (gcc 2.95) but
  on trying again after update to NetBSD 3.0  (gcc 3.3.3) and failure
  of xmail-1.22 to compile I found that wouldn't compile either and
  gave same error.
 
  That would suggest I try again with gcc 2.95 which I'll try after
  working out how I can safely install it without messing up existing
  setup.
 
 Ok, now I remember. This is not a gcc problem. You seem to be missing
 (or have a broken setup) of the libc development package (dunno how it
 is called in NetBSD.
 
Thanks Davide

I just found this in /usr/src/UPDATING 20040418:

  statfs(2) and friends have been replaced by statvfs(2).
  ...
  In addition your libc build might not work 
  (undefined SYS_statfs symbol) because make clean does not know how
  to remove files it does not know about anymore.

So that's got me progressed a bit further and seems to be related as 
my hack was to change statfs to statvfs in SysDepBSD.cpp. However I 
thought there were compatibility settings in use that were supposed 
to handle this and the suggested solution above doesn't seem 
applicable.

David

-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: XMail on FC4

2006-03-12 Thread Davide Libenzi

On Sun, 12 Mar 2006, Dale Qualls wrote:


 Any horror stories about running xmail on FC4?

 I've given up on running it on Open Suse 10, it just doesn't like the
 hardware I guess (it's a strong running Dell but OpenSuse just drags
 on it.  Stopping xmail takes forever, and eventually the processes are
 stopped but the /etc/init.d/xmail stop command never finishes, this
 along with other issues including my filter error -97 woes

Uh? XMail does not care at all and runs everywhere there's a SuS POSIX 
subsystem. Delays in the XMail stop procedure are very likely related to a 
slow DNS name/IP resolution. You can modify the xmail script to issue a 
kill after waiting for 8-10 seconds.
Wait, error -97 is related to filter execution errors or segfaults, so you 
might want to look into that before blaming XMail ;)


- Davide


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: Unable to compile Xmail on NetBSD 3.0

2006-03-12 Thread Davide Libenzi

On Sun, 12 Mar 2006, David Lord wrote:

 Thanks Davide

 I just found this in /usr/src/UPDATING 20040418:

  statfs(2) and friends have been replaced by statvfs(2).
  ...
  In addition your libc build might not work
  (undefined SYS_statfs symbol) because make clean does not know how
  to remove files it does not know about anymore.

 So that's got me progressed a bit further and seems to be related as
 my hack was to change statfs to statvfs in SysDepBSD.cpp. However I
 thought there were compatibility settings in use that were supposed
 to handle this and the suggested solution above doesn't seem
 applicable.

I am definitely a Unix kinda of guy, but I have to say that there is a 
reason why Microsoft makes bazillions of dollars. They never do that. You 
can get a Win32 binary (leaving DOS stuff apart) built in 1995 and run it 
today w/out problems. And we're talking about binaries, letting apart 
all the times ABI are broken in the middle. Now, the fix is not a problem, 
but the source files start becoming a mess in trying to distinguish even 
between versions of the same OS. Crap!



- Davide


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: XMail on FC4

2006-03-12 Thread Jeffrey Laramie

On Sunday 12 March 2006 11:20, Dale Qualls wrote:
 Hmmm.  On this box it starts up fine but doesn't stop easily.  It is
 an Intel chip.

I know... a little tongue is cheek there. Dell is the last of the major PC 
manufacturers to refuse to use AMD chips. It appears that is about to end 
since their customers are demanding Opteron servers and Dell is said to be 
working on an AMD based line. I'm personally not a big fan of Intel, 
nevertheless if it were a chip issue I'm sure lot's of people would be having 
the same problems.


 Also, for some reason it's very sluggish.  Running in debug mode
 showed approximately 8-10 seconds to connect via POP3 and SMTP from
 the client (and both were on a 100mb switch with nobody else on).

In my experience slow connections have always been DNS or firewall related; 
waiting for the primary nameserver to timeout before trying the secondary, or 
a connection waiting for a response which is being blocked by a firewall.

Another possibility is one of your filters is hanging which might explain all 
of your symptoms. If I recall correctly checkvirus.cfg has path settings that 
need to be changed when switching to SUSE.

Jeff
-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: XMail on FC4

2006-03-12 Thread Dale Qualls

Hiya!

Trust me, I'm not blaming xmail, I'm blaming the OpenSuse.  xmail runs
beautifully on everything I've had it on (RH and Mandrake).


No disrespect meant towards the xmail product or you Davide.

-- 
later,
 Dale
 mailto:[EMAIL PROTECTED]  


Sunday, March 12, 2006, 10:52:17 AM, you wrote:


 On Sun, 12 Mar 2006, Dale Qualls wrote:


 Any horror stories about running xmail on FC4?

 I've given up on running it on Open Suse 10, it just doesn't like the
 hardware I guess (it's a strong running Dell but OpenSuse just drags
 on it.  Stopping xmail takes forever, and eventually the processes are
 stopped but the /etc/init.d/xmail stop command never finishes, this
 along with other issues including my filter error -97 woes

 Uh? XMail does not care at all and runs everywhere there's a SuS POSIX
 subsystem. Delays in the XMail stop procedure are very likely related to a
 slow DNS name/IP resolution. You can modify the xmail script to issue a
 kill after waiting for 8-10 seconds.
 Wait, error -97 is related to filter execution errors or segfaults, so you
 might want to look into that before blaming XMail ;)


 - Davide


 -
 To unsubscribe from this list: send the line unsubscribe xmail in
 the body of a message to [EMAIL PROTECTED]
 For general help: send the line help in the body of a message to
 [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]



[xmail] Re: XMail on FC4

2006-03-12 Thread Eric Garnice

On 3/12/2006 3:03 PM Dale Qualls wrote:
 Hiya!
 
 Trust me, I'm not blaming xmail, I'm blaming the OpenSuse.  xmail runs
 beautifully on everything I've had it on (RH and Mandrake).
 
 
 No disrespect meant towards the xmail product or you Davide.
 

Three production boxes, all XMail 1.22 on FC4 on Dell PowerEdges of 
various vintage.  Lindeman AV and Dario XSpamc filters on all three and 
never a hiccup.

Actually, I have run XMail on RH6, 7, 8, 9, FC3 and 4, OS X and various 
versions of that thing once called Caldera and have never had a problem.

Hope this helps,

Eric


-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]