Flow does not trigger when testing - power-automate

I have set the trigger for the flow which is when an email arrives in a shared mailbox, it will extract the information in the email. I set the connection to the user who has access to the shared mailbox and entered the email address of the shared mailbox and subfolder of the email. I tested the flow by manually sending email to the shared mailbox sub folder, but the flow did not start. There were no errors either. Does anyone know what is the issue?

Related

Cannot send emails using SES with a DKIM-enabled verified domain

I've looked at similar questions and AWS documentation, but so far I don't know what the issue can be.
In my SES dashboard, I have two verified identities.
example#abc.com
xyz.com (uses easy DKIM and Custom Mail From). All DNS entries have been created.
Using my Laravel 9 application, I'm able to send emails using the verified email address, but using the domain, no errors are thrown, and no email gets delivered either.
Both scenarios use the same IAM user API keys and permissions.
The email I'm using to send from the domain is noreply#xyz.com which is not a real email. And the Custom Mail From I've specified is mail.xyz.com. As I mentioned, I can see all the DNS entries have been created for the domain.

Sending an email using Exchange Web Services on behalf of a distribution group

I have an email account with exchange, i can send and receive emails from that account's email.
This account is a member of a distribution list, i want to be able to send the replies from this account with the address of the distribution list (on behalf of).
I tried to set the Email.From property and that made no difference
I tried to set the Email.Sender property and it gave me at error that this property cannot be changed although it is a set and get.
The account does have permissions to send on behalf of the distribution list.
Please any ideas?
Regards
Yazeed

How to pass msExchArchiveGUID to IMAPISession:OpenMsgStore to access Archive mailbox

I am trying to access user's mailbox as well as archive mailbox using Outlook MAPI. Outlook version is 2013. User's mailbox and archive both are in O365 (Exchange Online)
I am able to access users mailbox. However, access to users archive mailbox fails.
I have user's email address and Archive GUID of the archive mailstore.
Can someone please help me understand how to pass Archive GUID of user's mailbox to IMAPISession:OpenMsgStore.
Thanks,
Pranay
You will need to retrieve the legacy DN and server information from the autodiscover XML (Type == Archive), then construct the store entry id using IExchangeManageStore::CreateStoreEntryID in the same fashion as when opening a delegate mailbox.

How to use a shared Mailbox configured in Lotus Notes to send messages?

I have an application in VB6 using Lotus Notes so send emails to various recipients.
This is a heavy applications that sends daily reports and since it's a rather heavy task, there is a dedicated machine running it.
It has a win user logged in and the Lotus session that is being used, is the one related to the WIN user. Email messages are sent by the user who has a Lotus/Win session.
Now, this user has access to a shared Mailbox in Lotus. I want the email to be sent from this new shared Mailbox. I can do it manualy, and I noticed that the message is sent from the main email of this shared mailbox but is adds below it the fiedl "sent from UserX".
This is the situation that I want to automate.
I've this (VB6) code:
'Start a session to notes
Set Session = CreateObject("Notes.NotesSession")
'Get the sessions username and then calculate the mail file name
UserName = Session.UserName
MailDbName = Left(UserName, 1) & Right(UserName, (Len(UserName) - InStr(1, UserName, " "))) & ".nsf"
'Open the mail database in notes
Set Maildb = Session.GETDATABASE("", MailDbName)
I think I need to change this last line where I choose the MailDbName.
Can anyone give me some guideance, please?
Thank you.
The MailDbName is a string that contains the path and filename of the mail database within the server, for example "mail/user.nsf". In this case, the server is local, since the first parameter of the GETDATABASE method is passing an empty string. You can replace that with a server name if the database is on the server.
If you open the shared mail database and look at File > Database > Properties you can see the server and file path information and use that in this method call.
However, if the email is sent programmatically, you may need to check out this tip on how to make the "From" appear as someone different.

Magento incoming mail (replies) going to wrong email SMTP issue?

I have a client that keeps getting the customer service reply to emails in his mail box when they should be going to the customer service email. I've searched everywhere for record of his email and it is nowhere. I am guessing now that because the customer service emails are of a different domain the replies are getting marked as spam and being sent to the server admin account instead. I have downloaded this extension: http://www.magentocommerce.com/magento-connect/ASchroder/extension/1865/aschroder.com-smtp-pro. Would a different domain email be SMTP? Advice appreciated.
We had this problem with a few of our recipients as well.
Mainly Comcast users and Century Link to name a few. What the problem is, is that you are sending from (for example) www-data#thisdomain (this will be the machines domain name ie. www-data#WebServer01) -- in the header, regardless of who is in the FROM field. Your actual domain in the FROM field is customer_service#yourstoredomain.com. You will need to do one of two things.
If you host the Magento install on your own operating system and you have control of it, you'll need to change the machines hostname to match that of your web domain name. ie yourwebsite.com.
If that isn't an option, then you will need to use a Magento plugin like the one you mentioned, and have it log in via SMTP to your email service provider (We use Office365) and send the email from a "real" email address that you have created.
The reason this fails is due to the SPF record on the providers (ie Comcast CenturyLink) not allowing emails from a domain that is other than that which is specified in the header. This is usually to prevent spam etc to their customers. So companies like these simply block or, in some cases, redirect that email back to the user at the originating FROM domain.
If at all possible, the easiest route is going to be to try to change the domain in the header of the email. Hopefully you manage your own operating system so you have control over this. IF not, try to see if your hosting provider will provide you access to a "jailed" area so that you can change said settings. The SMTP route is NO FUN ...

Resources