On Mon, Apr 23, 2001 at 11:22:24PM +0200, Erich Schubert wrote:
> > Most users will never enable such a function because of not understanding it.
> That's what i way saying. They thus won't benefit from it as well.
Most users don't benefit from TLS, we offer it and there are users using and
loving it.
Most users don't benefit from IMAP, we offer it and there are...
Most users don't benefit from IMAP over SSL, we offer it...
Most users don't benefit from POP3 over SSL, we offer it...
Most users don't benefit from webmail, we offer it...
Most users don't benefit from autoresponders, we offer it...
Most users don't benefit from dash-ext stuff, we offer it...
The list is endless. If you only wan't to offer what most clients want, offer
smtp + pop3, period.
> > > I currently use rblsmtpd, a separate package which is inserted between
> > > tcpserver and qmail-smtpd and which rejects smtp connection from rbl sites.
> > And breaks SSL.
> sslwrap works; i havn't testet TLS yet.
> I'm not sure if this really breaks TLS, but i havn't read these RFCs
TLS won't work reliable.
> rblsmtpd is a leftover from my old qmail installation.
> > And is totally unneeded for qmail-ldap as this feature is builtin.
> The builtin has some drawbacks, too.
> It has no RBL-Specific error message as rbmlsmtpd does, and does not give
> the user an url explaining why his mail was rejected.
> The error message should at least include http://mail-abuse.org/rbl/ as
> reference.
it's easy enough to customize the error message, in qmail-smtpd somewhere
around line 148.
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
http://www.bsws.de | Germany
