Thanks. Since my post I noticed that this was only occurring on one of my MX's and that MX was the one I'd had LDAP aliasing enabled on for testing. After turning LDAP aliasing off the problem went away.
I don't quite understand why/how this would affect it? I'm currently running Courier 0.43.1.20030903. Any suggestions? For now I've got LDAP aliasing turned off but I'm trying to migrate away from using .courier files to facilitate an online account management interface to the forwards. Thanks. ________________________ saxon jones network infrastructure admin interbaun communications suite 200 18404 stony plain road edmonton, ab T5S 2M8 mailto:[EMAIL PROTECTED] http://www.interbaun.com/ (780) 447-8276 -----Original Message----- From: Sam Varshavchik [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 4:46 PM To: '[EMAIL PROTECTED]' Subject: [courier-users] Re: System Error forwarding messages Saxon Jones writes: > � HTML content follows � > > I have started to receive a number of complaints of bounces reporting: > > � > > <<< System error - unable to forward message. > > � > > What could possibly cause this error?� So far the bounce has only been > reported when delivering to a mailbox with a .courier file listing two > email addresses, one being a locally hosted address and the other on a > remote host. submit is rejecting the forwarded message. If you have some antivirus filter hooked into submit, the dumb filter is probably rejecting the forward, even though it didn't complain about a nearly identical message that was received only a few seconds ago. Either that, or one of the forwarded addresses is invalid. The current version of Courier now logs the additional error messages, which would've clarified the situation.
smime.p7s
Description: S/MIME cryptographic signature
