We use this same basic email tool as everyone else to send from the i.   Recently, we have seen email take more than 30 minutes to arrive, some even more than an hour.  I found how to look at the email header in the client we use, Outlook. I am not sure how to read it and tell if the holdup is from the i or downstream.  I need to be able to direct either our network staff or our cloud provider for the i to make the needed changes.  This is starting to impact the business workflow. 

 SNDSMTPEMM RCP((&REPORT1) (&REPORT2) (&REPORT3)) SUBJECT(&SUBJECT) + 
              NOTE(&NOTE) ATTACH((&PDFNAME1) (&PDFNAME2) (&PDFNAME3)) 

------------------------------
David Taylor
Sr Application Developer
Range Resources
Fort Worth
------------------------------

Hi David - have you considered using journaling to answer that question. Take a look -> Using Component Journaling for E-Mail. You can also use this document as well -> Mail server journal entries - IBM Documentation

Hope the above helps - Rich

------------------------------
Rich Malloy
------------------------------

If found this on the second link and the screen is empty.  If guess I need to turn something on first.  Will keep reading.

WRKSMTPEMM SORTBY(*TIME) QUEUE(*ALL)    

------------------------------
David Taylor
Sr Application Developer
Range Resources
Fort Worth
------------------------------

Original Message:
Sent: Tue January 07, 2025 04:58 PM
From: Rich Malloy
Subject: SNDSMTPEMM Delayed somewhere

Hi David - have you considered using journaling to answer that question. Take a look -> Using Component Journaling for E-Mail. You can also use this document as well -> Mail server journal entries - IBM Documentation

Hope the above helps - Rich

------------------------------
Rich Malloy
------------------------------

   David - Unless I am mistaken (always possible and even likely :-) ) , that command is meant if the IBMi is the SERVER

From the links...

Use this information to help you understand the codes and messages used in journal entries when using the Mail Server Framework. Typically this is utilized when the directory type is *SDD. The new directory types *SMTP an *SMTPMSF have their own method of journaling which can be accessed with the WRKSMTPEMM command. The directory type *SMTPMSF will use the following journal entries when an email is inserted into MSF, but not before.
                                                       
Help Text on the Command itself...

  The Work with SMTP E-mail Messages (WRKSMTPEMM) command allows        
  working with e-mail messages that are currently being processed by    
  the SMTP server for use with the local SMTP mailbox directory.        


Based on your description earlier of the problem... I think you are the CLIENT and NOT the Server....If that's true, then the journal codes you want (yes, you still need to turn on journaling for this) is for the client portion of SMTP and NOT the server side.

------------------------------
Rich Malloy
------------------------------

Original Message:
Sent: Tue January 07, 2025 05:08 PM
From: David Taylor
Subject: SNDSMTPEMM Delayed somewhere

If found this on the second link and the screen is empty.  If guess I need to turn something on first.  Will keep reading.

WRKSMTPEMM SORTBY(*TIME) QUEUE(*ALL)    

------------------------------
David Taylor
Sr Application Developer
Range Resources
Fort Worth
------------------------------


Original Message:
Sent: Tue January 07, 2025 04:58 PM
From: Rich Malloy
Subject: SNDSMTPEMM Delayed somewhere

Hi David - have you considered using journaling to answer that question. Take a look -> Using Component Journaling for E-Mail. You can also use this document as well -> Mail server journal entries - IBM Documentation

Hope the above helps - Rich

------------------------------
Rich Malloy

Thanks @Rich Malloy. I think I will dig into this with our network people to review the email headers for now.  The problem may not even be with the i. 

------------------------------
David Taylor
Sr Application Developer
Range Resources
Fort Worth
------------------------------

Original Message:
Sent: Tue January 07, 2025 05:18 PM
From: Rich Malloy
Subject: SNDSMTPEMM Delayed somewhere

   David - Unless I am mistaken (always possible and even likely :-) ) , that command is meant if the IBMi is the SERVER

From the links...

Use this information to help you understand the codes and messages used in journal entries when using the Mail Server Framework. Typically this is utilized when the directory type is *SDD. The new directory types *SMTP an *SMTPMSF have their own method of journaling which can be accessed with the WRKSMTPEMM command. The directory type *SMTPMSF will use the following journal entries when an email is inserted into MSF, but not before.
                                                       
Help Text on the Command itself...

  The Work with SMTP E-mail Messages (WRKSMTPEMM) command allows        
  working with e-mail messages that are currently being processed by    
  the SMTP server for use with the local SMTP mailbox directory.        


Based on your description earlier of the problem... I think you are the CLIENT and NOT the Server....If that's true, then the journal codes you want (yes, you still need to turn on journaling for this) is for the client portion of SMTP and NOT the server side.

------------------------------
Rich Malloy
------------------------------


Original Message:
Sent: Tue January 07, 2025 05:08 PM
From: David Taylor
Subject: SNDSMTPEMM Delayed somewhere

If found this on the second link and the screen is empty.  If guess I need to turn something on first.  Will keep reading.

WRKSMTPEMM SORTBY(*TIME) QUEUE(*ALL)    

------------------------------
David Taylor
Sr Application Developer
Range Resources
Fort Worth


Original Message:
Sent: Tue January 07, 2025 04:58 PM
From: Rich Malloy
Subject: SNDSMTPEMM Delayed somewhere

Hi David - have you considered using journaling to answer that question. Take a look -> Using Component Journaling for E-Mail. You can also use this document as well -> Mail server journal entries - IBM Documentation

Hope the above helps - Rich

------------------------------
Rich Malloy

Hello

You may want to look at the mail source with Outlook. The headers to look at are Received:. Usually, you start with the last one (which is the first added to the mail) and end with the first one (which is the last added to the mail.

They show all the mail relays which have handled the mail, with a timestamp for each. That could provide you an idea about a possible delay between two of them.

Example:

Received: from toaster-e24-02.priv.proxad.net
	by toaster-e24-02.priv.proxad.net with LMTP
	id 8DWUBL+ifWd+nBMAJ+IDmA
	(envelope-from <0100019442c3b2fd-cad5f257-607f-4366-9269-880c90f2620c-000000@mail.ConnectedCommunity.org>)
	for xxxxx; Tue, 07 Jan 2025 22:55:11 +0100
Received: from a14-106.smtp-out.amazonses.com (mx25-g26.priv.proxad.net [172.20.243.95])
	by toaster-e24-02.priv.proxad.net (Postfix) with ESMTP id BC56BD4036E
	for xxxxx; Tue,  7 Jan 2025 22:55:10 +0100 (CET)
Received: from a14-106.smtp-out.amazonses.com ([54.240.14.106])
	by mx1-g20.free.fr (MXproxy) with ESMTPS for xxxxx
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA256 bits=128);
	Tue,  7 Jan 2025 22:55:11 +0100 (CET)

 

------------------------------
Marc Rauzier
------------------------------

Hello David

You have to find all Received: from xxx by xxx headers, starting by the last one and going up. Each one includes the timestamp provided by each mail relay. It might to find where is the gap. If Outlook does not show them, you have to find a way to show the source of the message.

Example from a real mail:

Received: from xxxx
	 by xxxx;
	 Wed, 17 Apr 2024 11:28:28 +0200
Received: from xxxx
	by xxxx
	for xxxx; Wed, 17 Apr 2024 11:28:28 +0200 (CEST)
Received: from xxxx
	by xxxx
	for xxxx; Wed, 17 Apr 2024 11:28:28 +0200 (CEST)

------------------------------
Marc Rauzier
------------------------------

I did reach out to the network staff.  They found what they expect is the issue on their side.  Thanks for all the input. 

------------------------------
David Taylor
Sr Application Developer
Range Resources
Fort Worth
------------------------------

This post was removed