Can the SMTP port for the Pop 3 connector in Exchange 2007 be changed?
I'm working with Exchange 2007 on a SBS server and have the SMTP receive connector in Exchange setup for port 26. This is to allow Trend Interscan Virus Wall to handle all in bound SMTP traffic from the Internet as a relay. It accepts Internet mail on port 25, then forwards it to Exchange on port 26.
My problem is the POP3 connector in Exchange, which I'm trying to use to download some external POP3 mailboxes. These will eventually disappear, but for now I need to be able to get the mail from these and get email normally through SMTP as well.
The problem is that with the receive SMTP port in Exchange set for 26, the POP3 connector doesn't work and I can't figure out how to change the SMTP port it uses for forwarding the mail through to Exchange.
Anyone know if that port can be changed? If so, how? If it cannot be changed, then I will resort to something like Popcon.
Thanks,
JimD.
My problem is the POP3 connector in Exchange, which I'm trying to use to download some external POP3 mailboxes. These will eventually disappear, but for now I need to be able to get the mail from these and get email normally through SMTP as well.
The problem is that with the receive SMTP port in Exchange set for 26, the POP3 connector doesn't work and I can't figure out how to change the SMTP port it uses for forwarding the mail through to Exchange.
Anyone know if that port can be changed? If so, how? If it cannot be changed, then I will resort to something like Popcon.
Thanks,
JimD.
ASKER
Sorry, but what the POP3 connector in Exchange does is downloads e-mail from a POP3 server on port 110, then turns around and forwards it to Exchange via SMTP. The port it's doing that though is on port 25. If I leave the Exchange SMTP receive port set on 25, the connector works fine. If I change it to port 26, which is what I need, the connector stops working.
I need to change the SMTP port the connector is sending on.
JimD.
I need to change the SMTP port the connector is sending on.
JimD.
oh i see.
there's a 3rd party tool that can replace your pop3 connector and let you specify the back channel to 26:
http://mybroadband.co.za/vb/showthread.php?67798-Has-anyone-successfully-used-SBS-2003-POP3-connector-to-download-from-a-gmail-account
but, another option is you can add a second ip address to this box, bind one for trendmicro at port 25, bind the other for exchange smtp at port 25... then tell trend micro to pass it to the opposite ip at 25... and your pop3 would work out of the box
i understand the only reason you can't have two things listening on 25 is because you have both installed on the same machine with only one ip address
so one box might have 10.100.1.1 and 10.100.1.2
trendmicro is 10.100.1.2:25
exchange smtp is 10.10.1.1:25
exchange pop3 is 10.10.1.1:110
firewall/router forwards 25 over to 10.100.1.2
firewall/router forwards 110 over to 10.10.10.1
trend forwards clean mail to 10.10.10.1
there's a 3rd party tool that can replace your pop3 connector and let you specify the back channel to 26:
http://mybroadband.co.za/vb/showthread.php?67798-Has-anyone-successfully-used-SBS-2003-POP3-connector-to-download-from-a-gmail-account
but, another option is you can add a second ip address to this box, bind one for trendmicro at port 25, bind the other for exchange smtp at port 25... then tell trend micro to pass it to the opposite ip at 25... and your pop3 would work out of the box
i understand the only reason you can't have two things listening on 25 is because you have both installed on the same machine with only one ip address
so one box might have 10.100.1.1 and 10.100.1.2
trendmicro is 10.100.1.2:25
exchange smtp is 10.10.1.1:25
exchange pop3 is 10.10.1.1:110
firewall/router forwards 25 over to 10.100.1.2
firewall/router forwards 110 over to 10.10.10.1
trend forwards clean mail to 10.10.10.1
I honestly wouldn't change the port this way. Port 25 is EXTREMELY important. Look at getting Forefront - it sounds like a better solution for what your trying to do - much easier!!!
Hope that helps.
Hope that helps.
ASKER
@byron,
<<oh i see. there's a 3rd party tool that can replace your pop3 connector and let you specify the back channel to 26:
http://mybroadband.co.za/vb/showthread.php?67798-Has-anyone-successfully-used-SBS-2003-POP3-connector-to-download-from-a-gmail-account>>
I already have one of those. As I mentioned in my question, my alternative was to use Popcon, a POP 3 connector which like the one you mentioned above, supports changing the SMTP port. I really didn't want to pay for it though as I will only be using it for a week or two at most (hopefully only days) and the project is a bit over budget already. However I felt a bit guilty using the 30 day trial in that way.
But after posting last night and seeing the first couple of responses, I moved ahead with that. Hopefully I'll find a need with which I can justify the purchase of it. However at this point, I've got it all configured and working fine and it will get me over this hump.
Thanks.
@proadmin:
<<I honestly wouldn't change the port this way. Port 25 is EXTREMELY important. >>
This is done all the time for various reasons and unless you have something specific to offer that will give me problems because I've changed the port on the Exchange receive connectors, then I don't find your comment all that helpfull.
As I mentioned to Byron, it's all congifured and everything seems to be working fine. Mail is going in / out from Exchange and being handled by Inter Scan Virus Wall just fine. I've tested the Exchange mailboxes both from a regular Outlook client and Outlook Web Access and I've got nothing in any event logs to tell me that anything is a miss.
If there is a specific concern, I would be glad to hear it.
JimD.
<<oh i see. there's a 3rd party tool that can replace your pop3 connector and let you specify the back channel to 26:
http://mybroadband.co.za/vb/showthread.php?67798-Has-anyone-successfully-used-SBS-2003-POP3-connector-to-download-from-a-gmail-account>>
I already have one of those. As I mentioned in my question, my alternative was to use Popcon, a POP 3 connector which like the one you mentioned above, supports changing the SMTP port. I really didn't want to pay for it though as I will only be using it for a week or two at most (hopefully only days) and the project is a bit over budget already. However I felt a bit guilty using the 30 day trial in that way.
But after posting last night and seeing the first couple of responses, I moved ahead with that. Hopefully I'll find a need with which I can justify the purchase of it. However at this point, I've got it all configured and working fine and it will get me over this hump.
Thanks.
@proadmin:
<<I honestly wouldn't change the port this way. Port 25 is EXTREMELY important. >>
This is done all the time for various reasons and unless you have something specific to offer that will give me problems because I've changed the port on the Exchange receive connectors, then I don't find your comment all that helpfull.
As I mentioned to Byron, it's all congifured and everything seems to be working fine. Mail is going in / out from Exchange and being handled by Inter Scan Virus Wall just fine. I've tested the Exchange mailboxes both from a regular Outlook client and Outlook Web Access and I've got nothing in any event logs to tell me that anything is a miss.
If there is a specific concern, I would be glad to hear it.
JimD.
consider the multiple ip addresses if you need to do this in the future, there's no reason it won't work :)
ASKER
<<consider the multiple ip addresses if you need to do this in the future, there's no reason it won't work :)>>
Actually, I'm not so sure on that. It was late for me last night, so I may be wrong, but I just could not picture how that would solve anything. Remember, both Exchange and Trend ISVW were on the same machine.
You started your solution off with:
so one box might have 10.100.1.1 and 10.100.1.2
trendmicro is 10.100.1.2:25
exchange smtp is 10.10.1.1:25
and I don't have two boxes. Although now that I think about it some more this morning, I do have two NIC's on this box, so I could have setup a second IP and some port forwarding. But that would be a bunch a work and complexity for the simple problem I was trying to resolve (plus having to go physcially on-site), which was to change the SMTP port used by the Exchange POP3 connector. And I'm still not sure that would ultimately solve the problem.
Here's the situation I had:
Exchange in bound SMTP 26 <----- (POP3 connector SMTP out bound 25, POP3 in bound on 110) <----- ISVW <----- ISP POP3 mailbox
only change I needed to make it work was to have the POP3 connector use port 26 for the SMTP hand off to Exchange.
Exchange was setup to use port 26 inbound on SMTP because this is the normal mail setup:
In bound mail: Exchange - SMTP in bound 26 <---- ISVW SMTP in bound 25, Forward to Exchange on port 26<----- Internet
Out bound mail: Exchange - SMTP out bound 25 ---->ISVW SMTP in bound 25, Forward to Internet on port 25 ------> Internet
and as you said, I can't have Exchange and ISVW both living on the same box and both listening on port 25 for incoming SMTP requests.
Jim.
Actually, I'm not so sure on that. It was late for me last night, so I may be wrong, but I just could not picture how that would solve anything. Remember, both Exchange and Trend ISVW were on the same machine.
You started your solution off with:
so one box might have 10.100.1.1 and 10.100.1.2
trendmicro is 10.100.1.2:25
exchange smtp is 10.10.1.1:25
and I don't have two boxes. Although now that I think about it some more this morning, I do have two NIC's on this box, so I could have setup a second IP and some port forwarding. But that would be a bunch a work and complexity for the simple problem I was trying to resolve (plus having to go physcially on-site), which was to change the SMTP port used by the Exchange POP3 connector. And I'm still not sure that would ultimately solve the problem.
Here's the situation I had:
Exchange in bound SMTP 26 <----- (POP3 connector SMTP out bound 25, POP3 in bound on 110) <----- ISVW <----- ISP POP3 mailbox
only change I needed to make it work was to have the POP3 connector use port 26 for the SMTP hand off to Exchange.
Exchange was setup to use port 26 inbound on SMTP because this is the normal mail setup:
In bound mail: Exchange - SMTP in bound 26 <---- ISVW SMTP in bound 25, Forward to Exchange on port 26<----- Internet
Out bound mail: Exchange - SMTP out bound 25 ---->ISVW SMTP in bound 25, Forward to Internet on port 25 ------> Internet
and as you said, I can't have Exchange and ISVW both living on the same box and both listening on port 25 for incoming SMTP requests.
Jim.
ASKER
Now this is weird, I should have gotten 0 points for accepting my own comment. I've got to turn this in as a bug. I think.
JimD.
JimD.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
pop3 uses port 110... which is what your clients use to go get the mail
if you forward your router/firewall port 110 to the exchange server, they'll be able to check their mail, and get it