We are using James to send email for a challenge response anti-spam tool we developed inhouse. 

 

When we ran the server on a Windows environment, it seemed to work fine, but now that we have moved it to Linux, we are getting odd errors on "bounced" addresses.

 

Essentially, when we send a challenge, the return address is [EMAIL PROTECTED].  Here is what I am seeing in the James log

 

07/10/04 08:10:55 INFO  James: Processing a bounce request for a message with an empty return path.  No bounce will be sent.

07/10/04 08:10:55 INFO  James: Processing a bounce request for a message with a return path header.  The bounce will be sent to <[EMAIL PROTECTED]>

07/10/04 08:10:55 INFO  James: Processing a bounce request for a message with an empty return path.  No bounce will be sent.

07/10/04 08:11:55 INFO  James: Processing a bounce request for a message with a return path header.  The bounce will be sent to <[EMAIL PROTECTED]>

07/10/04 08:11:55 INFO  James: Processing a bounce request for a message with an empty return path.  No bounce will be sent.

07/10/04 08:11:55 INFO  James: Processing a bounce request for a message with a return path header.  The bounce will be sent to <[EMAIL PROTECTED]>

07/10/04 08:11:56 INFO  James: Processing a bounce request for a message with an empty return path.  No bounce will be sent.

 

The [EMAIL PROTECTED] actually points to our exchange environment where the challenge response application uses imap to pull inbound responses from challenged addresses.

 

I am using the same config.xml file from the previous environment except for a few minor adjustments for the fetchmail includes.  This is still disabled.

 

Can anyone provide any suggestions on why this may be happening?  It almost seems like James needs to be told to send the error to [EMAIL PROTECTED], but shouldn't the return path header address that?

 

Bill Callahan

 

Reply via email to