Hi Kay:
It looks like you're running XMail on Windows, right? When XMail is run as a
service on Windows, the command-line parameters (including -SI, etc.) are
kept in a registry key - see the "NT/Win2K" section of the main XMail README
file ( http://xmailserver.org/Readme.html#nt_win2k ) for mor
Have another look at the manual...
The -SI and every other parameter goes in the cmd line entry in the registry
(separate entry).
http://www.xmailserver.org/Readme.html#nt_win2k (step 7)
Dave
- Original Message -
From: "Kay Seljeseth" <[EMAIL PROTECTED]>
To:
Sent: Monday, June 26, 2006
... some more ..
d) Added completely fresh/new IP address to server after xmail restart.
Immediately XMail Server is available for telnet on port 25 also for this
new IP address.
Xmail server appears to start listening on any IP as soon as it is created
on the server.
-Original Message--
Thanks, but I'm experiencing problems when playing around with this option.
I have tried to set it in different ways:
a) Remove and add service with SI option:
xmail --remove
xmail --install -SI x.x.x.204
Afterwards XMail does answer on both the primary (204) and my spam
designated IP address (
Yes, the sending IP address is the server's primary address... but that
shouldn't matter in his case.
--John
Rob Arends wrote:
> I seem to remember that the -SI option was for incoming, but the sending
> from xmail was still on the Servers primary Address - Please check the List
> Archive for
You can get at them with the "frozlist" and "frozgetlog" ctrl commands...
Rob Arends wrote:
> Thanks Soenke.
>
> I'm just confirming my understanding then:
> The /slog/ logs are removed once successful transmission is completed - and
> then logged to smail.
> Upon failure they are removed also,
I seem to remember that the -SI option was for incoming, but the sending
from xmail was still on the Servers primary Address - Please check the List
Archive for verification, in case I'm wrong.
Rob :-)
_
Note To Self: Remember to put something wi
Thanks Soenke.
I'm just confirming my understanding then:
The /slog/ logs are removed once successful transmission is completed - and
then logged to smail.
Upon failure they are removed also, if "RemoveSpoolErrors" is set to "1",
otherwise they are left behind.
Does this require manual cleanup?
Use the -SI command line option.
From: http://www.xmailserver.org/Readme.html#command_line
-SI ip[:port]
Bind server to the specified ip address and (optional) port (can be
multiple).
--John
Kay Seljeseth wrote:
> We have been running XP and Xmail Server without any problems for a long
We have been running XP and Xmail Server without any problems for a long
time, but would now also like to run a spam filter (SpamFighter) on the same
machine. Hence, we would like to use two IP addresses where the SpamFighter
gets incoming mail first on one public SMTP IP address, checking the emai
> Thus, the 30 day expiry time is excessive overkill, and possibly a 14
> day window might be better under normal operating conditions. In this
I usually use 36 days. There is lot of newsletters and digests and so
on, which are issued with monthly periodicity.
--
Michal A. Valasek | Chief Softwa
Thank you for the answer Davide.
That basically means that as long as a source address sends e-mail, the
entry will immediately pass through the greylisting.
I know, I know, I should have read the man pages, but wasn't anywhere
near a machine to access the server... :)
Thus, the 30 day expiry t
12 matches
Mail list logo
