You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Clive Tonge <cv...@sympatico.ca> on 2003/08/04 08:09:27 UTC
James Isn't Picking Up Messages. SMTP error?
Hello,
I am still relatively new to Linux / Unix but, I have spent years
beating up DOS and Windows Machines. I have just spent two days trying
to get James to run correctly. I have read the documentation and reread
it. I have reviewed the FAQ. I have search the Archives and read many of
the posts from the past couple of months.
My problem is that I can't get James to receive email from outside of
the server ( tonge.ca ) that it is installed on. Please read on, I have
tried quite hard to fix this.
I do have the MX record correctly pointing to the server.
James actual will answer if I telnet into the server on port 25.
James will accept mail from the server, to the server and deliver it to
the correct account.
Mail can be picked up from a remote machine over the internet. i.e. pop
is working
I have added smtp:all to my hosts.allow file
dslreport.com reports everything in order except that mail is not being
accepted from the server. There are a couple of warnings but that seems
to be a function of the dynamic DNS service that I am using.
Now some background:
James version 2.1.3
Java version 1.4.1_02
MySQL version 4.0.11a-gamma
OS - Linux version Mandrake 9.1
Also working on the server -
Apache 2.0.44
Tomcat 2.1.4
James is setup to use MySQL database mail with tables for users and for
spooling, both tables have been setup by James, and I think as a
repository for mail. (maybe not there isn't a table).
Do you have any ideas that may cause this?
It may be unrelated but I am confused by the section of config.xml
dealing with the holding of mail. All of which are uncommented. 1 puts
mail into the file system. 2 puts the headers into a table on the
database and a link to the body of the message on the file system. 3
puts the mail in a table (tables) in the database.
I will be happy to provide more information if you need it.
Thanks,
Clive.
Soon to be reached at clive@tonge.ca :-) ... I hope.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Isn't Picking Up Messages. SMTP error?
Posted by Clive Tonge <cv...@sympatico.ca>.
The following is the smtpserver log. for the same period as the
spoolmanager log that I just sent.
Note: arts-council.ca is virtually hosted at tonge.ca.
I notice that it is using the IP address of the card itself not the IP
address that is asighned to it by ADSL /PPP. Would that have any bearing
on the problem?
Clive
05/08/03 02:48:50 INFO smtpserver: SMTP Service uses default thread group.
05/08/03 02:48:50 INFO smtpserver: SMTP Service is running on: tonge.ca
05/08/03 02:48:50 INFO smtpserver: SMTP Service handler hello name is:
tonge.ca
05/08/03 02:48:50 INFO smtpserver: SMTP Service handler connection
timeout is: 360000
05/08/03 02:48:50 INFO smtpserver: This SMTP server does not require
authentication.
05/08/03 02:48:50 INFO smtpserver: No maximum message size is enforced
for this server.
05/08/03 02:48:50 INFO smtpserver: The idle timeout will be reset every
20480 bytes.
05/08/03 02:48:50 DEBUG smtpserver: SMTP Service init...
05/08/03 02:48:50 DEBUG smtpserver: SMTP Service ...init end
05/08/03 02:48:50 INFO smtpserver: SMTP Service started plain:25
05/08/03 02:48:50 DEBUG smtpserver: Using an unbounded pool for SMTP
handlers.
05/08/03 02:49:36 DEBUG smtpserver: Retrieving a
org.apache.james.smtpserver.SMTPHandler from the pool
05/08/03 02:49:36 DEBUG smtpserver: Getting SMTPHandler from pool.
05/08/03 02:49:36 INFO smtpserver: Connection from tonge.ca (10.0.0.10)
05/08/03 02:49:36 DEBUG smtpserver: Sent: 220 tonge.ca SMTP Server
(JAMES SMTP Server 2.1.3) ready Tue, 5 Aug 2003 02:49:36 -0400 (EDT)
05/08/03 02:49:36 DEBUG smtpserver: Calling start()
05/08/03 02:49:36 DEBUG smtpserver: Watchdog default Worker #14 has time
to sleep 359998
05/08/03 02:49:36 DEBUG smtpserver: Command received: EHLO tonge.ca
05/08/03 02:49:36 DEBUG smtpserver: Sent: 250 tonge.ca Hello tonge.ca
(tonge.ca [10.0.0.10])
05/08/03 02:49:36 DEBUG smtpserver: Calling reset() default Worker #14
05/08/03 02:49:36 DEBUG smtpserver: Command received: MAIL
FROM:<cl...@tonge.ca>
05/08/03 02:49:36 DEBUG smtpserver: Sent: 250 Sender <cl...@tonge.ca> OK
05/08/03 02:49:36 DEBUG smtpserver: Calling reset() default Worker #14
05/08/03 02:49:36 DEBUG smtpserver: Command received: RCPT
TO:<cv...@arts-council.ca>
05/08/03 02:49:36 DEBUG smtpserver: Sent: 250 Recipient
<cv...@arts-council.ca> OK
05/08/03 02:49:36 DEBUG smtpserver: Calling reset() default Worker #14
05/08/03 02:49:36 DEBUG smtpserver: Command received: DATA
05/08/03 02:49:36 DEBUG smtpserver: Sent: 354 Ok Send data ending with
<CRLF>.<CRLF>
05/08/03 02:49:37 DEBUG smtpserver: Successfully spooled mail
)Mail1060066176801-0 from clive@tonge.ca for [cv@arts-council.ca]
05/08/03 02:49:37 DEBUG smtpserver: Sent: 250 Message received
05/08/03 02:49:37 DEBUG smtpserver: Calling reset() default Worker #14
05/08/03 02:49:37 DEBUG smtpserver: Command received: RSET
05/08/03 02:49:37 DEBUG smtpserver: Sent: 250 OK
05/08/03 02:49:37 DEBUG smtpserver: Calling reset() default Worker #14
05/08/03 02:49:37 DEBUG smtpserver: Command received: QUIT
05/08/03 02:49:37 DEBUG smtpserver: Sent: 221 tonge.ca Service closing
transmission channel
05/08/03 02:49:37 DEBUG smtpserver: Calling stop() default Worker #14
05/08/03 02:49:37 DEBUG smtpserver: Closing socket.
05/08/03 02:49:37 DEBUG smtpserver: Calling disposeWatchdog() default
Worker #14
05/08/03 02:49:37 DEBUG smtpserver: Watchdog default Worker #14 is
exiting run().
05/08/03 02:49:37 DEBUG smtpserver: Returning SMTPHandler to pool.
05/08/03 02:49:37 DEBUG smtpserver: Returning a
org.apache.james.smtpserver.SMTPHandler to the pool
05/08/03 02:50:23 DEBUG smtpserver: Retrieving a
org.apache.james.smtpserver.SMTPHandler from the pool
05/08/03 02:50:23 DEBUG smtpserver: Getting SMTPHandler from pool.
05/08/03 02:50:23 INFO smtpserver: Connection from tonge.ca (10.0.0.10)
05/08/03 02:50:23 DEBUG smtpserver: Sent: 220 tonge.ca SMTP Server
(JAMES SMTP Server 2.1.3) ready Tue, 5 Aug 2003 02:50:23 -0400 (EDT)
05/08/03 02:50:23 DEBUG smtpserver: Calling start()
05/08/03 02:50:23 DEBUG smtpserver: Watchdog default Worker #22 has time
to sleep 359994
05/08/03 02:50:23 DEBUG smtpserver: Command received: EHLO tonge.ca
05/08/03 02:50:23 DEBUG smtpserver: Sent: 250 tonge.ca Hello tonge.ca
(tonge.ca [10.0.0.10])
05/08/03 02:50:23 DEBUG smtpserver: Calling reset() default Worker #22
05/08/03 02:50:23 DEBUG smtpserver: Command received: MAIL
FROM:<cl...@tonge.ca>
05/08/03 02:50:23 DEBUG smtpserver: Sent: 250 Sender <cl...@tonge.ca> OK
05/08/03 02:50:23 DEBUG smtpserver: Calling reset() default Worker #22
05/08/03 02:50:23 DEBUG smtpserver: Command received: RCPT
TO:<cl...@tonge.ca>
05/08/03 02:50:23 DEBUG smtpserver: Sent: 250 Recipient <cl...@tonge.ca> OK
05/08/03 02:50:23 DEBUG smtpserver: Calling reset() default Worker #22
05/08/03 02:50:23 DEBUG smtpserver: Command received: DATA
05/08/03 02:50:23 DEBUG smtpserver: Sent: 354 Ok Send data ending with
<CRLF>.<CRLF>
05/08/03 02:50:23 DEBUG smtpserver: Successfully spooled mail
)Mail1060066223962-1 from clive@tonge.ca for [clive@tonge.ca]
05/08/03 02:50:23 DEBUG smtpserver: Sent: 250 Message received
05/08/03 02:50:23 DEBUG smtpserver: Calling reset() default Worker #22
05/08/03 02:50:23 DEBUG smtpserver: Command received: RSET
05/08/03 02:50:23 DEBUG smtpserver: Sent: 250 OK
05/08/03 02:50:23 DEBUG smtpserver: Calling reset() default Worker #22
05/08/03 02:50:23 DEBUG smtpserver: Command received: QUIT
05/08/03 02:50:24 DEBUG smtpserver: Sent: 221 tonge.ca Service closing
transmission channel
05/08/03 02:50:24 DEBUG smtpserver: Calling stop() default Worker #22
05/08/03 02:50:24 DEBUG smtpserver: Closing socket.
05/08/03 02:50:24 DEBUG smtpserver: Calling disposeWatchdog() default
Worker #22
05/08/03 02:50:24 DEBUG smtpserver: Watchdog default Worker #22 is
exiting run().
05/08/03 02:50:24 DEBUG smtpserver: Returning SMTPHandler to pool.
05/08/03 02:50:24 DEBUG smtpserver: Returning a
org.apache.james.smtpserver.SMTPHandler to the pool
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Isn't Picking Up Messages. SMTP error?
Posted by Clive Tonge <cv...@sympatico.ca>.
The following is the smtpserver log. for the same period as the
spoolmanger log that I just sent.
Note: arts-council.ca is virtually hosted at tonge.ca.
I notice that it is using the IP address of the card itself not the IP
address that is asighned to it by ADSL /PPP. Would that have any bearing
on the problem?
Clive
05/08/03 02:48:50 INFO smtpserver: SMTP Service uses default thread group.
05/08/03 02:48:50 INFO smtpserver: SMTP Service is running on: tonge.ca
05/08/03 02:48:50 INFO smtpserver: SMTP Service handler hello name is:
tonge.ca
05/08/03 02:48:50 INFO smtpserver: SMTP Service handler connection
timeout is: 360000
05/08/03 02:48:50 INFO smtpserver: This SMTP server does not require
authentication.
05/08/03 02:48:50 INFO smtpserver: No maximum message size is enforced
for this server.
05/08/03 02:48:50 INFO smtpserver: The idle timeout will be reset every
20480 bytes.
05/08/03 02:48:50 DEBUG smtpserver: SMTP Service init...
05/08/03 02:48:50 DEBUG smtpserver: SMTP Service ...init end
05/08/03 02:48:50 INFO smtpserver: SMTP Service started plain:25
05/08/03 02:48:50 DEBUG smtpserver: Using an unbounded pool for SMTP
handlers.
05/08/03 02:49:36 DEBUG smtpserver: Retrieving a
org.apache.james.smtpserver.SMTPHandler from the pool
05/08/03 02:49:36 DEBUG smtpserver: Getting SMTPHandler from pool.
05/08/03 02:49:36 INFO smtpserver: Connection from tonge.ca (10.0.0.10)
05/08/03 02:49:36 DEBUG smtpserver: Sent: 220 tonge.ca SMTP Server
(JAMES SMTP Server 2.1.3) ready Tue, 5 Aug 2003 02:49:36 -0400 (EDT)
05/08/03 02:49:36 DEBUG smtpserver: Calling start()
05/08/03 02:49:36 DEBUG smtpserver: Watchdog default Worker #14 has time
to sleep 359998
05/08/03 02:49:36 DEBUG smtpserver: Command received: EHLO tonge.ca
05/08/03 02:49:36 DEBUG smtpserver: Sent: 250 tonge.ca Hello tonge.ca
(tonge.ca [10.0.0.10])
05/08/03 02:49:36 DEBUG smtpserver: Calling reset() default Worker #14
05/08/03 02:49:36 DEBUG smtpserver: Command received: MAIL
FROM:<cl...@tonge.ca>
05/08/03 02:49:36 DEBUG smtpserver: Sent: 250 Sender <cl...@tonge.ca> OK
05/08/03 02:49:36 DEBUG smtpserver: Calling reset() default Worker #14
05/08/03 02:49:36 DEBUG smtpserver: Command received: RCPT
TO:<cv...@arts-council.ca>
05/08/03 02:49:36 DEBUG smtpserver: Sent: 250 Recipient
<cv...@arts-council.ca> OK
05/08/03 02:49:36 DEBUG smtpserver: Calling reset() default Worker #14
05/08/03 02:49:36 DEBUG smtpserver: Command received: DATA
05/08/03 02:49:36 DEBUG smtpserver: Sent: 354 Ok Send data ending with
<CRLF>.<CRLF>
05/08/03 02:49:37 DEBUG smtpserver: Successfully spooled mail
)Mail1060066176801-0 from clive@tonge.ca for [cv@arts-council.ca]
05/08/03 02:49:37 DEBUG smtpserver: Sent: 250 Message received
05/08/03 02:49:37 DEBUG smtpserver: Calling reset() default Worker #14
05/08/03 02:49:37 DEBUG smtpserver: Command received: RSET
05/08/03 02:49:37 DEBUG smtpserver: Sent: 250 OK
05/08/03 02:49:37 DEBUG smtpserver: Calling reset() default Worker #14
05/08/03 02:49:37 DEBUG smtpserver: Command received: QUIT
05/08/03 02:49:37 DEBUG smtpserver: Sent: 221 tonge.ca Service closing
transmission channel
05/08/03 02:49:37 DEBUG smtpserver: Calling stop() default Worker #14
05/08/03 02:49:37 DEBUG smtpserver: Closing socket.
05/08/03 02:49:37 DEBUG smtpserver: Calling disposeWatchdog() default
Worker #14
05/08/03 02:49:37 DEBUG smtpserver: Watchdog default Worker #14 is
exiting run().
05/08/03 02:49:37 DEBUG smtpserver: Returning SMTPHandler to pool.
05/08/03 02:49:37 DEBUG smtpserver: Returning a
org.apache.james.smtpserver.SMTPHandler to the pool
05/08/03 02:50:23 DEBUG smtpserver: Retrieving a
org.apache.james.smtpserver.SMTPHandler from the pool
05/08/03 02:50:23 DEBUG smtpserver: Getting SMTPHandler from pool.
05/08/03 02:50:23 INFO smtpserver: Connection from tonge.ca (10.0.0.10)
05/08/03 02:50:23 DEBUG smtpserver: Sent: 220 tonge.ca SMTP Server
(JAMES SMTP Server 2.1.3) ready Tue, 5 Aug 2003 02:50:23 -0400 (EDT)
05/08/03 02:50:23 DEBUG smtpserver: Calling start()
05/08/03 02:50:23 DEBUG smtpserver: Watchdog default Worker #22 has time
to sleep 359994
05/08/03 02:50:23 DEBUG smtpserver: Command received: EHLO tonge.ca
05/08/03 02:50:23 DEBUG smtpserver: Sent: 250 tonge.ca Hello tonge.ca
(tonge.ca [10.0.0.10])
05/08/03 02:50:23 DEBUG smtpserver: Calling reset() default Worker #22
05/08/03 02:50:23 DEBUG smtpserver: Command received: MAIL
FROM:<cl...@tonge.ca>
05/08/03 02:50:23 DEBUG smtpserver: Sent: 250 Sender <cl...@tonge.ca> OK
05/08/03 02:50:23 DEBUG smtpserver: Calling reset() default Worker #22
05/08/03 02:50:23 DEBUG smtpserver: Command received: RCPT
TO:<cl...@tonge.ca>
05/08/03 02:50:23 DEBUG smtpserver: Sent: 250 Recipient <cl...@tonge.ca> OK
05/08/03 02:50:23 DEBUG smtpserver: Calling reset() default Worker #22
05/08/03 02:50:23 DEBUG smtpserver: Command received: DATA
05/08/03 02:50:23 DEBUG smtpserver: Sent: 354 Ok Send data ending with
<CRLF>.<CRLF>
05/08/03 02:50:23 DEBUG smtpserver: Successfully spooled mail
)Mail1060066223962-1 from clive@tonge.ca for [clive@tonge.ca]
05/08/03 02:50:23 DEBUG smtpserver: Sent: 250 Message received
05/08/03 02:50:23 DEBUG smtpserver: Calling reset() default Worker #22
05/08/03 02:50:23 DEBUG smtpserver: Command received: RSET
05/08/03 02:50:23 DEBUG smtpserver: Sent: 250 OK
05/08/03 02:50:23 DEBUG smtpserver: Calling reset() default Worker #22
05/08/03 02:50:23 DEBUG smtpserver: Command received: QUIT
05/08/03 02:50:24 DEBUG smtpserver: Sent: 221 tonge.ca Service closing
transmission channel
05/08/03 02:50:24 DEBUG smtpserver: Calling stop() default Worker #22
05/08/03 02:50:24 DEBUG smtpserver: Closing socket.
05/08/03 02:50:24 DEBUG smtpserver: Calling disposeWatchdog() default
Worker #22
05/08/03 02:50:24 DEBUG smtpserver: Watchdog default Worker #22 is
exiting run().
05/08/03 02:50:24 DEBUG smtpserver: Returning SMTPHandler to pool.
05/08/03 02:50:24 DEBUG smtpserver: Returning a
org.apache.james.smtpserver.SMTPHandler to the pool
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Isn't Picking Up Messages. SMTP error? Solved.
Posted by Clive Tonge <cv...@sympatico.ca>.
Thanks Noel for all of your help in particular.
I have finally solved the problem with not being able to receive email
through James SMTP.
Port 25 is turned off by my ISP.
I could telnet into port 25 because I was an internal part of the domain.
I have bypassed that by having all of my email sent to a temporary email
address and having fetchpop pick it up.
It is working like a charm.
I could have also had my DNS Service use a port other than 25.
Thanks,
Clive
Noel J. Bergman wrote:
>>There only one address clive@tonge.ca
>>
>>
>
>I can't telnet into your smtp port from the outside, so unless it is
>temporarily down, you've got another problem.
>
> --- Noel
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>For additional commands, e-mail: server-user-help@james.apache.org
>
>
>
>
RE: James Isn't Picking Up Messages. SMTP error?
Posted by "Noel J. Bergman" <no...@devtech.com>.
> There only one address clive@tonge.ca
I can't telnet into your smtp port from the outside, so unless it is
temporarily down, you've got another problem.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Isn't Picking Up Messages. SMTP error?
Posted by Clive Tonge <cv...@sympatico.ca>.
There only one address
clive@tonge.ca
Thanks Noel
Noel J. Bergman wrote:
>>While I can get the server (James ) to accept an email if I telnet into
>>it and do it manually. I can't get the server (james) to accept the
>>emails from any other source. So I can't get emails that are sent to me.
>>
>>
>
>What is an address at that server?
>
> --- Noel
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>For additional commands, e-mail: server-user-help@james.apache.org
>
>
>
>
RE: James Isn't Picking Up Messages. SMTP error?
Posted by "Noel J. Bergman" <no...@devtech.com>.
> While I can get the server (James ) to accept an email if I telnet into
> it and do it manually. I can't get the server (james) to accept the
> emails from any other source. So I can't get emails that are sent to me.
What is an address at that server?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Isn't Picking Up Messages. SMTP error?
Posted by Clive Tonge <cv...@sympatico.ca>.
Sorry I am not being clear.
While I can get the server (James ) to accept an email if I telnet into
it and do it manually. I can't get the server (james) to accept the
emails from any other source. So I can't get emails that are sent to me.
Everything else seems to working perfectly.
Clive
Noel J. Bergman wrote:
>>I can telnet to the server and pass James a message manually. Below is
>>the log of the session to send an email. And it worked too. :-)
>>
>>
>
>Good, then what isn't?
>
>
>
>>I noticed that it did require the information to be in <>.
>>
>>
>
>Correct. That is part of the RFC.
>
> --- Noel
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>For additional commands, e-mail: server-user-help@james.apache.org
>
>
>
>
RE: James Isn't Picking Up Messages. SMTP error?
Posted by "Noel J. Bergman" <no...@devtech.com>.
> I can telnet to the server and pass James a message manually. Below is
> the log of the session to send an email. And it worked too. :-)
Good, then what isn't?
> I noticed that it did require the information to be in <>.
Correct. That is part of the RFC.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Isn't Picking Up Messages. SMTP error?
Posted by Clive Tonge <cv...@sympatico.ca>.
Hi all,
It has been a week and a half of trying everything I can think of to get
James to pick up, or accept the mail.
I am finally making a bit of progress. Maybe from this information you
can help me fix whatever is wrong.
I can telnet to the server and pass James a message manually. Below is
the log of the session to send an email. And it worked too. :-)
I noticed that it did require the information to be in <>.
It is so close to working that I really don't won't to quit. but nothing
seems to fix this.
I would really appreciate some help.
Thanks,
Clive
helo tonge.ca
250 tonge.ca Hello tonge.ca (London-HSE-ppp3544152.sympatico.ca
[65.93.19.99])
mail from:<cv...@sympatico.ca>
250 Sender <cv...@sympatico.ca> OK
rcpt to:<cl...@tonge.ca>
250 Recipient <cl...@tonge.ca> OK
data
354 Ok Send data ending with <CRLF>.<CRLF>
subject: Test test test!
This is the body of the message.
With a space above it and below the subject.
.
250 Message received
quit
221 tonge.ca Service closing transmission channel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: James Isn't Picking Up Messages. SMTP error?
Posted by "Noel J. Bergman" <no...@devtech.com>.
> I didn't make a copy of the file before I made any changes to it.
> Is there an easy way to get a fresh copy of config.xml?
Yes. Delete the one you have, and James will extract a fresh copy when it
starts again.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Isn't Picking Up Messages. SMTP error?
Posted by Clive Tonge <cv...@sympatico.ca>.
Thanks for the help Noel.
I think that I may have made a change in the config.xml that is the
cause of this problem. I will uninstall James then reinstall it on the
weekend if I need to.
I am ashamed that I didn't make a copy of the file before I made any
changes to it. Is there an easy way to get a fresh copy of config.xml?
or can I convince one of the experts on the maillist to have a look at
it? Maybe someone can see my error right off? See below for a copy of
config.xml.
Regards,
Clive Tonge
Noel J. Bergman wrote:
>That means whomever the mail was for wasn't recognized as having a mail box,
>the domain was local, and the message was sent to the error processor.
>
> --- Noel
>
>
<?xml version="1.0"?>
<!-- Configuration file for the Apache Jakarta James server -->
<!-- This file contains important settings that control the behaviour -->
<!-- of all of the services and repositories. -->
<!-- README! -->
<!-- This configuration file is designed to run without alteration for
simple tests. -->
<!-- It assumes you have a DNS server on localhost and assigns a root
password of root. -->
<!-- In case the defaults do not suit you, the items you are most likely
to need to change -->
<!-- are preceded by a CHECKME! or CONFIRM? comment in the left margin. -->
<!-- For production use you will probably need to make more extensive
changes, see -->
<!-- http://james.apache.org/documentation_2_1.html -->
<!-- $Revision: 1.40.2.5 $ Committed on $Date: 2003/05/12 21:10:24 $ by:
$Author: noel $ -->
<config>
<James>
<!-- CHECKME! -->
<!-- This is the postmaster email address for this mail server. -->
<!-- Set this to the appropriate email address for error reports -->
<!-- If this is set to a non-local email address, the mail server -->
<!-- will still function, but will generate a warning on startup. -->
<postmaster>clive@localhost</postmaster>
<!-- servernames identifies the DNS namespace served by this
instance of James. -->
<!-- These servernames are used for both matcher/mailet processing
and SMTP auth -->
<!-- to determine when a mail is intended for local delivery. -->
<!-- -->
<!-- If autodetect is TRUE, James wil attempt to discover its own
host name AND -->
<!-- use any explicitly specified servernames. -->
<!-- If autodetect is FALSE, James will use only the specified
servernames. -->
<!-- -->
<!-- If autodetectIP is not FALSE, James will also allow add the
IP address for each servername. -->
<!-- The automatic IP detection is to support RFC 2821, Sec 4.1.3,
address literals. -->
<!-- -->
<!-- To override autodetected server names simply add explicit
servername elements. -->
<!-- In most cases this will be necessary. -->
<!-- By default, the servername 'localhost' is specified. This can
be removed, if required. -->
<!-- -->
<!-- Warning: If you are using fetchpop it is important to include
the -->
<!-- fetched domains in the server name list to prevent
looping. -->
<servernames autodetect="true" autodetectIP="true">
<!-- CONFIRM? -->
<servername>localhost</servername>
<servername>tonge.ca</servername>
<servername>domain2.ca</servername>
<servername>domain3.com</servername>
<servername>domain4.ca</servername>
<servername>domain5.ca</servername>
</servernames>
<!-- Set whether user names are case sensitive or case insensitive -->
<!-- Set whether to enable local aliases -->
<!-- Set whether to enable forwarding -->
<usernames ignoreCase="true" enableAliases="true"
enableForwarding="true"/>
<!-- The inbox repository is the location for users inboxes -->
<!-- Default setting: file based repository - enter path ( use
"file:///" for absolute) -->
<!--
<inboxRepository>
<repository destinationURL="file://var/mail/inboxes/" type="MAIL"/>
</inboxRepository>
-->
<!-- Alternative inbox repository definition for DB use. -->
<!-- The format for the destinationURL is
"db://<data-source>/<table>" -->
<!-- <data-source> is the datasource name set up in the
database-connections block, below -->
<!-- <table> is the name of the table to store user inboxes in -->
<!-- The user name is used as <repositoryName> for this repository
config. -->
<inboxRepository>
<repository destinationURL="db://maildb/inbox/" type="MAIL"/>
</inboxRepository>
<!-- Alternative inbox repository definition for DB use. -->
<!-- Stores message body in file system, rest in database -->
<!--
<inboxRepository>
<repository destinationURL="dbfile://maildb/inbox/" type="MAIL"/>
</inboxRepository>
-->
</James>
<!-- Fetch pop block, fetches mail from POP3 servers and inserts it
into the incoming spool -->
<!-- Warning: It is important to prevent mail from looping by setting
the -->
<!-- fetched domains in the <servernames> section of the <James>
block -->
<!-- above. This block is disabled by
default. -->
<fetchpop enabled="false">
<!-- You can have as many fetch tasks as you want, but each must
have a -->
<!-- unique name by which it identified -->
<fetch name="mydomain.com">
<!-- Host name or IP address -->
<host>mail.mydomain.com</host>
<!-- Account login username -->
<user>username</user>
<!-- Account login password -->
<password>pass</password>
<!-- How frequently this account is checked - in
milliseconds. 600000 is every ten minutes -->
<interval>600000</interval>
</fetch>
</fetchpop>
<!-- The James Spool Manager block -->
<!-- -->
<!-- This block is responsible for processing messages on the spool. -->
<spoolmanager>
<!-- Number of spool threads -->
<threads> 5 </threads>
<!-- Set the Java packages from which to load mailets and matchers -->
<mailetpackages>
<mailetpackage>org.apache.james.transport.mailets</mailetpackage>
</mailetpackages>
<matcherpackages>
<matcherpackage>org.apache.james.transport.matchers</matcherpackage>
</matcherpackages>
<!-- The root processor is a required processor - James routes all
mail on the spool -->
<!-- through this processor first. -->
<!-- -->
<!-- This configuration is a sample configuration for the root
processor. -->
<processor name="root">
<!-- Checks that the email Sender is associated with a valid
domain. -->
<!-- Useful for detecting and eliminating spam. -->
<!-- For this block to function, the spam processor must be
configured. -->
<!--
<mailet match="SenderInFakeDomain" class="ToProcessor">
<processor> spam </processor>
</mailet>
-->
<!-- Important check to avoid looping -->
<mailet match="RelayLimit=30" class="Null"/>
<!-- White List:
If you use block lists, you will probably want to check
for known permitted senders. This is particularly true
if you use more aggressive block lists, such as SPEWS,
that are prone to block entire subnets without regard
for non-spamming senders.
-->
<!-- specific known senders -->
<!--
<mailet match="SenderIs=goodboy@goodhost"
class="ToProcessor">
<processor> transport </processor>
</mailet>
-->
<!-- People on this list agree to pay a penalty if they send
spam -->
<mailet match="InSpammerBlacklist=query.bondedsender.org"
class="ToProcessor">
<processor> transport </processor>
</mailet>
<!-- E-mail legally required not to be spam (see:
http://www.habeas.com) -->
<!--
<mailet match="HasHabeasWarrantMark" class="ToProcessor">
<processor> transport </processor>
</mailet>
-->
<!-- End of White List -->
<!-- Check for delivery from a known spam server -->
<!-- This set of matchers/mailets redirect all emails from
known -->
<!-- black holes, open relays, and spam servers to the spam
processor -->
<!-- For this set to function properly, the spam processor must
be configured. -->
<mailet match="InSpammerBlacklist=dnsbl.njabl.org"
class="ToProcessor">
<processor> spam </processor>
<notice>550 Requested action not taken: rejected - see
http://njabl.org/ </notice>
</mailet>
<mailet match="InSpammerBlacklist=relays.ordb.org"
class="ToProcessor">
<processor> spam </processor>
<notice>550 Requested action not taken: rejected - see
http://www.ordb.org/ </notice>
</mailet>
<!-- Sample matching to kill a message (send to Null) -->
<!--
<mailet match="RecipientIs=badboy@badhost" class="Null"/>
-->
<!-- Send remaining mails to the transport processor for either
local or remote delivery -->
<mailet match="All" class="ToProcessor">
<processor> transport </processor>
</mailet>
</processor>
<!-- The error processor is required. James may internally set
emails to the -->
<!-- error state. The error processor is generally invoked when
there is an -->
<!-- unexpected error either in the mailet chain or internal to
James. -->
<!-- -->
<!-- By default configuration all email that generates an error in
placed in -->
<!-- an error repository. -->
<processor name="error">
<!-- Logs any messages to the repository specified -->
<mailet match="All" class="ToRepository">
<repositoryPath> file://var/mail/error/</repositoryPath>
<!-- An alternative database repository example follows. -->
<!--
<repositoryPath> db://maildb/deadletter/error </repositoryPath>
-->
<passThrough> true </passThrough>
</mailet>
<!-- If you want to notify the sender their message generated
an error, uncomment this -->
<!--
<mailet match="All" class="NotifySender"/>
-->
<!-- If you want to notify the postmaster that a message
generated an error, uncomment this -->
<!--
<mailet match="All" class="NotifyPostmaster"/>
-->
</processor>
<!-- Processor CONFIGURATION SAMPLE: transport is a sample custom
processor for local or -->
<!-- remote delivery -->
<processor name="transport">
<!-- Is the recipient is for a local account, deliver it
locally -->
<mailet match="RecipientIsLocal" class="LocalDelivery"/>
<!-- If the host is handled by this server and it did not get -->
<!-- locally delivered, this is an invalid recipient -->
<mailet match="HostIsLocal" class="ToProcessor">
<processor>error</processor>
</mailet>
<!-- CHECKME! -->
<!-- This is an anti-relay matcher/mailet combination -->
<!-- -->
<!-- Emails sent from servers not in the network list are -->
<!-- rejected as spam. This is one method of preventing your -->
<!-- server from being used as an open relay. Make sure you
understand -->
<!-- how to prevent your server from becoming an open relay
before -->
<!-- changing this configuration. -->
<!-- -->
<!-- This matcher/mailet combination must come after local
delivery has -->
<!-- been performed. Otherwise local users will not be able to
receive -->
<!-- email from senders not in this remote address list. -->
<!-- -->
<!-- If you are using this matcher/mailet you will probably
want to -->
<!-- update the configuration to include your own
network/addresses. The -->
<!-- matcher can be configured with a comma separated list of
IP addresses -->
<!-- wildcarded IP subnets, and wildcarded hostname subnets. -->
<!-- e.g. "RemoteAddrNotInNetwork=127.0.0.1, abc.de.*,
192.168.0.*" -->
<!-- -->
<!-- If you are using SMTP authentication then you can (and
generally -->
<!-- should) disable this matcher/mailet pair. -->
<mailet match="RemoteAddrNotInNetwork=127.0.0.1"
class="ToProcessor">
<processor> spam </processor>
</mailet>
<!-- Attempt remote delivery using the specified repository for
the spool, -->
<!-- using delay time to retry delivery and the maximum number
of retries -->
<mailet match="All" class="RemoteDelivery">
<!--
<outgoing> file://var/mail/outgoing/ </outgoing> -->
<!-- alternative database repository example below -->
<outgoing> db://maildb/spool/outgoing </outgoing>
<!-- Number of milliseconds between delivery attempts -->
<delayTime> 21600000 </delayTime>
<!-- Number of failed attempts before returning to the
sender -->
<maxRetries> 5 </maxRetries>
<!-- The number of threads that should be trying to deliver
outgoing messages -->
<deliveryThreads> 1 </deliveryThreads>
<!-- A single mail server to deliver all outgoing messages. -->
<!-- This is useful if this server is a backup or failover
machine, -->
<!-- or if you want all messages to be routed through a
particular mail server, -->
<!-- regardless of the email addresses specified in the
message -->
<!-- -->
<!-- The gateway element specifies the gateway SMTP server
name. -->
<!-- If your gateway mail server is listening on a port
other than 25, -->
<!-- you can set James to connect to it on that port using
the gatewayPort -->
<!-- element. -->
<!--
<gateway> otherserver.mydomain.com </gateway>
<gatewayPort>25</gatewayPort>
-->
</mailet>
</processor>
<!-- Processor CONFIGURATION SAMPLE: spam is a sample custom
processor for handling -->
<!-- spam. -->
<!-- You can either log these, bounce these, or just ignore them. -->
<processor name="spam">
<!-- To destroy all messages, uncomment this matcher/mailet
configuration -->
<!--
<mailet match="All" class="Null"/>
-->
<!-- To notify the sender their message was marked as spam,
uncomment this matcher/mailet configuration -->
<!--
<mailet match="All" class="NotifySender"/>
-->
<!-- To notify the postmaster that a message was marked as
spam, uncomment this matcher/mailet configuration -->
<!--
<mailet match="All" class="NotifyPostmaster"/>
-->
<!-- To log the message to a repository, this matcher/mailet
configuration should be uncommented. -->
<!-- This is the default configuration. -->
<mailet match="All" class="ToRepository">
<!--
<repositoryPath>file://var/mail/spam/</repositoryPath>
-->
<!-- Changing the repositoryPath, as in this commented out
example, will -->
<!-- cause the mails to be stored in a database repository. -->
<!-- Please note that only one repositoryPath element can be
present for the mailet -->
<!-- configuration. -->
<repositoryPath> db://maildb/deadletter/spam </repositoryPath>
</mailet>
</processor>
</spoolmanager>
<!-- DNS Server Block -->
<!-- -->
<!-- Specifies DNS Server information for use by various components
inside -->
<!-- James. -->
<!-- -->
<!-- Information includes a list of DNS Servers to be used by James.
These are -->
<!-- specified by the server elements, each of which is a child
element of the -->
<!-- servers element. Each server element is the IP address of a
single DNS server. -->
<!-- The servers element can have multiple server children. -->
<dnsserver>
<servers>
<!-- CONFIRM? -->
<!--Enter ip address of your DNS server, one IP address per
server -->
<!-- element. The default configuration assumes a DNS server on
the localhost. -->
<server>206.47.244.102</server>
<server>206.47.244.89</server>
</servers>
<authoritative>false</authoritative>
</dnsserver>
<remotemanager enabled="true">
<port>4555</port>
<!-- Uncomment this if you want to bind to a specific inetaddress -->
<!--
<bind> </bind>
-->
<!-- Uncomment this if you want to use TLS (SSL) on this port -->
<!--
<useTLS>true</useTLS>
-->
<handler>
<!-- This is the name used by the server to identify itself in
the RemoteManager -->
<!-- protocol. If autodetect is TRUE, the server will discover
its -->
<!-- own host name and use that in the protocol. If discovery
fails, -->
<!-- the value of 'localhost' is used. If autodetect is FALSE,
James -->
<!-- will use the specified value. -->
<helloName autodetect="true">myMailServer</helloName>
<administrator_accounts>
<!-- CHECKME! -->
<!-- Change the default login/password. -->
<account login="user" password="password"/>
</administrator_accounts>
<connectiontimeout> 60000 </connectiontimeout>
</handler>
</remotemanager>
<!-- The POP3 server is enabled by default -->
<!-- Disabling blocks will stop them from listening, -->
<!-- but does not free as many resources as removing them would -->
<pop3server enabled="true">
<!-- port 995 is the well-known/IANA registered port for POP3S ie
over SSL/TLS -->
<!-- port 110 is the well-known/IANA registered port for Standard
POP3 -->
<port>110</port>
<!-- Uncomment this if you want to bind to a specific inetaddress -->
<!--
<bind> </bind>
-->
<!-- Uncomment this if you want to use TLS (SSL) on this port -->
<!--
<useTLS>true</useTLS>
-->
<handler>
<!-- This is the name used by the server to identify itself in
the POP3 -->
<!-- protocol. If autodetect is TRUE, the server will discover
its -->
<!-- own host name and use that in the protocol. If discovery
fails, -->
<!-- the value of 'localhost' is used. If autodetect is FALSE,
James -->
<!-- will use the specified value. -->
<helloName autodetect="true">myMailServer</helloName>
<connectiontimeout>120000</connectiontimeout>
</handler>
</pop3server>
<!-- The SMTP server is enabled by default -->
<!-- Disabling blocks will stop them from listening, -->
<!-- but does not free as many resources as removing them would -->
<smtpserver enabled="true">
<!-- port 25 is the well-known/IANA registered port for SMTP -->
<port>25</port>
<!-- Uncomment this if you want to bind to a specific inetaddress -->
<!--
<bind> </bind>
-->
<!-- Uncomment this if you want to use TLS (SSL) on this port -->
<!--
<useTLS>true</useTLS>
-->
<handler>
<!-- This is the name used by the server to identify itself in
the SMTP -->
<!-- protocol. If autodetect is TRUE, the server will discover
its -->
<!-- own host name and use that in the protocol. If discovery
fails, -->
<!-- the value of 'localhost' is used. If autodetect is FALSE,
James -->
<!-- will use the specified value. -->
<helloName autodetect="false">myMailServer</helloName>
<connectiontimeout>360000</connectiontimeout>
<!-- Uncomment this if you want to require SMTP
authentication. -->
<!--
<authRequired>true</authRequired>
-->
<!-- Uncomment this if you want to verify sender addresses,
ensuring that -->
<!-- the sender address matches the user who has
authenticated. -->
<!-- This prevents a user of your mail server from acting as
someone else -->
<!--
<verifyIdentity>true</verifyIdentity>
-->
<!-- This sets the maximum allowed message size (in kilobytes)
for this -->
<!-- SMTP service. If unspecified, the value defaults to 0,
which means no limit. -->
<maxmessagesize>0</maxmessagesize>
</handler>
</smtpserver>
<!-- The NNTP server is enabled by default -->
<!-- Disabling blocks will stop them from listening, -->
<!-- but does not free as many resources as removing them would -->
<!-- NNTP-specific: if you disable the NNTP Server, you should also
set the nntp-repository's
threadCount to 0, otherwise there will be threads active and
polling -->
<nntpserver enabled="false">
<!-- THE NNTP PROTOCOL IS EXPERIMENTAL AND NOT AS WELL TESTED AS SMTP
AND POP3 IN THIS RELEASE.
The James project recommends that you check the James web site
for updates to the NNTP
service. -->
<!-- port 563 is the well-known/IANA registered port for NNTP over
SSL/TLS -->
<!-- port 119 is the well-known/IANA registered port for Standard
NNTP -->
<port>119</port>
<!-- Uncomment this if you want to bind to a specific inetaddress -->
<!--
<bind> </bind>
-->
<!-- Uncomment this if you want to use TLS (SSL) on this port -->
<!--
<useTLS>true</useTLS>
-->
<handler>
<!-- This is the name used by the server to identify itself in
the NNTP -->
<!-- protocol. If autodetect is TRUE, the server will discover
its -->
<!-- own host name and use that in the protocol. If discovery
fails, -->
<!-- the value of 'localhost' is used. If autodetect is FALSE,
James -->
<!-- will use the specified value. -->
<helloName autodetect="true">myMailServer</helloName>
<connectiontimeout>120000</connectiontimeout>
<!-- Set the authRequired value to true to enable
authenticated NNTP -->
<authRequired>false</authRequired>
</handler>
</nntpserver>
<nntp-repository>
<!-- If this is set to true, posting will be disallowed. -->
<readOnly>false</readOnly>
<rootPath>file://var/nntp/groups</rootPath>
<tempPath>file://var/nntp/temp</tempPath>
<articleIDPath>file://var/nntp/articleid</articleIDPath>
<articleIDDomainSuffix>news.james.apache.org</articleIDDomainSuffix>
<!-- The news groups hosted in this NNTP repository. -->
<newsgroups>
<newsgroup>org.apache.james.dev</newsgroup>
<newsgroup>org.apache.james.user</newsgroup>
<newsgroup>org.apache.avalon.dev</newsgroup>
<newsgroup>org.apache.avalon.user</newsgroup>
</newsgroups>
<spool>
<configuration>
<spoolPath>file://var/nntp/spool</spoolPath>
<!-- The number of threads that process spooler related
tasks. -->
<threadCount>1</threadCount>
<!-- The spool thread(s) should idle for some time, if it
has nothing to do -->
<threadIdleTime>60000</threadIdleTime>
</configuration>
</spool>
</nntp-repository>
<!-- The Mailstore block -->
<mailstore>
<repositories>
<!-- File based repositories. These repositories store all
message data -->
<!-- in the file system. -->
<!-- CLosing File Repository ... Just to keep things tidy.
<repository
class="org.apache.james.mailrepository.AvalonMailRepository">
<protocols>
<protocol>file</protocol>
</protocols>
<types>
<type>MAIL</type>
</types>
</repository>
<repository
class="org.apache.james.mailrepository.AvalonSpoolRepository">
<protocols>
<protocol>file</protocol>
</protocols>
<types>
<type>SPOOL</type>
</types>
</repository>
-->
<!-- JDBC based repositories. These repositories store all
message data -->
<!-- in the database. -->
<repository
class="org.apache.james.mailrepository.JDBCMailRepository">
<protocols>
<protocol>db</protocol>
</protocols>
<types>
<type>MAIL</type>
</types>
<config>
<sqlFile>file://conf/sqlResources.xml</sqlFile>
</config>
</repository>
<repository
class="org.apache.james.mailrepository.JDBCSpoolRepository">
<protocols>
<protocol>db</protocol>
</protocols>
<types>
<type>SPOOL</type>
</types>
<config>
<sqlFile>file://conf/sqlResources.xml</sqlFile>
</config>
</repository>
<!-- These repositories store message delivery and headers in
the DB, and the body to the filesystem -->
<!-- To close of the file-database storage repository. to keep
things tidy
<repository class="org.apache.james.mailrepository.JDBCMailRepository">
<protocols>
<protocol>dbfile</protocol>
</protocols>
<types>
<type>MAIL</type>
</types>
<config>
<sqlFile>file://conf/sqlResources.xml</sqlFile>
<filestore>file://var/dbmail</filestore>
</config>
</repository>
<repository
class="org.apache.james.mailrepository.JDBCSpoolRepository">
<protocols>
<protocol>dbfile</protocol>
</protocols>
<types>
<type>SPOOL</type>
</types>
<config>
<sqlFile>file://conf/sqlResources.xml</sqlFile>
<filestore>file://var/dbmail</filestore>
</config>
</repository>
</repositories>
-->
<!-- Spool repository configuration -->
<!-- The spool repository is the location where incoming mails are
temporarily stored -->
<!-- before being processed. -->
<!--
<spoolRepository>
<repository destinationURL="file://var/mail/spool/" type="SPOOL"/>
</spoolRepository>
-->
<!-- Alternative spool repository definition for JDBC use -->
<spoolRepository>
<repository destinationURL="db://maildb/spool/spool" type="SPOOL"/>
</spoolRepository>
<!-- Alternative spool repository definition for JDBC use -->
<!-- Stores message body in file system, rest in database -->
<!--
<spoolRepository>
<repository destinationURL="dbfile://maildb/spool/spool"
type="SPOOL"/>
</spoolRepository>
</mailstore>
-->
<!-- The User Storage block -->
<users-store>
<!-- Configure User Repositories here. -->
<!-- -->
<!-- User repositories are required for the following purposes: -->
<!-- - storing James user information, including forwards,
aliases, -->
<!-- and authentication data. -->
<!-- - holding lists of users for the listserv mailet -->
<!-- Currently, two different storage options are available: -->
<!-- - file-based storage using Java serialization -->
<!-- - database-backed storage -->
<!-- (Use of database or file-system is defined on a
"per-repository" basis) -->
<!-- -->
<!-- Note: One user repository is required for James: -->
<!-- LocalUsers - the users for whom you are providing POP3,
NNTP, or SMTP service -->
<!-- -->
<!-- Other repositories may be used by matchers or mailets. -->
<!-- Default: File-based user repositories Use these
configurations to store user info in the filesystem -->
<!-- The LocalUsers repository, for storing James' User info. -->
<!--<repository name="LocalUsers"
class="org.apache.james.userrepository.UsersFileRepository">
<destination URL="file://var/users/"/>
</repository>
-->
<!-- Database backed user repositories -->
<!-- -->
<!-- Use these configurations to store user info in a database. -->
<!-- Note: The <data-source> element must refer to a connection
configured -->
<!-- in the <database-connections> configuration section. -->
<!-- The LocalUsers repository, for storing James' User info. -->
<repository name="LocalUsers"
class="org.apache.james.userrepository.JamesUsersJdbcRepository"
destinationURL="db://maildb/users">
<sqlFile>file://conf/sqlResources.xml</sqlFile>
</repository>
</users-store>
<!-- The database-connections block -->
<database-connections>
<!-- These connections are referred to by name elsewhere in the
config file -->
<!-- CHECKME! -->
<!-- To allow James to use a database you must configure the
database connection here. -->
<!-- If you are not using a database, you can leave this section
unchanged. -->
<!-- These connections are referred to by name in URLs elsewhere
in the config file. -->
<data-sources>
<!-- James is distributed with a built in relevant copy of the
mm.mysql JDBC -->
<!-- driver. No additional driver is needed for mysql. Read
the mm.mysql LGPL -->
<!-- license at
apps\james\SAR-INF\lib\mm.mysql.LICENCE -->
<!-- JDBC driver .jar libraries for other RDBMS can be placed
in ~james/lib/ -->
<!-- Example, connecting to a MySQL database called "mail" on
localhost-->
<!-- -->
<!-- The max value is the maximum number of concurrent
connections James will -->
<!-- open to this database-->
<!-- If you see "SQLException: Giving up... no connections
available." in your -->
<!-- log files or bounced mail you should increase this value -->
<data-source name="maildb"
class="org.apache.james.util.mordred.JdbcDataSource">
<driver>org.gjt.mm.mysql.Driver</driver>
<dburl>jdbc:mysql://127.0.0.1/mail?autoReconnect=true</dburl>
<user>user</user>
<password>password</password>
<max>30</max>
</data-source>
<!-- Example, connecting to a Microsoft MSSQL database called
"mail" on localhost-->
<!-- -->
<!-- The max value is the maximum number of concurrent
connections James will -->
<!-- open to this database-->
<!-- If you see "SQLException: Giving up... no connections
available." in your -->
<!-- log files or bounced mail you should increase this value -->
<!--
<data-source name="maildb"
class="org.apache.james.util.mordred.JdbcDataSource">
<driver>com.inet.tds.TdsDriver</driver>
<dburl>jdbc:inetdae7:127.0.0.1?database=James</dburl>
<user>sa_james</user>
<password>blahblah</password>
<max>20</max>
</data-source>
-->
</data-sources>
</database-connections>
<!-- Configuration for Cornerstone Services -->
<!-- -->
<!-- For a simple configuration, nothing beneath this line should
require -->
<!-- alteration. -->
<!-- -->
<!-- You will need to adjust the Socket Manager service configuration
if you want -->
<!-- to enable secure sockets (TLS) for any James
service. -->
<!-- -->
<!-- Complex or high volume configurations may require changes to the
parameters -->
<!-- in this section. Please read the James and Avalon documentation
before -->
<!-- attempting to adjust this section. -->
<!-- -->
<!-- The Object Storage block -->
<!-- -->
<!-- Defines file storage details that are used for file-based
repositories. -->
<objectstorage>
<repositories>
<repository
class="org.apache.james.mailrepository.filepair.File_Persistent_Object_Repository">
<protocols>
<protocol>file</protocol>
</protocols>
<types>
<type>OBJECT</type>
</types>
<models>
<model>SYNCHRONOUS</model>
<model>ASYNCHRONOUS</model>
<model>CACHE</model>
</models>
</repository>
<repository
class="org.apache.james.mailrepository.filepair.File_Persistent_Stream_Repository">
<protocols>
<protocol>file</protocol>
</protocols>
<types>
<type>STREAM</type>
</types>
<models>
<model>SYNCHRONOUS</model>
<model>ASYNCHRONOUS</model>
<model>CACHE</model>
</models>
</repository>
</repositories>
</objectstorage>
<!-- The Connection Manager block -->
<!-- -->
<!-- The idle-timeout is the number of milliseconds that it will take
for idle -->
<!-- client connections managed by this connection manager to be
marked at timed out. -->
<!-- If no value is specified, the value defaults to 5 minutes,
300000 milliseconds -->
<!-- A value of 0 means that client sockets will not timeout. -->
<!-- -->
<!-- The max-connections parameter specifies the default maximum
number of client -->
<!-- connections that this connection manager will allow per managed
server socket. -->
<!-- This value can be overridden by each individual service. -->
<!-- If no value is specified, the value defaults to 30. -->
<!-- A value of 0 means that there is no limit imposed by the
connection manager, although -->
<!-- resource limitations imposed by other components (i.e. max # of
threads) may -->
<!-- serve to limit the number of open connections. -->
<!-- -->
<connections>
<idle-timeout>300000</idle-timeout>
<max-connections>30</max-connections>
</connections>
<!-- The Socket Manager block -->
<!-- -->
<!-- The server-sockets element has a number of factory sub-elements. -->
<!-- Each of the factory elements has a name and class attribute -->
<!-- The name attribute for each factory element must be unique. -->
<!-- The class attribute is the name of a class that implements the -->
<!-- interface
org.apache.avalon.cornerstone.services.ServerSocketFactory -->
<!-- Specific factory elements may require some sub-elements. This
is -->
<!-- factory class dependent. -->
<!-- -->
<!-- The client-sockets element has a number of factory sub-elements. -->
<!-- Each of the factory elements has a name and class attribute -->
<!-- The name attribute for each factory element must be unique. -->
<!-- The class attribute is the name of a class that implements the -->
<!-- interface org.apache.avalon.cornerstone.services.SocketFactory -->
<!-- Specific factory elements may require some sub-elements. This
is -->
<!-- factory class dependent. -->
<!-- -->
<sockets>
<server-sockets>
<factory name="plain"
class="org.apache.avalon.cornerstone.blocks.sockets.DefaultServerSocketFactory"/>
<!--
<factory name="ssl"
class="org.apache.avalon.cornerstone.blocks.sockets.TLSServerSocketFactory">
<keystore>
<file>conf/keystore</file>
<password>secret</password>
<type>JKS</type>
<protocol>TLS</protocol>
<algorithm>SunX509</algorithm>
<authenticate-client>false</authenticate-client>
</keystore>
</factory>
-->
</server-sockets>
<client-sockets>
<factory name="plain"
class="org.apache.avalon.cornerstone.blocks.sockets.DefaultSocketFactory"/>
</client-sockets>
</sockets>
<!-- The Thread Manager block -->
<!-- -->
<!-- The thread manager provides thread pools for use throughout the
server. -->
<!-- -->
<!-- A thread pool with the name "default" must be defined in this
thread manager -->
<!-- configuration. -->
<!-- -->
<!-- Each thread pool is defined with a "thread-group" element. -->
<!-- Each of these elements has the following required sub-elements: -->
<!-- name - the name of the thread pool, used by other components
to -->
<!-- lookup the thread pool -->
<!-- priority - the thread priority for threads in the pool. This
is -->
<!-- a value between 0 and 10, with 5 being the normal -->
<!-- priority and 10 being the maximum. -->
<!-- is-daemon - whether the threads in the pool are daemon
threads. -->
<!-- max-threads - the maximum number of threads allowed in the
pool. -->
<!-- min-threads - the minimum number of threads allowed in the
pool. (not implemented) -->
<!-- min-spare-threads - (not implemented) -->
<thread-manager>
<thread-group>
<name>default</name>
<priority>5</priority>
<is-daemon>false</is-daemon>
<max-threads>100</max-threads>
<min-threads>10</min-threads>
<min-spare-threads>10</min-spare-threads>
</thread-group>
</thread-manager>
</config>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: James Isn't Picking Up Messages. SMTP error?
Posted by "Noel J. Bergman" <no...@devtech.com>.
Clive,
What I see in your log is this:
spoolmanager.transport: Checking Mail1060066176801-0 with
org.apache.james.transport.matchers.RecipientIsLocal
spoolmanager.transport: Checking Mail1060066176801-0 with
org.apache.james.transport.matchers.HostIsLocal
spoolmanager.transport: Servicing Mail1060066176801-0 by ToProcessor Mailet
spoolmanager: Result was error
That means whomever the mail was for wasn't recognized as having a mail box,
the domain was local, and the message was sent to the error processor.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Isn't Picking Up Messages. SMTP error?
Posted by Clive Tonge <cv...@sympatico.ca>.
Thanks Noel,
I have turned on the debug for both the spoolmanager and the smtpserver.
I have also shutoff the secondary MX. for the time being.
Noel J. Bergman wrote:
>Did you turn on DEBUG for the spool manager to trace the message flow?
>
>
The following is the Spoolmanager log. I can only see the email sent
from the server itself.
05/08/03 02:48:49 INFO spoolmanager: JamesSpoolManager init...
05/08/03 02:48:49 INFO spoolmanager: Matcher RelayLimit=30 instantiated.
05/08/03 02:48:49 INFO spoolmanager: Mailet Null instantiated.
05/08/03 02:48:49 INFO spoolmanager: Matcher
InSpammerBlacklist=query.bondedsender.org instantiated.
05/08/03 02:48:49 INFO spoolmanager: Mailet ToProcessor instantiated.
05/08/03 02:48:49 INFO spoolmanager: Matcher
InSpammerBlacklist=dnsbl.njabl.org instantiated.
05/08/03 02:48:49 INFO spoolmanager: Mailet ToProcessor instantiated.
05/08/03 02:48:49 INFO spoolmanager: Matcher
InSpammerBlacklist=relays.ordb.org instantiated.
05/08/03 02:48:49 INFO spoolmanager: Mailet ToProcessor instantiated.
05/08/03 02:48:49 INFO spoolmanager: Matcher All instantiated.
05/08/03 02:48:49 INFO spoolmanager: Mailet ToProcessor instantiated.
05/08/03 02:48:49 INFO spoolmanager: Processor root instantiated.
05/08/03 02:48:49 INFO spoolmanager: Matcher All instantiated.
05/08/03 02:48:49 INFO spoolmanager: Mailet ToRepository instantiated.
05/08/03 02:48:49 INFO spoolmanager: Processor error instantiated.
05/08/03 02:48:49 INFO spoolmanager: Matcher RecipientIsLocal instantiated.
05/08/03 02:48:49 INFO spoolmanager: Mailet LocalDelivery instantiated.
05/08/03 02:48:49 INFO spoolmanager: Matcher HostIsLocal instantiated.
05/08/03 02:48:49 INFO spoolmanager: Mailet ToProcessor instantiated.
05/08/03 02:48:49 INFO spoolmanager: Matcher
RemoteAddrNotInNetwork=127.0.0.1 instantiated.
05/08/03 02:48:49 INFO spoolmanager: Mailet ToProcessor instantiated.
05/08/03 02:48:49 INFO spoolmanager: Matcher All instantiated.
05/08/03 02:48:49 INFO spoolmanager: Mailet RemoteDelivery instantiated.
05/08/03 02:48:49 INFO spoolmanager: Processor transport instantiated.
05/08/03 02:48:49 INFO spoolmanager: Matcher All instantiated.
05/08/03 02:48:49 INFO spoolmanager: Mailet ToRepository instantiated.
05/08/03 02:48:49 INFO spoolmanager: Processor spam instantiated.
05/08/03 02:48:49 INFO spoolmanager: Spooler Manager uses 5 Thread(s)
05/08/03 02:48:49 INFO spoolmanager: Run JamesSpoolManager: default
Worker #1
05/08/03 02:48:49 INFO spoolmanager:
Spool=org.apache.james.mailrepository.JDBCSpoolRepository
05/08/03 02:48:50 INFO spoolmanager: Run JamesSpoolManager: default
Worker #2
05/08/03 02:48:50 INFO spoolmanager:
Spool=org.apache.james.mailrepository.JDBCSpoolRepository
05/08/03 02:48:50 INFO spoolmanager: Run JamesSpoolManager: default
Worker #3
05/08/03 02:48:50 INFO spoolmanager:
Spool=org.apache.james.mailrepository.JDBCSpoolRepository
05/08/03 02:48:50 INFO spoolmanager: Run JamesSpoolManager: default
Worker #4
05/08/03 02:48:50 INFO spoolmanager:
Spool=org.apache.james.mailrepository.JDBCSpoolRepository
05/08/03 02:48:50 INFO spoolmanager: Run JamesSpoolManager: default
Worker #5
05/08/03 02:48:50 INFO spoolmanager:
Spool=org.apache.james.mailrepository.JDBCSpoolRepository
05/08/03 02:49:37 DEBUG spoolmanager: ==== Begin processing mail
Mail1060066176801-0====
05/08/03 02:49:37 DEBUG spoolmanager: Processing Mail1060066176801-0
through root
05/08/03 02:49:37 DEBUG spoolmanager.root: Servicing mail:
Mail1060066176801-0
05/08/03 02:49:37 DEBUG spoolmanager.root: Checking Mail1060066176801-0
with org.apache.james.transport.matchers.All@1947496
05/08/03 02:49:37 DEBUG spoolmanager.root: Servicing Mail1060066176801-0
by Postmaster aliasing mailet
05/08/03 02:49:37 DEBUG spoolmanager.root: Checking Mail1060066176801-0
with org.apache.james.transport.matchers.RelayLimit@1724a9d
05/08/03 02:49:37 DEBUG spoolmanager.root: Checking Mail1060066176801-0
with org.apache.james.transport.matchers.InSpammerBlacklist@18166e5
05/08/03 02:49:37 DEBUG spoolmanager.root: Checking Mail1060066176801-0
with org.apache.james.transport.matchers.InSpammerBlacklist@8a548b
05/08/03 02:49:37 DEBUG spoolmanager.root: Checking Mail1060066176801-0
with org.apache.james.transport.matchers.InSpammerBlacklist@1b4a74b
05/08/03 02:49:37 DEBUG spoolmanager.root: Checking Mail1060066176801-0
with org.apache.james.transport.matchers.All@15356d5
05/08/03 02:49:37 DEBUG spoolmanager.root: Servicing Mail1060066176801-0
by ToProcessor Mailet
05/08/03 02:49:37 DEBUG spoolmanager: Processed Mail1060066176801-0
through root
05/08/03 02:49:37 DEBUG spoolmanager: Result was transport
05/08/03 02:49:37 DEBUG spoolmanager: ==== Begin processing mail
Mail1060066176801-0====
05/08/03 02:49:37 DEBUG spoolmanager: Processing Mail1060066176801-0
through transport
05/08/03 02:49:37 DEBUG spoolmanager.transport: Servicing mail:
Mail1060066176801-0
05/08/03 02:49:37 DEBUG spoolmanager.transport: Checking
Mail1060066176801-0 with
org.apache.james.transport.matchers.RecipientIsLocal@e1eea8
05/08/03 02:49:38 DEBUG spoolmanager.transport: Checking
Mail1060066176801-0 with
org.apache.james.transport.matchers.HostIsLocal@fb6354
05/08/03 02:49:38 DEBUG spoolmanager.transport: Servicing
Mail1060066176801-0 by ToProcessor Mailet
05/08/03 02:49:38 DEBUG spoolmanager: Processed Mail1060066176801-0
through transport
05/08/03 02:49:38 DEBUG spoolmanager: Result was error
05/08/03 02:49:38 DEBUG spoolmanager: ==== Begin processing mail
Mail1060066176801-0====
05/08/03 02:49:38 DEBUG spoolmanager: Processing Mail1060066176801-0
through error
05/08/03 02:49:38 DEBUG spoolmanager.error: Servicing mail:
Mail1060066176801-0
05/08/03 02:49:38 DEBUG spoolmanager.error: Checking Mail1060066176801-0
with org.apache.james.transport.matchers.All@ae3364
05/08/03 02:49:38 DEBUG spoolmanager.error: Servicing
Mail1060066176801-0 by ToRepository Mailet
05/08/03 02:49:38 DEBUG spoolmanager.error: Checking Mail1060066176801-0
with org.apache.james.transport.LinearProcessor$1@fced4
05/08/03 02:49:38 DEBUG spoolmanager.error: Servicing
Mail1060066176801-0 by Terminating%Mailet%Name
05/08/03 02:49:38 DEBUG spoolmanager: Processed Mail1060066176801-0
through error
05/08/03 02:49:38 DEBUG spoolmanager: Result was ghost
05/08/03 02:49:38 DEBUG spoolmanager: ==== Removed from spool mail
Mail1060066176801-0====
05/08/03 02:50:24 DEBUG spoolmanager: ==== Begin processing mail
Mail1060066223962-1====
05/08/03 02:50:24 DEBUG spoolmanager: Processing Mail1060066223962-1
through root
05/08/03 02:50:24 DEBUG spoolmanager.root: Servicing mail:
Mail1060066223962-1
05/08/03 02:50:24 DEBUG spoolmanager.root: Checking Mail1060066223962-1
with org.apache.james.transport.matchers.All@1947496
05/08/03 02:50:24 DEBUG spoolmanager.root: Servicing Mail1060066223962-1
by Postmaster aliasing mailet
05/08/03 02:50:24 DEBUG spoolmanager.root: Checking Mail1060066223962-1
with org.apache.james.transport.matchers.RelayLimit@1724a9d
05/08/03 02:50:24 DEBUG spoolmanager.root: Checking Mail1060066223962-1
with org.apache.james.transport.matchers.InSpammerBlacklist@18166e5
05/08/03 02:50:24 DEBUG spoolmanager.root: Checking Mail1060066223962-1
with org.apache.james.transport.matchers.InSpammerBlacklist@8a548b
05/08/03 02:50:24 DEBUG spoolmanager.root: Checking Mail1060066223962-1
with org.apache.james.transport.matchers.InSpammerBlacklist@1b4a74b
05/08/03 02:50:24 DEBUG spoolmanager.root: Checking Mail1060066223962-1
with org.apache.james.transport.matchers.All@15356d5
05/08/03 02:50:24 DEBUG spoolmanager.root: Servicing Mail1060066223962-1
by ToProcessor Mailet
05/08/03 02:50:24 DEBUG spoolmanager: Processed Mail1060066223962-1
through root
05/08/03 02:50:24 DEBUG spoolmanager: Result was transport
05/08/03 02:50:24 DEBUG spoolmanager: ==== Begin processing mail
Mail1060066223962-1====
05/08/03 02:50:24 DEBUG spoolmanager: Processing Mail1060066223962-1
through transport
05/08/03 02:50:24 DEBUG spoolmanager.transport: Servicing mail:
Mail1060066223962-1
05/08/03 02:50:24 DEBUG spoolmanager.transport: Checking
Mail1060066223962-1 with
org.apache.james.transport.matchers.RecipientIsLocal@e1eea8
05/08/03 02:50:24 DEBUG spoolmanager.transport: Servicing
Mail1060066223962-1 by Local Delivery Mailet
05/08/03 02:50:24 DEBUG spoolmanager: Processed Mail1060066223962-1
through transport
05/08/03 02:50:24 DEBUG spoolmanager: Result was ghost
05/08/03 02:50:24 DEBUG spoolmanager: ==== Removed from spool mail
Mail1060066223962-1====
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: James Isn't Picking Up Messages. SMTP error?
Posted by "Noel J. Bergman" <no...@devtech.com>.
> I can't get James to receive email from outside of the server
> ( tonge.ca ) that it is installed on.
> I do have the MX record correctly pointing to the server.
> James actual will answer if I telnet into the server on port 25.
> James will accept mail from the server, to the server and deliver it to
> the correct account.
> I have added smtp:all to my hosts.allow file
Did you turn on DEBUG for the spool manager to trace the message flow?
FWIW, when I look at the DNS, I see:
tonge.ca MX preference = 1, mail exchanger = tonge.ca
tonge.ca MX preference = 5, mail exchanger = smtp.easydns.com
but tonge.ca doesn't respond.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org