In plugins/check_badrcptto, is there a particular reason $recipient-user
isn't lowercased while $recipient-host is? Or was it just oversight?
-Frank
Frank wrote:
In plugins/check_badrcptto, is there a particular reason $recipient-user
isn't lowercased while $recipient-host is? Or was it just oversight?
Those are the rules in the RFC's. The local portion must be transparently
passed (i.e. capitalization or special quoting preserved) but the
John Peacock wrote:
Hmmm... I'll play around with that.
No go; once check_relay has fired, later plugins cannot DENY based on rcpt.
I'll go back to my original plan.
John
I was just checking out qpsmtpd from CVS, to install on my Debian
box as a front end for my long-standing qmail system. I noticed that
config/plugins has been truncated by 33 lines at v1.10, and the comment
doesn't seem to relate why. Just asking for clarification, as I have a
working full
cvsuser 03/11/06 14:31:38
Modified:config plugins
Log:
reinstate the default plugins config (from revision 1.9)
Revision ChangesPath
1.11 +33 -0 qpsmtpd/config/plugins
Index: plugins
===
On Nov 6, 2003, at 2:20 PM, Nick Leverton wrote:
I was just checking out qpsmtpd from CVS, to install on my Debian
box as a front end for my long-standing qmail system. I noticed that
config/plugins has been truncated by 33 lines at v1.10, and the comment
doesn't seem to relate why. Just asking
On 6 Nov 2003, at 22:32, Ask Bjørn Hansen wrote:
Good question. I don't think it was intentional. :-) (Matt?)
*blush*
Total accident, sorry.
Andrew Pam [EMAIL PROTECTED] wrote:
Usernames with different capitalisation may not be identical (and on
Unix-based qmail servers generally are not), while hostnames are by
definition.
Qmail doesn't distinguish between usernames on the basis of
case. It lowercases everything and doesn't
