We have two branch offices. Email to users at these offices comes to Mercury (v4.80) at our main office (eg user1@eslers.com.au) and is redirected to the appropriate site using aliases (eg user1@branch1.eslers.com.au).
If a user at a branch office sends an email to a user at head office with delivery confirmation, Mercury seems to attempt to send the confirmation email ignoring the alias for that user, so I can see on the MercuryE window:
15:50:48: processing job MO005185
Resolved MX for 'eslers.com.au' to 115.69.20.109
Connecting to 115.69.20.109
Connection error.
There seem to be two problems here. One is that the module handling the delivery confirmation ignores the alias, and the other is that Mercury is using MercuryE to send to a local address.
Does anyone know how to fix this?
Pat
<p>We have two branch offices. Email to users at these offices comes to Mercury (v4.80) at our main office (eg user1@eslers.com.au) and is redirected to the appropriate site using aliases (eg user1@branch1.eslers.com.au).</p><p>If a user at a branch office sends an email to a user at head office with delivery confirmation, Mercury seems to attempt to send the confirmation email ignoring the alias for that user, so I can see on the MercuryE window:</p><p>15:50:48: processing job MO005185
Resolved MX for 'eslers.com.au' to 115.69.20.109
Connecting to 115.69.20.109
Connection error.
</p><p>There seem to be two problems here. One is that the module handling the delivery confirmation ignores the alias, and the other is that Mercury is using MercuryE to send to a local address.
</p><p>Does anyone know how to fix this?</p><p>Pat
</p><p>&nbsp;
</p>
