> On Apr 1, 2016, at 10:06 AM, tbucha...@vinu.edu wrote:
>
> My successful ldapsearch command is this: ldapsearch -x -H
> ldap://ldapserver.example.com:389/ -b
> "ou=People,o=oldserver.example.com,o=example.com" -D "uid=admin,
> ou=Administrators, ou=TopologyManagement, o=NetscapeRoot" -w
On Fri, Apr 01, 2016 at 08:13:14AM -0700, jaso...@mail-central.com wrote:
> I'm learning about whitelist scoring in postscreen_dnsbl_sites=
>
> /dev/rob0 mentioned using these
>
> postscreen_dnsbl_sites=
>... BLACKLISTS ...
>swl.spamhaus.org*-4
You can pretty much
On Fri, Apr 1, 2016, at 12:21 PM, Noel Jones wrote:
> dwl.spamhaus.org lists domain names and is not compatible with
> postscreen, which only knows the IP.
I needed to be reminded of that :-/
> dwl can be used in one of the
> smtpd_*_restrictions sections.
>
Quanah Gibson-Mount:
> --On Thursday, March 31, 2016 9:15 PM -0400 Wietse Venema
> wrote:
>
> >> Is this a known issue with Barracuda? Anyone have an idea how to work
> >> around this? Clearly having their spam appliance be non-functional
> >> isn't a great start. ;)
>
On 4/1/2016 10:13 AM, jaso...@mail-central.com wrote:
> I'm learning about whitelist scoring in postscreen_dnsbl_sites=
...
>
> One of the servers that's been shown to me has, instead
>
> postscreen_dnsbl_sites=
>... BLACKLISTS ...
>dwl.spamhaus.org=127.0.2.[2;3]*-3
>
On Fri, Apr 01, 2016 at 10:36:17AM -0700, Quanah Gibson-Mount wrote:
> --On Thursday, March 31, 2016 9:15 PM -0400 Wietse Venema
> wrote:
>
> >>Is this a known issue with Barracuda? Anyone have an idea how to work
> >>around this? Clearly having their spam appliance be
--On Friday, April 01, 2016 11:36 AM -0700 Quanah Gibson-Mount
wrote:
--On Thursday, March 31, 2016 9:15 PM -0400 Wietse Venema
wrote:
Is this a known issue with Barracuda? Anyone have an idea how to work
around this? Clearly having their spam
> > Running Postscreen after a spam appliance is pointless. It is a
> > spambot detector (in more sophisticated words, it implements IP
> > address-based reputation).
>
> Ok. But I still would like to know where in the stack the problem is.
> Right now, they are simply testing a release
--On Thursday, March 31, 2016 9:15 PM -0400 Wietse Venema
wrote:
Is this a known issue with Barracuda? Anyone have an idea how to work
around this? Clearly having their spam appliance be non-functional
isn't a great start. ;)
Running Postscreen after a spam
> On Apr 1, 2016, at 12:31 PM, /dev/rob0 wrote:
>
>> Apr 1 17:12:19 elrng-backup postfix/smtp[10780]: warning:
>> SASL authentication failure: No worthy mechs found
>
> This very warning is mentioned in SASL_README:
>
>
On Fri, Apr 01, 2016 at 05:20:54PM +0200, Paolo Mioni wrote:
> I'm writing to ask for help with the following problem. I
> cannot use outlook365 as a relay host for Postfix.
> I'm using postfix 2.6
(which happens to be 3+ years past its EOL date)
> I receive the following error:
>
> Apr 1
Sorry, forget about this mail. I've solved it myself.
Thanks anyway.
On 04/01/2016 05:20 PM, Paolo Mioni wrote:
Hi,
I'm writing to ask for help with the following problem. I cannot
use outlook365 as a relay host for Postfix.
I'm using postfix 2.6
I receive the following error:
Apr 1
jaso...@mail-central.com:
> (1) Does order matter in [postscreen_dnsbl_sites]?
There is no "order": the lookups happen in parallel. The result is
computed when all replies are received, or when the greet_wait time
limit is reached.
Wietse
Wietse:
> > Correct. Postscreen remembers tests that a client has passed. But
> > the client must pass all tests before postscreen will log a "PASS".
Brad Chandler:
> If a spamming IP is at first not listed on an RBL and gets a postscreen
> PASS, but is later added to an RBL, will postscreen
Hi,
I'm writing to ask for help with the following problem. I cannot
use outlook365 as a relay host for Postfix.
I'm using postfix 2.6
I receive the following error:
Apr 1 17:12:19 elrng-backup postfix/smtp[10780]: warning: SASL
authentication failure: No worthy mechs found
Apr 1
> Why do you care?
Because I'm actually trying to understand how things works and are best used.
On Thu, Mar 31, 2016, at 04:57 PM, Wietse Venema wrote:
> However the dnsblog client is stateless; it relies on caching in your local
> DNS resolver.
Okay, that's the part I missed.
Thanks.
Jason
I'm learning about whitelist scoring in postscreen_dnsbl_sites=
/dev/rob0 mentioned using these
postscreen_dnsbl_sites=
... BLACKLISTS ...
swl.spamhaus.org*-4
list.dnswl.org=127.[0..255].[0..255].0*-2
list.dnswl.org=127.[0..255].[0..255].1*-3
> My understanding was that postscreen, once it catches a bad actor, it caches
the result so subsequent attempts get a response from the cache.
IIRC postscreen caches PASS results only.
Correct. Postscreen remembers tests that a client has passed. But
the client must pass all tests before
I am trying to set up a Postfix mail server to take emails to a certain
domain and redirect them to external email addresses based on LDAP
information. I am new to Postfix and LDAP. Back story -- we no longer
want to host email accounts for a certain domain and have directed members
of that
19 matches
Mail list logo