Re: Outgoing SMTP ports

2003-10-29 Thread BruceG
On Tue, 2003-10-28 at 23:18, Monique Y. Herman wrote:
 On Wed, 29 Oct 2003 at 02:06 GMT, BruceG penned:
  On Tue, 2003-10-28 at 20:36, James W. Thompson, II wrote:
  When sendmail sends mail destined for outside my server what port is
  it coming from and what port is it going to? 25? And does it use TCP,
  UDP or both?
  
  -Dubbs
  
  I believe sendmail uses TCP port 25, and ipopd uses TCP port 110.
  Least that's how I configured my Linksys router for port-forwarding
  and it's working.
  
 
 For incoming, right?  For outgoing, you shouldn't need a special router
 rule.
 

You're right. The router will not block outbound connections over www,
pop and smtp.(at least I don't have it configured to do so!). But it
will block inbound connections - so you need to set up port forwarding
to allow selected ports in and to NAT them to an inside server. 

But - reading the original note, he was asking about outbound ports, so
my post has been completely (um, er, ahem) off topic.

(I noticed when replying using Ximian Evolution, it does the to: as the
original poster. If I reply to all, it cc:'s the debian-user list. I had
to delete the to: and move debian-users from cc: to to:  Wonder why that
is?)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Outgoing SMTP ports

2003-10-29 Thread James W. Thompson, II
My problem seems to persist, let me delve more into it and see if y'all 
can help.

My firewall allows all incoming and outgoing connections that are 
ESTABLISHED or RELATED
My firewall allows all incoming connections on port 25 that are NEW 
(TCP)
My firewall allows all outgoing connections to port 25 that are NEW 
(TCP)

Is there some other rule that I need to set because outgoing mail is 
just not going, I have my 3 nameservers setup in /etc/resolve.conf and 
can dig all the domains which mail should be going to so DNS doesn't 
seem to be the problem. Any suggestions?

-James

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Outgoing SMTP ports

2003-10-29 Thread Richard Lyons
On Wednesday 29 October 2003 14:23, BruceG wrote:
[...]
 (I noticed when replying using Ximian Evolution, it does the to: as the
 original poster. If I reply to all, it cc:'s the debian-user list. I had
 to delete the to: and move debian-users from cc: to to:  Wonder why that
 is?)
It's because the headers as sent by lists.debian.org to the list include 
   From: BruceG [EMAIL PROTECTED]
   To: [EMAIL PROTECTED]

See the lengthy thread netiquette: CCing on lists on this list.

-- 
richard



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Outgoing SMTP ports

2003-10-29 Thread James W. Thompson, II
I figured out the problem.

My firewall was applying the same rules to my eth0 and lo interfaces, 
so I set the first rule in my inbound and outbound sets to allow any 
traffice on lo...

Is there any security risk posed by this? Should I be security concious 
about have no restricitions on the loopback interface?

-James

On Oct 29, 2003, at 7:35 AM, James W. Thompson, II wrote:

My problem seems to persist, let me delve more into it and see if 
y'all can help.

My firewall allows all incoming and outgoing connections that are 
ESTABLISHED or RELATED
My firewall allows all incoming connections on port 25 that are NEW 
(TCP)
My firewall allows all outgoing connections to port 25 that are NEW 
(TCP)

Is there some other rule that I need to set because outgoing mail is 
just not going, I have my 3 nameservers setup in /etc/resolve.conf and 
can dig all the domains which mail should be going to so DNS doesn't 
seem to be the problem. Any suggestions?

-James



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Replying to the list in evolution [was Re: Outgoing SMTP ports]

2003-10-29 Thread Oliver Elphick
On Wed, 2003-10-29 at 13:50, Richard Lyons wrote:
 On Wednesday 29 October 2003 14:23, BruceG wrote:
 [...]
  (I noticed when replying using Ximian Evolution, it does the to: as the
  original poster. If I reply to all, it cc:'s the debian-user list. I had
  to delete the to: and move debian-users from cc: to to:  Wonder why that
  is?)

If you want to reply to the list only, that option is available in
evolution from the pop-up menu put up by your mouse right-button.
(At least in evolution 1.4 -- I don't remember seeing it in earlier
releases.)

-- 
Oliver Elphick[EMAIL PROTECTED]
Isle of Wight, UK http://www.lfix.co.uk/oliver
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839  932A 614D 4C34 3E1D 0C1C
 
 Now unto him that is able to do exceeding abundantly 
  above all that we ask or think, according to the power
  that worketh in us...Ephesians 3:20 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Outgoing SMTP ports

2003-10-29 Thread Derrick 'dman' Hudson
On Wed, Oct 29, 2003 at 09:19:30AM -0600, James W. Thompson, II wrote:
| I figured out the problem.
| 
| My firewall was applying the same rules to my eth0 and lo interfaces, 
| so I set the first rule in my inbound and outbound sets to allow any 
| traffice on lo...
| 
| Is there any security risk posed by this? Should I be security concious 
| about have no restricitions on the loopback interface?

The loopback interface is for your machine only.  No outside system
can access that interface.  I always allow anything on the loopback.


| On Oct 29, 2003, at 7:35 AM, James W. Thompson, II wrote:
| 
| My problem seems to persist, let me delve more into it and see if 
| y'all can help.

| Is there some other rule that I need to set because outgoing mail is 
| just not going, I have my 3 nameservers setup in /etc/resolve.conf and 
| can dig all the domains which mail should be going to so DNS doesn't 
| seem to be the problem. Any suggestions?

Look in the logs.  It is impossible to debug a problem without first
knowing what the problem is.  The software will report, in the logs,
why it can't deliver the mail.

-D

-- 
If we claim we have not sinned, we make Him out to be a liar and His
Word has no place in our lives.
I John 1:10
 
http://dman13.dyndns.org/~dman/


pgp0.pgp
Description: PGP signature


Re: Outgoing SMTP ports

2003-10-28 Thread Steve Lamb
James W. Thompson, II wrote:
When sendmail sends mail destined for outside my server what port is it 
coming from and what port is it going to? 25? And does it use TCP, UDP 
or both?
A port  1024, port 25, TCP.

--
 Steve C. Lamb | I'm your priest, I'm your shrink, I'm your
   PGP Key: 8B6E99C5   | main connection to the switchboard of souls.
---+-


pgp0.pgp
Description: PGP signature


Re: Outgoing SMTP ports

2003-10-28 Thread BruceG
On Tue, 2003-10-28 at 20:36, James W. Thompson, II wrote:
 When sendmail sends mail destined for outside my server what port is it 
 coming from and what port is it going to? 25? And does it use TCP, UDP 
 or both?
 
 -Dubbs
 
I believe sendmail uses TCP port 25, and ipopd uses TCP port 110. Least
that's how I configured my Linksys router for port-forwarding and it's
working.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Outgoing SMTP ports

2003-10-28 Thread Monique Y. Herman
On Wed, 29 Oct 2003 at 02:06 GMT, BruceG penned:
 On Tue, 2003-10-28 at 20:36, James W. Thompson, II wrote:
 When sendmail sends mail destined for outside my server what port is
 it coming from and what port is it going to? 25? And does it use TCP,
 UDP or both?
 
 -Dubbs
 
 I believe sendmail uses TCP port 25, and ipopd uses TCP port 110.
 Least that's how I configured my Linksys router for port-forwarding
 and it's working.
 

For incoming, right?  For outgoing, you shouldn't need a special router
rule.

-- 
monique
PLEASE don't CC me.  Please.  Pretty please with sugar on top.
Whatever it takes, just don't CC me!  I'm already subscribed!!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]