On Tue, 22 Jul 2014 13:30:13 -0800
Kevin Miller wrote:
> I guess catting the output of the ldap
> query onto the access table and hash it once a night would be just as
> easy. I'll give that test.
Another option, since you're running Sendmail, is to use a milter such
as MIMEDefang and do a real
ssage-
From: Kevin A. McGrail [mailto:kmcgr...@pccc.com]
Sent: Tuesday, July 22, 2014 12:01 PM
To: Kevin Miller; users@spamassassin.apache.org
Subject: Re: Exchange 2013 and rejection of invalid RCPTs (was Re: one word
spam (continued))
On 7/22/2014 3:54 PM, Kevin Miller wrote:
> Resurrec
On 7/22/2014 3:54 PM, Kevin Miller wrote:
Resurrecting an old thread here. We're finally migrating to Exchange 2013, and
I have a script that will extract email addresses from ldap, but when looking
at the virtualuser table it seems that it's used to map one address to another.
The script pu
amassassin.apache.org
Subject: Re: Exchange 2013 and rejection of invalid RCPTs (was Re: one word
spam (continued))
Just be aware that Microsoft's "standard" is to use LDAP queries to the AD.
Every major commercial antispam product does this and you will save yourself a
lot of work
On 17/10/13 09:03, Kevin A. McGrail wrote:
> We've done similar real time checks using Sendmail but seen this
> actually bring down Exchange Servers (more like bringing it to its
> knees from a resource perspective than actually crashing it) from the
> LDAP queries associated with these type of is
On 10/16/2013 3:46 PM, David F. Skoll wrote:
On Wed, 16 Oct 2013 15:41:04 -0400
"Kevin A. McGrail" wrote:
So in the beginning for our issue, our firm implemented something
similar and it's documented at http://www.pccc.com/downloads/ldap/
thanks primarily to Brian Landers and his
work. This
On Wed, 16 Oct 2013 15:41:04 -0400
"Kevin A. McGrail" wrote:
> So in the beginning for our issue, our firm implemented something
> similar and it's documented at http://www.pccc.com/downloads/ldap/
> thanks primarily to Brian Landers and his
> work. This is a nice solution that uses LDAP an
On 10/16/2013 2:27 PM, David F. Skoll wrote:
I think this is a deliberate strategy on the part of Microsoft. I
think they're making Exchange so complicated and such a PITA that
people give up and go to the cloud, ideally to Office 365. For many
small companies, going to the cloud probably makes
"David F. Skoll" 10/16/13 2:32 PM >>>
>. . . .as long as they don't mind
>paying extra and don't mind the NSA having access to their email. :)
>
>Regards,
>
>David.
Of course you mean "easier access" . . . ?
joe a.
On Wed, 16 Oct 2013 10:52:08 -0700
Ted Mittelstaedt wrote:
> Just be aware that Microsoft's "standard" is to use LDAP queries to
> the AD.
True, and we support that. But not everyone wants to open up their LDAP
to the outside world, even to a few outside IPs.
Furthermore, if you use Office 365
Just be aware that Microsoft's "standard" is to use LDAP queries to the
AD. Every major commercial antispam product does this and you will
save yourself a lot of work later when MS changes the next version of
Exchange to not support the 2525 hack. (which they could easily do)
if you do it that
On Wed, 16 Oct 2013 09:21:46 -0800
Kevin Miller wrote:
> So if I'm reading this right, milters such as smf-sav or milter-ahead
> will no longer be of any use?
You are reading it correctly. On our anti-spam service, we require
some sort of recipient validation so we don't go insane scanning
mess
12 matches
Mail list logo
