A couple of months ago there was a long thread discussing the problem of synonyms not being used by auto-replies. A solution was found, or so we thought. The problem was that the From: header in the auto-reply was populated with localusername@domain.com rather than domainusername@domain.com. It was apparent that the synonym files was ignored by the auto-reply process (triggered by a FORWARD file). Removing the local user entries from the MercuryD configuration appeared to have solved the problem but the problem is back for me. The only change I can think of is switching from MercuryC to MercuryE. Does anyone know if or why this change would affect this behavior?
Edit: I got it working again on auto-replies but not on auto-forwards generated by a FORWARD file. The emphasis during the previous discussion on this topic was to get the From: header correct in the auto-replies. I don't recall that the Resent-from: header in auto-forwards was given much attention so it may have never worked. It is of low importance so I consider this problem fixed.
<p>A couple of months ago there was a long thread discussing the problem of synonyms not being used by auto-replies.&nbsp; A solution was found, or so we thought.&nbsp; The problem was that the From: header in the auto-reply was populated with <i>localusername</i>@domain.com rather than <i>domainusername</i>@domain.com.&nbsp; It was apparent that the synonym files was ignored by the auto-reply process (triggered by a FORWARD file).&nbsp; Removing the local user entries from the MercuryD configuration appeared to have solved the problem but the problem is back for me.&nbsp; The only change I can think of is switching from MercuryC to MercuryE.&nbsp; Does anyone know if or why this change would affect this behavior?</p><p>Edit: I got it working again on auto-replies but not on auto-forwards generated by a FORWARD file.&nbsp; The emphasis during the previous discussion on this topic was to get the From: header correct in the auto-replies.&nbsp; I don't recall that the Resent-from: header in auto-forwards was given much attention so it may have never worked.&nbsp; It is of low importance so I consider this problem fixed.
</p><p>&nbsp;</p>