Hi Rolf,
Many thanks for the daemon. In general it works and our ISP SMTP server accept the autoreply again. Great.
But following remarks for your information:
Mercury Core Process is nevertheless showing:
Mon 12, 9:03:10: Job MG000002: from <> (local)
*Job killed by daemin.
when automatically answering with autoreply.
The receiver sees the local user (jd@domain.com) within the from field instead of the adjusted noreply@domain.com.
I've checked the header of the returned mail and found:
From: jd@domain.com (the real address reads j.doe@domain.com, jd is the local user name only, to be translated by synonym.mer into j.doe@domain.com)
X-Autoreply-From: jd
Return-Path: noreply@domain.com
We could live with, since <localuser>@domain.com as autoreply address is also a not existing address, to avoid that spammers get oour real adresses.
Hi Rolf,
Many thanks for the daemon. In general it works and our ISP SMTP server accept the autoreply again. Great.
But following remarks for your information:
Mercury Core Process is nevertheless showing:
**Mon 12, 9:03:10: Job MG000002: from <> (local)**
** *Job killed by daemin.**
when automatically answering with autoreply.
The receiver sees the **local** user (jd@domain.com) within the from field instead of the adjusted noreply@domain.com.
I've checked the header of the returned mail and found:
**From: jd@domain.com** (the real address reads j.doe@domain.com, **jd** is the local user name only, to be translated by synonym.mer into j.doe@domain.com)
**X-Autoreply-From: jd
Return-Path: noreply@domain.com**
We could live with, since <localuser>@domain.com as autoreply address is also a not existing address, to avoid that spammers get oour real adresses.
