Using Outlook wrt New email client for Sage X3 workflow notifications post.

Question

Reference: https://www.sagecity.com/us/sage_erp_x3/f/sage-x3-announcements-news-and-alerts/187389/new-email-client-for-sage-x3-workflow-notifications 
 
 I am using a Microsoft Outlook account (assume name as mymail@outlook.com ) which requires FROM to match the email relay's email account used (in this case: mymail@outlook.com ). 
 I switch over to the new email client and did the settings as per the post. 
 The email relay test mail is all OK. 
 
 When I do a direct workflow email 
 
 ``` 
 Application error 
 error : 4 Message failed: 554 5.2.252 SendAsDenied; mymail@outlook.com not allowed to send as a@mycompany.com; STOREDRV.Submission.Exception:SendAsDeniedException.MapiExceptionSendAsDenied; Failed to process message due to a permanent 
 ``` 
 I was login as ADMIN and the workflow email set for this user is: a@mycompany.com 
 
 Previously, I would use a customized YAWRKMEL (based on AWRKMEL script) to resolve this issue by hardcoding in the sender mail address but this script seems to be skipped out. 
 How to resolve this without recommending using other email providers like GMail or installing a dedicated email relay inside the server or setting every user to use the sender email?

Andy S · Accepted Answer

The entry point is only required if you are below V12 patch 33 as the sender email field on the workflow doesn't exist before P33. We have done the solution I posted here for several clients now without issue.

chris h. · Answer

Hello, It's only possible to set up one email in each notification server (authentication) which is a current limitation and already reported as an issue. the Sender email is the only email that is able to send out from the notification server. so if the setup user user (tied to the workflow) is not the notification server sender email. it will fail. the meladx is completely ignored when the notification server is in user. the YAWRKMEL will be ignored as it would typically coincide with the meladx. https://online-help.sageerpx3.com/erp/12/staticpost/notification-servers/?highlight=notificationServer 
 your best bet is to setup a 3rd party SMTP / relay server of some type like hmail, sendgrid, aws, etc... which I think someone already mentioned 
 or you can go back to meladx by turning off notification server.

Andy S · Answer

Hi, 
 AWRKMEL may not run anymore (for obvious reasons), but there is still a workaround to this issue. 
 Since script AWRK still needs to get called to build the message, you can use entry point MESSAGE in script AWRK. The only thing you need to have is a classic user that contains the email of the notification server. Variable USRWRK is the code of the user that triggered the workflow. The script below changes the user that triggered the workflow it to someone else. When it goes to send the email, it takes the email from that new classic user. 
 
 If you add an entry point to script AWRK, your specific script in the entry point can say something like this: 
 --- 
 $ACTION Case ACTION When "MESSAGE" : Gosub MESSAGE When Default Endcase Return 
 $MESSAGE If [F:AWA]CODE = "BLKUSR" #conditional is optional, in this example I say to change only for workflow BLKUSR USRWRK = "MYUSR" #where MYUSR is classic user code containing the email of the notification server. Endif 
 Return 
 --- 
 This was tested in V12 P33 with success. 
 
 Regards, 
 
 Andrew

Andy S · Answer

Have you considered seeing if adding a default value to field SENDMAIL in screen AWA3 so that at least for future created workflows, the Sender line gets filled automatically? Then also add a control to say that the field is both mandatory and must be that email value so when someone goes to modify the workflow, it forces their hand? 
 You can then mass update table AWRKPAR SENDMAIL field with your email and the just have to validate your workflows again. So a bit of pain at the beginning, then smooth sailing afterwards.

chunheng · Answer

For anyone using Sage X3 v12p34 onwards (with latest Syracuse hotfixes), please do add in Sage X3 fully qualified web domain name (without any port number) to the Administration > Global Settings: The mail can not be sent: it contains a link with a domain not allowed 
 Additional information from Sage X3 v12p35: https://online-help.sagex3.com/x3-release-notes/index.html#/release/en-US/2024-r1-35

Sage X3

Using Outlook wrt New email client for Sage X3 workflow notifications post.

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING