Mac Users...
-
@BBigford said:
@scottalanmiller said:
But that doesn't explain how the copiers POINT to the Exchange 2007 instance. How do they send the email to it in the first place? IP address?
Uses the hostname instead of IP... Some of the settings I've saw in the config:
Server FQDN: exchange-server.domain.com (older server with relay configured)
Server Port: 25
From Address: [email protected] (has a resource mailbox in Exchange, with a password to authenticate)I can't think of any other settings off the top of my head...
Right... so what are the questions about how to do this with a Linux relay? You already have a dedicated relay. It's just swapping out the name of the OS and the cost and stability involved. Nothing "changes." You are already doing everything as if you had a Linux relay.
-
@Dashrender said:
@scottalanmiller said:
Why not replace that old Exchange machine with Postfix today? What's the purpose for keeping something old like that around?
Better yet, why have a second one at all?
I don't have much say in that area. I'm told to setup a second instance in the summer, as a failover should one go down for some reason (power outage, building gets flooded, etc), they are about 5 hours apart geographically.
-
@BBigford said:
@scottalanmiller said:
Why not replace that old Exchange machine with Postfix today? What's the purpose for keeping something old like that around?
It's more time than cost.. The CALs aren't expensive. It's definitely not sticking around for functionality. We are stretched pretty thin so we have enough time to do about 10 users per month. Some users have like 50GB mailboxes so trying to migrate them runs for a long time then fails everyone after them. So we identify the larger mailboxes and run those on their own. I've increased the sizes on the new databases to unlimited for the transfer size (I think they were defaulted to about 2GB) and all of them pass fine except ones that are over about 10-20GB.
No users involved in a relay, though. Are you saying that the relay still has users on it, too?
-
@BBigford said:
@scottalanmiller How do you transfer large amounts of users from one Exchange instance to the other, or do you not?
We do all the time, but not me personally
-
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
But that doesn't explain how the copiers POINT to the Exchange 2007 instance. How do they send the email to it in the first place? IP address?
Uses the hostname instead of IP... Some of the settings I've saw in the config:
Server FQDN: exchange-server.domain.com (older server with relay configured)
Server Port: 25
From Address: [email protected] (has a resource mailbox in Exchange, with a password to authenticate)I can't think of any other settings off the top of my head...
Right... so what are the questions about how to do this with a Linux relay? You already have a dedicated relay. It's just swapping out the name of the OS and the cost and stability involved. Nothing "changes." You are already doing everything as if you had a Linux relay.
There's no more confusion. You answered it way up the thread already.
I just didn't know how the Linux relay tied to hosted Exchange, but you already said you can define that in the relay by entering credentials for the hosted instance.
-
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
Why not replace that old Exchange machine with Postfix today? What's the purpose for keeping something old like that around?
It's more time than cost.. The CALs aren't expensive. It's definitely not sticking around for functionality. We are stretched pretty thin so we have enough time to do about 10 users per month. Some users have like 50GB mailboxes so trying to migrate them runs for a long time then fails everyone after them. So we identify the larger mailboxes and run those on their own. I've increased the sizes on the new databases to unlimited for the transfer size (I think they were defaulted to about 2GB) and all of them pass fine except ones that are over about 10-20GB.
No users involved in a relay, though. Are you saying that the relay still has users on it, too?
Yeah, that server just happens to have a relay on it. It isn't acting as just a relay. It has about half of the company still on it.
-
@Dashrender said:
@scottalanmiller said:
Why not replace that old Exchange machine with Postfix today? What's the purpose for keeping something old like that around?
Better yet, why have a second one at all?
Yeah! But the question was more theoretical... what if they wanted to move to hosted, how would the relay work.
-
@scottalanmiller said:
@BBigford said:
@scottalanmiller How do you transfer large amounts of users from one Exchange instance to the other, or do you not?
We do all the time, but not me personally
Haha, any tips for such an instance? Like I said, if we transfer large amounts it seems to lock up Exchange.
-
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
But that doesn't explain how the copiers POINT to the Exchange 2007 instance. How do they send the email to it in the first place? IP address?
Uses the hostname instead of IP... Some of the settings I've saw in the config:
Server FQDN: exchange-server.domain.com (older server with relay configured)
Server Port: 25
From Address: [email protected] (has a resource mailbox in Exchange, with a password to authenticate)I can't think of any other settings off the top of my head...
Right... so what are the questions about how to do this with a Linux relay? You already have a dedicated relay. It's just swapping out the name of the OS and the cost and stability involved. Nothing "changes." You are already doing everything as if you had a Linux relay.
There's no more confusion. You answered it way up the thread already.
I just didn't know how the Linux relay tied to hosted Exchange, but you already said you can define that in the relay by entering credentials for the hosted instance.
They tie through the magic of email
No, you wouldn't really use the credentials, that's pretty silly. You just... relay. Email is WAY simpler than I think you are picturing. None of that is necessary.
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
Why not replace that old Exchange machine with Postfix today? What's the purpose for keeping something old like that around?
Better yet, why have a second one at all?
Yeah! But the question was more theoretical... what if they wanted to move to hosted, how would the relay work.
Also, if we did go to hosted we wouldn't have a second server. One could argue how would an interrupt in a hosted service be any different than having 2 in separate buildings... you would have to assume you'd go with 2 cloud servers, on 2 different providers like DO & AWS for that kind of availability should one provider have an issue. I wouldn't want to do that.
-
@BBigford said:
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
Why not replace that old Exchange machine with Postfix today? What's the purpose for keeping something old like that around?
Better yet, why have a second one at all?
Yeah! But the question was more theoretical... what if they wanted to move to hosted, how would the relay work.
Also, if we did go to hosted we wouldn't have a second server. One could argue how would an interrupt in a hosted service be any different than having 2 in separate buildings... you would have to assume you'd go with 2 cloud servers, on 2 different providers like DO & AWS for that kind of availability should one provider have an issue. I wouldn't want to do that.
That doesn't make sense. The provider already does that. You are doing an apples to oranges comparison. You dont' have a second IT department running a second HA Exchange cluster for you now... why would you need one in the future?
-
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
But that doesn't explain how the copiers POINT to the Exchange 2007 instance. How do they send the email to it in the first place? IP address?
Uses the hostname instead of IP... Some of the settings I've saw in the config:
Server FQDN: exchange-server.domain.com (older server with relay configured)
Server Port: 25
From Address: [email protected] (has a resource mailbox in Exchange, with a password to authenticate)I can't think of any other settings off the top of my head...
Right... so what are the questions about how to do this with a Linux relay? You already have a dedicated relay. It's just swapping out the name of the OS and the cost and stability involved. Nothing "changes." You are already doing everything as if you had a Linux relay.
There's no more confusion. You answered it way up the thread already.
I just didn't know how the Linux relay tied to hosted Exchange, but you already said you can define that in the relay by entering credentials for the hosted instance.
They tie through the magic of email
No, you wouldn't really use the credentials, that's pretty silly. You just... relay. Email is WAY simpler than I think you are picturing. None of that is necessary.
ok, so you point the Linux relay at the IP issued to the O365 instance, with a transport rule setup on the O365 instance to accept the traffic from the relay?
-
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
Why not replace that old Exchange machine with Postfix today? What's the purpose for keeping something old like that around?
Better yet, why have a second one at all?
Yeah! But the question was more theoretical... what if they wanted to move to hosted, how would the relay work.
Also, if we did go to hosted we wouldn't have a second server. One could argue how would an interrupt in a hosted service be any different than having 2 in separate buildings... you would have to assume you'd go with 2 cloud servers, on 2 different providers like DO & AWS for that kind of availability should one provider have an issue. I wouldn't want to do that.
That doesn't make sense. The provider already does that. You are doing an apples to oranges comparison. You dont' have a second IT department running a second HA Exchange cluster for you now... why would you need one in the future?
Sorry, I meant if we could go to the cloud instead of setting up a second Exchange server in another building. I would rather not do any of that (cloud or in a second building).
-
One Exchange server is quite enough.
-
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
But that doesn't explain how the copiers POINT to the Exchange 2007 instance. How do they send the email to it in the first place? IP address?
Uses the hostname instead of IP... Some of the settings I've saw in the config:
Server FQDN: exchange-server.domain.com (older server with relay configured)
Server Port: 25
From Address: [email protected] (has a resource mailbox in Exchange, with a password to authenticate)I can't think of any other settings off the top of my head...
Right... so what are the questions about how to do this with a Linux relay? You already have a dedicated relay. It's just swapping out the name of the OS and the cost and stability involved. Nothing "changes." You are already doing everything as if you had a Linux relay.
There's no more confusion. You answered it way up the thread already.
I just didn't know how the Linux relay tied to hosted Exchange, but you already said you can define that in the relay by entering credentials for the hosted instance.
They tie through the magic of email
No, you wouldn't really use the credentials, that's pretty silly. You just... relay. Email is WAY simpler than I think you are picturing. None of that is necessary.
ok, so you point the Linux relay at the IP issued to the O365 instance, with a transport rule setup on the O365 instance to accept the traffic from the relay?
No... still way too complex. You do nothing. I literally listed all of the steps.
Email doesn't need any of those things. It doesn't get pointed anywhere.
-
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
But that doesn't explain how the copiers POINT to the Exchange 2007 instance. How do they send the email to it in the first place? IP address?
Uses the hostname instead of IP... Some of the settings I've saw in the config:
Server FQDN: exchange-server.domain.com (older server with relay configured)
Server Port: 25
From Address: [email protected] (has a resource mailbox in Exchange, with a password to authenticate)I can't think of any other settings off the top of my head...
Right... so what are the questions about how to do this with a Linux relay? You already have a dedicated relay. It's just swapping out the name of the OS and the cost and stability involved. Nothing "changes." You are already doing everything as if you had a Linux relay.
There's no more confusion. You answered it way up the thread already.
I just didn't know how the Linux relay tied to hosted Exchange, but you already said you can define that in the relay by entering credentials for the hosted instance.
They tie through the magic of email
No, you wouldn't really use the credentials, that's pretty silly. You just... relay. Email is WAY simpler than I think you are picturing. None of that is necessary.
ok, so you point the Linux relay at the IP issued to the O365 instance, with a transport rule setup on the O365 instance to accept the traffic from the relay?
No... still way too complex. You do nothing. I literally listed all of the steps.
Email doesn't need any of those things. It doesn't get pointed anywhere.
How would the Linux relay know how to pass on the traffic from the copier to the hosted Exchange instance then...?
-
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
Why not replace that old Exchange machine with Postfix today? What's the purpose for keeping something old like that around?
Better yet, why have a second one at all?
Yeah! But the question was more theoretical... what if they wanted to move to hosted, how would the relay work.
Also, if we did go to hosted we wouldn't have a second server. One could argue how would an interrupt in a hosted service be any different than having 2 in separate buildings... you would have to assume you'd go with 2 cloud servers, on 2 different providers like DO & AWS for that kind of availability should one provider have an issue. I wouldn't want to do that.
That doesn't make sense. The provider already does that. You are doing an apples to oranges comparison. You dont' have a second IT department running a second HA Exchange cluster for you now... why would you need one in the future?
Sorry, I meant if we could go to the cloud instead of setting up a second Exchange server in another building. I would rather not do any of that (cloud or in a second building).
No... but if you go cloud (enterprise cloud) you are getting DAG clusters, multiple buildings, etc. That's all built in.
-
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
But that doesn't explain how the copiers POINT to the Exchange 2007 instance. How do they send the email to it in the first place? IP address?
Uses the hostname instead of IP... Some of the settings I've saw in the config:
Server FQDN: exchange-server.domain.com (older server with relay configured)
Server Port: 25
From Address: [email protected] (has a resource mailbox in Exchange, with a password to authenticate)I can't think of any other settings off the top of my head...
Right... so what are the questions about how to do this with a Linux relay? You already have a dedicated relay. It's just swapping out the name of the OS and the cost and stability involved. Nothing "changes." You are already doing everything as if you had a Linux relay.
There's no more confusion. You answered it way up the thread already.
I just didn't know how the Linux relay tied to hosted Exchange, but you already said you can define that in the relay by entering credentials for the hosted instance.
They tie through the magic of email
No, you wouldn't really use the credentials, that's pretty silly. You just... relay. Email is WAY simpler than I think you are picturing. None of that is necessary.
ok, so you point the Linux relay at the IP issued to the O365 instance, with a transport rule setup on the O365 instance to accept the traffic from the relay?
No... still way too complex. You do nothing. I literally listed all of the steps.
Email doesn't need any of those things. It doesn't get pointed anywhere.
How would the Linux relay know how to pass on the traffic from the copier to the hosted Exchange instance then...?
How does email ever get to where it is going? It just sends the email. It looks up the server's MX record. It's how every email everywhere gets delivered.
-
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
But that doesn't explain how the copiers POINT to the Exchange 2007 instance. How do they send the email to it in the first place? IP address?
Uses the hostname instead of IP... Some of the settings I've saw in the config:
Server FQDN: exchange-server.domain.com (older server with relay configured)
Server Port: 25
From Address: [email protected] (has a resource mailbox in Exchange, with a password to authenticate)I can't think of any other settings off the top of my head...
Right... so what are the questions about how to do this with a Linux relay? You already have a dedicated relay. It's just swapping out the name of the OS and the cost and stability involved. Nothing "changes." You are already doing everything as if you had a Linux relay.
There's no more confusion. You answered it way up the thread already.
I just didn't know how the Linux relay tied to hosted Exchange, but you already said you can define that in the relay by entering credentials for the hosted instance.
They tie through the magic of email
No, you wouldn't really use the credentials, that's pretty silly. You just... relay. Email is WAY simpler than I think you are picturing. None of that is necessary.
ok, so you point the Linux relay at the IP issued to the O365 instance, with a transport rule setup on the O365 instance to accept the traffic from the relay?
No... still way too complex. You do nothing. I literally listed all of the steps.
Email doesn't need any of those things. It doesn't get pointed anywhere.
How would the Linux relay know how to pass on the traffic from the copier to the hosted Exchange instance then...?
How does email ever get to where it is going? It just sends the email. It looks up the server's MX record. It's how every email everywhere gets delivered.
Oh ok, so the relay relies on MX records found in DNS?
-
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
But that doesn't explain how the copiers POINT to the Exchange 2007 instance. How do they send the email to it in the first place? IP address?
Uses the hostname instead of IP... Some of the settings I've saw in the config:
Server FQDN: exchange-server.domain.com (older server with relay configured)
Server Port: 25
From Address: [email protected] (has a resource mailbox in Exchange, with a password to authenticate)I can't think of any other settings off the top of my head...
Right... so what are the questions about how to do this with a Linux relay? You already have a dedicated relay. It's just swapping out the name of the OS and the cost and stability involved. Nothing "changes." You are already doing everything as if you had a Linux relay.
There's no more confusion. You answered it way up the thread already.
I just didn't know how the Linux relay tied to hosted Exchange, but you already said you can define that in the relay by entering credentials for the hosted instance.
They tie through the magic of email
No, you wouldn't really use the credentials, that's pretty silly. You just... relay. Email is WAY simpler than I think you are picturing. None of that is necessary.
ok, so you point the Linux relay at the IP issued to the O365 instance, with a transport rule setup on the O365 instance to accept the traffic from the relay?
No... still way too complex. You do nothing. I literally listed all of the steps.
Email doesn't need any of those things. It doesn't get pointed anywhere.
How would the Linux relay know how to pass on the traffic from the copier to the hosted Exchange instance then...?
How does email ever get to where it is going? It just sends the email. It looks up the server's MX record. It's how every email everywhere gets delivered.
Oh ok, so the relay relies on MX records found in DNS?
Of course, that's how all email is sent that is not internal to the server itself, which wouldn't actually be email. So to simplify... yes, that is how all email is sent.
