|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: aichains (aichains
nonstophate.com)
Date: Sat Nov 17 2007 - 13:48:46 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, 2007-11-17 at 20:43 +0100, Ralf Hildebrandt wrote:
> * Michael Richards <hackish
gmail.com>:
>
> > This is in fact why I want the server to first receive the messages
> > before they hit the spam appliance. The spam appliance has no idea if
> > an account is non-existent or not so the extra load would be
> > significant.
>
> So the appliance is broken. Or misconfigured. It's hard to believe
> that something like the Barracude would have such a crass bug.
>
> I had a look.
>
> According to their "Barracuda Spam Firewall" Datasheet it has a step
> called "Recipient Verification" (step 5), first page of that PDF.
>
barracuda only supports ldap user verification. to get around it, we
wrote a script that dumps mysql user db into ldif format that barracuda
recognizes, then imports into openldap (runs out of cron). a disgusting
hack, but its the only way to get smtp-time user verification info into
the barracuda.
other mail-washers are more flexible in their import methods.
--
aichains <aichains
nonstophate.com>
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]