🚀 go-pugleaf

"Ben" <bjblackmore@mailhot.com> wrote in message
news:ds7la0$l97$1@nwrdmz01.dmz.ncs.ea.ibs-infra.bt.com...
[chronology fix. Please don't top post. See below.]
>
> "Dr.X" <Dr.X@NOSPAMnull.com> wrote in message
> news:JfIFf.15306$Fw6.14407@tornado.tampabay.rr.com...
> > "Ben" <bjblackmore@mailhot.com> wrote in message
> > news:ds7fjv$qnq$1@nwrdmz02.dmz.ncs.ea.ibs-infra.bt.com...
> >> Hi,
> >>
> >> Does anyone know any free white/black list software, that I can install
> >> in
> >> our local LAN to allow our users to add email address to a white/black
> > list?
> >>
> >> Cheers
> >>
> >> Ben
> >
> > I think that would depend on the existing software on your "local LAN".
> > When
> > you say local LAN, should it be assumed that you're talking about
software
> > you can install on a local server (possibly mail server)? or do you mean
> > software you can install on the individual workstations (possibly
> > integrating with your client software)?
> >
> > -Dr.X

> Hi Dr. X
>
> Thanks for the reply.
>
> We currently have a spam filter, on our firewall. As well as using it's
own
> rules to filter mail, it can also check against a white/black list server.
> So what I'd like is a bit of software that can be installed on a server
> somewhere (preferably NT, but Linux would do) so people can connect to it,
> maybe via web page, and add their own entries.
>
> We did test a product from McAfee, that would install on IIS, you could
open
> a web page, and configure it with mailboxs, then you could add black/white
> list entries against each mailbox. But it had an issue with adding mailbox
> entries, where it wouldn't recognise a period in the email address, and
> according to McAfee it won't be fixed until the next release of their
> software.
>
> If an existing product doesn't exist, I may just write my own web page,
that
> can read/write XML, looking at the McAfee product, it just reads a file
with
> the format:
>
>   <?xml version="1.0" encoding="UTF-8" ?>
> - <MailboxUpdate>
> - <Mailbox name="user.one@DOMAIN" owner="user.one@DOMAIN"
> lastUpdate="1139234841" Delete="0">
>   <DenySender>spam@spam.com</DenySender>
>   <AllowSender>allow.email@DOMAIN.com</AllowSender>
>   </Mailbox>
> - <Mailbox name="user.two@DOMAIN" owner="user.two@DOMAIN"
> lastUpdate="1139234869" Delete="0">
>   <DenySender>spam@spam.com</DenySender>
>   <AllowSender>allow.email@DOMAIN.com</AllowSender>
>   </Mailbox>
>   </MailboxUpdate>
>
> If you need anymore info please let me know
>
> Ben

Hi Ben.

    If I understand you correctly, your McAfee product generated a XML file
that your firewall/filter understood. I can't think of a product that
generates that file format, but like you said, it's only XML and therefore
easily reproducible. Is XML the only format your firewall/filter
understands? Can it also import regular old everyday lists of email
addresses?

    Also, what do you do about email addresses that are forged? Do you just
assume that the victims of the forgery will never send an email to you/your
co.? Do you also assume that the spammer will continue to use that forged
email address? I'm not badgering your method of filtering. I'm just trying
to understand the goal.

    Anyways, I think you're gonna be stuck making your own. I have a
suggestion though. If you're willing to make a web page that users will log
on to add the addresses, then maybe you can bypass that part and make a
script or program that reads a mailbox. Have your users send the email
addresses in an email to that box. The script checks the box periodically
and generates the list from that.

for example (per your example), the user can send an email to
BLOCKthisBASTARD@domain with a list of just the email addresses to block or
allow like this:

B badperson@baddomain
B anotherbaduser@anotherbaddomain
A agooduser@anicedomian
B someScume@aCreepyDomain

    Then your script would read B for block and A for allow. If I understand
the xml you provided, then Mailbox name refers to the local user that wants
to do the blocking. In that case, just have them send the list from that
mailbox and your script will know what box to apply the rule to.

    Now, depending on whether your filter can take just plain lists, you can
easily parse this into straight lists. Or, if your filter can only
understand the xml, then you can still supply that from this input. Still
that all depends on if my assumptions about your setup is correct.

    You mentioned that your firewall/filter can "check against a white/black
list server". Are you meaning a dns type server?

lemme know.
-Dr.X
PS: Please don't top post your replies. It makes it difficult to follow a
conversation if one of us posts at the top and the other posts at the
bottom. The general rule is to bottom post and/or insert where appropriate.
Thanks.