[sims] Sims Finance and Remittance emails sending problem

[browolf]

So...sims finance used to use a (Cleo) open relay and everything worked fine. That old relay got decommissioned and sending remittances hasn't worked since.

 

I said, "we've got our own smtp relay, lets use that instead whilst BTLancs figure out what to do. "

 

Then I found out that our relay wasn't working and there's 3000 emails stuck in the outbox.

 

I've managed to fix our relay and lots of staff got lots of old voicemails. Naturally nobody had mentioned email voicemails had stopped working. Test emails using Blat also work.

 

Sims finance still isn't working and is now creating bad email logs.

 

This is in the bad email log file:

Diagnostic-Code: smtp;554 5.2.0 STOREDRV.Submission.Exception:SendAsDeniedException.MapiExceptionSendAsDenied; Failed to process message due to a permanent exception with message Cannot submit message.

 

Our smtp relay links to office 365.

 

I suspect sims finance is trying to send emails in a way that office365 doesn't like.

 

this is the whole bad mail log with privatized addresses. What is everyone else (in lancashire) doing?

 

From: [email protected]
To: [email protected]
Date: Fri, 19 Jul 2019 13:10:20 +0100
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="9B095B5ADSN=_01D53E2977752CF300000001RMM01.school"
X-DSNContext: 7ce717b1 - 1196 - 00000002 - 00000000
Message-ID: 
Subject: Delivery Status Notification (Failure)

This is a MIME-formatted message.  
Portions of this message may be unreadable without a MIME-capable mail program.

--9B095B5ADSN=_01D53E2977752CF300000001RMM01.school
Content-Type: text/plain; charset=unicode-1-1-utf-7

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

      [email protected]




--9B095B5ADSN=_01D53E2977752CF300000001RMM01.school
Content-Type: message/delivery-status

Reporting-MTA: dns;RMM01.school.lancs.sch.uk
Received-From-MTA: dns;LAP-89.school.lancs.sch.uk
Arrival-Date: Fri, 19 Jul 2019 13:10:17 +0100

Final-Recipient: rfc822;[email protected]
Action: failed
Status: 5.2.0
Diagnostic-Code: smtp;554 5.2.0 STOREDRV.Submission.Exception:SendAsDeniedException.MapiExceptionSendAsDenied; Failed to process message due to a permanent exception with message Cannot submit message. 0.35250:0A00C082, 1.36674:0A000000, 1.61250:00000000, 1.45378:02000000, 1.44866:29250000, 1.36674:0E000000, 1.61250:00000000, 1.45378:2E250000, 1.44866:EE010000, 16.55847:E2110000, 17.43559:0000000004020000000000000000000000000000, 20.52176:140F198800001010BE050000, 20.50032:140F1988701700000A00C665, 0.35180:C3050000, 255.23226:02000E84, 255.27962:0A000000, 255.27962:0E000000, 255.31418:80030400, 0.35250:80030400, 1.36674:0A000000, 1.61250:00000000, 1.45378:02000000, 1.44866:82000000, 1.36674:32000000, 1.61250:00000000, 1.45378:87000000, 1.44866:02000000, 16.55847:EE000000, 17.43559:0000000000030000000000003300000000000000, 20.52176:140F1988000070200A001684, 20.50032:140F1988701710101D040000, 0.35180:0A008F83, 255.23226:0A00A381, 255.27962:0A000000, 255.27962:32000000, 255.17082:DC040000, 0.27745:27040000, 4.21921:DC040000, 255.27962:FA000000, 255.1494:2C040000, 0.38698:00000000, 0.37692:0F010480, 0.44092:0D000100, 0.40348:0D000100, 0.34608:0D000100, 0.55056:0D000100, 0.42768:0D000100, 0.56112:0D000100, 0.52807:0D000100, 4.33016:DC040000, 7.40748:010000000000010B0D000100, 7.57132:00000000000000000D000100, 1.63016:32000000, 4.39640:DC040000, 8.45434:55A919E26EFFB64FB449A17DC33DD49800000000, 5.10786:0000000031352E32302E323037332E3030303A4C4E58503132334D42323533383A35623839366537642D636237642D343565662D626337352D36383736363134323662316300201000000000, 255.1750:5E040000, 255.31418:0A00E785, 0.22753:0A002B0E, 255.21817:DC040000, 4.60547:DC040000, 0.21966:0300080E, 4.30158:DC040000 [Hostname=LNXP123MB2538.GBRP123.PROD.OUTLOOK.COM]

--9B095B5ADSN=_01D53E2977752CF300000001RMM01.school
Content-Type: message/rfc822

Received: from LAP-89.school.lancs.sch.uk ([10.77.32.8]) by RMM01.school.lancs.sch.uk with Microsoft SMTPSVC(10.0.14393.2608);
 Fri, 19 Jul 2019 13:10:17 +0100
MIME-Version: 1.0
Date: Fri, 19 Jul 2019 13:10:18 +0100
X-Mailer: Chilkat Software Inc (http://www.chilkatsoft.com)
X-Priority: 3 (Normal)
Subject: Test Message for L ..... College
From: "L .... College" 
To: "LSA ....College" 
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Message-ID: 
Return-Path: [email protected]
X-OriginalArrivalTime: 19 Jul 2019 12:10:17.0918 (UTC) FILETIME=[EDF62DE0:01D53E2A]

Test message from L .... College sent from FMS=
BACS e-mail Remittance advice setup


--9B095B5ADSN=_01D53E2977752CF300000001RMM01.school--

Edited July 19, 2019 by browolf

[localzuk]

The key part there I think is the "MapiExceptionSendAsDenied".

 

So, is the email address you're sending as the same one as the account the relay is working as? Basically, you have to ensure the sending account has the rights to send as that email address.

[caffrey]

Not sure about office 365 but with Gapps I had to add the public IP to the SMTP relay service in the admin interface

[browolf]

The key part there I think is the "MapiExceptionSendAsDenied".

 

So, is the email address you're sending as the same one as the account the relay is working as? Basically, you have to ensure the sending account has the rights to send as that email address.

 

The relay uses the address "[email protected]"

 

I think I've figured it out. In the sims settings is the field "return email address" is being used as the from address. You wouldn't normally want relay as the return email on a remittance. the smtp relay is authenticating as the relay address and then sims is trying to send as a different address. I suppose I could make the relay mailbox forward back to me in case anyone replies to their remittance mail. Thanks

[localzuk]

You can also just give the relay@ account "send as" permissions for the other address. https://docs.microsoft.com/en-us/office365/admin/add-users/give-mailbox-permissions-to-another-user?view=o365-worldwide

[Warwick_Tech]

Hey All,

 

Sorry to hijack the thread, but our FMS doesn't want to send emails on clients, but is fine with the server sending them.

 

I think this is our firewall blocking emails out for client machines (servers get a free pass)

 

without having to go through lines of code and addresses, does anyone know what to allow to let FMS emails specifically through?

 

ATM we just have a blanket ban on all email traffic except office 365

[Cache]

Port 587 to Office 365 (smtp.office365.com).