> Vincenzo Gianferrari Pini wrote: > > What is the meaning of a mail object having getSender() return null? > > As I read the code, this is what is supposed to happen in the case of > a message which was sent with: > > MAIL FROM: <> > > As I recall, the RFC says this is the way of sending administrative > error reports which should never generate replies (as this might > create an infinite loop). > This latter shoud be the case of
Return-Path: <> Anyhow, I'm fixing a bug in AbstractRedirect that was causing a NPE trying to build a new TO using the sender, that it turned out null in some cases (spam or virus). I'm going to do the following in such case: use the sender, if null use the return path, if null set it to <>. But I'm asking myself too on what James does if it tries to send a message to an empty list of recipients, because for example NotifySender processes a mail that has a null sender as said above. The original NotifySender was doing this way, and the new one too. Should I change it to something like the following: use the sender, if null use the return path, if null leave it null (or throw an exception)? Any suggestion? Vincenzo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
