On Fri, 2008-01-18 at 17:31 -0500, Rich Huff wrote:
> On Fri, 2008-01-18 at 14:11 -0700, Miark wrote:
> > Having been accomodating about it in the past, the technical
> > geniuses at Comcast have permanently blocked port 25, separating
> > me (at my home office) from my employer's e-mail server.
>
Kai Schaetzl wrote:
Miark wrote on Fri, 18 Jan 2008 17:55:32 -0500:
The winning solution
Nevertheless, Bowie's solution is the correct one.
Indeed, 587 is the standard port for mail submission.
http://www.ietf.org/rfc/rfc2476.txt
http://www.ietf.org/rfc/rfc5068.txt
and since "s
Yeah, I resolved that problem when I switched ISPs recently by using
something like this:
> submission inet n - n - - smtpd
> -o smtpd_etrn_restrictions=reject
> -o smtpd_sasl_auth_enable=yes
> -o receive_override_options=no_address_mappings
> -o
smtpd
Miark wrote on Fri, 18 Jan 2008 17:55:32 -0500:
> The winning solution
Nevertheless, Bowie's solution is the correct one.
Kai
--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
___
CentOS mailing
Les Mikesell wrote:
Miark wrote:
Thanks to everybody for the responses. The winning solution
was Ricks (see below) which worked like a charm after poking a
suitable hole in my firewall.
I missed most of that conversation, but can't you configure postfix to
use smtps on port 465 on both ends a
Miark wrote:
Thanks to everybody for the responses. The winning solution
was Ricks (see below) which worked like a charm after poking a
suitable hole in my firewall.
I missed most of that conversation, but can't you configure postfix to
use smtps on port 465 on both ends and get encryption ove
Thanks to everybody for the responses. The winning solution
was Ricks (see below) which worked like a charm after poking a
suitable hole in my firewall.
Miark
> [To listen to port 2525], in /etc/postfix/master.cf file,
> locate the lines that look like this:
>
> smtp inet n - n - - smtpd -o cle
On Fri, 18 Jan 2008 17:31:13 -0500, Rich wrote:
>
> On Fri, 2008-01-18 at 14:11 -0700, Miark wrote:
> > Having been accomodating about it in the past, the technical
> > geniuses at Comcast have permanently blocked port 25,
> > separating me (at my home office) from my employer's e-mail
> > server
On Fri, 2008-01-18 at 14:11 -0700, Miark wrote:
> Having been accomodating about it in the past, the technical
> geniuses at Comcast have permanently blocked port 25, separating
> me (at my home office) from my employer's e-mail server.
>
> What can be done on the server side to keep Postfix list
Brian Mathis wrote:
> On Jan 18, 2008 4:11 PM, Miark <[EMAIL PROTECTED]> wrote:
> > Having been accomodating about it in the past, the technical
> > geniuses at Comcast have permanently blocked port 25, separating
> > me (at my home office) from my employer's e-mail server.
> >
> > What can be don
On Jan 18, 2008 4:11 PM, Miark <[EMAIL PROTECTED]> wrote:
> Having been accomodating about it in the past, the technical
> geniuses at Comcast have permanently blocked port 25, separating
> me (at my home office) from my employer's e-mail server.
>
> What can be done on the server side to keep Post
On Jan 18, 2008 4:11 PM, Miark <[EMAIL PROTECTED]> wrote:
> Having been accomodating about it in the past, the technical
> geniuses at Comcast have permanently blocked port 25, separating
> me (at my home office) from my employer's e-mail server.
>
> What can be done on the server side to keep Post
Having been accomodating about it in the past, the technical
geniuses at Comcast have permanently blocked port 25, separating
me (at my home office) from my employer's e-mail server.
What can be done on the server side to keep Postfix listening on
25 _and_ accept my connections on some other port?
13 matches
Mail list logo
