[quote user="Sellerie"][quote user="Anaglypta"]

E 20180228 171521 5a1d7606 DATA state failure - 554 Message rejected on 2018/02/28 17:15:21 GMT, policy (3.2.1.1) – Your messa

T 20180228 171521 5a1d7606 Connection closed normally. 

[/quote]

Please can you post the complete entry? I think the interesting part comes after "Your message" 

[/quote]

Sellerie,

The Mercury smtpE log file has been truncated, so that is all I have. But the intertesting bit is "policy (3.2.1.1)" which from this email provider (British Telecom in the UK) means "Your message was rejected because the "FROM" field is empty." I don't blame BT for doing this, I also do this using a Transaction Filter M, "*", RSN, "554 Your message was rejected because the "FROM" field is empty."

In order to overcome this I have now set up a client to receive messages for this account and created some filter rules to achieve this:-

• Match all messages
• Reply with template
• Mark as read
• Delete message

It is annoying that I have no solution in Mercury.

John.

I have set up an autresponder using a "Simple Autoreply" as described in the Mercury help file, which sends back a text file AREPLY.PM from a real account responder@mydomain.

Recently I am getting a lot of failures which look like they are being rejected because the FROM field is blank. Snippet of MercuryE log below (edited to remove user name from email address).

Is there any way around this, or an alternative way of sending auto replies where the from field is populated.

John.

T 20180228 171516 5a1d7606 Begin processing job MO00044B from <>

T 20180228 171517 5a1d7606 Established ESMTP connection to 65.20.0.49

T 20180228 171517 5a1d7606 MAIL FROM:<> SIZE=855

T 20180228 171517 5a1d7606 250 MAIL FROM:<> OK

T 20180228 171517 5a1d7606 RCPT TO:<a.user@btinternet.com>

T 20180228 171517 5a1d7606 250 RCPT TO:<a.user@btinternet.com> OK

E 20180228 171521 5a1d7606 DATA state failure - 554 Message rejected on 2018/02/28 17:15:21 GMT, policy (3.2.1.1) – Your messa

T 20180228 171521 5a1d7606 Connection closed normally. 

Hi John,

can't help on this, but in addition had a test with following headers found in autoreply:

Return-Path: <>
X-Autoreply-From: <synonym@xxx.domain.de>
From: <synonym@xxx.domain.de>
To: <mailsender@anydomain.de>
Subject: [Autoreply] Re: Test

It seems Mercury knows the correct mailaddress of the user sending autoreply, but doesn't include it in Envelope-From. [:(]

bye    Olaf

[quote user="Anaglypta"]

E 20180228 171521 5a1d7606 DATA state failure - 554 Message rejected on 2018/02/28 17:15:21 GMT, policy (3.2.1.1) – Your messa

T 20180228 171521 5a1d7606 Connection closed normally. 

[/quote]

Please can you post the complete entry? I think the interesting part comes after "Your message" 

Hi,

We are using Mercury's SYNONYM.MER database functionality to "translate" our official (internet) user e-mail addresses into the local user names and vice versa. For example:

"a.testname@domain.com" is connected to the local user account of user "at". Means, when the local user "at" is sending an e-mail to the internet, Mercury is replacing his local user name (at@domain.com) by the full name defined in synonym.mer.

When activating the autoresponse function in Pmail, Mercury is using "at@domain.com" as sender's address for autoresponse mails. At the beginning I was annoyed about it, but in the meantime I believe this "feature" has also advantages. Spammers, which are sending their mails to thousands of possible addresses, don't get back a confirmation of my real address. Further my autoresponse mails, which contain the sentence "Do not reply to this mail", could really not be used for responses to me.

Refer also to former discussions in this regard: http://community.pmail.com/forums/thread/41750.aspx

[quote]We are using Mercury's SYNONYM.MER database functionality to "translate" our official (internet) user e-mail addresses into the local user names and vice versa.[/quote]

/me too, but ...

[quote]When activating the autoresponse function in Pmail, Mercury is using "at@domain.com" as sender's address for autoresponse mails.[/quote]

... as shown in posting above in my case Mercury replaces "from" with synonym.

Hmm ... maybe the difference is, that my Mercury runs with NDS-module for accessing eDirectory of Novell Netware and takes synonym directly from there instead of using synonym.mer?! Seems Mercury behaves different depending on infrastructure.

Anyway - the problem of Anaglypta remains the same in all cases: Mercury includes a mail-from but doesn't inculde an envelope-from and more and more servers reject mails, if it is not filled.

[quote]At the beginning I was annoyed about it, but in the meantime I believe this "feature" has also advantages.[/quote]

No - if the recipient of the autoreply can't identify who is autoreplying (because username and synonym may not be similar enough), he may wonder, why he is getting no answer. Sorry - not acceptable.

[quote user="FJR"]No - if the recipient of the autoreply can't identify who is autoreplying (because username and synonym may not be similar enough), he may wonder, why he is getting no answer. Sorry - not acceptable.
bye    Olaf[/quote]

Generally I would agree. But as per my experiences with Mercury over years it doesn't matter. The "wrong" reply address still contains our domain name and the user initials. Further the reply mail text contains our service numbers - insofar no problem for our customers to identify the sender.

But of course, in case more and more mail servers don't accept empty "envelope" sections, this should be bugfixed.

Gruß aus Rostock

Jörg