Mac Users...
-
@BBigford said:
@scottalanmiller said:
That's for generic relay, if you want authenticated relay, you can do more config steps and make Postfix sign into O365 or Gmail or whatever.
I can see how the Linux relay could point to O365, I'm having difficulty seeing how a copier would point to the Linux relay. Like if you had 2 copiers, and 2 different relays (maybe not practical, just seeing how you could have a copier be pointed at that specific relay).
Well, HOW do you point it to your relay now? Nothing would change there. And using two relays, while REALLY weird, is super simple.
-
@scottalanmiller said:
@BBigford said:
So then when you scan to email from the copier... it's going to look on the local LAN for 25, find the Linux relay, the relay points to the hosted instance of Exchange...?
It works the same as it does now. Which is it looks to the server and the server relays the message on. Nothing changes at all in how it works. Just Postfix instead of Exchange.
Ok, so the copier is seeing the Postfix server instead of Exchange, but then Postfix just forwards it on to the hosted Exchange instance?
-
@BBigford said:
@scottalanmiller said:
@BBigford said:
So then when you scan to email from the copier... it's going to look on the local LAN for 25, find the Linux relay, the relay points to the hosted instance of Exchange...?
It works the same as it does now. Which is it looks to the server and the server relays the message on. Nothing changes at all in how it works. Just Postfix instead of Exchange.
Ok, so the copier is seeing the Postfix server instead of Exchange, but then Postfix just forwards it on to the hosted Exchange instance?
Postfix sends it to whatever email address it's told to send to. That's what Exchange is doing now.
-
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
That's for generic relay, if you want authenticated relay, you can do more config steps and make Postfix sign into O365 or Gmail or whatever.
I can see how the Linux relay could point to O365, I'm having difficulty seeing how a copier would point to the Linux relay. Like if you had 2 copiers, and 2 different relays (maybe not practical, just seeing how you could have a copier be pointed at that specific relay).
Well, HOW do you point it to your relay now? Nothing would change there. And using two relays, while REALLY weird, is super simple.
There's an option in our Konicas that you to put in the server's FQDN. I guess you could just enter that Linux server in there...
-
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
That's for generic relay, if you want authenticated relay, you can do more config steps and make Postfix sign into O365 or Gmail or whatever.
I can see how the Linux relay could point to O365, I'm having difficulty seeing how a copier would point to the Linux relay. Like if you had 2 copiers, and 2 different relays (maybe not practical, just seeing how you could have a copier be pointed at that specific relay).
Well, HOW do you point it to your relay now? Nothing would change there. And using two relays, while REALLY weird, is super simple.
There's an option in our Konicas that you to put in the server's FQDN. I guess you could just enter that Linux server in there...
Sure.
But you said that you have a relay now. How is that working? How is the copier finding the Exchange server today?
-
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
That's for generic relay, if you want authenticated relay, you can do more config steps and make Postfix sign into O365 or Gmail or whatever.
I can see how the Linux relay could point to O365, I'm having difficulty seeing how a copier would point to the Linux relay. Like if you had 2 copiers, and 2 different relays (maybe not practical, just seeing how you could have a copier be pointed at that specific relay).
Well, HOW do you point it to your relay now? Nothing would change there. And using two relays, while REALLY weird, is super simple.
There's an option in our Konicas that you to put in the server's FQDN. I guess you could just enter that Linux server in there...
Sure.
But you said that you have a relay now. How is that working? How is the copier finding the Exchange server today?
Pretty janky actually. We have an older 2007 Exchange server, and a newer 2013 Exchange server. Old server has receive relay from a variety of IPs (copiers are included), then forwards off to the newer Exchange server if the message has to continue on. Hoping we get enough money and time this summer to dump the old instance, stand up a second 2013 instance and configure a DAG for balance/failover. Would be nice to have 2 servers on the same version.
Edit: It's more of a time matter, we've already had the funding set aside for a while since it doesn't cost that much.
-
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?
-
Why not replace that old Exchange machine with Postfix today? What's the purpose for keeping something old like that around?
-
@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...
-
@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.
-
Oh, and there were a few instances where a failed user migration completely locked up Exchange for about 10 hours. So the admin that usually does those transfers was pretty leary about doing such large transfers at one time again.
-
@scottalanmiller How do you transfer large amounts of users from one Exchange instance to the other, or do you not?
-
@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?
-
@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.
