Highlighted
Absent Member.
Absent Member.
1590 views

SMTP, Delayed Mail notifications from relay

Hi,

two problems/questions:

our GWIA (2014 SP2) sends outgoing mails to a postfix relay. If postfix
can't connect the target server after a while it generates a "Delayed Mail"-
Message and sends it back to the sending user. This mail does not get
delivered to the user - any idea why?

Second question: if the sending user has delivery confirmation enabled(!)
postfix does not even send a "Delayed Mail" notification.

Both seems strange to me - does this work as designed?

Thanks,
Mirko
Labels (1)
0 Likes
4 Replies
Highlighted
Absent Member.
Absent Member.

Re: SMTP, Delayed Mail notifications from relay

Well, I'm not sure about the second part, because that shouldn't matter. But have you tried to capture the messages from Postfix for the delay to see what they actually say?
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: SMTP, Delayed Mail notifications from relay

Hi Danita,

what do you mean by "shouldn't matter"? If delivery confirmation is enabled,
delay confirmations should not matter?

We found that if delivery confirmation is enabled GroupWise sends an
envelope header "notify_flags=6", which it does not if delivery confirmation
is disabled. But we did not find any information about notify_flags...

We tried Outlook and Thunderbird: they set notify_flags=14 - this does not
prevent postfix from sending a "Delayed Mail" message. Why does GW set
notify_flags to 6? Is that correct?


Below is an example of one "Delayed Mail"-message captured from postfix
before sent to GWIA.

If the original mail to xxtest-gw@my-pc.rz.my-domain is sent by Thunderbird
(SMTP to postfix, same sender) a similar message is generated by postfix and
successfully delivered to the GW mailbox of the sender.

So obviously GW detects if the original mail came from GW and handles the
"Delayed Mail" message differently. How does GW know where the original mail
came from? Is it becauese of "Original-Envelope-Id:
groupwise.566809A5.BC7:dd:267e:N"?

BTW, it does not depend on "sent item" in GW - even if we chose to not
create one, there is no "Delayed Mail" message. It also does not depend on
the "Return notification to sender when a message is delayed" and "Convert
Status to Messages" settings of the GWIA.

Thanks,
Mirko


*** ENVELOPE RECORDS deferred/5/52CBA551DE ***
message_size: 3093 231 1
0 3093
message_arrival_time: Wed Dec 9 12:06:04 2015
create_time: Wed Dec 9 12:06:04 2015
named_attribute: log_message_origin=local
named_attribute: trace_flags=0
sender:
original_recipient: My.Name@my-domain
recipient: My.Name@my-domain
*** MESSAGE CONTENTS deferred/5/52CBA551DE ***
Received: by mx.my-domain (Postfix)
id 52CBA551DE; Wed, 9 Dec 2015 12:06:04 +0100 (CET)
Date: Wed, 9 Dec 2015 12:06:04 +0100 (CET)
From: MAILER-DAEMON@mx.my-domain (Mail Delivery System)
Subject: Delayed Mail (still being retried)
To: My.Name@my-domain
Auto-Submitted: auto-replied
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="645DC5518E.1449659164/mx.my-domain"
Message-Id: <20151209110604.52CBA551DE@mx.my-domain>

This is a MIME-encapsulated message.

--645DC5518E.1449659164/mx.my-domain
Content-Description: Notification
Content-Type: text/plain; charset=us-ascii

This is the mail system at host mx.my-domain.

####################################################################
# THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE. #
####################################################################

Your message could not be delivered for more than 0 hour(s).
It will be retried until it is 5 day(s) old.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The mail system

<xxtest-gw@my-pc.rz.my-domain>: connect to
my-pc.rz.my-domain[xxx.xxx.xxx.145]:25: Connection timed out

--645DC5518E.1449659164/mx.my-domain
Content-Description: Delivery report
Content-Type: message/delivery-status

Reporting-MTA: dns; mx.my-domain
Original-Envelope-Id: groupwise.566809A5.BC7:dd:267e:N
X-Postfix-Queue-ID: 645DC5518E
X-Postfix-Sender: rfc822; My.Name@my-domain
Arrival-Date: Wed, 9 Dec 2015 11:59:52 +0100 (CET)

Final-Recipient: rfc822; xxtest-gw@my-pc.rz.my-domain
Original-Recipient: rfc822;groupwise-xxtest-gw@my-pc.rz.my-domain:1:1
Action: delayed
Status: 4.4.1
Diagnostic-Code: X-Postfix; connect to
my-pc.rz.my-domain[xxx.xxx.xxx.145]:25: Connection timed out
Will-Retry-Until: Mon, 14 Dec 2015 11:59:52 +0100 (CET)

--645DC5518E.1449659164/mx.my-domain
Content-Description: Undelivered Message Headers
Content-Type: text/rfc822-headers

Return-Path: <My.Name@my-domain>
Received: from gwia.rz.my-domain (stud.my-domain [141.79.10.30])
by mx.my-domain (Postfix) with ESMTPS id 645DC5518E
for <xxtest-gw@my-pc.rz.my-domain>; Wed, 9 Dec 2015 11:59:52 +0100
(CET)
Received: from gw-domain-MTA by gwia.rz.my-domain
with Novell_GroupWise; Wed, 09 Dec 2015 11:59:52 +0100
Message-Id: <566817B5020000DD0009F010@gwia.rz.my-domain>
X-Mailer: Novell GroupWise Internet Agent 14.0.2
Date: Wed, 09 Dec 2015 11:59:49 +0100
From: "Gerhard Rappenecker" <My.Name@my-domain>
To: <xxtest-gw@my-pc.rz.my-domain>
Subject: test3 von GW
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

--645DC5518E.1449659164/mx.my-domain--
*** HEADER EXTRACTED deferred/5/52CBA551DE ***
*** MESSAGE FILE END deferred/5/52CBA551DE ***



dzanre wrote:

>
>
> Well, I'm not sure about the second part, because that shouldn't matter.
> But have you tried to capture the messages from Postfix for the delay
> to see what they actually say?
>
>


0 Likes
Highlighted
Absent Member.
Absent Member.

Re: SMTP, Delayed Mail notifications from relay

We found out something more:

1.
http://stackoverflow.com/questions/17169890/postfix-transferring-notify-command-to-script-using-pipe

notify_flagsis bitwise: never: 1 success: 2 failure: 4 delay: 8

GroupWise sets 6 = 2+4 = "success,failure"
Thunderbird, Outlook: 14 = 2+4+8 = "success,failure,delay"

The question is: why does GW do so?


2. It's definitely "Original-Envelope-Id:groupwise...." which causes to GW
to suppress the delivery of the "Delayes Mail"-messager.


Are there opinions about this? Bugs, time for a Service Request? Or rather a
case for "Ideas"?

Thanks,
Mirkos


Mirko Guldner wrote:

> Hi Danita,
>
> what do you mean by "shouldn't matter"? If delivery confirmation is
> enabled, delay confirmations should not matter?
>
> We found that if delivery confirmation is enabled GroupWise sends an
> envelope header "notify_flags=6", which it does not if delivery
> confirmation is disabled. But we did not find any information about
> notify_flags...
>
> We tried Outlook and Thunderbird: they set notify_flags=14 - this does not
> prevent postfix from sending a "Delayed Mail" message. Why does GW set
> notify_flags to 6? Is that correct?
>
>
> Below is an example of one "Delayed Mail"-message captured from postfix
> before sent to GWIA.
>
> If the original mail to xxtest-gw@my-pc.rz.my-domain is sent by
> Thunderbird (SMTP to postfix, same sender) a similar message is generated
> by postfix and successfully delivered to the GW mailbox of the sender.
>
> So obviously GW detects if the original mail came from GW and handles the
> "Delayed Mail" message differently. How does GW know where the original
> mail came from? Is it becauese of "Original-Envelope-Id:
> groupwise.566809A5.BC7:dd:267e:N"?
>
> BTW, it does not depend on "sent item" in GW - even if we chose to not
> create one, there is no "Delayed Mail" message. It also does not depend on
> the "Return notification to sender when a message is delayed" and "Convert
> Status to Messages" settings of the GWIA.
>
> Thanks,
> Mirko
>
>
> *** ENVELOPE RECORDS deferred/5/52CBA551DE ***
> message_size: 3093 231 1
> 0 3093
> message_arrival_time: Wed Dec 9 12:06:04 2015
> create_time: Wed Dec 9 12:06:04 2015
> named_attribute: log_message_origin=local
> named_attribute: trace_flags=0
> sender:
> original_recipient: My.Name@my-domain
> recipient: My.Name@my-domain
> *** MESSAGE CONTENTS deferred/5/52CBA551DE ***
> Received: by mx.my-domain (Postfix)
> id 52CBA551DE; Wed, 9 Dec 2015 12:06:04 +0100 (CET)
> Date: Wed, 9 Dec 2015 12:06:04 +0100 (CET)
> From: MAILER-DAEMON@mx.my-domain (Mail Delivery System)
> Subject: Delayed Mail (still being retried)
> To: My.Name@my-domain
> Auto-Submitted: auto-replied
> MIME-Version: 1.0
> Content-Type: multipart/report; report-type=delivery-status;
> boundary="645DC5518E.1449659164/mx.my-domain"
> Message-Id: <20151209110604.52CBA551DE@mx.my-domain>
>
> This is a MIME-encapsulated message.
>
> --645DC5518E.1449659164/mx.my-domain
> Content-Description: Notification
> Content-Type: text/plain; charset=us-ascii
>
> This is the mail system at host mx.my-domain.
>
> ####################################################################
> # THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE. #
> ####################################################################
>
> Your message could not be delivered for more than 0 hour(s).
> It will be retried until it is 5 day(s) old.
>
> For further assistance, please send mail to postmaster.
>
> If you do so, please include this problem report. You can
> delete your own text from the attached returned message.
>
> The mail system
>
> <xxtest-gw@my-pc.rz.my-domain>: connect to
> my-pc.rz.my-domain[xxx.xxx.xxx.145]:25: Connection timed out
>
> --645DC5518E.1449659164/mx.my-domain
> Content-Description: Delivery report
> Content-Type: message/delivery-status
>
> Reporting-MTA: dns; mx.my-domain
> Original-Envelope-Id: groupwise.566809A5.BC7:dd:267e:N
> X-Postfix-Queue-ID: 645DC5518E
> X-Postfix-Sender: rfc822; My.Name@my-domain
> Arrival-Date: Wed, 9 Dec 2015 11:59:52 +0100 (CET)
>
> Final-Recipient: rfc822; xxtest-gw@my-pc.rz.my-domain
> Original-Recipient: rfc822;groupwise-xxtest-gw@my-pc.rz.my-domain:1:1
> Action: delayed
> Status: 4.4.1
> Diagnostic-Code: X-Postfix; connect to
> my-pc.rz.my-domain[xxx.xxx.xxx.145]:25: Connection timed out
> Will-Retry-Until: Mon, 14 Dec 2015 11:59:52 +0100 (CET)
>
> --645DC5518E.1449659164/mx.my-domain
> Content-Description: Undelivered Message Headers
> Content-Type: text/rfc822-headers
>
> Return-Path: <My.Name@my-domain>
> Received: from gwia.rz.my-domain (stud.my-domain [141.79.10.30])
> by mx.my-domain (Postfix) with ESMTPS id 645DC5518E
> for <xxtest-gw@my-pc.rz.my-domain>; Wed, 9 Dec 2015 11:59:52
> +0100
> (CET)
> Received: from gw-domain-MTA by gwia.rz.my-domain
> with Novell_GroupWise; Wed, 09 Dec 2015 11:59:52 +0100
> Message-Id: <566817B5020000DD0009F010@gwia.rz.my-domain>
> X-Mailer: Novell GroupWise Internet Agent 14.0.2
> Date: Wed, 09 Dec 2015 11:59:49 +0100
> From: "Gerhard Rappenecker" <My.Name@my-domain>
> To: <xxtest-gw@my-pc.rz.my-domain>
> Subject: test3 von GW
> Mime-Version: 1.0
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: inline
>
> --645DC5518E.1449659164/mx.my-domain--
> *** HEADER EXTRACTED deferred/5/52CBA551DE ***
> *** MESSAGE FILE END deferred/5/52CBA551DE ***
>
>
>
> dzanre wrote:
>
>>
>>
>> Well, I'm not sure about the second part, because that shouldn't matter.
>> But have you tried to capture the messages from Postfix for the delay
>> to see what they actually say?
>>
>>


0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: SMTP, Delayed Mail notifications from relay

In article <sChay.756$ct1.285@novprvlin0913.provo.novell.com>, Mirko Guldner
wrote:
> Are there opinions about this? Bugs, time for a Service Request? Or rather a
> case for "Ideas"?


Depends on how you are equipped for SRs, If you have full maintenance with lots
to use, that would be your best first bet as that will check if this is Working
as Designed (WAD) or a problem. If WAD, then proceed to generating an Idea (it
would be nice to be able to configure that number) and post the link here so
that we can then go vote for it.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please show
your appreciation by clicking on the star below. Thanks!

___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.