* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2006-02-03 15:11]:
> Thanks a bunch fella's.
>
> I got TLS working. Except for the fact that I cannot use port 587 in
> (yes I know) Outlook Express. If I keep it at port 25, everything runs
> like a charm. The server is listening on port tcp 587. However,
On 2/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm running Postfix 2.3.20050716-sasl2 (chrooted) and
> cyrus-sasl-2.1.20p4 on OpenBSD 3.8 stable. Everything is running peachy.
> My roaming users are able to connect and send e-mail.
> Now I wish to enable the fantastic SpamD f
al Message-
From: Peter Hessler [mailto:[EMAIL PROTECTED]
Sent: vrijdag 3 februari 2006 20:44
To: [EMAIL PROTECTED]
Subject: Re: SpamD, Postfix and mobile users
Have them send to port 587. That will bypass greylisting, as well as
port 25 blocking.
enable the following line in your master.cf file.
rhaps it's an
Outlook Express bug. I'll test it with firefox tomorrow.
Thanks again.
Nils
-Original Message-
From: Kurt Mosiejczuk [mailto:[EMAIL PROTECTED]
Sent: vrijdag 3 februari 2006 22:31
To: misc@openbsd.org
Subject: Re: SpamD, Postfix and mobile users
Bob Beck wrote:
Bob Beck wrote:
This is the right solution for roaming users, and is why
I will *not* make spamd ever have a notion of sasl :)
It is also, exactly, what we do here. Our users use
port 587 for this, NOT port 25
Doing it this way also helps those users who have ISPs who block
* Stuart Henderson <[EMAIL PROTECTED]> [2006-02-03 13:16]:
> On 2006/02/03 20:28, [EMAIL PROTECTED] wrote:
> > But I was hoping SpamD had some kind of understanding of SASL.
>
> I'm quite glad it *doesn't*. Port 587 (msa/submission) is the right
> answer here. I wouldn't want a daemon that's inten
On Friday, February 3, [EMAIL PROTECTED] wrote:
>
> I'm running Postfix 2.3.20050716-sasl2 (chrooted) and
> cyrus-sasl-2.1.20p4 on OpenBSD 3.8 stable. Everything is running peachy.
> My roaming users are able to connect and send e-mail.
We use authpf to do this. If you're authenticated through a
On 2006/02/03 20:28, [EMAIL PROTECTED] wrote:
> But I was hoping SpamD had some kind of understanding of SASL.
I'm quite glad it *doesn't*. Port 587 (msa/submission) is the right
answer here. I wouldn't want a daemon that's intended to talk to bad
connections having such high access to the system.
Thanks for your quick response Maxim.
Sure, I could enforce TLS connections for my roaming (outside/internet)
users. That might be a good solution and I would bypass SpamD.
I could also setup another postfix instance on another port and allow
sasl_authenticated only.
But I was hoping SpamD had so
Hi all,
I'm running Postfix 2.3.20050716-sasl2 (chrooted) and
cyrus-sasl-2.1.20p4 on OpenBSD 3.8 stable. Everything is running peachy.
My roaming users are able to connect and send e-mail.
Now I wish to enable the fantastic SpamD feature in OpenBSD. However,
I'm foreseeing a problem. I do not want
10 matches
Mail list logo
