Actually, no extra information was gleaned from turning on DEBUG level
logging (see previous email):
DEBUG spoolmanager.transport: Checking Mail1197375942572-106 with
[EMAIL PROTECTED]
DEBUG spoolmanager.transport: Checking Mail1197375942572-106 with
[EMAIL PROTECTED]
2.3.1 simply doesn't find the user as local anymore. Do you know what
would cause that?
DK
On Dec 11, 2007, at 1:41 AM, Jerry M wrote:
Not sure if you've done all of this yet... but these steps have
often helped me determine precisely what is happening with a message:
1) set the log levels to DEBUG for everything in environment.xml. 2)
Run an email through the flow
3) GREP the log dir for the target email address (you might want to
clear the log dir prior to starting this). You should see a log
entry displayed for that email.
4) determine the message number (a long string of numbers, possibly
with a dash in the middle) for the email from the previous GREP
output log message
5) GREP the log dir for that message number
Your resulting output from the GREP should be a trace of every match/
mailet the message went through. This should tell you precisely
where your emails are going awry.
If the output doesn't make sense, post the GREP output here. I'm
sure one of us can interpret it.
Dain Kaplan wrote:
Also, anent the logs, I checked earlier and it seems like the mails
enter the system normally. Plenty of messages for successfully
spooling mails. The POP requests also register without error. The
mails that get spooled successfully just don't make it to the inbox
that gets POPed. The email addresses are of course the same, and
switching to 2.2.0 returns to correct behavior (upon transmission
of additional emails). Is there something specific I should look
for that would signify an error indicative of this problem?
DK
On Dec 11, 2007, at 12:35 AM, Stefano Bagnara wrote:
Either you send your config.xml or you tell us exactly what
changes you
did to config.xml in 2.2.0 and in 2.3.1.
Furthermore, looking at the apps/james/logs folder may help.
Stefano
Dain Kaplan ha scritto:
After an upgrade to the stable release of 2.3.1, following the
included
upgrade instructions, James starts up fine. Incoming mail also
seems to
be processed as well (after looking in the logs and watching the
spool
DB table).
However, mails simply don't show up in the user's inbox via POP3.
Authentication works fine through mail client (OS X Mail), and
incredibly old mail (somehow still on the server) was
downloaded. But
no new mail arrives (despite no errors in the logs).
Running: Java 1.5_013. Also with increased memory usage (settings
copied from 2.2.0 installation). A few "swap out of space"
errors have
been received as well.
After starting backup 2.2.0, any mails sent while 2.3.1 was
running are
lost (perhaps in the var folder? though the database is the storage
engine...)
Where is the mail going? Perhaps a setting of some kind is
missing?
The configuration really hasn't been messed with too much, so I
am at a
loss as to how to proceed.
Perhaps related to thread: "James can send but cannot receive
email...???"
DK
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
