I’m trying to move our SMTP from our on premise exchange to O365…
I’m trying to use smtp.outlook365 as the SMTP host, ive tried port 25 and 587 but nothing works..
someone mentioned that they used a mail.protection.outlook.com host and port 25 which sort of works for internal addresses but i still cant send external…
has anyone successfully got this working? what settings have you used?
Thanks,
Mick.
Page 1 / 1
Hi @MickD ,
What exactly is the error that you see in the application messages? Office 365 outbound emails would need to use “smtp.office365.com” as the SMTP_HOST and should have “USE_TLS” checked. your “USER_NAME” and “DEFAULT_MAIL_SENDER” should both map to a valid O365 account with “PERFORM_SMTP_AUTH” checked.
One thing to note is that O365 will not allow this account to relay email for other senders. So the “FROM” address for your email notifications should always match the address defined in “USER_NAME”.
Cheers
We migrated to O365 from on prem Exchange a little while back and have it working nicely.
Config below.
Our mail is set to only work with an authenticated account, so we have an Exchange account exclusively to allow IFS to send emails i.e. we don’t allow anonymous sending.
Hi @MickD ,
What exactly is the error that you see in the application messages? Office 365 outbound emails would need to use “smtp.office365.com” as the SMTP_HOST and should have “USE_TLS” checked. your “USER_NAME” and “DEFAULT_MAIL_SENDER” should both map to a valid O365 account with “PERFORM_SMTP_AUTH” checked.
One thing to note is that O365 will not allow this account to relay email for other senders. So the “FROM” address for your email notifications should always match the address defined in “USER_NAME”.
Cheers
Sajith,
Thanks for your reply.
If I configure our mail sender like this then nothing happens, no error ( that I can see ? ), then when I change it back to our on premise exchange server all the emals that I sent will then be delivered..
One thing that may be an issue, currently we haven’t got SSL enabled on either of our environments, does this need to be enabled for this to work?
Mick.
We migrated to O365 from on prem Exchange a little while back and have it working nicely.
Config below.
Our mail is set to only work with an authenticated account, so we have an Exchange account exclusively to allow IFS to send emails i.e. we don’t allow anonymous sending.
Garak,
Thanks for your reply.
As per my reply to Sajith if I configure the mail sender like this then nothing happens, no error the Emails just aren’t sent, then when I configure it to use our on site exchange server then all the emails get delivered.. also as mentioned could it be the SSL that is the issue?
Thanks,
Mick.
Hi @MickD ,
Quite strange that you are not seeing anything in the Application Messages? Do all the messages go in to the status Finished/Transferred? If there is an error with the message they should go in to Waiting and eventually Error.
Not having SSL in your apps environment shouldn't really cause any issues as far as i can see but probably worth checking up on. If that is the case, you should most probably see some sort of an SSL related error in the Application messages though.
Cheers.
Hi @MickD ,
Quite strange that you are not seeing anything in the Application Messages? Do all the messages go in to the status Finished/Transferred? If there is an error with the message they should go in to Waiting and eventually Error.
Not having SSL in your apps environment shouldn't really cause any issues as far as i can see but probably worth checking up on. If that is the case, you should most probably see some sort of an SSL related error in the Application messages though.
Cheers.
Thanks for your reply.
I couldn’t remember what the status was ( if any ) so i retried… and get the following error ( stopped at a Waiting Status )
I’ve checked the username and password and these are definitely correct..
I’ll continue to look at this.
Thanks,
Mick.
Hi @MickD ,
If i’m not mistaken this is caused by having the sender address in your email notification different from the account you are using in the Connect sender.
One way to work around this would be to make sure that you always have a single sender for any emails going out of the system. I.e. If you are using “ifsadmin@mydomain.com” as your email user in your connect sender, assign the same address to the IFSADMIN user account as its email address. Then you use IFSADMIN in the FROM field in all your email events so that the from email address will always be “ifsadmin@mydomain.com”
Cheers
I am unable to get IFS to send emails. All my ricoh printers/scanners are working great with the same credentials.
It describes how you can set up a connector between o365 and your own mail server, but you can use the connector as a relay directly from IFS. Just tested it with our own Apps 9 installation.
As you can see, you don’t need user name and password for this configuration. Depending on your security needs, this could be a solution for you.
We only use O365, we don’t have an onsite exchange server. We currently use that setup with port 25 but many of the emails from IFS are getting block by a SPAM filter or going to a junk folder because we are not using a legit O365 account. This should be easy to setup in that Microsoft is a known email provider and many people use O365 online.
Hi! Has anyone got this to work properly yet? Also on Apps9 trying to switch to O365.
Job stuck at Waiting state with Error while sending data… Error Text. Which is not very helpful.
Thanks,
Kasia
Hi,
OK looking at this again as it dropped off the importance at the time, but now with the recent Exchange vulnerabilities its come to the top of my list to retire our on site mail server…
So testing again… and have setup the username and also default mail sender as my email account etc.. but still it won’t send… when i look at the application message it still looks as though ifsevent is still trying to send the email… so my question is where else could this be set..? this must have been setup by IFS when the system was installed as I can’t find any record of this user…
Any ideas?
Thanks,
Mick.
Hey @MickD exactly why I am doing it also!
Check if SMTP is enabled for that user/email account specified in Setup - think you can check that in O365 admin center.
Also restart your connect service when you make a change in your test environment to see if it worked.
Thanks,
Kasia
Is it possible that you need to whitelist your IFS server(s) on the o365 mail environment, or allow it to be used as a mail relay by your IFS server/account? That’s essentially what you are doing (relaying off your mail server) and that is typically secured.
Not my area of expertise, but whenever we set up a new server internally to redirect off our mail server we need to do some changes on the mail server side to allow the connection/relay.
HTH,
Nick
Nick,
Do you have anymore information on this, ie. what you did exactly to get this working? I’ve asked the guys that look after our O365 install and they say its all setup OK. so just wanted to check what we need to look at.
There would be a lot of things that might be needed or could be wrong, but nothing overly complicated. I am assuming the sender email address domain and any credentials and you are using in the IFS email connector (e.g. MAIL_SENDER1) are valid.
HTH,
Nick
Hi,
I’m new to IFS and really struggling to get the mail sender (IFS Connect) working with Exchange Online. We are on Apps 10.
I’ve configured the sender as mentioned above :
The user and default_mail_sender are both the email address of the 365 mailbox account.
The online mailbox has SMTP Auth enabled and SmtpClientAuthenticationDisabled set to false.
I can login to this account on OWA, using the username and password from the sender config, but when I send a report via the connector, it always fails with javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful
I’ve checked on Azure against the user logins, but there is nothing showing for failed attempts, either interactive or non-interactive.
I’ve tried connecting to smtp.office365.com from the middleware server via telnet, and that works fine.
Does anyone have any suggestions of what else to check?
Thanks
Try going into Exchange Admin and select the user that is wanting to send the Email…
Then in Mailbox delegation add the account of the default mail sender into the Send As…
This worked for us following advice from another member.
Once you make the changes, give it a while took sometime for the changes to take effect with us.
Mick.
Yes +1 for @MickD’s note about the mailbox delegations. I forgot about that in my post above.