Issue Details (XML | Word | Printable)

Key: JAMES-580
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Vincenzo Gianferrari Pini
Reporter: Vincenzo Gianferrari Pini
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JAMES Server

NPE is issued when receiving a "read receipt" from MS Outlook, and <checkValidSenderDomain> is set to true

Created: 27/Jul/06 03:34 PM   Updated: 21/Nov/07 08:31 AM
Return to search
Component/s: SMTPServer
Affects Version/s: 2.3.0
Fix Version/s: 2.3.0

Time Tracking:
Not Specified

Resolution Date: 28/Jul/06 02:09 PM


 Description  « Hide
A NPE is issued when receiving a "read receipt" from MS Outlook (not Outlook express nor Thunderbird), and <checkValidSenderDomain> is set to true and the sender IP address is not in <authorizedAddresses>:

27/07/06 17:17:00 ERROR smtpserver: Exception opening socket: null
java.lang.NullPointerException
at org.apache.james.smtpserver.MailCmdHandler.doMAIL(MailCmdHandler.java:210)
at org.apache.james.smtpserver.MailCmdHandler.onCommand(MailCmdHandler.java:83)
at org.apache.james.smtpserver.SMTPHandler.handleConnection(SMTPHandler.java:391)
at org.apache.james.util.connection.ServerConnection$ClientConnectionRunner.run(ServerConnection.java:422)
at org.apache.excalibur.thread.impl.ExecutableRunnable.execute(ExecutableRunnable.java:55)
at org.apache.excalibur.thread.impl.WorkerThread.run(WorkerThread.java:116)


 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Vincenzo Gianferrari Pini added a comment - 27/Jul/06 03:37 PM
I don't know if this error was also in 2.2. In such case IMO we should consider it a blocker :-( , because after an upgrade from 2.2.0 to 2.3.0 the systems having <checkValidSenderDomain> set to true would lose messages.

Vincenzo Gianferrari Pini added a comment - 28/Jul/06 02:05 PM
The fix was ok for 3.0 in trunk, but not for 2.3.0.

Vincenzo Gianferrari Pini added a comment - 28/Jul/06 02:09 PM
The fix now is checking senderAddress != null, instead of sender != null.

Danny Angus added a comment - 21/Nov/07 08:31 AM
Closing issue fixed in released version.