After a recent conversation with Mr. Sam (thanx for the help!!) I was able to resolve a return-path issue. In my /etc/courier/maildrop file, it was listed /usr/lib/courier/bin/maildrop. In my .courier file for my account, I was pointing to /usr/local/bin/maildrop, which was a symlink to the above mentioned maildrop. Even though they were ultimately using the same file, none of my messages would get a return-path set on them until I pointed my .courier file directly at /usr/lib/courier/bin/maildrop.
My question, is this by design, or some odd flaw that nobody else has run across yet? I'm just curious, as now I have return-path working again. -- Jesse Keating RHCE MCSE For Web Services and Linux Consulting, Visit --> j2Solutions.net Mondo DevTeam (www.mondorescue.org) Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating ------------------------------------------------------- This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at: http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
