Custom Query (1181 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (55 - 57 of 1181)

Ticket Resolution Summary Owner Reporter
#1776 Undeliverable: Re: [SGE] #1719: Re: New Purchase Order-030220- SMART SOURCING INC. postmaster@…
Description

https://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?version=b8d100a9-0a8b-8e6a-88e1-ef488fee0470 Your message to info@… couldn't be delivered. info wasn't found at smart-sourcing.com. sge-bugs Office 365 info Action Required Recipient Unknown To address

How to Fix It The address may be misspelled or may not exist. Try one or more of the following:

  • Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
  • Contact the recipient (by phone, for example) to check that the address exists and is correct.
  • The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
  • Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.10 in Office 365<https://go.microsoft.com/fwlink/?LinkId=532972>, and then send the message again. Retype the entire recipient address before selecting Send.

If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Admins section below.

Was this helpful? Send feedback to Microsoft<https://go.microsoft.com/fwlink/?LinkId=525921>.

More Info for Email Admins Status code: 550 5.1.10

This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:

The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.

Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.

Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.

Recipient has a valid license - Make sure the recipient has an Office 365 license assigned to them. The recipient's email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > Assigned License > Edit).

Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.

For more information and additional tips to fix this issue, see Fix email delivery issues for error code 5.1.10 in Office 365<https://go.microsoft.com/fwlink/?LinkId=532972>.

Original Message Details Created Date: 12/6/2020 7:48:28 PM Sender Address: sge-bugs@… Recipient Address: info@… Subject: Re: [SGE] #1719: Re: New Purchase Order-030220- SMART SOURCING INC.

Error Details Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound?; Recipient info@… not found by SMTP address lookup DSN generated by: BN8PR05MB6563.namprd05.prod.outlook.com

Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 12/6/2020 7:48:28 PM arc.liv.ac.uk * 2 12/6/2020 7:48:28 PM arc.liv.ac.uk bhmhub1.liv.ac.uk esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) * 3 12/6/2020 7:48:28 PM localhost bhmhub1.liv.ac.uk esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) * 4 12/6/2020 7:48:28 PM bhmhub1.liv.ac.uk chmx1.liv.ac.uk esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) * 5 12/6/2020 7:48:28 PM chmx1.liv.ac.uk sophxr.liv.ac.uk ESMTP * 6 12/6/2020 7:48:28 PM sophxr.liv.ac.uk localhost SMTP * 7 12/6/2020 7:48:31 PM sophxr.liv.ac.uk CO1NAM11FT049.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 3 sec 8 12/6/2020 7:48:34 PM CO1NAM11FT049.eop-nam11.prod.protection.outlook.com MW3PR05CA0030.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 3 sec 9 12/6/2020 7:48:34 PM MW3PR05CA0030.namprd05.prod.outlook.com BN8PR05MB6563.namprd05.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *

Original Message Headers

Received: from MW3PR05CA0030.namprd05.prod.outlook.com (2603:10b6:303:2b::35)

by BN8PR05MB6563.namprd05.prod.outlook.com (2603:10b6:408:4e::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3654.7; Sun, 6 Dec 2020 19:48:34 +0000

Received: from CO1NAM11FT049.eop-nam11.prod.protection.outlook.com

(2603:10b6:303:2b:cafe::ce) by MW3PR05CA0030.outlook.office365.com (2603:10b6:303:2b::35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3654.7 via Frontend Transport; Sun, 6 Dec 2020 19:48:34 +0000

Authentication-Results: spf=temperror (sender IP is 138.253.100.180)

smtp.mailfrom=liverpool.ac.uk; smart-sourcing.com; dkim=none (message not signed) header.d=none;smart-sourcing.com; dmarc=temperror action=none header.from=liverpool.ac.uk;

Received-SPF: TempError? (protection.outlook.com: error in processing during

lookup of liverpool.ac.uk: DNS Timeout)

Received: from sophxr.liv.ac.uk (138.253.100.180) by

CO1NAM11FT049.mail.protection.outlook.com (10.13.175.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3632.17 via Frontend Transport; Sun, 6 Dec 2020 19:48:31 +0000

Received: from sophxr.liv.ac.uk (localhost [127.0.0.1])

by localhost (Postfix) with SMTP id D8E5C120217; Sun, 6 Dec 2020 19:48:28 +0000 (GMT)

Received: from chmx1.liv.ac.uk (chmx1.liv.ac.uk [138.253.100.141])

by sophxr.liv.ac.uk (Postfix) with ESMTP id D4559120226; Sun, 6 Dec 2020 19:48:28 +0000 (GMT)

Received: from bhmhub1.liv.ac.uk ([138.253.100.153])

by chmx1.liv.ac.uk with esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) id 1km01E-0007es-NO; Sun, 06 Dec 2020 19:48:28 +0000

Received: from localhost ([127.0.0.1] helo=bhmhub1.liv.ac.uk)

by bhmhub1.liv.ac.uk with esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) id 1km01E-0001DI-LK; Sun, 06 Dec 2020 19:48:28 +0000

Received: from arc.liv.ac.uk ([138.253.242.206])

by bhmhub1.liv.ac.uk with esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) id 1km01E-0001DE-Iw; Sun, 06 Dec 2020 19:48:28 +0000

Received: by arc.liv.ac.uk (Postfix, from userid 33)

id 8BE0744C7; Sun, 6 Dec 2020 19:48:28 +0000 (GMT)

MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "SGE" <sge-bugs@…> X-Trac-Version: 1.0.13 Precedence: bulk CC: sge-bugs@… Auto-Submitted: auto-generated X-Mailer: Trac 1.0.13, by Edgewall Software To: info@…, postmaster@… X-Trac-Project: SGE Date: Sun, 06 Dec 2020 19:48:28 -0000 Reply-To: X-URL: https://arc.liv.ac.uk/trac/SGE Subject: Re: [SGE] #1719: Re: New Purchase Order-030220- SMART SOURCING INC. X-Trac-Ticket-URL: https://arc.liv.ac.uk/trac/SGE/ticket/1719 Message-ID: <080.53229fd7cdb76d1035f4bf686f618b0b@…> References: <065.3a19984644b7198841a93b18077daba6@…> X-Trac-Ticket-ID: 1719 In-Reply-To: <065.3a19984644b7198841a93b18077daba6@…> Return-Path: sge-bugs@… X-EOPAttributedMessage: 0 X-EOPTenantAttributedMessage: 591a7d31-4300-4fc5-ab7c-aaad0ceb2756:0 X-MS-PublicTrafficType?: Email X-MS-Office365-Filtering-Correlation-Id: f858dbb5-9ce7-41c1-4867-08d89a1fe95f X-MS-TrafficTypeDiagnostic?: BN8PR05MB6563:

untitled-part.bin

untitled-part.mht

#1719: Re: New Purchase Order-030220- SMART SOURCING INC.


Reporter: info@… | Owner:

Type: defect | Status: new

Priority: normal | Milestone:

Component: sge | Version: 8.1.9

Severity: minor | Resolution: Keywords: |


Changes (by postmaster@…):

  • Attachment "untitled-part-18.bin" removed.

Added by email2trac

-- Ticket URL: <https://arc.liv.ac.uk/trac/SGE/ticket/1719> SGE <https://arc.liv.ac.uk/trac/SGE> Son of Grid Engine: Community continuation of work on Grid Engine

#1777 Undeliverable: Re: [SGE] #1719: Re: New Purchase Order-030220- SMART SOURCING INC. postmaster@…
Description

https://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?version=b8d100a9-0a8b-8e6a-88e1-ef488fee0470 Your message to info@… couldn't be delivered. info wasn't found at smart-sourcing.com. sge-bugs Office 365 info Action Required Recipient Unknown To address

How to Fix It The address may be misspelled or may not exist. Try one or more of the following:

  • Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
  • Contact the recipient (by phone, for example) to check that the address exists and is correct.
  • The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
  • Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.10 in Office 365<https://go.microsoft.com/fwlink/?LinkId=532972>, and then send the message again. Retype the entire recipient address before selecting Send.

If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Admins section below.

Was this helpful? Send feedback to Microsoft<https://go.microsoft.com/fwlink/?LinkId=525921>.

More Info for Email Admins Status code: 550 5.1.10

This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:

The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.

Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.

Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.

Recipient has a valid license - Make sure the recipient has an Office 365 license assigned to them. The recipient's email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > Assigned License > Edit).

Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.

For more information and additional tips to fix this issue, see Fix email delivery issues for error code 5.1.10 in Office 365<https://go.microsoft.com/fwlink/?LinkId=532972>.

Original Message Details Created Date: 12/6/2020 7:48:27 PM Sender Address: sge-bugs@… Recipient Address: info@… Subject: Re: [SGE] #1719: Re: New Purchase Order-030220- SMART SOURCING INC.

Error Details Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound?; Recipient info@… not found by SMTP address lookup DSN generated by: SN6PR05MB4896.namprd05.prod.outlook.com

Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 12/6/2020 7:48:27 PM arc.liv.ac.uk * 2 12/6/2020 7:48:27 PM arc.liv.ac.uk bhmhub1.liv.ac.uk esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) * 3 12/6/2020 7:48:27 PM localhost bhmhub1.liv.ac.uk esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) * 4 12/6/2020 7:48:28 PM bhmhub1.liv.ac.uk bhmx2.liv.ac.uk esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) 1 sec 5 12/6/2020 7:48:28 PM bhmx2.liv.ac.uk sophxm.liv.ac.uk ESMTP * 6 12/6/2020 7:48:28 PM sophxm.liv.ac.uk localhost SMTP * 7 12/6/2020 7:48:31 PM sophxm.liv.ac.uk CO1NAM11FT021.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 3 sec 8 12/6/2020 7:48:33 PM CO1NAM11FT021.eop-nam11.prod.protection.outlook.com MWHPR20CA0041.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec 9 12/6/2020 7:48:33 PM MWHPR20CA0041.namprd20.prod.outlook.com SN6PR05MB4896.namprd05.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *

Original Message Headers

Received: from MWHPR20CA0041.namprd20.prod.outlook.com (2603:10b6:300:ed::27)

by SN6PR05MB4896.namprd05.prod.outlook.com (2603:10b6:805:98::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3654.7; Sun, 6 Dec 2020 19:48:33 +0000

Received: from CO1NAM11FT021.eop-nam11.prod.protection.outlook.com

(2603:10b6:300:ed:cafe::72) by MWHPR20CA0041.outlook.office365.com (2603:10b6:300:ed::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3632.17 via Frontend Transport; Sun, 6 Dec 2020 19:48:33 +0000

Authentication-Results: spf=pass (sender IP is 138.253.100.164)

smtp.mailfrom=liverpool.ac.uk; smart-sourcing.com; dkim=none (message not signed) header.d=none;smart-sourcing.com; dmarc=pass action=none header.from=liverpool.ac.uk;

Received-SPF: Pass (protection.outlook.com: domain of liverpool.ac.uk

designates 138.253.100.164 as permitted sender) receiver=protection.outlook.com; client-ip=138.253.100.164; helo=sophxm.liv.ac.uk;

Received: from sophxm.liv.ac.uk (138.253.100.164) by

CO1NAM11FT021.mail.protection.outlook.com (10.13.175.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3632.17 via Frontend Transport; Sun, 6 Dec 2020 19:48:31 +0000

Received: from sophxm.liv.ac.uk (localhost [127.0.0.1])

by localhost (Postfix) with SMTP id 1282B260132; Sun, 6 Dec 2020 19:48:28 +0000 (GMT)

Received: from bhmx2.liv.ac.uk (bhmx2.liv.ac.uk [138.253.100.156])

by sophxm.liv.ac.uk (Postfix) with ESMTP id 0DF88260295; Sun, 6 Dec 2020 19:48:28 +0000 (GMT)

Received: from bhmhub1.liv.ac.uk ([138.253.100.153])

by bhmx2.liv.ac.uk with esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) id 1km01E-0002ym-0g; Sun, 06 Dec 2020 19:48:28 +0000

Received: from localhost ([127.0.0.1] helo=bhmhub1.liv.ac.uk)

by bhmhub1.liv.ac.uk with esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) id 1km01D-0001Cw-UY; Sun, 06 Dec 2020 19:48:27 +0000

Received: from arc.liv.ac.uk ([138.253.242.206])

by bhmhub1.liv.ac.uk with esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) id 1km01D-0001Cs-S1; Sun, 06 Dec 2020 19:48:27 +0000

Received: by arc.liv.ac.uk (Postfix, from userid 33)

id D114644BD; Sun, 6 Dec 2020 19:48:27 +0000 (GMT)

MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "SGE" <sge-bugs@…> X-Trac-Version: 1.0.13 Precedence: bulk CC: sge-bugs@… Auto-Submitted: auto-generated X-Mailer: Trac 1.0.13, by Edgewall Software To: info@…, postmaster@… X-Trac-Project: SGE Date: Sun, 06 Dec 2020 19:48:27 -0000 Reply-To: X-URL: https://arc.liv.ac.uk/trac/SGE Subject: Re: [SGE] #1719: Re: New Purchase Order-030220- SMART SOURCING INC. X-Trac-Ticket-URL: https://arc.liv.ac.uk/trac/SGE/ticket/1719 Message-ID: <080.91caaec1e7b604c2fef66ab9e58c2cb3@…> References: <065.3a19984644b7198841a93b18077daba6@…> X-Trac-Ticket-ID: 1719 In-Reply-To: <065.3a19984644b7198841a93b18077daba6@…> Return-Path: sge-bugs@… X-EOPAttributedMessage: 0 X-EOPTenantAttributedMessage: 591a7d31-4300-4fc5-ab7c-aaad0ceb2756:0 X-MS-PublicTrafficType?: Email X-MS-Office365-Filtering-Correlation-Id: fcc78552-21e6-4d34-a8ad-08d89a1fe931 X-MS-TrafficTypeDiagnostic?: SN6PR05MB4896:

untitled-part.bin

untitled-part.mht

#1719: Re: New Purchase Order-030220- SMART SOURCING INC.


Reporter: info@… | Owner:

Type: defect | Status: new

Priority: normal | Milestone:

Component: sge | Version: 8.1.9

Severity: minor | Resolution: Keywords: |


Changes (by postmaster@…):

  • Attachment "untitled-part-13.bin" removed.

Added by email2trac

-- Ticket URL: <https://arc.liv.ac.uk/trac/SGE/ticket/1719> SGE <https://arc.liv.ac.uk/trac/SGE> Son of Grid Engine: Community continuation of work on Grid Engine

#1778 Undeliverable: Re: [SGE] #1719: Re: New Purchase Order-030220- SMART SOURCING INC. postmaster@…
Description

https://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?version=b8d100a9-0a8b-8e6a-88e1-ef488fee0470 Your message to postmaster@… couldn't be delivered. postmaster wasn't found at ehciss.onmicrosoft.com. sge-bugs Office 365 postmaster Action Required Recipient Unknown To address

How to Fix It The address may be misspelled or may not exist. Try one or more of the following:

  • Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
  • Contact the recipient (by phone, for example) to check that the address exists and is correct.
  • The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
  • Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.10 in Office 365<https://go.microsoft.com/fwlink/?LinkId=532972>, and then send the message again. Retype the entire recipient address before selecting Send.

If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Admins section below.

Was this helpful? Send feedback to Microsoft<https://go.microsoft.com/fwlink/?LinkId=525921>.

More Info for Email Admins Status code: 550 5.1.10

This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:

The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.

Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.

Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.

Recipient has a valid license - Make sure the recipient has an Office 365 license assigned to them. The recipient's email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > Assigned License > Edit).

Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.

For more information and additional tips to fix this issue, see Fix email delivery issues for error code 5.1.10 in Office 365<https://go.microsoft.com/fwlink/?LinkId=532972>.

Original Message Details Created Date: 12/6/2020 7:48:32 PM Sender Address: sge-bugs@… Recipient Address: postmaster@… Subject: Re: [SGE] #1719: Re: New Purchase Order-030220- SMART SOURCING INC.

Error Details Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound?; Recipient postmaster@… not found by SMTP address lookup DSN generated by: BYAPR05MB6358.namprd05.prod.outlook.com

Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 12/6/2020 7:48:32 PM arc.liv.ac.uk * 2 12/6/2020 7:48:32 PM arc.liv.ac.uk bhmhub2.liv.ac.uk esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) * 3 12/6/2020 7:48:32 PM localhost bhmhub2.liv.ac.uk esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) * 4 12/6/2020 7:48:32 PM bhmhub2.liv.ac.uk bhmx2.liv.ac.uk esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) * 5 12/6/2020 7:48:33 PM bhmx2.liv.ac.uk sophxr.liv.ac.uk ESMTP 1 sec 6 12/6/2020 7:48:33 PM sophxr.liv.ac.uk localhost SMTP * 7 12/6/2020 7:48:34 PM sophxr.liv.ac.uk BN8NAM11FT068.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 8 12/6/2020 7:48:34 PM BN8NAM11FT068.eop-nam11.prod.protection.outlook.com BN6PR17CA0033.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) * 9 12/6/2020 7:48:34 PM BN6PR17CA0033.namprd17.prod.outlook.com BYAPR05MB6358.namprd05.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *

Original Message Headers

Received: from BN6PR17CA0033.namprd17.prod.outlook.com (2603:10b6:405:75::22)

by BYAPR05MB6358.namprd05.prod.outlook.com (2603:10b6:a03:e4::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3654.11; Sun, 6 Dec 2020 19:48:34 +0000

Received: from BN8NAM11FT068.eop-nam11.prod.protection.outlook.com

(2603:10b6:405:75:cafe::c8) by BN6PR17CA0033.outlook.office365.com (2603:10b6:405:75::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3632.17 via Frontend Transport; Sun, 6 Dec 2020 19:48:34 +0000

Authentication-Results: spf=pass (sender IP is 138.253.100.180)

smtp.mailfrom=liverpool.ac.uk; ehciss.onmicrosoft.com; dkim=none (message not signed) header.d=none;ehciss.onmicrosoft.com; dmarc=pass action=none header.from=liverpool.ac.uk;

Received-SPF: Pass (protection.outlook.com: domain of liverpool.ac.uk

designates 138.253.100.180 as permitted sender) receiver=protection.outlook.com; client-ip=138.253.100.180; helo=sophxr.liv.ac.uk;

Received: from sophxr.liv.ac.uk (138.253.100.180) by

BN8NAM11FT068.mail.protection.outlook.com (10.13.177.69) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3632.17 via Frontend Transport; Sun, 6 Dec 2020 19:48:34 +0000

Received: from sophxr.liv.ac.uk (localhost [127.0.0.1])

by localhost (Postfix) with SMTP id 18EAC1201F7 for <postmaster@…>; Sun, 6 Dec 2020 19:48:33 +0000 (GMT)

Received: from bhmx2.liv.ac.uk (bhmx2.liv.ac.uk [138.253.100.156])

by sophxr.liv.ac.uk (Postfix) with ESMTP id 0B00A120253 for <postmaster@…>; Sun, 6 Dec 2020 19:48:33 +0000 (GMT)

Received: from bhmhub2.liv.ac.uk ([138.253.100.154])

by bhmx2.liv.ac.uk with esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) id 1km01I-00031d-W8 for postmaster@…; Sun, 06 Dec 2020 19:48:32 +0000

Received: from localhost ([127.0.0.1] helo=bhmhub2.liv.ac.uk)

by bhmhub2.liv.ac.uk with esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) id 1km01I-0007F8-VN; Sun, 06 Dec 2020 19:48:32 +0000

Received: from arc.liv.ac.uk ([138.253.242.206])

by bhmhub2.liv.ac.uk with esmtp (Exim 4.92.3) (envelope-from <sge-bugs@…>) id 1km01I-0007Ev-Sa; Sun, 06 Dec 2020 19:48:32 +0000

Received: by arc.liv.ac.uk (Postfix, from userid 33)

id D363F4501; Sun, 6 Dec 2020 19:48:32 +0000 (GMT)

MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "SGE" <sge-bugs@…> X-Trac-Version: 1.0.13 Precedence: bulk CC: sge-bugs@… Auto-Submitted: auto-generated X-Mailer: Trac 1.0.13, by Edgewall Software To: info@…, postmaster@… X-Trac-Project: SGE Date: Sun, 06 Dec 2020 19:48:32 -0000 Reply-To: X-URL: https://arc.liv.ac.uk/trac/SGE Subject: Re: [SGE] #1719: Re: New Purchase Order-030220- SMART SOURCING INC. X-Trac-Ticket-URL: https://arc.liv.ac.uk/trac/SGE/ticket/1719 Message-ID: <080.40c4ac6f9790c40b823d27515e9d21e1@…> References: <065.3a19984644b7198841a93b18077daba6@…> X-Trac-Ticket-ID: 1719 In-Reply-To: <065.3a19984644b7198841a93b18077daba6@…> Return-Path: sge-bugs@… X-EOPAttributedMessage: 0 X-EOPTenantAttributedMessage: 591a7d31-4300-4fc5-ab7c-aaad0ceb2756:0 X-MS-PublicTrafficType?: Email X-MS-Office365-Filtering-Correlation-Id: 6261652e-f7b3-4279-bad1-08d89a1fea95 X-MS-TrafficTypeDiagnostic?: BYAPR05MB6358:

untitled-part.bin

untitled-part.mht

#1719: Re: New Purchase Order-030220- SMART SOURCING INC.


Reporter: info@… | Owner:

Type: defect | Status: new

Priority: normal | Milestone:

Component: sge | Version: 8.1.9

Severity: minor | Resolution: Keywords: |


Changes (by postmaster@…):

  • Attachment "untitled-part-46.bin" removed.

Added by email2trac

-- Ticket URL: <https://arc.liv.ac.uk/trac/SGE/ticket/1719> SGE <https://arc.liv.ac.uk/trac/SGE> Son of Grid Engine: Community continuation of work on Grid Engine

Note: See TracQuery for help on using queries.