Re: [DNG] [kato...@freaknet.org: Re: Debugging Devuan .onion/TOR]
On 12/25/18 10:28 AM, ghostlands via Dng wrote: > Still timing out on my end. Error messages in full: > > "The repository may no longer be available or could not be contacted because > of network problems. If available an older version of the failed index will > be used. Otherwise the repository will be ignored. Check your network > connection and ensure the repository address in the preferences is correct. > > Failed to fetch tor://devuanfwojg73k6r.onion/merged/dists/ascii/InRelease > SOCKS proxy socks5h://localhost:9050 could not connect to > devuanfwojg73k6r.onion (0.0.0.0:0) due to: Host unreachable (6) [IP: > 127.0.0.1 9050]Failed to fetch > tor://devuanfwojg73k6r.onion/merged/dists/ascii-security/InRelease SOCKS > proxy socks5h://localhost:9050 could not connect to devuanfwojg73k6r.onion > (0.0.0.0:0) due to: Host unreachable (6) [IP: 127.0.0.1 9050]Failed to fetch > tor://devuanfwojg73k6r.onion/merged/dists/ascii-updates/InRelease SOCKS > proxy socks5h://localhost:9050 could not connect to devuanfwojg73k6r.onion > (0.0.0.0:0) due to: Host unreachable (6) [IP: 127.0.0.1 9050]Some index files > failed to download. They have been ignored, or old ones used instead." > > On a lighter note: Happy Holidays, Devuan community! > > gl > > tor+http:// is working for me at this time. Maybe restart your tor server? And happy holidays to all! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Admins can you fix/set the header overrides?
On Wed, 26 Dec 2018 20:06:52 + Simon Hobson wrote: > Michael wrote: > > >> Argh. Sending to the list this time. > >> > >> Please don't set "Reply-to" on list emails. > >> > >> Antony. > > > > I’m pretty sure the individuals aren’t doing it explicitly. This > > list just doesn’t seem to create, or override really, the headers > > quite right. Some messages here I hit reply (like this one) and > > the proper “To: dng@lists.dyne.org” shows up, on others someone’s > > name is populated in the To: box. Other lists, you hit reply and > > To: is always populated correctly. > > > > golinux?, other admins?, is there a config option somewhere in the > > backend to ‘fix’ this? > > Unfortunately I think it's one of those things where you have to > break some stuff to work around the deliberate breakage implemented > with malice aforethought by many large email providers. > > The problem is SPF, DMARC, and friends. These basically provide > information about where emails may come from - eg gmail may only come > from Google's servers. This is a problem for any system that forwards > email - such as mailing lists and mail servers setup to forward email > for (say) i...@nicetownplumbers.co.uk to > ntplumb2458...@someispmail.com. > > So, someone using gmail sends a message to dng@lists.dyne.org which > is delivered and then forwarded to all the list users. Some of those > users will be using mail services that check SPF etc - and oh dear, > there's an email which purports to come from gmail but it's actually > being sent from a dyne.org server. So it gets discarded as obviously > spam. I'd suggest we ban email from gmail, yahoo, protonmail, and the rest that demand strict adherence to DMARC. A person can pay $18.00/year for his/her own domain, and that domain will give them at least one email address, maybe more. If somebody is too cheap to pay $18/year for email that doesn't require every list they're on to do all sorts of BS that often leads to an accidental sending to the whole list of an intended private response, they don't belong here. Eat only beans for four days and you've probably saved enough to buy good email for the whole year. On another of my mailing lists, I filtered all DMARC clusterscrewups to /dev/null. Everyone on DNG is smart enough to understand the value of a real email address. SteveT Steve Litt December 2018 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Admins can you fix/set the header overrides?
Quoting Michael (mb_devuan-mailingl...@inet-design.com):
> I am going to say, that the Trinity Desktop Environment (TDE) Users
> mailing list seems to send from/to ProtonMail without the reply to
> issue the Devuan Users list has. The list admin, and owner of the
> project, is Timothy Pearson, and his publicly published email is:
If you're saying that the TDE Users mailing list doesn't apply the
Mailman-recommended DMARC mitigation, then you are correct that no
MLM-level munging of the sender's 'From: ' header (or appending of a
Reply-To: header for DMARC-mitigation reasons) will be applied to any
subscriber's mail.
Unfortunately, that would _also_ mean that TDE Users postings from domains
with aggressive DMARC policies will encounter deliverability issues to
receiving domains that enforce DMARC (e.g., to GMail). And this bad
situation will persist for TDE Users members unles/until the listadmin
applies DMARC mitigations.
> The headers are fairly different, not that I know what specifically ‘fixes’
> this issue, but I’ll guess it would hopefully give a clue as to what/where
> the fix lies.
{sigh} Nobody listens.
There is nothing needing a 'fix' (unless you wish to argue with
operators of domains publishing aggressive DMARC policies (p=reject or
p=quarantine) and convince them that such is an unwise policy). In a
world where DMARC is being rolled out by many domains, mailing lists can
either attempt to mitigate the DMARC-caused damage, or do nothing and
let some subscribers and their readers figure out the hard way why
certain posters aren't being received at certain domains (e.g., GMail)
and are getting gradually auto-unsubscribed by Mailman on account of
excessive 'bounce scores'.
--
Cheers,"He who laughs last, lasts."
Rick Moen -- Leo Rosten
r...@linuxmafia.com
McQ! (4x80)
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Admins can you fix/set the header overrides?
Simon, I appreciate your pitching in to attempt to answer this question. A few necessary corrections, though: Quoting Simon Hobson (li...@thehobsons.co.uk): > Unfortunately I think it's one of those things where you have to break > some stuff to work around the deliberate breakage implemented with > malice aforethought by many large email providers. Indeed it's a regrettable but small breakage, necessitated by (specifically) the DKIM cryptographic signing component within DMARC's omnibus framework.[1] > The problem is SPF, DMARC, and friends. Incorrect. SPF poses _no_ challenges for mailing lists. E.g., my domains have since 2003 published aggressive SPF policies, and encounter absolutely zero problems with either sent or received mailing list mail (to or from my domains) getting spamboxed or rejected on account of perceived forgery. $ dig -t txt linuxmafia.com +short "v=spf1 ip4:198.144.195.186 -all" $ dig -t txt unixmercenary.net +short "v=spf1 ip4:198.144.195.186 -all" $ That hyphen in concluding field '-all' signifies 'Dear receiving SMTP hosts, please hardfail as conclusively forged any SMTP mail that doesn't originate in one of the places listed' (the only place listed in this case being a single IP). So, given the many mailing lists I host, and the many mailing lists I subscribe to, if SPF caused a problem for mailing lists, I would know. Indeed, if you understand how SPF works, you can figure out that there is no way that SPF _could_ claim MLM-reflected (mailing list manager-reflected) mail is forged, because the reflected copy bears a fresh envelope header from the mailing list's domain, in contrast to that of the sender's domain it had during the initial hop. Simon, I really do appreciate your effort to help, but we already had this conversation on Dng in August 2017. You confidently made these same mistakes and I painstakingly corrected the erroneous information, so it's rather unfortunate to have to go through this with you yet again. Would you mind doing me a solid? Please read up about antiforgery methods before making similar claims again. > So, someone using gmail sends a message to dng@lists.dyne.org which is > delivered and then forwarded to all the list users. Some of those > users will be using mail services that check SPF etc - and oh dear, > there's an email which purports to come from gmail but it's actually > being sent from a dyne.org server. So it gets discarded as obviously > spam. As to SPF, this claim is (again) flatly incorrect. SPF validates (solely) the envelope 'From ' header (used in the SMTP MAIL FROM operation) against forgery, not the internal 'From:' (etc.) headers. So, it does _not_ cause the effect you describe. > What they've down with the list (and I've seen it with other lists > too) is: if the mail matches some criteria, then the originator's > address is replaced with the list address and a reply to header is > added. Thus for those users on a broken mail system (such as gmail, or > hotmail, or ... they still get the list emails instead of not seeing > mails from some proportion of list users. This is almost but not quite correct. Retransmission by the mailing list software introduces unavoidable header and body alterations that cause a message's DKIM cryptographic signature to be no longer able to be validatable against the sending domain's DKIM public key. _If_ the sending domain has published an aggressive DMARC policy (p=reject or p=quarantine) _and_ the subscriber's receiving domain enforces sending domains' DMARC policies, then the subscriber copy will be (respectively) rejected or spamboxed. > Not sure what the criteria are - whether it's based on there being > certain headers in the email, whether the sender domain has SPF > records etc, or what. Criterion used: Sender's domain publishes an aggressive DMARC policy (=reject or p=quarantine). > One answer is to always use reply to all and then move/remove > addresses so you just have a single destination of the list address. I am unclear on what you mean, here, by 'answer' -- but the Dng mailing list's DMARC-mitigation configuration will categorically munge the internal 'From:' header (upon retransmission to subscribers) of any posting from a domain with an aggressive DMARC policy, and (by way of attempt to compensate for the regrettable but necessary damage) appending a Reply-To: header pointing back to the poster's real posting address. The steps you recommend (above) would have no effect whatsoever on Mailman's DMARC mitigation. Not intended to complain, but I comprehensively explained Dng's alterations to do DMARC mitigation on December 6th, when the listadmins rolled out GNU Mailman's most-recommended DMARC mitigation: https://lists.dyne.org/lurker/message/20181206.100230.c6157b41.en.html [1] DMARC is a mammoth superset of SPF and DKIM in which either or both of those pre-existing antiforgery mechanisms is present along with checking what is called 'alignment'
Re: [DNG] Admins can you fix/set the header overrides?
On Wednesday 26 December 2018 02:06:52 pm Simon Hobson wrote: > The problem is SPF, DMARC, and friends. These basically provide information > about where emails may come from - eg gmail may only come from Google's > servers. This is a problem for any system that forwards email - such as > mailing lists and mail servers setup to forward email for (say) > i...@nicetownplumbers.co.uk to ntplumb2458...@someispmail.com. On Wednesday 26 December 2018 03:05:43 pm Rick Moen wrote: > _Why_, and why (specifically) _your_ mail? Actually, it's not just > you, but rather your sending domain, protonmail.com. Protonmail creates > a challenge to any mailing list by publishing an aggressive DMARC > antiforgery policy in its public DNS: Okay, I'm not disagreeing with either of you on SPF/DMARC/etc.’s inner workings, as I have to wrangle those beasts myself for my clients' DNS to work correctly. Literal headache every time. I am going to say, that the Trinity Desktop Environment (TDE) Users mailing list seems to send from/to ProtonMail without the reply to issue the Devuan Users list has. The list admin, and owner of the project, is Timothy Pearson, and his publicly published email is: "Timothy Pearson" He's somewhat hard to get a hold of, but I can certainly provide copies of my message headers to the TDE users list privately to the admin(s) of this list. The headers are fairly different, not that I know what specifically ‘fixes’ this issue, but I’ll guess it would hopefully give a clue as to what/where the fix lies. I was also a member of the LEAF user list for near 20 years, I don’t remember them ever having the issue either. I can dig up some old headers (‘17) off that list as well if an admin here thinks it would help. # # # Admittedly, just being able to always click reply and it ‘just works’ is a triviality on any issue scale, but if there’s anything I can do to help get there, I’m in, as it’s momentous on my annoyance scale. Best All, Michael ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] IceCat
Hi again, On 25/12/18 10:53, aitor wrote: On 25/12/18 10:51, aitor wrote: Today i'll start uploading the releases of gnuinos ascii, including xfce, lxde, mate, lxqt, kde... I'll share the sources of the live-sdk with d-i. Here you are the souces: http://gnuinos.org/live-sdk/ Just run: $ sudo su # zsh -f # source sdk # load devuan i386 gnuinos-lxde [*] # build_iso_dist I list the builddeps: gnupg2 schroot debootstrap debhelper makedev curl rsync dpkg-dev squashfs-tools \ gcc-arm-none-eabi parted kpartx qemu-user-static pinthread sudo debmirror reprepro zsh \ build-essential:native debhelper dctrl-tools bc debiandoc-sgml xsltproc docbook-xml docbook-xsl \ libbogl-dev libc6-pic libslang2-pic libnewt-pic genext2fs mklibs genisoimage dosfstools syslinux \ syslinux-utils isolinux pxelinux syslinux-common grub-efi-ia32-bin grub-common xorriso tofrodos \ mtools kmod bf-utf-source openssl win32-loader librsvg2-bin sed cpio \ grub-efi-amd64-bin liblz4-1 debmirror rpl [*] Use the same arch for both the holiday and the guest systems. Otherwise, debian-installer will not build succesfully. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Admins can you fix/set the header overrides?
Quoting chillfan via Dng (dng@lists.dyne.org): > I can confirm that I haven't set a reply-to header, but this is just a > web mail. It could be that my webmail provider just doesn't allow me > to unset the header, but I haven't looked that far into it. Indeed, you didn't set it in this case. Short version: It's a mitigation on the mailing list server for the problem of DMARC. Your headers as you send them were like this: From: chillfan > To: "dng@lists.dyne.org" Mailman is configured to alter your postings' headers (for retransmission to all subscribers) as follows: From: chillfan via Dng To: "dng@lists.dyne.org" Reply-To: chill...@protonmail.com _Why_, and why (specifically) _your_ mail? Actually, it's not just you, but rather your sending domain, protonmail.com. Protonmail creates a challenge to any mailing list by publishing an aggressive DMARC antiforgery policy in its public DNS: $ dig -t txt _dmarc.protonmail.com +short "v=DMARC1; p=quarantine; fo=1;" $ Because of that aggressive 'p=quarantine' policy, and because Mailman (like all other MLM = mailing list manager packages) makes changes to postings (upon retransmission to subscribers) that unavoidably cause the subscriber copies to fail checks of the message's DMARC cryptographic signature. This is a serious problem for mailing lists, causing retransmitted mail to either be rejected (if 'p=reject') or spamboxed (if 'p=quarantined') at any receiving domain that enforces DMARC. Mailman's mitigation (see above example) circumvents the damage from 'p=quarantine' or 'p=reject' policies by substituting the mailing list's domain as sending domain during retransmission. It adds a Reply-To as described in the above example, in order to preserve the sender's intended originating address as well as possible under the circumstances. Mailman does _not_ apply this mitigation to all postings, only to ones from domains with p=quarantine or p=reject DMARC policies (aggressive ones). Admittedly, the end-result is a bit irksome, but it's the least-bad solution to the DMARC challenge the Mailman developers have so far come up with. (I advised Devuan's mailing list administrators on how to handle the DMARC problem, which was causing subscribers problems, as is happening on mailing lists everywhere.) -- Cheers,"He who laughs last, lasts." Rick Moen -- Leo Rosten r...@linuxmafia.com McQ! (4x80) ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Admins can you fix/set the header overrides?
Michael wrote: >> Argh. Sending to the list this time. >> >> Please don't set "Reply-to" on list emails. >> >> Antony. > > I’m pretty sure the individuals aren’t doing it explicitly. This list just > doesn’t seem to create, or override really, the headers quite right. Some > messages here I hit reply (like this one) and the proper “To: > dng@lists.dyne.org” shows up, on others someone’s name is populated in the > To: box. Other lists, you hit reply and To: is always populated correctly. > > golinux?, other admins?, is there a config option somewhere in the backend > to ‘fix’ this? Unfortunately I think it's one of those things where you have to break some stuff to work around the deliberate breakage implemented with malice aforethought by many large email providers. The problem is SPF, DMARC, and friends. These basically provide information about where emails may come from - eg gmail may only come from Google's servers. This is a problem for any system that forwards email - such as mailing lists and mail servers setup to forward email for (say) i...@nicetownplumbers.co.uk to ntplumb2458...@someispmail.com. So, someone using gmail sends a message to dng@lists.dyne.org which is delivered and then forwarded to all the list users. Some of those users will be using mail services that check SPF etc - and oh dear, there's an email which purports to come from gmail but it's actually being sent from a dyne.org server. So it gets discarded as obviously spam. What they've down with the list (and I've seen it with other lists too) is: if the mail matches some criteria, then the originator's address is replaced with the list address and a reply to header is added. Thus for those users on a broken mail system (such as gmail, or hotmail, or ... they still get the list emails instead of not seeing mails from some proportion of list users. The downside is what you see. Not sure what the criteria are - whether it's based on there being certain headers in the email, whether the sender domain has SPF records etc, or what. One answer is to always use reply to all and then move/remove addresses so you just have a single destination of the list address. I do ths all the time out of habit - partly because my mailer does somethings slightly differently with reply all, partly because I'm on a few lists and they all seem to do things differently (some have always left the senders address, some have always replaced it, some have always used a reply to, ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Admins can you fix/set the header overrides?
I can confirm that I haven't set a reply-to header, but this is just a web mail. It could be that my webmail provider just doesn't allow me to unset the header, but I haven't looked that far into it. Cheers, chillfan ‐‐‐ Original Message ‐‐‐ On Wednesday, December 26, 2018 4:07 PM, Michael wrote: > On Wednesday 26 December 2018 03:24:24 am Antony Stone wrote: > > > Argh. Sending to the list this time. > > Please don't set "Reply-to" on list emails. > > Antony. > > I’m pretty sure the individuals aren’t doing it explicitly. This list just > doesn’t seem to create, or override really, the headers quite right. Some > messages here I hit reply (like this one) and the proper “To: > dng@lists.dyne.org” shows up, on others someone’s name is populated in the > To: box. Other lists, you hit reply and To: is always populated correctly. > > golinux?, other admins?, is there a config option somewhere in the backend > to ‘fix’ this? > > Best, > Michael > > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng publickey - chillfan@protonmail.com - 0xB179B25B.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Admins can you fix/set the header overrides?
On Wednesday 26 December 2018 03:24:24 am Antony Stone wrote: > Argh. Sending to the list this time. > > Please don't set "Reply-to" on list emails. > > Antony. I’m pretty sure the individuals aren’t doing it explicitly. This list just doesn’t seem to create, or override really, the headers quite right. Some messages here I hit reply (like this one) and the proper “To: dng@lists.dyne.org” shows up, on others someone’s name is populated in the To: box. Other lists, you hit reply and To: is always populated correctly. golinux?, other admins?, is there a config option somewhere in the backend to ‘fix’ this? Best, Michael ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] IceCat
Argh. Sending to the list this time. Please don't set "Reply-to" on list emails. Antony. On Wednesday 26 December 2018 at 00:23:37, chillfan via Dng wrote: > Spam detection software, running on the system "tupac3.dyne.org", > has identified this incoming email as possible spam. > 2.3 URI_NO_WWW_INFO_CGIURI: CGI in .info TLD other than third-level > "www" That seems to me like a dangerously high score to apply for detecting the URL wiki dot hyperbola dot info slash doku dot php. Antony. -- What do you call a dinosaur with only one eye? A Doyouthinkesaurus. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] try Tor Browser Bundle? [was:] IceCat
On Tue, 25 Dec 2018 12:50:14 -0600, Michael wrote in message
<201812251250.14637.mb_devuan-mailingl...@inet-design.com>:
> On Tuesday 25 December 2018 04:40:09 am Edward Bartolo via Dng wrote:
> > So, this is yet another limited browser that many modern web-sites
> > find repulsive to connect to. It is clear the problem is not the
> > browsers themselves, but economical and political.
>
> [snip basic reality]
>
> I know nothing of IceCat, nor am I trying to dismiss it. But... If
> you’re looking for a browser that’s exceptionally good at displaying
> modern web-sites and keeping capitalists ‘out of your business’ try
> the Tor Browser Bundle (TBB),
> https://www.torproject.org/projects/torbrowser.html .
>
> If you’re still concerned with ads and privacy, but are sticking with
> one of the ‘big 6,’ try the addon AdBlocker Ultimate (AU),
> https://adblockultimate.net/ .
>
> TBB with AU seems to be one of the better combinations to view
> websites as intended while maintaining your privacy.
..work-around idea: tempuser=$(date |sum |tr -d [:blank:]) && \
adduser $tempuser # ..creates a credible newbie new user \
mkdir -vp $tempuser &&ssh -X $tempuser@127.0.0.1 nice -n 17 \
chromium --proxy-server="socks://127.0.0.1:9050" &&cp -avf \
/home/$tempuser/.config/chromium/Default/{Bookmarks,History} \
$tempuser/ &&deluser $tempuser --backup-to $tempuser/
.."create a credible newbie new user, have him browse the web
exactly once, copy his history and bookmark files, kill him."
--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] [kato...@freaknet.org: Re: Debugging Devuan .onion/TOR]
On Tue, 25 Dec 2018 16:28:56 +, ghostlands wrote in message <-b5H-82mXxk-GT_T1IAS3WeAwJiTE6MCIpM9m9DS3J5ve7IVnFCT2597S2-Wy0x1lDzcSZImket_N2ggqAiBsotruFhJjUnOrbtDAOtYu94=@protonmail.ch>: > Still timing out on my end. Error messages in full: > > "The repository may no longer be available or could not be contacted > because of network problems. If available an older version of the > failed index will be used. Otherwise the repository will be ignored. > Check your network connection and ensure the repository address in > the preferences is correct. > > Failed to fetch > tor://devuanfwojg73k6r.onion/merged/dists/ascii/InRelease SOCKS > proxy socks5h://localhost:9050 could not connect to > devuanfwojg73k6r.onion (0.0.0.0:0) due to: Host unreachable (6) [IP: > 127.0.0.1 9050]Failed to fetch > tor://devuanfwojg73k6r.onion/merged/dists/ascii-security/InRelease > SOCKS proxy socks5h://localhost:9050 could not connect to > devuanfwojg73k6r.onion (0.0.0.0:0) due to: Host unreachable (6) [IP: > 127.0.0.1 9050]Failed to fetch > tor://devuanfwojg73k6r.onion/merged/dists/ascii-updates/InRelease > SOCKS proxy socks5h://localhost:9050 could not connect to > devuanfwojg73k6r.onion (0.0.0.0:0) due to: Host unreachable (6) [IP: > 127.0.0.1 9050]Some index files failed to download. They have been > ignored, or old ones used instead." > > On a lighter note: Happy Holidays, Devuan community! ..thanks, try again, it's up now. > gl > > > ‐‐‐ Original Message ‐‐‐ > On Sunday, December 23, 2018 3:06 PM, KatolaZ > wrote: > > > On Sun, Dec 23, 2018 at 01:39:31PM +0100, Arnt Karlsen wrote: > > > > > On Sun, 23 Dec 2018 12:48:11 +0100, KatolaZ wrote in message > > > 20181223114811.p4u6c3et2vsi4...@katolaz.homeunix.net: > > > > > > > On Sat, Dec 22, 2018 at 11:32:37PM +0100, Arnt Karlsen wrote: > > > > > > > > > On Sat, 22 Dec 2018 22:23:12 +0100, KatolaZ wrote in message > > > > > 2018112311.yxleukxbnjohj...@katolaz.homeunix.net: > > > > > > > > > > > Sorry, replied to sender instead of list. > > > > > > Just to confirm that the onion address seems to be working > > > > > > correctly from here now. > > > > > > > > > > ..it still times out on my chrome-thru-tor, "from" > > > > > 91.219.236.171 and 199.87.154.255 and 199.249.230.83. > > > > > > > > Can you please try again now? It looks like some trafic shaping > > > > setup was too strict. > > > > > > ..now it works ok. > > > > You are welcome. > > > > HND > > > > KatolaZ > > > > - > > > > [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] > > [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] > > [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] > > [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] > > [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
