Dolan, This is 90% likely nothing to do with DNS, although you are right to figure on DNS as a common culprit.
I have been reading everywhere for information regarding this, but have run into a wall....
Ouch. <snip>
250 2.6.0 Message received
That all looks good. What that means is that James has consumed the message and you now need to find out, not why it isn't available via POP, but where the Sam Hill it has gone. Look in <james>/var/mail/error and <james>/var/mail/spam and check the spoolmanager and mailet logs. Increase logging by editing <james>/SAR-INF/environment.xml and making some or all of the loggers DEBUG instead of INFO. Then you might get enough info to understand what's going wrong, or to let us spot it for you. d. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]