Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Connect » Status mails were sent .... but why?
  •  
m.ludwig

Messages: 25
Karma: 1
Send a private message to this user
Hi all,

our KMS 7.4.3 sends statusmails like "...successfully delivered..." or "...receipient has complained about content..."

BUT WHY?? Where can i stop these mails. Earlier there were no mails like this. I'm sure that we haven't changed the config. Sad

many thanks for help
  •  
Kedar

Messages: 1320
Karma: 48
Send a private message to this user
AFAIK there is no such "feature" in Kerio Connect. Look to the source of messages - header X-Mailer
  •  
m.ludwig

Messages: 25
Karma: 1
Send a private message to this user
Hi. Thx for answer.

looks like following. we have a mailaddress in our domain which will be forwarded over mx to another address outside our domain. it seems that the receiving server sends this statusmail back to our KMS and KMS is forwarding this mail to the source. is there a way to block this "forwarding"? as it is the "spam-senders" may be able to recognize that this address exists. so there will be more spam in future.

thx in advance
  •  
puretech

Messages: 118
Karma: 5
Send a private message to this user
I am not entirely sure I understood the above explanation. But maybe try posting header content of the message here so we can point you to the right direction?
  •  
m.ludwig

Messages: 25
Karma: 1
Send a private message to this user
A status message concerning a successful delivery:
The message-text is in german. hope you can read Wink

(text in # has been changed)

------------------------------------------------------------ --------
Return-Path: <>
Received: from localhost
by #OUR KERIO MACHINE#; Fri, 2 Nov 2012 04:08:43 +0100
Date: Fri, 2 Nov 2012 04:08:43 +0100
Message-ID: <583247250-2324@#OUR KERIO MACHINE#>
MIME-Version: 1.0
From: Mail Delivery Subsystem <#OUR KERIO MACHINE#>
To: <TUACM<_at_>wpm.axime.com>
Subject: =?utf-8?Q?#xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx#
Content-Type: multipart/report; report-type=delivery-status;
boundary="MIME-583247250-41-delim"

--MIME-583247250-41-delim
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit


Dies ist eine Informationsnachricht gesendet durch #OUR KERIO MACHINE#.

Der Server hat Ihre Nachricht

Subject: #xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx#
Date: Fri, 2 Nov 2012 04:08:03 +0100 (CET)



erfolgreich an folgende Adressen zugestellt:

<#RECEIPIENT#> (delivered)
--MIME-583247250-41-delim
Content-Type: message/delivery-status

Reporting-MTA: dns; #OUR KERIO MACHINE#
Arrival-Date: Fri, 2 Nov 2012 04:08:39 +0100

Original-Recipient: #RECEIPIENT#
Final-Recipient: rfc822;#RECEIPIENT#
Action: delivered
Status: 2.0.0

--MIME-583247250-41-delim
Content-Type: text/rfc822-headers

X-Spam-Status: No, hits=1.5 required=5.0
tests=BAYES_50: 1.567,HTML_MESSAGE: 0.001,MIME_HTML_ONLY: 0.001,
TOTAL_SCORE: 1.569,autolearn=no
X-Spam-Level: *
Received: from massmail.mx5.atos.net ([160.92.141.149])
by #OUR KERIO MACHINE#
for #RECEIPIENT#;
Fri, 2 Nov 2012 04:08:38 +0100
Received: from mmut01 (mmut01.priv.atos.fr [192.168.9.79])
by nmail05.priv.atos.fr (Postfix) with ESMTP id A7A9A98209
for <#RECEIPIENT#>; Fri, 2 Nov 2012 04:08:03 +0100 (CET)
Message-ID: <TUACM;PUSHSHELL;797060;h90q3x7qro6tc8<_at_>euroshell.com>
Date: Fri, 2 Nov 2012 04:08:03 +0100 (CET)
From: wli<_at_>euroshell.com
Reply-To: wli<_at_>euroshell.com
To: #RECEIPIENT#
Subject: =?UTF-8?#xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx#
Mime-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
mailTodoId: 797060-1048160-132662496
X-project: TUACM
X-service: PUSHSHELL
X-userInfo: 797060

--MIME-583247250-41-delim--
------------------------------------------------------------ ---------
  •  
TorW

Messages: 769
Karma: 9
Send a private message to this user
This is a standard delivery status report which the sender asked for. The client must configure how a request for a delivery report should be handled since it's not something you can (or should) turn on or off at the server level.

  •  
puretech

Messages: 118
Karma: 5
Send a private message to this user
TorW is right, the delivery reports is something client should configure. I have seen it with koff, before sending a read receipt, it asks the recipient if they want to send it or not, but I am not sure if its the same with the delivery report.

Actually I take it back. the delivery report is when the message has been delivered, regardless of reading.
  •  
TorW

Messages: 769
Karma: 9
Send a private message to this user
Ah, well, yes. There's a slight difference there; the user can configure how a read receipt should be handled, but not a delivery receipt.
  •  
m.ludwig

Messages: 25
Karma: 1
Send a private message to this user
TorW wrote on Fri, 02 November 2012 12:33
Ah, well, yes. There's a slight difference there; the user can configure how a read receipt should be handled, but not a delivery receipt.


Hit! Client is configured to ask if a read receipt is requested. So it must be something different.

[Updated on: Fri, 02 November 2012 13:12]

  •  
clan

Messages: 236
Karma: 22
Send a private message to this user
Is the client configured to ask for delivery status? In the German Kerio Webmail interface it is called Sendebestätigung anfordern. This generates just the message you quote.
Is there a way to configure Kerio not to generate DSN, even if asked for it?
  •  
m.ludwig

Messages: 25
Karma: 1
Send a private message to this user
clan wrote on Fri, 02 November 2012 15:40
Is the client configured to ask for delivery status?


The Mail was sent by external domain to our domain and forwarded to another one. so we have no control to the client who sent the mail.

Maybe the sender marks that hook in his mailclient but it would be nice to block this status-messages generally.
Previous Topic: Double-Take Replication with Websphere Application Server 7
Next Topic: Kerio Offline Connector Sync/Refresh interval?
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Thu Oct 19 23:58:51 CEST 2017

Total time taken to generate the page: 0.00452 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.