Mailing List Message #96657
From: Urs Gruetzner <>
Subject: RE: CGP SMTP Server frequently not available
Date: Thu, 6 Nov 2008 17:54:08 +0100
To: CommuniGate Pro Discussions <>
X-Mailer: CTM PowerMail version 5.6.2 build 4501 German (PPC) <>

Thanks for this input. As I understood its basically free which port I
am opening, as long as its not a reserved port, used by other services.

CGP is proposing 587, so I used that, with SSL. Your example shows that
8025, 8125 are a good choice too.

My brother is happy with the solution now. He can send now mails without
the troubles before.


From: "Salman Sheikh" <s.sheikh>
Subject: RE: CGP SMTP Server frequently not available
Date: Wed, 05 Nov 2008 14:09:57 -0500
To: "CommuniGate Pro Discussions" <CGatePro>
X-Mailer: CommuniGate Pro MAPI Connector


This is not a problem that is limited to dealing overseas colleagues.
Here in the good ol' US of A, it can be a problem dealing with AOL,
RoadRunner, Comcast, Cablevision, et. al. All the ISP's (at least, the
good ones these days) actively monitor or block port 25. It is an anti-
spam measure for them and it relieves the Internet of what would be a
lot more spam. Unfortunately, for us legitimate postmasters, we have to
work around the workaround.

When I first this years ago, CGP tech support recommended I open up port
8025 for SMTP traffic and have all my users configure their Outlook/OE/
TB/Netscape Mail 1.0/etc to use port 8025. It worked like a charm.

Since then, I have added port 8125 for SMTP traffic over SSL as well. I
also have users now in Europe and Asia. Using the custom ports for SMTP
has worked well for us. I recommend you try this out as well.



Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster