I am running James on a WinXP box serving three domains with MySQL stores. Postmaster was and is setup on the localhost. I notify postmaster on errors, spam, relays, etc... I recently upgraded to 2.2.0 and James began having problems with those notifications. The message that generates the notification is handled correctly, i.e. to deadletter; and any Bounce direction is handled correctly. The "NotifyPostmaster" generates the message and injects it in to the root processor. The "PostmasterAlias" mailet then reworks the address to <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] as configured Then in the "SenderInFakeDomain" the DNSServer is not capable of resolving the domain localhost I use my ISP DNS as I am on a DynamicIP and have not set up a caching DNS on my server box This causes the notification to be serviced by the SPAM processor which loops through the above again and again and again I upgraded to 2.2.1-RC1 but experienced the same problem This seems to be related to the JIRA issue #302 opened by Steve Berwin. Steve indicates on 3 Jan that the fix is in 2.1.1-RC1 (? / Typo). Again, I have upgraded to 2.2.1-RC1and the problem persists. I don't know if this is a bug or not. I did not have the problem under 2.1.1 with a similar configuration. It does appear to be with the DNSServer not resolving localhost. As a work around, I added a HostIs=localhost matcher to the root before the SenderInFakeDomain matcher. I send the matched mail to a custom processor that I intend to use to adjust the postmaster address based on the domain that generated the error. Regardless, it works now. Any ideas... Regards, Tony Freeman TEAMXL 678.344.2305 Office 509.693.2598 eFax [EMAIL PROTECTED]
