What Are You Doing Right Now
-
FINALLY got our Exchange server to send emails again... New ISP blocks port 25 (thanks for telling us). A little powershell magic and we are up and running again.
-
@RojoLoco said in What Are You Doing Right Now:
FINALLY got our Exchange server to send emails again... New ISP blocks port 25 (thanks for telling us). A little powershell magic and we are up and running again.
Ugh, that sucks.
-
@scottalanmiller said in What Are You Doing Right Now:
@RojoLoco said in What Are You Doing Right Now:
FINALLY got our Exchange server to send emails again... New ISP blocks port 25 (thanks for telling us). A little powershell magic and we are up and running again.
Ugh, that sucks.
I was very near the point of attempting physical assault on a server.
-
Get out there and give @nic some love.
-
@scottalanmiller said in What Are You Doing Right Now:
Get out there and give @nic some love.
He's kicking some ass so far.
Just like Webroot.
-
@scottalanmiller said in What Are You Doing Right Now:
@RojoLoco said in What Are You Doing Right Now:
FINALLY got our Exchange server to send emails again... New ISP blocks port 25 (thanks for telling us). A little powershell magic and we are up and running again.
Ugh, that sucks.
How did a script save this? You sending out a non standard port now? How do you receive email?
-
Finished setting up a Zabbix server vm following @JaredBusch's guide.
-
I have 3-5 hours of trainings/meetings every single day this week. I have no idea how I'm supposed to do my job at all.
-
@Dashrender said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@RojoLoco said in What Are You Doing Right Now:
FINALLY got our Exchange server to send emails again... New ISP blocks port 25 (thanks for telling us). A little powershell magic and we are up and running again.
Ugh, that sucks.
How did a script save this? You sending out a non standard port now? How do you receive email?
We were receiving external mail just fine. After switching our ISP on Friday, we could no longer send on port 25. ISP support lets us know they block all port 25 traffic, so I used PS (well, Exchange Management Shell) to change the port number to 2525. It was just 2 commands:
Get-SendConnector -Identity "SENDCONNECTORNAME" | fl
Set-SendConnector -Identity "SENDCONNECTORNAME" -port 2525
All inbound stuff remains unchanged.
-
@RojoLoco said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@RojoLoco said in What Are You Doing Right Now:
FINALLY got our Exchange server to send emails again... New ISP blocks port 25 (thanks for telling us). A little powershell magic and we are up and running again.
Ugh, that sucks.
How did a script save this? You sending out a non standard port now? How do you receive email?
We were receiving external mail just fine. After switching our ISP on Friday, we could no longer send on port 25. ISP support lets us know they block all port 25 traffic, so I used PS (well, Exchange Management Shell) to change the port number to 2525. It was just 2 commands:
Get-SendConnector -Identity "SENDCONNECTORNAME" | fl
Set-SendConnector -Identity "SENDCONNECTORNAME" -port 2525
All inbound stuff remains unchanged.
Could you wind up with any long term effects caused by this?
-
@Dashrender said in What Are You Doing Right Now:
@RojoLoco said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@RojoLoco said in What Are You Doing Right Now:
FINALLY got our Exchange server to send emails again... New ISP blocks port 25 (thanks for telling us). A little powershell magic and we are up and running again.
Ugh, that sucks.
How did a script save this? You sending out a non standard port now? How do you receive email?
We were receiving external mail just fine. After switching our ISP on Friday, we could no longer send on port 25. ISP support lets us know they block all port 25 traffic, so I used PS (well, Exchange Management Shell) to change the port number to 2525. It was just 2 commands:
Get-SendConnector -Identity "SENDCONNECTORNAME" | fl
Set-SendConnector -Identity "SENDCONNECTORNAME" -port 2525
All inbound stuff remains unchanged.
Could you wind up with any long term effects caused by this?
AFAIK the only long term effect will be being able to send mail to external domains. But I suppose time will tell...
-
@Dashrender said in What Are You Doing Right Now:
@RojoLoco said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@RojoLoco said in What Are You Doing Right Now:
FINALLY got our Exchange server to send emails again... New ISP blocks port 25 (thanks for telling us). A little powershell magic and we are up and running again.
Ugh, that sucks.
How did a script save this? You sending out a non standard port now? How do you receive email?
We were receiving external mail just fine. After switching our ISP on Friday, we could no longer send on port 25. ISP support lets us know they block all port 25 traffic, so I used PS (well, Exchange Management Shell) to change the port number to 2525. It was just 2 commands:
Get-SendConnector -Identity "SENDCONNECTORNAME" | fl
Set-SendConnector -Identity "SENDCONNECTORNAME" -port 2525
All inbound stuff remains unchanged.
Could you wind up with any long term effects caused by this?
Not from any properly configured email server. They'll continue to retry for up to a month. The system was designed for email servers to not be reliable/online.
-
it's possible that a receiving email server could be setup to not accept email coming from a non standard port. This seems highly unlikely, but possible.
A thought that someone might have is, only someone trying to use a consumer class internet connection would be trying to send email out a port other than port 25, therefore anyone who tries to connect on my port 25 from a port other than 25 will be blocked.
This is kinda crazy and leaves so much room for problems, but it's completely possible.
-
@Dashrender said in What Are You Doing Right Now:
it's possible that a receiving email server could be setup to not accept email coming from a non standard port. This seems highly unlikely, but possible.
Hadn't really considered that. Our 2 choices were 2525 or 587, and since we were scrambling, the idea of the nonstandard port getting booted at the other end slipped our minds. I'll keep an eye out, but I'm fairly sure it won't be an issue since we route through a smart host.
-
@RojoLoco said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
it's possible that a receiving email server could be setup to not accept email coming from a non standard port. This seems highly unlikely, but possible.
Hadn't really considered that. Our 2 choices were 2525 or 587, and since we were scrambling, the idea of the nonstandard port getting booted at the other end slipped our minds. I'll keep an eye out, but I'm fairly sure it won't be an issue since we route through a smart host.
aww.. well, then as long as your smart host is working, you should be fine.
Though I have to ask - you have a business class connection that blocks your ability to use a port? WTF? And you're not freaking out on them?
Is it in their contract that you'll send all outgoing email through their servers? Talk about your Man-in-the-Middle!
-
Making plans to attend calling hours for a friend this week. He died Saturday. He was possibly as young as 25, but was probably 26. He had a heart attack and died. My girl and I both knew him pretty well and were both friends with him but for totally independent reasons...it's been a rough weekend...
-
@thanksajdotcom That really sucks. Im sorry for your loss
-
@thanksajdotcom said in What Are You Doing Right Now:
Making plans to attend calling hours for a friend this week. He died Saturday. He was possibly as young as 25, but was probably 26. He had a heart attack and died. My girl and I both knew him pretty well and were both friends with him but for totally independent reasons...it's been a rough weekend...
Oh wow, that really sucks
Sorry for your loss. -
@Dashrender said in What Are You Doing Right Now:
@RojoLoco said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
it's possible that a receiving email server could be setup to not accept email coming from a non standard port. This seems highly unlikely, but possible.
Hadn't really considered that. Our 2 choices were 2525 or 587, and since we were scrambling, the idea of the nonstandard port getting booted at the other end slipped our minds. I'll keep an eye out, but I'm fairly sure it won't be an issue since we route through a smart host.
aww.. well, then as long as your smart host is working, you should be fine.
Though I have to ask - you have a business class connection that blocks your ability to use a port? WTF? And you're not freaking out on them?
Is it in their contract that you'll send all outgoing email through their servers? Talk about your Man-in-the-Middle!
I couldn't agree more, but those decisions are out of my hands. And I would guess that they are using security / spam blockage as a reason to kill port 25. Our smart hosts are through a different (new) company (I think).
-
We just had an awesome side by side posting between two communities. Those are exciting to see because they really put the community to the test in a way that normal posting does not. It's the best test that I know of both activity and technical expertise. And the result... eighteen posts on ML to zero there. And the answer was determined here before any posts happened there. Not a big thing, but it's very encouraging that the activity and quality level here are staying high and keeping pace like they should.
