[xmail] Re: @Davide - compliments and suggestions.
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Henri van riel Sent: Tuesday, 16 November 2004 5:58 PM To: Davide Libenzi Subject: [xmail] Re: @Davide - compliments and suggestions. Hello Davide, Tuesday, November 16, 2004, 7:03:28 AM, you wrote: On Sun, 14 Nov 2004, Rob Arends wrote: Also my compliments to Davide on an excellent product. I wonder why comliments are always followed by change requests :) Cause we're suck-ups ;) But really, it's a great product but there's *always* room for improvement. And because we don't tell you often enough how great xmail really is. (and because we're suck-ups) Rob ;-) -- Best regards, Henrimailto:[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] - 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: @Davide - compliments and suggestions.
On Sun, 14 Nov 2004, Rob Arends wrote: Also my compliments to Davide on an excellent product. I wonder why comliments are always followed by change requests :) - 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: @Davide - compliments and suggestions.
Hello Davide, Tuesday, November 16, 2004, 7:03:28 AM, you wrote: On Sun, 14 Nov 2004, Rob Arends wrote: Also my compliments to Davide on an excellent product. I wonder why comliments are always followed by change requests :) Cause we're suck-ups ;) But really, it's a great product but there's *always* room for improvement. -- Best regards, Henrimailto:[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: @Davide - compliments and suggestions.
Also my compliments to Davide on an excellent product. I too have suggested Clement's point 1 about moving cmd line params to server.tab. And point 2 about the ability to disable a service makes Xmail able to suit more individual configurations. I too would like to disable finger, but cannot. Can it be bound to 0.0.0.0 ? I would rather it no run at all. Also Davide, can you start v2 with v2.01 rather than v2.1 It makes for less confusion. For example the recent v1.20 was confused with v1.2 Rob :) _ Note To Self: Remember to put something witty here later... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of CLEMENT Francis Sent: Friday, 12 November 2004 8:50 PM To: '[EMAIL PROTECTED]' Subject: [xmail] Re: @Davide - compliments and suggestions. Hello Davide I compliment you too for xmail server ... Just two question/suggestion : 1 - Is it not possible in next 2.0 release to place ANY xmail command line switchs in the server.tab file as all of these settings are 'server' width ? Except the debug option and an option or (default) argument to specifing 'working directory' ? xmail [working directory] [-Md] if working directory is ommited, then xmail load server.tab file as currently implemented This will avoid two places for server width parameters (some in cmd line, some in server.tab file) First think xmail have to do is locate the server.tab file, then read it and start init , ... and/or if these 'old' cmd line options are specified in cmd line they override server.tab files (for test purpose and compatibility with old implementations) Options precedence : cmd line then server.tab then defaults 2 - The option to disable some protocol by binding them to localhost is not the perfect solution as these services will continu to be accessible from local host ..., so 'customers' processes could access these protocols ... (in 'mutualised' hosting services as a sample config). Is it not possible to completly disable them to run, as Henri suggested ? I tried this in 1.20 source code, and it seems to work fine : (here for finger and pop3, for a relay only server) (First tries were done in 1.17 code and tested in production before applying them to 1.20 currently in test from 1 month with these patchs) To do this, I introduced new cmd line params '-PD' to disable pop3, and a '-FD' to disable Finger (not yet in server.tab file as in question/suggestion 1 ;-) ) With these patchs, minimal service init is allways done, to avoid conflic or bad common parts init, but no thread (so no bindings) is launched if disabled flag is set, and test is done at stop to not try to stop inexistant threads - 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: @Davide - compliments and suggestions.
-Message d'origine- De : Rob Arends [mailto:[EMAIL PROTECTED] Envoy=E9 : dimanche 14 novembre 2004 13:20 =C0 : [EMAIL PROTECTED] Objet : [xmail] Re: @Davide - compliments and suggestions. =20 =20 Also my compliments to Davide on an excellent product. =20 I too have suggested Clement's point 1 about moving cmd line params = to server.tab. And point 2 about the ability to disable a service makes=20 Xmail able to suit more individual configurations. I too would like to disable=20 finger, but cannot. Can it be bound to 0.0.0.0 ? If I remember sockets/network programming, generaly, binding to 0.0.0.0 means bind to all !!! not bind to none .. So it's equivalent to not specify any bind in xmail cmd line for this particular protocol I would rather it no run at all. =20 Also Davide, can you start v2 with v2.01 rather than v2.1 It makes for less confusion. For example the recent v1.20=20 was confused with v1.2 =20 Rob :) =20 Francis - 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: @Davide - compliments and suggestions.
Hello Davide
I compliment you too for xmail server ...
Just two question/suggestion :
1 - Is it not possible in next 2.0 release to place ANY xmail command line
switchs in the server.tab file as all of these settings are 'server' width ?
Except the debug option and an option or (default) argument to specifing
'working directory' ?
xmail [working directory] [-Md]
if working directory is ommited, then xmail load server.tab file as
currently implemented
This will avoid two places for server width parameters (some in cmd line,
some in server.tab file)
First think xmail have to do is locate the server.tab file, then read it and
start init , ...
and/or if these 'old' cmd line options are specified in cmd line they
override server.tab files (for test purpose and compatibility with old
implementations)
Options precedence : cmd line then server.tab then defaults
2 - The option to disable some protocol by binding them to localhost is not
the perfect solution as these services will continu to be accessible from
local host ..., so 'customers' processes could access these protocols ...
(in 'mutualised' hosting services as a sample config). Is it not possible to
completly disable them to run, as Henri suggested ?
I tried this in 1.20 source code, and it seems to work fine : (here for
finger and pop3, for a relay only server)
(First tries were done in 1.17 code and tested in production before applying
them to 1.20 currently in test from 1 month with these patchs)
To do this, I introduced new cmd line params '-PD' to disable pop3, and a
'-FD' to disable Finger
(not yet in server.tab file as in question/suggestion 1 ;-) )
With these patchs, minimal service init is allways done, to avoid conflic or
bad common parts init, but no thread (so no bindings) is launched if
disabled flag is set, and test is done at stop to not try to stop inexistant
threads
(Sorry no diff present on the computer used to mail ...)
In POP3Svr.h :
--
..
..
..
#define POP3F_STOP_SERVER (1 0)
#define POP3F_LOG_ENABLED (1 1)
#define POP3F_HANG_ON_BADLOGIN (1 2)
//**
#define POP3F_DISABLED (1 3)// to disable pop3 service
//**
..
..
..
In FINGSvr.h :
--
..
..
..
#define FINGF_STOP_SERVER (1 0)
#define FINGF_LOG_ENABLED (1 1)
//**
#define FINGF_DISABLED (1 2)// to disable finger service
//**
..
..
..
In MailSvr.cpp :
..
..
..
static int SvrSetupFING(int iArgCount, char *pszArgs[])
{
..
..
..
case ('I'):
if ((++ii iArgCount)
(MscGetServerAddress(pszArgs[ii],
SvrAddr[iNumAddr]) == 0))
++iNumAddr;
break;
//**
// Added Finger Disabled flag option parsing
case ('D'):
ulFlags |= FINGF_DISABLED;
break;
//**
}
}
..
..
..
for (int nn = 0; nn iNumAddr; nn++)
pFINGCfg-SvrAddr[nn] = SvrAddr[nn];
ShbUnlock(hShbFING);
//**
//-Added Finger Disabled flag Test
//--Don't start any thread if Finger Disabled flag is set
if (! ((pFINGCfg-ulFlags) FINGF_DISABLED)) {
//
if ((hFINGThread = SysCreateThread(FINGThreadProc, NULL)) ==
SYS_INVALID_THREAD) {
ShbCloseBlock(hShbFING);
return (ErrGetErrorCode());
}
//--close if--
}
//**
return (0);
}
static void SvrCleanupFING(void)
{
..
..
..
pFINGCfg-ulFlags |= FINGF_STOP_SERVER;
ShbUnlock(hShbFING);
//**
//-Added Finger Disabled flag Test
//--Don't try to stop NO existant threads if never started due to Finger
Disabled flag set
if (! ((pFINGCfg-ulFlags) FINGF_DISABLED)) {
//
///
// Wait FINGER
///
SysWaitThread(hFINGThread, SVR_EXIT_WAIT);
///
// Close FINGER Thread
[xmail] Re: @Davide - compliments and suggestions.
Hi! On Wed, 10 Nov 2004, Henri van riel wrote: Would it be possible to enhance the log function with compress and delete options? I mean, I can rotate the log every so many hours with the -Mr option but would it be possible to compress the old logfile to a .bz2 for example and to let XMail delete logs older than so many days? I have to delete my logs manually now and I sometimes forget... I use a cron job that gzips and archive old logs. Better compression, w/out bloating XMail code. Also remeber that XMail is multiplatform, and that my rule of thumb is zero-dependecies on external packages. I like the option to retrieve email from an external pop server but I would like the options to set the timer per pop server. There are basically 2 ways you can do that: by setting an interval that controls after how many checks (-Yi) a pop server is sync'ed or by setting the -Yi per poplink. The reason is, I have several pop3 accounts but I only need to check 1 or 2 every half hour or so. The others I need to check maybe once a day at most. This would require a statefull implementation of the thing. I am not sure it is worth doing it, according to the number of requests. Being able to redirect incoming mail is great but why is there a REDIRECT.TAB and a LREDIRECT.TAB? Can't these two tab files be merged into one tab file and add an option that defines which email address is shown to the recipient? (by the way, I don't see the difference between REDIRECT and LREDIRECT...). ?? They differ from the way XMail advertise itself to the redirection target server. One final question about threading. I have to set the number of smtp, pop and smail threads to start on the command line. Would it be possible to enhance that so that XMail can spawn off new threads whenever necessary? For example, I have -SX 3 on my server but for some reason 5 smtp servers try to connect at the same time to deliver mail. Now, 2 of them will get `-Err server too busy, retry later` or something like that. The same goes for the other servers (pop3, smail). If XMail could start a new thread (up to a certain limit of threads, say 20 or so) that problem wouldn't exist. Off course XMail should also be capable of terminating old threads to free up memory. The number of SMAIL threads are fixed at startup time, while SMTP and POP3 are only upperly bounded. There's no fixed pool of threads and they get created for every connection (up to the limit of 1000 IIRC). Oh, one more thing... ;) Is it possible to disable smtp or pop all together? Can I simply add -SX 0 to disable smtp and -PX0 to disable pop3 or is it a bit more complicated than that? Bind them to localhost. - 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]
