Configuring Jackpot
Jackpot is configured by making changes to the file jackpot.properties.
This file comprises comments (lines starting with "#"), and a collection
of name/value pairs, of the form:
Name=value
The meanings of the various parameters in this file are as follows.
General
These are settings you should at least look at before running Jackpot for real.
- ServerHeader
- This entry specifies the value retuned
in the "Server: " HTTP header returned by Jackpot. By default, Jackpot
claims to be "Jackpot 1.0.0".
- SmtpAddress
- Specifies, in dotted-quad notation (nnn.nnn.nnn.nnn)
the IP-address(es) on which Jackpot is to serve SMTP. If this entry is missing, then
if the host is multi-homed, Jackpot will serve SMTP on all the host's
IP-addresses. Tp specify a list of addresses, separate them with commas.
- HtmlPath
- Specifies a virtual path for HTML. This defaults to "html", i.e.
the home-page is http://:/html/.
If you set this value to "xyzzy", then HTTP requests must be of the
form http://:/xyzzy/something.html, otherwise they
will elicit a 404. This is supposed to make it easier for Jackpot to be
stealthy.
- RoleAccountAlias
- Specifies an email address to which all mail to
postmaster@[jackpot] or abuse@[jackpot] is to be forwarded. Such mail could
be sent as a consequence of, for example, an invalid bounce, or the inadvertent
emission of spam.
- AdminUser
- Name of the user who is allowed to administer Jackpot via the
web-admin interface. Default is admin.
- AdminUser
- Password of the user who is allowed to administer Jackpot via the
web-admin interface. Default is admin. CHANGE THIS!
Customisations
These are things you may want to change, to make your Jackpot look different
to visitors from other Jackpots. This will make it harder for spammers to
fingerprint Jackpot.
- VrfyResponse
- Specifies the response the SMTP service gives when
presented with a VRFY command. VRFY asks the mail-server to confirm that
the address given in it's parameter is a user of this mailhost; Jackpot,
of course, has no users.
- ExpnResponse
- Specifies the response the SMTP service gives when
presented with a EXPN command. EXPN asks the mail-server to expand a
mailing-list. Jackpot has no mailing lists.
- TurnResponse
- Specifies the response the SMTP service gives when
presented with a TURN command. The TURN command is used to reverse the
direction of the SMTP dialogue; your visitor is requesting that you become
the client, and that you become the server, so that you can relay
messages via him.
- DataResponse
- Specifies the response the SMTP service gives when
presented with a DATA command.
- BadSequenceResponse
- Specifies the 503 message.
- DiskFullResponse
- This entry specifies the response to a
connection request when no threads are available in the SMTP threadpool.
- AddReceivedHeader
- If this is set to Yes, then Jackpot will pre-pend
a Received: header to any message it relays. Otherwise your Jackpot server
will appear to be a blind relay.
- ShowReceivedHost
- If this is set to Yes, then Jackpot will perform a DNS
lookup on the visitor's IP-address, and include this in the Received: header it
pre-pends to relayed messages (if, indeed, it does add a Received: header at all).
Some mailservers appear to be configured to simply report the domain given
by the visitor in the HELO command as being authentic, without checking it; if the
Received: header also excludes the visitor's IP-address, then the header is useless
for tracking spam, and from the spammer's point of view, the relay is as good as
blind.
- MTADescription
- This entry specifies the name of the mail server,
as output in the banner.
- ServerName
- specifies the name of this machine, used
in the response to HELO/EHLO, in any Received: header added by Jackpot to
relayed messages, and to construct a postmaster address. Defaults to the name
of your localhost (best setting).
-
System Parameters
This section contains stuff related to logging and so on -
general system control.
- logfile
- Easy. This gives the name of the system log file.
- MaxQueueSize
- This entry is to protect your server. Messages accepted
by the SMTP service are placed in a queue in memory, to await relaying or
binning. If this queue is allowed to grow without limit, then a spam-run
could exhaust the memory allocated to your Java Virtual Machine, and cause
Jackpot to stop responding to requests. If you configure Jackpot as a tarpit,
then this should never happen - as soon as a spam-run comes in, Jackpot's
response to HELO dialogues should skow to a crawl, so that messages are
accepted much more slowly than they can be relayed.
- MaxRecipients
- The maximum number of recipients a message may have
before it is classified as spam. This refers to the number of recipients
identified in the HELO dialogue, not the recipients specified in the To:,
and Cc: headers, which are basically junk - these headers are of no
significance, and in spam email they are always forged.
- TarpitDelay
- Extra time taken to respond to commands when in a spamrun.
This is applied to every line entered in a HELO dioalog; the default is 1s. This
is enough to make a HTML message from Outlook Express take almost a minute to enter.
- MinSpamInterval
- The amount of time considered 'too soon' for the
purposes of determining if a message should be relayed. Messages submitted via SMTP
may also be subject to tarpitting if they arrive 'too soon'. Default is 20s.
- MaxThreads
- This entry controls the sizes of the two ThreadPools.
Jackpot will politely decline protocol activities on ports 25 and [HTTP-port]
once the number of free threads falls below 5.
- NameServer
- Specifies the nameserver to use. If not provided, uses the system default.
Doesn't seem to affect anything much.
- LogServers
- Specifies the (comma-delimited)names:ports of the HTTP servers to be updated
when SMTP traffic is captured. Defaults to using the LocalHost on port 8080.
- IdentForAbuse
- Determines whether an Ident service should be offered to abuse.net
(speeds up enquiries).
FileLogging, ConsoleLogging- These two settings specify what kinds of message get output to
the system logs. These are bit-sets, the bit values are as follows:
SMTP = 1;
HTTP = 2;
RELAY = 4;
STATUS = 8;
PROXY = 16;
ENVE = 32;
CONFIG = 64;
DEBUG = 128;
- MaxStoragePerSource
- Specifies a limit on the number of spams that should be stored for
each spam-source.
Timeouts
This section specifies timouts for socket-connections used for
several different purposes. Times are in milliseconds.
- ProxyCheckTimeout
- How long to wait for proxy-test results.
- SBLLookupTimeout
- How long to wait for SBL lookups.
- AbuseLookupTimeout
- How long to wait for abuse.net lookups.
Startup
- StartupHttp
- Whether to start the HTTP service.
- StartupSmtp
- Whether to start the SMTP service.
- StartupRelay
- Whether to start with relaying enabled.
- StartupTarpit
- Whether to start with tarpitting enabled.
- StartupStorage
- Whether to start with POSTing to storage enabled.
- StartupStorage
- Whether to start up with the. bogus SOCKSV4 Proxy Server running.
Miscellaneous
The last section contains stuff you are unlikely to need to
change, at least for now.
- SmtpPort
- Port for serving SMTP; if you change this, you'll probably be the only
person who ever sends mail to your Jackpot server.
- MaxQueueSize
- This entry restricts the maximum number of messages that can be
queued at any one time. The queue is in memory, and Spammy will have to send relay-requests on
multiple connections simultaneously to have a chance of filling it up.
Back