The current EXIM can and will do all from PGSQL or MYSQL and more. A/V,
SpamAssassin, Per User/Domain, etc... pump to dbmail.
Actually we recieve mail for 34 domains and accept all mail that hit the box.
Local/Relay domains -> process, Local/Relay accounts -> Deliver, NOT OURS ->
/dev/null... WHY?
(your favorite script language)
FOR ? FROM a TO Z
Do
mail ->
( LOG ALL REJECTS HERE, AND WE KNOW YOUR ACTUALS)
END
The danger is not in receiving ALL mail, it is in what you do with it...
Be Sfae!!
Smitty
On Sunday 05 October 2003 02:39 pm, Daniel Brown wrote:
> Wrote [EMAIL PROTECTED]:
> > I'm a newbie to DBMail and had a question about setting up an MTA with
> > multiple domain names.
> >
> > I'd like to be able to define the domain names that my mail server
> > accepts mail from by a mysql database. I know some people have made perl
> > scripts to download the domains from the database and output them to a
> > rcpthost or postfix transport file, but that is a pain.
> >
> > My question is, is there any MTAs that will simply pass the mail onto
> > dbmail-smtp without checking to see if the domain is valid? Or is there a
> > way I can define sendmail to accept all mail that it is sent? Would there
> > be a downside to doing this? My understanding is that DBMail would still
> > bounce the email if it did not match a domain in the database.
> >
> > As more and more people require email systems that handle multiple domain
> > names, I think this is the single most compelling reason to make a dbmail
> > MTA agent (but again, I'm a newbie).
> >
> > Matt
>
> I'll quickly answer your question about a downside to accepting all
> mail: Yup!. Sendmail (and other MTAs) assumes that if it has grabbed
> hold of an email, it is authorized to deliver it, even if it is a
> non-local destination. That of course opens up to spamming
> third-party hosts, and a lot of downsides with that.
>
> Now, IMO, for the time being, using perl scripts to re-generate your
> MTA config files is not a bad idea. In fact I'm building a hosting
> system based on that. I agree though "it'd be nice", but in reality
> generating MTA config files via perl script isn't bad.
>
> I see 3 alternatives to that, though, assuming (correctly in the case
> of Sendmail) there is no current support for DBmail in your favorite
> MTA:
>
> * Write your perl script as a named-pipe program instead: your perl
> script opens something like /etc/mail/local-host-names as a UNIX
> named pipe and automatically generates the contents whenever your
> MTA attempts to read from the named-pipe. Yeah, yeah, same
> approach, different method. :)
>
> * If Perl is to slow, write it in C instead.
>
> * Edit your MTA's source code to include support and submit patches
> (both to your MTA's authors and here).
>
> Personally, I'd like to create for Sendmail the same kind of support
> that PureFTPd (www.pureftpd.org) does for SQL-based virtual users. In
> PureFTPd, You just supply your own custom SELECT queries for each type
> of data acquisition, right in the main config file.
>
> -Daniel
> _______________________________________________
> Dbmail mailing list
> [email protected]
> https://mailman.fastxs.nl/mailman/listinfo/dbmail
