Anyone here running qmail/vpopmail behind a COX connection? I'm having a problem with bounce messages generated by my server getting through COX's mail server. For instance if an outside email is addressed to a non-existent user at kuhns-la.com, my server generates a bounce with the "Sorry, no mailbox here by that name." message, this bounce message is then bounced back to my postmaster by the COX server with a "550 relaying mail to xxxxxx.yyy is not allowed" message where xxxxxx.yyy is the domain for the sending user (note, this is just an example - ALL bounce messages are coming back to postmaster with a 550 from COX). All other traffic seems to be going through COX fine.
I'm thinking it's a header issue, possibly return-path since it's blank in every bounce my server generates but has a value for all other traffic. This is an example header from one of the bounces (To address was changed in example): Return-Path: <> Received: (qmail 14933 invoked for bounce); 9 Mar 2004 13:48:50 -0000 Date: 9 Mar 2004 13:48:50 -0000 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: failure notice What do y'all think - am I on the right track? And if so, anyone know how to force qmail/vpopmail to include that return-path header. I've dug a little on goggle this morning and didn't turn up anything - granted I'm only on my first cup of coffee so far so I may have overlooked something obvious. Thanks, James
