This option :
"I was just thinking about another option. I might be able to make a
small program that analyzes the logfiles for each server, puts it in a
database with a timestamp, and then make it a POP/IMAP before SMTP.
That would be secure enough right?"
Is not valid for doing all you're customers mail machines to connect
to a relayhost, because machines connecting to relay host smtpd server
are not doing any pop against nothing. Take a list of users in all
databases, do a small table in mysql set the primary key properly
(refresh table with changes with cron several times per day, 2 or 3)
and set a dedicated mysql machine and another one in backup
replicating from the master and not be queried. And you should move
with this structure the mail without serious problems. I think you're
more worried about authentication wich is pretty easy and forgotten
about other problems... like spam I said... because if you have so
huge number of users you should control what are they doing and here
you should be perhaps more skillful. I'm working on a new project for
helping Postfix preventing spam and rejecting it quite easy (not just
through spamassassin, that is not enough) in some months I'll have it
available and opened under BSD license too as Postfix quota reject.
Any help just talk here :)
Bye!!!
El 19/09/2009, a las 16:49, Paul Beard escribió:
On Sep 19, 2009, at 7:30 AM, Martin Allan Jensen <mar...@deamon.dk>
wrote:
Yes there is - actually there is about six different ones - so
making a system that could talk to all those authentication
mechanisms would take me years to develop. That's why I am looking
for something simpler.
Looking up usernames in 6 passwd files or 1 isn't that complex, is it?
--
If this was a real .signature it would be more interesting.
