Pascal Dreissen wrote:
John Peacock wrote:
Skaag Argonius wrote:
So the question is this - does the latest check_delivery plugin work
with vpopmail-sql? and if it does, will it honour the local
.qmail-default file in case it contains a special catch-all?
That plugin is not actively maintained[1], so AFAICT, the "latest"
version is what is found here:
<http://www.redhotpenguin.com/check_delivery>
1. check_delivery has not been added to the core because I was
concerned about the number of prerequisites required to make it work
(specifically suidperl). There was some discussion about how to add
"unsupported" modules to the repository back in October, but it got
bogged down in discussing how/where to check it in. I think the
resolution was to add a "contrib" folder where moderately unsupported
plugins reside, but I never followed up on that.
I realy think qpsmtpd is a little useless right now without a plugin
wich checks if an e-mail address is correct on the local system!
I love qpsmtpd, but the main thing is that there are too many bounces
because qpsmtpd accepts email for every local domain and qmail rejects
unknown e-mail addresses and sends bounces back ...
The dot-qmail-exists has some unpredicted results and is afaik useless
in a production environment.
Here it rejects legimite e-mail even if the .qmail file exists!
I think qpsmtpd needs this option very soon!
Best regards,
Pascal
You definitely do not want just a rcpthosts file and then
dot qmail, that's not a configured system yet. That's a
debug stage, and then you build on that.
Maybe there ought to be a default .bdb method and
a script that sucks up a flat file and outputs the .bdb.
I use tinyldap and some here use sql lookups. You can
also write a plugin to try the next hop, such as dspam,
and if that fails, assume the user doesn't exist. That
lets dspam do a mysql lookup for you. Possibly other
agents such as postfix could do the lookup for you.
There are so many options for directory lookup that
qpsmtpd can't have one default option--they are
all pretty difficult to setup. Better to get you up and
running and then you can decide which architecture
for lookups.
tinyldap is so simple that you could write a file like
[EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED]
and a script could turn that into a tinyldap directory.
Skip the two-year pilgrimage to the dali lama. And
the default .bdb method would take the same file
as input.
Write method is what differentiates a production
lookup directory from something that only works
for a few hundred users. openldap and mysql
are production methods because they handle
writes(user adds and deletes). There can be a
web forms interface for self signup and self
alias and self unsubscribe, interfacing to
openldap or mysql. No, there isn't any default
in qpsmtpd for that.
-Bob
