Sandy,

FYI, restarting ORF doesn't affect MS SMTP as far as I can tell, and as long as you configure MS SMTP to accept all E-mail, all that a restart of ORF will do is cause a moment of un-validated E-mail which should get deleted by Declude as spam if it came from a dictionary attack.  The problem is really finding a way to reliably restart ORF in a script.  I have had two occasions where my script failed to restart it and that caused overflow each time.  I would look more into it, but I deeply desire something that can weight RBL's and some other very obvious things while also doing address validation, and I have little hope for ORF to do this anytime soon based on previous queries.

I will agree that doing an AD import would be a smoother implementation with ORF provided that you are comfortable with this.

Matt



Sanford Whiteman wrote:
Sandy's  ldap2aliases  can  be  used  for  this,  but  IMO, it isn't
something  that  I would use for multiple different Exchange servers
as  the  configuration  can  be  a bit much. For one or two Exchange
servers it would definitely be practicable.
    

Yes, exchange2aliases (ldap2aliases is for IMail MXs fronting IMail or
other  OpenLDAP  mailbox  servers) is designed for situations in which
the  mailbox  server(s)  are owned by, or at least open to control by,
the MX provider.

Though ORF speaks AD LDAP natively, it too is not built out-of-the-box
to  support  a  wide  range  of  remote mailbox servers with real-time
validation  and/or  live  recipient  list  updates (updates that don't
require  that  the ORF service be restarted). As a result, most end up
using ORF's plain-text recipient lists, which unlike LDAP does require
a  quick  service  restart  when the list is updated. If you have more
than  one  ORF  server,  rolling restarts will do you fine, but with a
single  server  and  high load, it can require more hoops to be jumped
through  to  ensure  that  nothing aberrant (leakage, orphans) happens
while the service restarts.

IME,  the  best  solution  with  ORF is to import the remote recipient
lists  into  a  dedicated AD/ADAM LDAP server (which happens live) and
point  ORF to that server for recipient validation (which also happens
live).  This  gives  you  a  real-time  route  for  consolidating  the
recipient  lists of multiple remote mail servers, but it requires real
LDAP knowledge to set up.

--Sandy


------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.
e-mail: [EMAIL PROTECTED]

SpamAssassin plugs into Declude!
  http://www.imprimia.com/products/software/freeutils/SPAMC32/download/release/

Defuse Dictionary Attacks: Turn Exchange or IMail mailboxes into IMail Aliases!
  http://www.imprimia.com/products/software/freeutils/exchange2aliases/download/release/
  http://www.imprimia.com/products/software/freeutils/ldap2aliases/download/release/

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.


  

-- 
=====================================================
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=====================================================

Reply via email to