So, your problem is that RecipientIsLocal is not matching your
recipient.
RecipientIsLocal checks that the domain is in servername and that the
username is a valid james user. HostIsLocal also checks the servername
so the problem must be in the "local part check" of the
RecipientIsLocal.
Sending an email to the account running 2.2.0 the mail shows up in the
inbox, using POP3 to check it. After launching 2.3.1 the same user
can still check mail (via POP3), but no mail is downloaded.
Are you using the assembly.xml from 2.3.1 or did you change
something in
there?
This file has not been touched.
Can you check in your "users" table in the db that the recipients
are there?
The user is there. Which makes sense, since they can POP without
error. Switching back to 2.2.0, after sending another email, the user
receives it fine.
I also see a problem in your mailstore XML configuration: please
take a
look at the james original config.xml <mailstore> item. You should
copy
it as-is in your configuration file. The way you mixed the
objectstorage
inside the mailstore is not ok.
Ah, perhaps this is it. In the upgrade document, it only says:
Step 2.5 : Move the objectstore
Move the objectstore config into the mailstore config.
But perhaps I should have been more careful. The <objectstore>
element is no longer present in the default configuration file, I take
it it no longer exists at all, and the repositories within should be
moved, not the element itself? The upgrade instructions are slightly
ambiguous, perhaps the WIKI should be updated to more emphatically
explain the migration of these repositories?
DK
On Dec 11, 2007, at 11:21 PM, Stefano Bagnara wrote:
Dain Kaplan ha scritto:
In my previous email i put "many servernames here", but not in the
last
email. There are 100+ servernames listed, i removed them to
protect the
privacy of my clients. You will also find XXX.XXX.XXX.XXX where IPs
should be, please assume those are actual IPs as well, and not Xs.
Sorry for the the ambiguity.
So, your problem is that RecipientIsLocal is not matching your
recipient.
RecipientIsLocal checks that the domain is in servername and that the
username is a valid james user. HostIsLocal also checks the servername
so the problem must be in the "local part check" of the
RecipientIsLocal.
Are you using the assembly.xml from 2.3.1 or did you change
something in
there?
Can you check in your "users" table in the db that the recipients
are there?
I also see a problem in your mailstore XML configuration: please
take a
look at the james original config.xml <mailstore> item. You should
copy
it as-is in your configuration file. The way you mixed the
objectstorage
inside the mailstore is not ok.
Stefano
DK
On Dec 11, 2007, at 10:32 PM, Stefano Bagnara wrote:
Dain Kaplan ha scritto:
Below is my config.xml file; spaces and comments removed to save
space.
Somethings (like <newsgroups>) seem unneeded altogether but...
Good call on turning debug level logging on. I'll do that, but
with
basic logging, it looks like the mail is winding up the the
deadletter
table:
James.Mailet: ToRepository: Storing mail Mail1197288970050-1728
in
db://maildb/deadletter/address-error
Which corresponds to the lines in the config file:
<mailet match="RecipientIsLocal" class="LocalDelivery"/>
<mailet match="HostIsLocal" class="ToProcessor">
<processor> local-address-error </processor>
<notice>550 - Requested action not taken: no such user
here</notice>
</mailet>
So it would seem switching versions (from 2.2.0 to 2.3.1) has
stopped
the LocalDelivery mailet from properly finding users' mailboxes.
Any
ideas?
[...]
<servernames autodetect="false" autodetectIP="true">
<servername>localhost</servername>
</servernames>
You have autodetect="false" and only "localhost" declared as local
servername. So only [EMAIL PROTECTED] will be considered a local
recipient.
You have to add your domain name to servernames.
I'm almost sure this worked the same way in 2.2.0.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
