Marc Dirix wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The MTA should only have to request if a user and/or domain exists, and
send it to the mailserver. The rewriting should be in there, as is the
information about real users etc.
I'm not sure how much spam you get, but I think it is better to check
for user existance at MTA level to reject spam instead of sending
bounces.
We even want to check at the incoming mailserver.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFFhbor2M1B/aDfmXsRAkxzAJ0db3+aL8+5xpCE8tLMU2QgOrSYjgCfb9L2
TjzmVkFfPDdpJCht5BjrL9Q=
=WDln
-----END PGP SIGNATURE-----
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
The right way is to check at the incoming mailserver, like postfix.
Suppose you also have a spam filter and virus scanner that works between
mailserver and dbmail. If you reject at the server level, then you don't
have to pass the email to non-existant users to your spam and virus
filter, saving some resources on your server.
Also, if you have any type of header checks or rbl checks, then you will
also save those resources because mailserver will reject mail to
non-existant users before it does the header checks and rbl checks.
If your users database in dbmail_users don't change too often, and you
use postfix, then you should also use the postfix's proxy function so it
can cache the list of users from your dbmail database and it will reduce
the number of mysql calls to check the users existance.
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
