I have no trouble sending SMTP directly with my SMTP accounts when I am
connected to my network which has an exchange server on it. It does not go
through exchange, it connects directly to the outside server. However, when
I am not connected to my network, I can receive POP3, but cannot send SMTP.
I checked configuration, and there is nothing wrong there. Test emails are
no problem.

"Bruce" <(E-Mail Removed)> wrote in message
news:768C0C19-6005-498F-8AA9-(E-Mail Removed)...
>I have no trouble sending SMTP directly with my SMTP accounts when I am
> connected to my network which has an exchange server on it. It does not
> go
> through exchange, it connects directly to the outside server. However,
> when
> I am not connected to my network, I can receive POP3, but cannot send
> SMTP.
> I checked configuration, and there is nothing wrong there. Test emails
> are
> no problem.


Presumably when "not connected to my network" you are connected to a network
somewhere, otherwise you couldn't receive emails. The usual answer is that
whilst on a different network to your smtp server, you cannot be authorised
to use it. Change your smtp server to one that e.g. uses smtp
authentication so that you can use it regardless of which network your are
on. Get yourself a gmail account and use the gmail smtp server.


--
John Blessing

http://www.LbeHelpdesk.com - Help Desk software priced to suit all
businesses
http://www.room-booking-software.com - Schedule rooms & equipment bookings
for your meeting/class over the web.
http://www.lbetoolbox.com - Remove Duplicates from MS Outlook, find/replace,
send newsletters

Likely when you're "not connected to your network" you're connected to some
other network, and your SMTP server by default isn't allowing people outside
of your network to use their server (which is as it should be).

Two things need to be in place in order for you to use your original SMTP
server from whatever your second network is:

1) Your server must support SMTP authentication

2) The second network must allow users on that network to connect to
external SMTP servers.

With regards to the first point, SMTP servers don't know who you are by
default, they only know where you're coming from, that is they see what IP
address the connection is coming from. The mail administrator configures a
list of IP addresses that are allowed to send mail to external addresses,
called "relaying". Odds are when you're on that second network the IP
address you're connecting from is NOT in that list, so you are unable to
send mail. Your test emails probably work because you're sending mail to
yourself, which is a local address on that network. That wouldn't be a
relay. Using mail.yourisp.com to send mail to (E-Mail Removed) is not a
relay. Using mail.yourisp.com to send mail to (E-Mail Removed) would
be a relay.

Regarding the second point you're probably not running into this issue,
since you can send test emails to yourself. I only bring it up because some
networks (such as SBC/AT&T) restrict SMTP traffic to their own SMTP server,
and drop traffic destined anywhere else. So if you were on AT&T Yahoo DSL
you could send mail using smtp.sbcglobal.yahoo.com, but not using
mail.comcast.net--AT&T's network wouldn't even allow you to connect to
Comcast's mail server directly.

My suggestion is to go into your mail settings where your incoming/outgoing
mail server are and click on the More Settings button, then click the
Outgoing Server tab. Check the box saying the server requires
authentication and try that. If that doesn't work contact the mail
administrator of the server you're trying to use to send mail and ask them
what settings (if any) to use to send mail the way you're trying to.

Joe

"Bruce" <(E-Mail Removed)> wrote in message
news:768C0C19-6005-498F-8AA9-(E-Mail Removed)...
>I have no trouble sending SMTP directly with my SMTP accounts when I am
> connected to my network which has an exchange server on it. It does not
> go
> through exchange, it connects directly to the outside server. However,
> when
> I am not connected to my network, I can receive POP3, but cannot send
> SMTP.
> I checked configuration, and there is nothing wrong there. Test emails
> are
> no problem.

Good discussion, but you should have mentioned that point #2
applies only when the SMTP server uses port 25. Many ISPs now
offer alternate ports which are not blocked, or, if all else fails,
get a Gmail account and do the sending chores with its port 465
SMTP server.

Gary VanderMolen


"Joe Grover" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> Likely when you're "not connected to your network" you're connected to some other network, and your SMTP server by default isn't
> allowing people outside of your network to use their server (which is as it should be).
>
> Two things need to be in place in order for you to use your original SMTP server from whatever your second network is:
>
> 1) Your server must support SMTP authentication
>
> 2) The second network must allow users on that network to connect to external SMTP servers.
>
> With regards to the first point, SMTP servers don't know who you are by default, they only know where you're coming from, that
> is they see what IP address the connection is coming from. The mail administrator configures a list of IP addresses that are
> allowed to send mail to external addresses, called "relaying". Odds are when you're on that second network the IP address
> you're connecting from is NOT in that list, so you are unable to send mail. Your test emails probably work because you're
> sending mail to yourself, which is a local address on that network. That wouldn't be a relay. Using mail.yourisp.com to send
> mail to (E-Mail Removed) is not a relay. Using mail.yourisp.com to send mail to (E-Mail Removed) would be a relay.
>
> Regarding the second point you're probably not running into this issue, since you can send test emails to yourself. I only
> bring it up because some networks (such as SBC/AT&T) restrict SMTP traffic to their own SMTP server, and drop traffic destined
> anywhere else. So if you were on AT&T Yahoo DSL you could send mail using smtp.sbcglobal.yahoo.com, but not using
> mail.comcast.net--AT&T's network wouldn't even allow you to connect to Comcast's mail server directly.
>
> My suggestion is to go into your mail settings where your incoming/outgoing mail server are and click on the More Settings
> button, then click the Outgoing Server tab. Check the box saying the server requires authentication and try that. If that
> doesn't work contact the mail administrator of the server you're trying to use to send mail and ask them what settings (if any)
> to use to send mail the way you're trying to.
>
> Joe
>
> "Bruce" <(E-Mail Removed)> wrote in message news:768C0C19-6005-498F-8AA9-(E-Mail Removed)...
>>I have no trouble sending SMTP directly with my SMTP accounts when I am
>> connected to my network which has an exchange server on it. It does not go
>> through exchange, it connects directly to the outside server. However, when
>> I am not connected to my network, I can receive POP3, but cannot send SMTP.
>> I checked configuration, and there is nothing wrong there. Test emails are
>> no problem.
>

I actually do not use my exchange server as a mail server. I only use it to
aid in synchronization and sharing of data in Outlook. My outgoing server is
already the same SMTP server I am trying to access when I am not connected to
my LAN. Again, I have no problem connecting and sending my SMTP mail
directly with the SMTP server when I am connected, but not when I am not
connected.

Bruce..

"John Blessing" wrote:

> "Bruce" <(E-Mail Removed)> wrote in message
> news:768C0C19-6005-498F-8AA9-(E-Mail Removed)...
> >I have no trouble sending SMTP directly with my SMTP accounts when I am
> > connected to my network which has an exchange server on it. It does not
> > go
> > through exchange, it connects directly to the outside server. However,
> > when
> > I am not connected to my network, I can receive POP3, but cannot send
> > SMTP.
> > I checked configuration, and there is nothing wrong there. Test emails
> > are
> > no problem.
>
>
> Presumably when "not connected to my network" you are connected to a network
> somewhere, otherwise you couldn't receive emails. The usual answer is that
> whilst on a different network to your smtp server, you cannot be authorised
> to use it. Change your smtp server to one that e.g. uses smtp
> authentication so that you can use it regardless of which network your are
> on. Get yourself a gmail account and use the gmail smtp server.
>
>
> --
> John Blessing
>
> http://www.LbeHelpdesk.com - Help Desk software priced to suit all
> businesses
> http://www.room-booking-software.com - Schedule rooms & equipment bookings
> for your meeting/class over the web.
> http://www.lbetoolbox.com - Remove Duplicates from MS Outlook, find/replace,
> send newsletters
>
>
>

1. The server does support SMTP authentication. It is a Linux based email
server that is POP3/SMTP.

2. When I am connected at the office, our provider does block port 25,
however, our server does have an alternate port that we are always configured
to use.

I spoke with the network admins, and they say IP addresses are not part of
the authentication process. When I described the situation, they assured me
that there is nothing in their configuration that would cause this.

The host does require authentication, so outlook is already configured to
logon POP3 prior to sending.

"Joe Grover" wrote:

> Likely when you're "not connected to your network" you're connected to some
> other network, and your SMTP server by default isn't allowing people outside
> of your network to use their server (which is as it should be).
>
> Two things need to be in place in order for you to use your original SMTP
> server from whatever your second network is:
>
> 1) Your server must support SMTP authentication
>
> 2) The second network must allow users on that network to connect to
> external SMTP servers.
>
> With regards to the first point, SMTP servers don't know who you are by
> default, they only know where you're coming from, that is they see what IP
> address the connection is coming from. The mail administrator configures a
> list of IP addresses that are allowed to send mail to external addresses,
> called "relaying". Odds are when you're on that second network the IP
> address you're connecting from is NOT in that list, so you are unable to
> send mail. Your test emails probably work because you're sending mail to
> yourself, which is a local address on that network. That wouldn't be a
> relay. Using mail.yourisp.com to send mail to (E-Mail Removed) is not a
> relay. Using mail.yourisp.com to send mail to (E-Mail Removed) would
> be a relay.
>
> Regarding the second point you're probably not running into this issue,
> since you can send test emails to yourself. I only bring it up because some
> networks (such as SBC/AT&T) restrict SMTP traffic to their own SMTP server,
> and drop traffic destined anywhere else. So if you were on AT&T Yahoo DSL
> you could send mail using smtp.sbcglobal.yahoo.com, but not using
> mail.comcast.net--AT&T's network wouldn't even allow you to connect to
> Comcast's mail server directly.
>
> My suggestion is to go into your mail settings where your incoming/outgoing
> mail server are and click on the More Settings button, then click the
> Outgoing Server tab. Check the box saying the server requires
> authentication and try that. If that doesn't work contact the mail
> administrator of the server you're trying to use to send mail and ask them
> what settings (if any) to use to send mail the way you're trying to.
>
> Joe
>
> "Bruce" <(E-Mail Removed)> wrote in message
> news:768C0C19-6005-498F-8AA9-(E-Mail Removed)...
> >I have no trouble sending SMTP directly with my SMTP accounts when I am
> > connected to my network which has an exchange server on it. It does not
> > go
> > through exchange, it connects directly to the outside server. However,
> > when
> > I am not connected to my network, I can receive POP3, but cannot send
> > SMTP.
> > I checked configuration, and there is nothing wrong there. Test emails
> > are
> > no problem.
>
>

Gary,

I just double checked with VerizonWireless regarding blocked ports, and they
advised me that there are no blocked ports in their broadband wireless
service. There is one other thing that might be an issue, but I do not think
so. I am not using personal folders, I am only using exchange folders in
cached mode.

Bruce..

"Gary VanderMolen" wrote:

> Good discussion, but you should have mentioned that point #2
> applies only when the SMTP server uses port 25. Many ISPs now
> offer alternate ports which are not blocked, or, if all else fails,
> get a Gmail account and do the sending chores with its port 465
> SMTP server.
>
> Gary VanderMolen
>
>
> "Joe Grover" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> > Likely when you're "not connected to your network" you're connected to some other network, and your SMTP server by default isn't
> > allowing people outside of your network to use their server (which is as it should be).
> >
> > Two things need to be in place in order for you to use your original SMTP server from whatever your second network is:
> >
> > 1) Your server must support SMTP authentication
> >
> > 2) The second network must allow users on that network to connect to external SMTP servers.
> >
> > With regards to the first point, SMTP servers don't know who you are by default, they only know where you're coming from, that
> > is they see what IP address the connection is coming from. The mail administrator configures a list of IP addresses that are
> > allowed to send mail to external addresses, called "relaying". Odds are when you're on that second network the IP address
> > you're connecting from is NOT in that list, so you are unable to send mail. Your test emails probably work because you're
> > sending mail to yourself, which is a local address on that network. That wouldn't be a relay. Using mail.yourisp.com to send
> > mail to (E-Mail Removed) is not a relay. Using mail.yourisp.com to send mail to (E-Mail Removed) would be a relay.
> >
> > Regarding the second point you're probably not running into this issue, since you can send test emails to yourself. I only
> > bring it up because some networks (such as SBC/AT&T) restrict SMTP traffic to their own SMTP server, and drop traffic destined
> > anywhere else. So if you were on AT&T Yahoo DSL you could send mail using smtp.sbcglobal.yahoo.com, but not using
> > mail.comcast.net--AT&T's network wouldn't even allow you to connect to Comcast's mail server directly.
> >
> > My suggestion is to go into your mail settings where your incoming/outgoing mail server are and click on the More Settings
> > button, then click the Outgoing Server tab. Check the box saying the server requires authentication and try that. If that
> > doesn't work contact the mail administrator of the server you're trying to use to send mail and ask them what settings (if any)
> > to use to send mail the way you're trying to.
> >
> > Joe
> >
> > "Bruce" <(E-Mail Removed)> wrote in message news:768C0C19-6005-498F-8AA9-(E-Mail Removed)...
> >>I have no trouble sending SMTP directly with my SMTP accounts when I am
> >> connected to my network which has an exchange server on it. It does not go
> >> through exchange, it connects directly to the outside server. However, when
> >> I am not connected to my network, I can receive POP3, but cannot send SMTP.
> >> I checked configuration, and there is nothing wrong there. Test emails are
> >> no problem.
> >
>
>