Doing an Office 365 Migration
-
I recall the thread here on ML, it only mentioned being able to do 500, there were no instructions.
As far as Spiceworks is concerned, why are you using relaying? I have an account setup on my Exchange server that SW logs into just like my outlook clients do.
Why would this be any different for O365? Assuming that O365 can doing SMTP/POP3 - your copiers/mopiers should be able to do the same (if you're lucky the device will use IMAP). -
@Dashrender said:
Assuming that O365 can doing SMTP/POP3 - your copiers/mopiers should be able to do the same (if you're lucky the device will use IMAP).
POP3 and IMAP cannot send email, they can only receive. Thinks like Copiers can only use SMTP since they only send mail. And they rarely support the range of security necessary to use Office 365 or any secured Exchange system. So a relay is normally necessary.
-
@scottalanmiller said:
@Dashrender said:
Assuming that O365 can doing SMTP/POP3 - your copiers/mopiers should be able to do the same (if you're lucky the device will use IMAP).
POP3 and IMAP cannot send email, they can only receive. Thinks like Copiers can only use SMTP since they only send mail. And they rarely support the range of security necessary to use Office 365 or any secured Exchange system. So a relay is normally necessary.
OK, I had a misunderstanding (I knew that POP3 didn't send) about IMAP. I thought it took care of both directions.
-
@Dashrender said:
OK, I had a misunderstanding (I knew that POP3 didn't send) about IMAP. I thought it took care of both directions.
By definition, email only exists as SMTP. Any other protocol involved, POP, IMAP, Exchange, etc. is a "mailbox management" protocol. They are used for manipulating email after it has been received. All sending of email is always SMTP and that will never change because it is the use of SMTP that defines something as email.
-
@scottalanmiller said:
@Dashrender said:
OK, I had a misunderstanding (I knew that POP3 didn't send) about IMAP. I thought it took care of both directions.
By definition, email only exists as SMTP. Any other protocol involved, POP, IMAP, Exchange, etc. is a "mailbox management" protocol. They are used for manipulating email after it has been received. All sending of email is always SMTP and that will never change because it is the use of SMTP that defines something as email.
OK.. Ha, I guess I can go home I've learned my thing for the day.
-
The 500 number helps, I highly doubt I will ever get over 100 in a day. I know there was no documentation posted, I was hoping whoever mentioned the 500 would post where they read that
-
@Dashrender said:
As far as Spiceworks is concerned, why are you using relaying? I have an account setup on my Exchange server that SW logs into just like my outlook clients do.
It is logging in now, I was thinking to change that. I do not need to keep an O365 mailbox just for a product that I only use a little.
-
@JaredBusch said:
@Dashrender said:
As far as Spiceworks is concerned, why are you using relaying? I have an account setup on my Exchange server that SW logs into just like my outlook clients do.
It is logging in now, I was thinking to change that. I do not need to keep an O365 mailbox just for a product that I only use a little.
I thought you could have service accounts with O365? no?
-
@Dashrender said:
@JaredBusch said:
@Dashrender said:
As far as Spiceworks is concerned, why are you using relaying? I have an account setup on my Exchange server that SW logs into just like my outlook clients do.
It is logging in now, I was thinking to change that. I do not need to keep an O365 mailbox just for a product that I only use a little.
I thought you could have service accounts with O365? no?
You can, just was aiming for one less is all.
-
That was possibly me mentioning the 500 limit? That's the maximum amount of outbound messages an Office 365 user can send per day.
For a quick and easy internal relay, add the Windows Server SMTP service, configure the IP addresses of the devices you want to relay, then add the authentication components. Just make sure the from: address is set the same as the account the relay's using to authenticate.
-
@JaredBusch said:
@Dashrender said:
@JaredBusch said:
@Dashrender said:
As far as Spiceworks is concerned, why are you using relaying? I have an account setup on my Exchange server that SW logs into just like my outlook clients do.
It is logging in now, I was thinking to change that. I do not need to keep an O365 mailbox just for a product that I only use a little.
I thought you could have service accounts with O365? no?
You can, just was aiming for one less is all.
Unless you have service accounts that need to retrieve mail, you could make a "Companyname Email" [email protected] service account and have everything use that.
-
In the case of Spiceworks, some people do want SW to receive email for mobile tickets.
-
@Nara said:
That was possibly me mentioning the 500 limit? That's the maximum amount of outbound messages an Office 365 user can send per day.
For a quick and easy internal relay, add the Windows Server SMTP service, configure the IP addresses of the devices you want to relay, then add the authentication components. Just make sure the from: address is set the same as the account the relay's using to authenticate.
This is what I did, only without setting it to send everything to O365, just a regular mail relay. Then on the SPF record leave my IP as one that can send mail for my domain. Has worked great so far.
-
@Dashrender said:
In the case of Spiceworks, some people do want SW to receive email for mobile tickets.
SW can log into Office 365 just fine. Mailing in tickets still works for me.
-
@ChristopherO said:
@Dashrender said:
In the case of Spiceworks, some people do want SW to receive email for mobile tickets.
SW can log into Office 365 just fine. Mailing in tickets still works for me.
Yes we always used SW with Office 365. No issues at all.
-
I contacted our mopier vendor (Konica). They showed me how I can put in usernames and passwords and assign ports and require SSL/TLS for SMTP - so my device should be able to send to O365 too.
-
@Dashrender said:
I contacted our mopier vendor (Konica). They showed me how I can put in usernames and passwords and assign ports and require SSL/TLS for SMTP - so my device should be able to send to O365 too.
Awesome.
