comp.protocols.dns.bind
Has the newsgroup gateway been switched off or is it just broken? The most recent post for this newsgroup in Google groups is 15-Feb-2011. -- John Marshall ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Double messages in comp.protocols.dns.bind
In article mailman.366.1250954533.14796.bind-us...@lists.isc.org, Barry Margolin bar...@alum.mit.edu wrote: It looks like there are two mail-to-news gateways running for bind-users, so every message to the list is being posted twice to the newsgroup. ... But at least messages are now being posted to the newsgroup - the gatewaying, at least as seen from here and from Google, went AWOL on 4 June 09. Postings from 15 Aug onward have now appeared. So thank you, ISC, even if the gatewaying is now a little overenthusiastic. :-) Sam ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Double messages in comp.protocols.dns.bind
In article mailman.369.1251129971.14796.bind-us...@lists.isc.org, Sam Wilson sam.wil...@ed.ac.uk wrote: In article mailman.366.1250954533.14796.bind-us...@lists.isc.org, Barry Margolin bar...@alum.mit.edu wrote: It looks like there are two mail-to-news gateways running for bind-users, so every message to the list is being posted twice to the newsgroup. ... But at least messages are now being posted to the newsgroup - the gatewaying, at least as seen from here and from Google, went AWOL on 4 June 09. Postings from 15 Aug onward have now appeared. You're right, I hadn't even noticed that the newsgroup has been silent for several months. So thank you, ISC, even if the gatewaying is now a little overenthusiastic. :-) It's gotten worse. Today I'm seeing quadruple messages in the I have a question concerning the spf thread. Two plain text messages, and two that are just a big block of base64 encoding. -- Barry Margolin, bar...@alum.mit.edu Arlington, MA *** PLEASE don't copy me on replies, I'll read them in the group *** ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Double messages in comp.protocols.dns.bind
It's gotten worse. Today I'm seeing quadruple messages in the I have a question concerning the spf thread. Two plain text messages, and two that are just a big block of base64 encoding. Strangely enough, just for that thread, we got 2 identical messages on bind-us...@lists.isc.org. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Double messages in comp.protocols.dns.bind
On Monday 24 August 2009 at 23:32 (CET), Andy Shellam wrote: It's gotten worse. Today I'm seeing quadruple messages in the I have a question concerning the spf thread. Two plain text messages, and two that are just a big block of base64 encoding. Strangely enough, just for that thread, we got 2 identical messages on bind-us...@lists.isc.org. Which was addressed to the list twice: To: Bind users bind-users@lists.isc.org, Bind users bind-us...@isc.org -- Regards, Ruben Laban Systems and Network Administrator ISM eCompany ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
bind-users - comp.protocols.dns.bind stopped?
I note that the last posting in comp.protocols.dns.bind seems to have been on 4-Jun-09, both on my local news server and on Google Groups. I can't see any relevant announcements in the archive. What's happened? Sam ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
comp.protocols.dns.bind
Hi all, Suppose a file named file.pdf stored in the following web location: http://some_domain/path/to/file.pdf Where, the *some_domain* is a name-based virtual host. In this case, is it possible to set a ddns hostname, say through http://www.changeip.net/, without using *some_domain* itself, to access this file? -- .: Hongyi Zhao [ hongyi.zhao AT gmail.com ] Free as in Freedom :. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: MIME garbage in comp.protocols.dns.bind
In message sam.wilson-404a4b.13132515122...@scotsman.ed.ac.uk, Sam Wilson wri tes: In article ghubkr$9l...@sf1.isc.org, Chris Buxton cbux...@menandmice.com wrote: On Dec 11, 2008, at 10:57 PM, Barry Margolin wrote: The old mail-to-news gateway either got this right or extracted the plain text alternative before forwarding. The old mail server stripped messages down to their plaintext values. The new one does not - it allows both formatted text and attachments. This is no doubt the change that's causing this problem with usenet. But it's doing it wrong - it's removing some MIME headers that it shouldn't. (I will defer to other people if there is a mismatch in what is acceptable in MIME headers on Usenet, but the old one worked and the new one creates unreadable news postings.) Sam ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users I've raised a ticket with our ops people. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: mark_andr...@isc.org ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: MIME garbage in comp.protocols.dns.bind
In article ghtjng$2pd...@sf1.isc.org, Barry Margolin bar...@alum.mit.edu wrote: Does anyone still read this list via the comp.protocols.dns.bind Usenet gateway? I do, and ever since the web site and mailing list revamp last month, it has been a real PITA. About 1/3 of the messages in the group have all sorts of MIME garbage in the body of the messages. The problem appears to be that the Content-type: multipart/alternative header line is being stripped from the header by the gateway; actually, it ends up in the body of the message. As a result, my newsreader doesn't recognize that the message is multipart, and shows all the pieces literally. You can see the same thing if you view the messages in Google Groups, so it's not just my news provider (Motzarella) or newsreader (MT-Newswatcher). The old mail-to-news gateway either got this right or extracted the plain text alternative before forwarding. I sent mail to bind-users-request a few weeks ago, but got no response. Is this bugging anyone else but me? Yes, it's bugging me. I use MT-Newswatcher (Mac OS X) and whilst I can cope with the multipart/alternative hassle (just stop reading where it turns into HTML - see [1]) the ones that really annoy me are the base64 encoded messages like [2]. I'm clearly less conscientious than Barry - I haven't complained before now. Sam [1] news:ghs3de$1f8...@sf1.isc.org [2] news:ghtbae$2er...@sf1.isc.org ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: MIME garbage in comp.protocols.dns.bind
In article ghtmfl$2rc...@sf1.isc.org, Sam Wilson sam.wil...@ed.ac.uk wrote: In article ghtjng$2pd...@sf1.isc.org, Barry Margolin bar...@alum.mit.edu wrote: Does anyone still read this list via the comp.protocols.dns.bind Usenet gateway? I do, and ever since the web site and mailing list revamp last month, it has been a real PITA. About 1/3 of the messages in the group have all sorts of MIME garbage in the body of the messages. The problem appears to be that the Content-type: multipart/alternative header line is being stripped from the header by the gateway; actually, it ends up in the body of the message. As a result, my newsreader doesn't recognize that the message is multipart, and shows all the pieces literally. You can see the same thing if you view the messages in Google Groups, so it's not just my news provider (Motzarella) or newsreader (MT-Newswatcher). The old mail-to-news gateway either got this right or extracted the plain text alternative before forwarding. I sent mail to bind-users-request a few weeks ago, but got no response. Is this bugging anyone else but me? Yes, it's bugging me. I use MT-Newswatcher (Mac OS X) and whilst I can cope with the multipart/alternative hassle (just stop reading where it turns into HTML - see [1]) the ones that really annoy me are the base64 encoded messages like [2]. I'm clearly less conscientious than Barry - I haven't complained before now. Sam [1] news:ghs3de$1f8...@sf1.isc.org [2] news:ghtbae$2er...@sf1.isc.org I was wondering what was going on. Some messages are just base64 and are completely useless/unreadable. -- Tom Schulz sch...@adi.com ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: MIME garbage in comp.protocols.dns.bind
On Dec 11, 2008, at 10:57 PM, Barry Margolin wrote: The old mail-to-news gateway either got this right or extracted the plain text alternative before forwarding. The old mail server stripped messages down to their plaintext values. The new one does not - it allows both formatted text and attachments. This is no doubt the change that's causing this problem with usenet. Chris Buxton Men Mice ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
