Re: [meta-sig] mailman problems
On Thu, 23 Apr 1998, Dmitry Khrustalev wrote:
Can the person responsible for python.org mailing lists fix mailman so it will understand .su TLD (add "su" to valid_toplevels at modules/mm_utils.py line 16)?
I tried contacting postmaster@python.org and mailman list, but have not heard back for several weeks.
I've added it in. Sorry about the non-acknowledgement of your pleas for help - looking back through my inbox i see that your complaints arrived here last wednesday, the fifteenth, just when i left for around a week vacation - and i hadn't gotten to them when i returned. My apologies for missing it.
Furthermore, i do have some questions about the strategy of qualifying registration addresses according to matches against a static list of known top level domains - i'd be interested to hear input about this on the mailman-developers list...
Finally, dmitry, thanks for going so far as to track down the specific changes that needed to be done - that was beyond the call of duty. Sorry that this got in the way of participating in the python.org mailing lists!
Ken Manheimer klm@python.org 703 620-8990 x268 (orporation for National Research |nitiatives
# If you appreciate Python, consider joining the PSA! #
# <http://www.python.org/psa/>. #
Ken writes:
Furthermore, i do have some questions about the strategy of qualifying registration addresses according to matches against a static list of known top level domains - i'd be interested to hear input about this on the mailman-developers list...
I think this is bogus; as Dmitri's mail shows it is a maintenance nightmare waiting to happen. If you really want to do a validation of an email address, use DNS to see if there's a host by that name or an MX record for that domain. What is the reason for validating addresses in the first place? If the address is invalid, the mail will bounce and the user won't be registered. Simple. Effective.
--Guido van Rossum (home page: http://www.python.org/~guido/)
"Guido" == Guido van Rossum <guido@cnri.reston.va.us> writes:
Guido> I think this is bogus; as Dmitri's mail shows it is a
Guido> maintenance nightmare waiting to happen. If you really
Guido> want to do a validation of an email address, use DNS to see
Guido> if there's a host by that name or an MX record for that
Guido> domain. What is the reason for validating addresses in the
Guido> first place? If the address is invalid, the mail will
Guido> bounce and the user won't be registered. Simple.
Guido> Effective.
I agree with Guido on all counts. TLD's probably don't change that often, but if they do, you'll have to propagate changes to everyone who's running MM. That's DNS's job!
-Barry
On Thu, 23 Apr 1998, Guido van Rossum wrote:
Ken writes:
Furthermore, i do have some questions about the strategy of qualifying registration addresses according to matches against a static list of known top level domains - i'd be interested to hear input about this on the mailman-developers list...
I think this is bogus; as Dmitri's mail shows it is a maintenance nightmare waiting to happen. If you really want to do a validation of an email address, use DNS to see if there's a host by that name or an MX record for that domain. What is the reason for validating addresses in the first place? If the address is invalid, the mail will bounce and the user won't be registered. Simple. Effective.
While i'm inclined to agree about the list-of-known-domains check being too maintenance intensive, i do see a reason to have the check in the first place. The benefit comes into play when the web interface is in play - the user is there, and can get definite feedback about faulty addresses. Without it, they only see address failures as the absence of any subscription confirmation - a decidedly vague and uncertain kind of feedback.
At this point i'm inclined to withdraw the known-domains criterion, but leave in the more definite, unchanging criterion, like presence of an '@' sign.
Ken
On Thu, Apr 23, 1998 at 11:22:06AM -0400, Ken Manheimer wrote: | On Thu, 23 Apr 1998, Guido van Rossum wrote: | | > Ken writes: | > [...] | At this point i'm inclined to withdraw the known-domains criterion, but | leave in the more definite, unchanging criterion, like presence of an | '@' sign. | | Ken
sounds good. maybe make sure there's atleast a dot in there to signify a FQDN.
scott
"KM" == Ken Manheimer <klm@cnri.reston.va.us> writes:
KM> While i'm inclined to agree about the list-of-known-domains
KM> check being too maintenance intensive, i do see a reason to
KM> have the check in the first place. The benefit comes into
KM> play when the web interface is in play - the user is there,
KM> and can get definite feedback about faulty addresses. Without
KM> it, they only see address failures as the absence of any
KM> subscription confirmation - a decidedly vague and uncertain
KM> kind of feedback.
Couldn't we do the same sort of DNS lookup when the form is submitted?
-Barry
participants (4)
-
Barry A. Warsaw -
Guido van Rossum -
Ken Manheimer -
Scott