Reputation
Top tag
Next privilege 250 Rep.
View close votes
Badges
2 14
Impact
~27k people reached

  • 0 posts edited
  • 0 helpful flags
  • 18 votes cast
Feb
11
accepted Using Outlook Anywhere on LAN - Routing Problem
Feb
11
comment Using Outlook Anywhere on LAN - Routing Problem
Our Exchange Server is an SBS 2008 box that hosts everything for the company. Would creating a 1-to-1 NAT cause some security issues? Also, we have four slow DSL lines, each with one external Class A IP address. I'm actually working on a solution where I'll be able to use two or three of our DSL connections to send and receive email instead of just one of them, as is the case now. We send a lot of emails with large attachments.
Feb
11
awarded  Editor
Feb
11
revised Using Outlook Anywhere on LAN - Routing Problem
added 439 characters in body
Feb
10
asked Using Outlook Anywhere on LAN - Routing Problem
Feb
10
comment Exchange Email Server on Multiple DSL Connections (SonicWall TZ-210)
OK Ernie, I gotcha. Thanks
Feb
10
awarded  Commentator
Feb
10
comment Exchange Email Server on Multiple DSL Connections (SonicWall TZ-210)
"I can think of a dozen other reasons to do so as well." - If I understand you correctly you're saying it would be advisable for a large variety of reasons to run the email server elsewhere? How would this help since the outlook clients still have to push/pull the same emails from the server?
Feb
10
accepted Emails From Our Website No Longer Received - hMailServer SMTP Relay
Feb
10
answered Emails From Our Website No Longer Received - hMailServer SMTP Relay
Feb
10
accepted Exchange Email Server on Multiple DSL Connections (SonicWall TZ-210)
Feb
10
comment Exchange Email Server on Multiple DSL Connections (SonicWall TZ-210)
For outgoing email, is the A record necessary?
Feb
10
awarded  Citizen Patrol
Feb
10
comment Exchange Email Server on Multiple DSL Connections (SonicWall TZ-210)
How do the receiving email systems use the PTR record? Do they strip off the subdomain and simply verify that mydomain.com in the PTR record matches the sender's stated email domain in the senders email address?
Feb
10
comment Exchange Email Server on Multiple DSL Connections (SonicWall TZ-210)
PTR is reverse DNS. Many email systems will reject an email that comes from an IP address that has a Reverse DNS name that does not match the email domain for the sent email. Does that make sense? A records deal more with receiving email into our email system which is, well, somewhat relevant. I'm more concerned about sending email I guess, which I did not say in the original post.
Feb
10
comment Exchange Email Server on Multiple DSL Connections (SonicWall TZ-210)
1) Your suggestion to configure 1 DSL for Internet and 3 for Email is spot on, except that it appears you missed the critical point of the post: How do you configure the DSL connections to so that we don't get return failures when using them to send out email? The A records your suggesting won't help.
Feb
10
comment Exchange Email Server on Multiple DSL Connections (SonicWall TZ-210)
The 90% on one connection is because, apparently, 90% of all our traffic is email. Remember, I'm forcing all email to go through X1 which is the one showing the high usage.
Feb
10
asked Exchange Email Server on Multiple DSL Connections (SonicWall TZ-210)
Feb
8
comment Emails From Our Website No Longer Received - hMailServer SMTP Relay
I've resolved this problem by setting up a rule in hMailServer that sends emails for "mydomain.com" directly to our Exchange Server, which is essentially bypassing the Sonicwall router. Do you have a suggestion for how I should close this question?
Feb
8
asked Emails From Our Website No Longer Received - hMailServer SMTP Relay