• Re: ThunderMail is coming soon

    From Paul@3:633/280.2 to All on Tue Apr 22 19:58:29 2025
    On Mon, 4/21/2025 6:36 PM, VanguardLH wrote:
    Andy Burns <usenet@andyburns.uk> wrote:

    VanguardLH wrote:

    kyonshi wrote:

    actually I don't know, who's behind thundermail?

    Mozilla devs. More explained in the above blog.

    Mozilla devs, or MZLA devs?

    I realise a few years ago they had reasons to separate them off, does it
    serve a purpose today to keep them separate?

    Po-tay-to. Po-tah-to. Saying it was your foot that kicked me, and not
    you, makes no difference to my butt. Organization hierarchy is of
    interest to managerial types, not to me. It's ALL Mozilla to me.


    You know that Mozilla is packing a parachute right now.

    The last article I read two hours ago, is looking at
    Google having to ditch Chrome as a part of the DOJ
    remedy, and the Mozilla contract got an honorable mention as
    part of the solution as well.

    If Mozilla is going into the poor house, this is why
    they're working on their own self-sustaining business
    opportunities (no matter what their corporate structure
    is, and how they would morph in view of the potential outcome).
    They will have to "shed something" and "belt tighten" and
    change their corporate structure and charter.

    It used to be, they practiced their business opportunities
    as a bit of a lark, but now it's crunch time. A donation model
    would never work.

    Paul

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From VanguardLH@3:633/280.2 to All on Tue Apr 22 22:43:12 2025
    Keywords: VanguardLH,VLH

    Paul <nospam@needed.invalid> wrote:

    You know that Mozilla is packing a parachute right now.

    The last article I read two hours ago, is looking at
    Google having to ditch Chrome as a part of the DOJ
    remedy, and the Mozilla contract got an honorable mention as
    part of the solution as well.

    If Mozilla is going into the poor house, this is why
    they're working on their own self-sustaining business
    opportunities (no matter what their corporate structure
    is, and how they would morph in view of the potential outcome).
    They will have to "shed something" and "belt tighten" and
    change their corporate structure and charter.

    It used to be, they practiced their business opportunities
    as a bit of a lark, but now it's crunch time. A donation model
    would never work.

    Yep, I've noted before that Google is getting nailed for bribing web
    browser authors, and other anti-trust marketing practices with their
    grip on online advertising. Mozilla could lose 97% of their revenue
    that comes from Google. That's why all those services from Mozilla are unlikely to [remain to] be free. They won't be able to afford any
    further altruism. The tit goes dry, and entitled users whine louder.

    If Google has to decouple from Chromium, can the rest of the Chromium
    dev team keep producing a competitive, up to date, and secure web
    browser into the future? Chromium is developed and maintained by
    Google. With Google gone, who is left to work on Chromium are a group
    of devs unknown and unrecognized by the vast majority of users. Chromium doesn't have automatic updates, API keys for Google services (e.g.,
    browser sync), Widevine DRM, licensed codecs for H.264 and AAC, crash reporting, etc. Chrome is oriented to a consumer market. Chromium is
    oriented to a much smaller more expert/nerd community. Ask your friends
    to see how many use Chromium. Chromium never shows up in browser market
    share statistics.

    If Google has to walk away from Chromium, who is left in its dev team?
    Chromium has been a Google project from its inception. Google does the
    vast bulk of development on Chromium. The Chromium projects (Chromium
    and ChromeOS) are not independent of Google. Some of the other
    contributors have been Microsoft, Intel, Samsung, and variant authors,
    like Opera, Vivaldi, and Brave. Of those, and after Google, Microsoft
    is the next biggest powerhouse, so, gee, might we end up with Microsoft
    Chrome? Well, there's already Edge-C (Edge that became a Chromium
    variant after Microsoft dropped EdgeHTML).

    Without Google to pay Mozilla, Mozilla won't have the financial strength anymore to continue the current level of development. Firefox might get
    more market share, but Mozilla becomes much weaker. If Google decouples
    from Chrome, could be Chromium loses their major developer along with
    all its services, so Chromium also becomes much weaker. No sponsors, no
    money. No money, no development. Programmers need to eat, too.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Usenet Elder (3:633/280.2@fidonet)
  • From VanguardLH@3:633/280.2 to All on Tue Apr 22 22:49:57 2025
    Keywords: VanguardLH,VLH

    Daniel70 <daniel47@eternal-september.org> wrote:

    On 22/04/2025 2:53 am, s|b wrote:
    On Sun, 20 Apr 2025 15:49:15 -0500, VanguardLH wrote:

    Additionally, you will be able to bring your own domain on day 1 of
    the service."

    I don't own a domain, I've registered it and pay for mailhosting to a
    firm in a country that respects GDPR. Why would want to move?

    "GDPR"?? Thank you, Google and Wikipedia

    "General Data Protection Regulation"

    https://en.wikipedia.org/wiki/General_Data_Protection_Regulation

    GDPR ruined DNS lookups by requiring redaction of registrants. Trying
    to get contact info on a domain registrant to alert them to a problem
    with their web site becomes much more difficult. Yeah, they want to
    provide a publicly accessible web site, but the registrant wants to
    hide. Thanks GDPR ... not!

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Usenet Elder (3:633/280.2@fidonet)
  • From Chris@3:633/280.2 to All on Tue Apr 22 23:58:10 2025
    VanguardLH <V@nguard.LH> wrote:
    Daniel70 <daniel47@eternal-september.org> wrote:

    On 22/04/2025 2:53 am, s|b wrote:
    On Sun, 20 Apr 2025 15:49:15 -0500, VanguardLH wrote:

    Additionally, you will be able to bring your own domain on day 1 of
    the service."

    I don't own a domain, I've registered it and pay for mailhosting to a
    firm in a country that respects GDPR. Why would want to move?

    "GDPR"?? Thank you, Google and Wikipedia

    "General Data Protection Regulation"

    https://en.wikipedia.org/wiki/General_Data_Protection_Regulation

    GDPR ruined DNS lookups by requiring redaction of registrants. Trying
    to get contact info on a domain registrant to alert them to a problem
    with their web site becomes much more difficult. Yeah, they want to
    provide a publicly accessible web site, but the registrant wants to
    hide. Thanks GDPR ... not!

    A decent website will a contact option. You should not have to be forced to give out personal information via a WHOIS lookup.

    So yes, thanks GDPR.


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Java Jive@3:633/280.2 to All on Wed Apr 23 00:39:29 2025
    On 2025-04-22 13:49, VanguardLH wrote:

    GDPR ruined DNS lookups by requiring redaction of registrants. Trying
    to get contact info on a domain registrant to alert them to a problem
    with their web site becomes much more difficult. Yeah, they want to
    provide a publicly accessible web site, but the registrant wants to
    hide. Thanks GDPR ... not!

    Can't say that I've noticed any such problem - I just use Whois - so
    I suspect that this is just another example of someone from the other
    side of the pond having an uninformed opinion against the EU and its legislation. Many countries in the EU, including Britain who was still
    a member at the time, had or were considering their own similar national legislation, but it was always obviously one of those matters where a continent wide harmonised approach made more sense.

    https://whois.domaintools.com/

    --

    Fake news kills!

    I may be contacted via the contact address given on my website: www.macfh.co.uk


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Frank Slootweg@3:633/280.2 to All on Wed Apr 23 01:32:10 2025
    Chris <ithinkiam@gmail.com> wrote:
    VanguardLH <V@nguard.LH> wrote:
    [...]

    GDPR ruined DNS lookups by requiring redaction of registrants. Trying
    to get contact info on a domain registrant to alert them to a problem
    with their web site becomes much more difficult. Yeah, they want to provide a publicly accessible web site, but the registrant wants to
    hide. Thanks GDPR ... not!

    A decent website will a contact option. You should not have to be forced to give out personal information via a WHOIS lookup.

    So yes, thanks GDPR.

    Exactly. And even if the website doesn't have a contact option, webmaster@<website> should work. If it doesn't, blame the website, not
    the GDPR.

    BTW, similarly for mailservers, news servers, etc.. Yes, many are
    broken, news at eleven.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: NOYB (3:633/280.2@fidonet)
  • From Robert@3:633/280.2 to All on Wed Apr 23 09:15:41 2025
    On 20/04/2025 20:15, James wrote:

    You can sign up here to be on the waiting list!!!!!:

    <https://thundermail.com/>

    Maybe I'll sign up when they announce BetterMail ;-)

    --
    Rob
    "I have never understood why it should be necessary to become irrational
    in order to prove that you care, or, indeed, why it should be necessary
    to prove it at all." - Avon, Blake's 7


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)
  • From NZ Rules OK@3:633/280.2 to All on Wed Apr 23 09:49:42 2025
    On 23/04/2025 00:15, Robert wrote:
    On 20/04/2025 20:15, James wrote:

    You can sign up here to be on the waiting list!!!!!:

    <https://thundermail.com/>

    Maybe I'll sign up when they announce BetterMail ;-)


    It's already released :)

    <https://www.bettermail.com/>


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: To protect and to server (3:633/280.2@fidonet)
  • From Nobody@3:633/280.2 to All on Wed Apr 23 11:36:31 2025
    On 2025-04-22 4:49 p.m., NZ Rules OK wrote:
    On 23/04/2025 00:15, Robert wrote:
    On 20/04/2025 20:15, James wrote:

    You can sign up here to be on the waiting list!!!!!:

    <https://thundermail.com/>

    Maybe I'll sign up when they announce BetterMail ;-)


    It's already released :)

    <https://www.bettermail.com/>


    Auē! Aotearoa tuatahi.

    Kia ora.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Char Jackson@3:633/280.2 to All on Wed Apr 23 12:14:46 2025
    On Mon, 21 Apr 2025 03:45:09 -0700, "John C." <r9jmg0@yahoo.com> wrote:

    Only things I use IMAP email for are Amazon and Craigslist. Otherwise, I >prefer my email to be downloaded onto my system (POP) so that I can read
    it when I'm offline.

    I've been using IMAP for decades and two things are true:
    - my email is downloaded to my PCs and my phone
    - my email is still available when I'm offline


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Newshosting.com - Highest quality at a great p (3:633/280.2@fidonet)
  • From VanguardLH@3:633/280.2 to All on Wed Apr 23 15:27:54 2025
    Keywords: VanguardLH,VLH

    Java Jive <java@evij.com.invalid> wrote:

    VanguardLH wrote:

    GDPR ruined DNS lookups by requiring redaction of registrants. Trying
    to get contact info on a domain registrant to alert them to a problem
    with their web site becomes much more difficult. Yeah, they want to
    provide a publicly accessible web site, but the registrant wants to
    hide. Thanks GDPR ... not!

    Can't say that I've noticed any such problem - I just use Whois -
    so I suspect that this is just another example of someone from the
    other side of the pond having an uninformed opinion against the EU
    and its legislation.

    I meant domain lookups, not DNS lookups. When did you last do a WhoIs
    lookup on a domain? You get a privatized domain registration where the registrar pretends they are the registrant (IANA requires someone be
    identified as the registrant), or a registrant that is redacted, because
    the registrar follows GDPR rules.

    As for WhoIs, yes, that is what I'm talking about: look at a domain's registration which is required by IANA to provide contact information on
    /some/ registrant.

    To get around IANA's requirement, some registrars provided a private registration service at an extra fee. The registrant in the domain registration was the registrar instead of the actual registrant. Then
    came the GDPR where registrants could request their registrant data to
    get redacted, or the registrar did it en masse. So, when you lookup the
    domain registration, you got shit for registrant info.

    The primary impetus for hiding the registrant info was because there
    were spammers that would lookup up domain registrations to see which
    ones were about to expire, and offer their registration service.
    Registrants didn't want to get the spam, so they wanted to hide their identification in the domain registration records. With privatized registration, the registrar was identified as the registrant. The
    registrar handled the "renew your domain with us" spam. The whole point
    of privatized registration was to hide the real registrant.

    The solution was extremely simple: use an e-mail address specifying and
    only for domain registration with your registrar. Create an e-mail
    account for just domain registration notifications, and add a filter
    that accepted e-mails only from your registrar, so all other messages
    get immediately discard on delivery. You could identify yourself as the registrant, and even give postal addresses (since spammers don't pay for
    a stamp to send spam).

    Then later came the GDPR where registrants could hide without having to
    pay extra for privatized registration. The registrant info got redacted
    to point at a registrar, or one of their services, like e-mail addresses
    that pointed back to the registrar.

    https://www.whois.com/whois/domaintools.com

    is registered with TuCows, and says the registrant is:

    https://tieredaccess.com/contact/eceac3b1-4ae2-4ab0-a2d8-f7647c12c66b

    but:

    https://www.whois.com/whois/tieredaccess.com

    shows that domain is TuCows, the registrar. The domaintools.com
    registration hides the actual registrant, and the purported registrant
    is the registrar whose domain lookup is not redacted for registrant
    info.

    Sorry to those who suggest a web site should provide contact
    information. Yeah, like that really works ... NOT! Rare few sites
    provide contact information. Instead they may provide a web form to
    contact them. Or worse is they push some AI chat bot at you that is of
    no help at all, and worthless to report problems to the website.

    Oh yes, send an e-mail to webmaster@<domain> or postmaster@<domain>.
    Most often those are bit buckets to automatically discard those
    messages. Those that suggest this method haven't tried it. The success
    rate is about the same as firing a .22 rifle while blindfolded at a
    pinata from a quarter mile away.

    It's not just small fry that get to hide it's their web site. Huge corporations do it, too. So, why continue with bogus domain
    registration records that do not identify the registrant? None of the
    other remaining information is of any value. All you're left with
    nowadays is to see when a domain got registered, when last updated, and
    when it expires. The whole point of WhoIS was neutered by privatized
    domain registrations, and then by the GDPR. So, just get rid of all
    domain lookups, and leave everyone in the dark who is operating a web
    site since that is effectively what WhoIs has become: nearly worthless.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Usenet Elder (3:633/280.2@fidonet)
  • From VanguardLH@3:633/280.2 to All on Wed Apr 23 15:54:49 2025
    Keywords: VanguardLH,VLH

    Char Jackson <none@none.invalid> wrote:

    "John C." <r9jmg0@yahoo.com> wrote:

    Only things I use IMAP email for are Amazon and Craigslist.
    Otherwise, I prefer my email to be downloaded onto my system (POP)
    so that I can read it when I'm offline.

    I've been using IMAP for decades and two things are true:
    - my email is downloaded to my PCs and my phone
    - my email is still available when I'm offline

    Some e-mail clients will allow, or default to, locally caching an IMAP
    store. That allows offline viewing of received messages. For Tbird,
    local caching is tied to the "Synchronization and Storage" settings.

    https://support.mozilla.org/en-US/kb/imap-synchronization
    See the pic on the per-account "Synchronization and Storage" settings.

    Even if you configure to retrieve headers only when Tbird polls the
    account, anytime you click on a message then Tbird connects to the
    server to retrieve the body of the message, and it gets locally cached. However, if both Tbird and the IMAP server use IMAP PUSH, then the
    server pushes a new message to Tbird, and it is cached locally.

    <account> -> Server settings -> Advanced -> Use IDLE command if server
    supports it

    When an IMAP client connects to an IMAP server, the server responds with
    a keyword string. If "IMAP IDLE" is in the keyword string, the IMAP
    server supports IMAP PUSH (PUSH requires IDLE). If you do not want to
    have new e-mails immediately pushed into your IMAP client, like you
    don't want them locally cached because you configured to retrieve
    headers only, then disable the "Allow immediate server notifications
    when new messages arrive" setting, "Use IDLE", or whatever it is called
    now. Just remember that you still get the headers for new messages, and clicking on them gets them retrieved and locally cached.

    IMAP supports PUSH/IDLE to immediately retrieve messages newly arrived
    at the server in your account. It can still use polling at fixed
    intervals. POP only does polling, so you wait until the next mail poll
    to get new messages, or you keep hitting some refresh/poll key or button
    in the client trying to get new messages while not waiting as long.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Usenet Elder (3:633/280.2@fidonet)
  • From R.Wieser@3:633/280.2 to All on Wed Apr 23 17:45:10 2025
    Vanguard,

    GDPR ruined DNS lookups by requiring redaction of registrants.

    Kiddo, if you don't know what you are talking about than why don't you just keep your mouth shut ?

    No, the GDPR doesn't *require* any form redaction. However, the
    *registrant* may now require that WHOIS replaces its *way-to-personal* data with something less personal (but it still must be valid!).

    https://blog.dnsimple.com/2019/04/gdpr-and-whois-privacy/

    See "GDPR and Its Impact"

    Trying to get contact info on a domain registrant to alert them to
    a problem with their web site becomes much more difficult.

    If you can't find their contact info *than that is fully the registrants choice*.

    Also, you're a nice example of only considering your own inconveniencing,
    and being /absolutily blind/ to the "inconveniencing" (understatement here)
    of the registrants which have been contacted (snail-mail, email, physical)
    by spammers of all kinds and levels on their own home adresses.

    Yeah, they want to provide a publicly accessible web site, but
    the registrant wants to hide. Thanks GDPR ... not!

    Challenge : go find a gouverment-mandated publicly accessible storage of the personal contact data of, for example, the management of the big brick-and-mortar stores (in your neighbourhood or otherwise). Those stores are rather public too, right ?


    Bottom line, you flap your jaw quite a bit, but all that you are showing us
    is that you are a screamer, not knowing the first thing of what you complain about -- and rather obviously having no interrest in looking at something
    from more than one, your own, POV.

    In short kid, you're willfully stupid.


    And not to be rubbing your face in it (yeah, right :-) ), but why are *you*, in these very public newsgroups, hiding behind a made-up name (and a going-who-knows-where (if anywhere) email) ? Where is *your* personal data
    ?

    Regards,
    Rudy Wieser



    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From R.Wieser@3:633/280.2 to All on Wed Apr 23 17:45:10 2025
    Vanguard,

    GDPR ruined DNS lookups by requiring redaction of registrants.

    Kiddo, if you don't know what you are talking about than why don't you just keep your mouth shut ?

    No, the GDPR doesn't *require* any form redaction. However, the
    *registrant* may now require that WHOIS replaces its *way-to-personal* data with something less personal (but it still must be valid!).

    https://blog.dnsimple.com/2019/04/gdpr-and-whois-privacy/

    See "GDPR and Its Impact"

    Trying to get contact info on a domain registrant to alert them to
    a problem with their web site becomes much more difficult.

    If you can't find their contact info *than that is fully the registrants choice*.

    Also, you're a nice example of only considering your own inconveniencing,
    and being /absolutily blind/ to the "inconveniencing" (understatement here)
    of the registrants which have been contacted (snail-mail, email, physical)
    by spammers of all kinds and levels on their own home adresses.

    Yeah, they want to provide a publicly accessible web site, but
    the registrant wants to hide. Thanks GDPR ... not!

    Challenge : go find a gouverment-mandated publicly accessible storage of the personal contact data of, for example, the management of the big brick-and-mortar stores (in your neighbourhood or otherwise). Those stores are rather public too, right ?


    Bottom line, you flap your jaw quite a bit, but all that you are showing us
    is that you are a screamer, not knowing the first thing of what you complain about -- and rather obviously having no interrest in looking at something
    from more than one, your own, POV.

    In short kid, you're willfully stupid.


    And not to be rubbing your face in it (yeah, right :-) ), but why are *you*, in these very public newsgroups, hiding behind a made-up name (and a going-who-knows-where (if anywhere) email) ? Where is *your* personal data
    ?

    Regards,
    Rudy Wieser



    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Java Jive@3:633/280.2 to All on Wed Apr 23 20:31:40 2025
    On 2025-04-23 06:27, VanguardLH wrote:

    Java Jive <java@evij.com.invalid> wrote:

    VanguardLH wrote:

    GDPR ruined DNS lookups by requiring redaction of registrants. Trying
    to get contact info on a domain registrant to alert them to a problem
    with their web site becomes much more difficult. Yeah, they want to
    provide a publicly accessible web site, but the registrant wants to
    hide. Thanks GDPR ... not!

    Can't say that I've noticed any such problem - I just use Whois -
    so I suspect that this is just another example of someone from the
    other side of the pond having an uninformed opinion against the EU
    and its legislation.

    I meant domain lookups, not DNS lookups. When did you last do a WhoIs
    lookup on a domain?

    Many times since GDPR was adopted by the EU. As for the gist of your argument, which I've snipped as it was unnecessarily long-winded, as far
    as I could tell it from skimming through it ...

    If you need to complain about a domain's behaviour, spamming or
    whatever, if you don't get any joy from the contacts given out by the
    website itself or the generally accepted default contacts, usually it is sufficient to complain next to the Registrant; if the problem behaviour persists, they can, and in my experience will, threaten to refuse to
    handle the domain. For example, there was a domain that held both
    incorrect information and personally identifying information about my
    family's descent from a younger son of a Chief of Clan Macfarlane, so I
    wrote to the domain's contact address given on the site, both correcting
    the wrong information and demanding the removal of personally
    identifying information of living people and their parents. Initially,
    the owner refused the latter, worse still, he bolshed about it, claiming
    that I was curtailing his freedoms, blah, blah. So I complained to the Registrant about his behaviour, and the personally identifying
    information was duly removed.

    As for wishing to complain about the actual functionality of a website,
    any reputable business will be at least somewhat interested if their
    website is causing their customers or users difficulties, after all it's
    the modern equivalent of their retail premises or shop window. If their
    site is causing sufficient problems to sufficient numbers of people,
    they'd be foolish to ignore the problem, as it will likely adversely
    affect their business bottom line. For example, I have written before
    here or hereabouts about why I ditched Three in the UK as my mobile
    supplier, partly because their site and management of personal data
    behind it were so appallingly programmed.

    More generally, often you don't need to know the actual site ownership
    details to work out what you need to know about a it. For example,
    during the covid pandemic, a great many fake and pseudo science sites
    sprung up concerning it, all you needed to know in that situation was
    that the sites having questionable information were created at or around
    the outbreak, so weren't likely to be reliable purveyors of reliable
    medical information from a reliable source. Similarly with other forms
    of scientific denialism.

    --

    Fake news kills!

    I may be contacted via the contact address given on my website: www.macfh.co.uk


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From VanguardLH@3:633/280.2 to All on Wed Apr 23 21:14:20 2025
    Keywords: VanguardLH,VLH

    Java Jive <java@evij.com.invalid> wrote:

    If you need to complain about a domain's behaviour, spamming or
    whatever, if you don't get any joy from the contacts given out by the
    website itself or the generally accepted default contacts, usually it
    is sufficient to complain next to the Registrant; ...

    Presumably you meant the registrar. The problem is the domain lookup
    nowadays often doesn't reveal contact info on the registrant, there is
    no contact info at the web site (assuming it is up and responsive, and
    you're not trying to report it is down), and the postmaster and
    webmaster e-mail addresses are just bit buckets, or not defined so I get
    back an NDR (Non-Delivery Report).

    I'm not trying to report an abusive web site. I'm trying to contact its registrant to report a problem with the web site, like it is not
    responsive, it may be hacked (e.g., a popup appears mentioning infection
    which is ransomware), or otherwise trying to help the registrant with
    their web site. Too many owners don't monitor their sites nor use tools
    to notify them when it is down. They don't know there is a problem
    until someone tells them. That is when contacting them phone or e-mail
    can notify them.

    Think of walking behind someone carrying a grocery bag, and a can falls
    out of a hole in the bag. You get their attention they are losing their groceries. You are helping them, not calling 911 to have them arrested
    for littering.

    As for wishing to complain about the actual functionality of a website,
    any reputable business will be at least somewhat interested if their
    website is causing their customers or users difficulties, after all it's
    the modern equivalent of their retail premises or shop window. If their site is causing sufficient problems to sufficient numbers of people,
    they'd be foolish to ignore the problem, as it will likely adversely
    affect their business bottom line.

    How would they know? Yes, there are monitoring services they could
    enlist, but not everyone uses them. Some web sites are e-tailers, but
    many are hobbyists. It's not they are ignoring a problem. It's they
    don't there is a problem.

    More generally, often you don't need to know the actual site ownership details to work out what you need to know about a it.

    Some web sites won't provide phone numbers, postal addresses, or e-mail addresses, but supply a web form to contact them. However, if the web
    site is down, obviously you cannot use their web form. You also cannot
    get any contact info published at the web site, because it is down. So,
    what are you left with? Postmaster and webmaster e-mail address that
    are often worthless, or to lookup the domain registrant to see if you
    can contact them that way.

    Someone recently noted they could not connect to a web site, because
    there was some alert in their web browser the site cert was invalid. I
    did the domain lookup, and saw the site cert expired the same day the
    user noted they could no longer connect to the site. Someone somehow
    notified the site admin their cert had expired, and they bought another
    lease to renew their cert the next day. The user couldn't load the web
    page to get contact info, if even published, at the web site. Their
    domain lookup had bogus registrant info. I would expect the registrar
    would have informed them about a soon-expiring site cert, but maybe the
    site owner didn't get it, or didn't see it, or the site owner changed
    their e-mail address, so the registrar's notifications were never
    received. You could wait until doomsday hoping the site admin got a new
    site cert figuring somehow they'd find out about it. Or you could be
    the someone that somehow told them their site cert had expired.

    Digging around a web site looking for contact info is fruitless if the
    site is down. You could try HTTP if HTTPS failed, but not all HTTPS
    sites have HTTP pages. You could send off e-mails to postmaster or
    webmaster, but that assumes the site owner reads those instead of
    discarding them, or that postmaster@<domain> is where the site's owner
    gets e-mails.

    Never had someone tell you your car lights were still on as you were
    walking away? Or you dropped your keys?

    With the GDPR, maybe one day you won't even be able to lookup a domain's registration period, because, gee, that can be construed as private
    between registrant and their registrar. I don't visit the Dark Web, and
    the White Web shouldn't behave like the Dark Web.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Usenet Elder (3:633/280.2@fidonet)
  • From Java Jive@3:633/280.2 to All on Wed Apr 23 21:36:59 2025
    On 2025-04-23 12:14, VanguardLH wrote:

    Java Jive <java@evij.com.invalid> wrote:

    If you need to complain about a domain's behaviour, spamming or
    whatever, if you don't get any joy from the contacts given out by the
    website itself or the generally accepted default contacts, usually it
    is sufficient to complain next to the Registrant; ...

    Presumably you meant the registrar.

    Yes, my mistake.

    I'm not trying to report an abusive web site. I'm trying to contact its registrant to report a problem with the web site, like it is not
    responsive, it may be hacked (e.g., a popup appears mentioning infection which is ransomware), or otherwise trying to help the registrant with
    their web site. Too many owners don't monitor their sites nor use tools
    to notify them when it is down. They don't know there is a problem
    until someone tells them. That is when contacting them phone or e-mail
    can notify them.

    A worthwhile website will have contact information you can use for this,
    if they don't, their problem.

    As for wishing to complain about the actual functionality of a website,
    any reputable business will be at least somewhat interested if their
    website is causing their customers or users difficulties, after all it's
    the modern equivalent of their retail premises or shop window. If their
    site is causing sufficient problems to sufficient numbers of people,
    they'd be foolish to ignore the problem, as it will likely adversely
    affect their business bottom line.

    How would they know?

    Again, a worthwhile website will have contact information you can use
    for this, if they don't, again their problem.

    More generally, often you don't need to know the actual site ownership
    details to work out what you need to know about a it.

    Some web sites won't provide phone numbers, postal addresses, or e-mail addresses, but supply a web form to contact them. However, if the web
    site is down, obviously you cannot use their web form. You also cannot
    get any contact info published at the web site, because it is down. So,
    what are you left with? Postmaster and webmaster e-mail address that
    are often worthless, or to lookup the domain registrant to see if you
    can contact them that way.

    Most people browsing wouldn't bother to notify a site owner if their
    site was so completely down that no contact details could even be
    loaded, but if someone is sufficiently motivated to do so, they could
    send the site a message via the registrar, asking them to pass it on.

    --

    Fake news kills!

    I may be contacted via the contact address given on my website: www.macfh.co.uk


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From VanguardLH@3:633/280.2 to All on Wed Apr 23 21:50:05 2025
    Keywords: VanguardLH,VLH

    Java Jive <java@evij.com.invalid> wrote:

    A worthwhile website will have contact information you can use for this,
    if they don't, their problem.

    A worthwhile site provides contact information.
    The web site is down, unresponsive, or unreachable.
    Just how are you going to get that contact information?

    Most people browsing wouldn't bother to notify a site owner if their
    site was so completely down that no contact details could even be
    loaded, but if someone is sufficiently motivated to do so, they could
    send the site a message via the registrar, asking them to pass it on.

    I could try that (ask the registrar to contact the registrant). Too
    often a service ignores requests not from their customers. Registrars
    dole out domain leases. Web admin is not their business, so I'd be
    asking a disinterested party. Never know, though. It could work.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Usenet Elder (3:633/280.2@fidonet)
  • From Chris@3:633/280.2 to All on Thu Apr 24 01:54:47 2025
    VanguardLH <V@nguard.LH> wrote:
    Java Jive <java@evij.com.invalid> wrote:

    If you need to complain about a domain's behaviour, spamming or
    whatever, if you don't get any joy from the contacts given out by the
    website itself or the generally accepted default contacts, usually it
    is sufficient to complain next to the Registrant; ...

    Presumably you meant the registrar. The problem is the domain lookup nowadays often doesn't reveal contact info on the registrant, there is
    no contact info at the web site (assuming it is up and responsive, and
    you're not trying to report it is down), and the postmaster and
    webmaster e-mail addresses are just bit buckets, or not defined so I get
    back an NDR (Non-Delivery Report).

    I'm not trying to report an abusive web site. I'm trying to contact its registrant to report a problem with the web site, like it is not
    responsive, it may be hacked (e.g., a popup appears mentioning infection which is ransomware), or otherwise trying to help the registrant with
    their web site. Too many owners don't monitor their sites nor use tools
    to notify them when it is down. They don't know there is a problem
    until someone tells them. That is when contacting them phone or e-mail
    can notify them.

    That's their choice. You don't have a right to be able to contact them.

    If they're a business and don't have appropriate "contact us" info, they'll soon cease being a business. If they're a hobbyist then it's still their
    choice and a they probably don't care to get feedback.


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From VanguardLH@3:633/280.2 to All on Thu Apr 24 20:00:11 2025
    Keywords: VanguardLH,VLH

    Chris <ithinkiam@gmail.com> wrote:

    That's their choice. You don't have a right to be able to contact them.

    Actually, and for registrars under the GDPR's thumb, the registrars
    *must* redact the registration info. It is NOT their customer's choice.

    https://blog.dnsimple.com/2019/04/gdpr-and-whois-privacy/
    "ICANN, domain registries, and domain registrars reacted to GDPR by
    introducing a new policy requiring redaction of personal information,
    thus changing the landscape of domain registrations."

    https://drs.whoisxmlapi.com/blog/retrieve-domain-data-after-redaction

    Yeah, many respondents claim "it's their choice". Nope.

    https://www.finnegan.com/en/insights/blogs/incontestable/concealed-registration-data-under-the-gdpr-complicates-udrp-complaints.html

    No wonder look-alike domains (using UTF8 characters instead of ASCII)
    don't get killed right away. The scammers get to continue with their look-alike domain until someone decides to take court action (in an
    actionable region governing the registrar). Class action suits don't
    happen overnight.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Usenet Elder (3:633/280.2@fidonet)
  • From VanguardLH@3:633/280.2 to All on Thu Apr 24 20:07:54 2025
    Keywords: VanguardLH,VLH

    NZ Rules OK <invalid@invalid.invalid> wrote:

    Robert wrote:

    James wrote:

    You can sign up here to be on the waiting list!!!!!:
    <https://thundermail.com/>

    Maybe I'll sign up when they announce BetterMail ;-)

    It's already released :)
    <https://www.bettermail.com/>

    Not free, but then neither will be Thundermail.

    https://www.bettermail.com/pricing/

    "Send email to thousands within minutes". They're oriented to customers
    that want to do bulk mailing, like spammers, and marketfolk.

    BetterMail and Betterbird are not affiliated to each other.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Usenet Elder (3:633/280.2@fidonet)
  • From Philip Herlihy@3:633/280.2 to All on Thu Apr 24 21:19:50 2025
    In article <13esvde35xjuj.dlg@v.nguard.lh>, V@nguard.LH says...
    No wonder look-alike domains (using UTF8 characters instead of ASCII)
    don't get killed right away.


    How does that work?

    --
    --
    Phil, London

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From R.Wieser@3:633/280.2 to All on Thu Apr 24 22:33:13 2025
    Philip,

    No wonder look-alike domains (using UTF8 characters instead of
    ASCII) don't get killed right away.

    How does that work?

    Look-alike domains using UTF8 characters ?

    Its (too) simple. There are a lot of UTF8 characters that, to us humans,
    look almost, if not completely the same as standard ASCII characters.

    Pretty-much the same as "o" and "”" in the normal ASCII range (the last one has two dots above it), but worse.

    Regards,
    Rudy Wieser



    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Chris@3:633/280.2 to All on Fri Apr 25 01:27:52 2025
    VanguardLH <V@nguard.LH> wrote:
    Chris <ithinkiam@gmail.com> wrote:

    That's their choice. You don't have a right to be able to contact them.

    Actually, and for registrars under the GDPR's thumb, the registrars
    *must* redact the registration info. It is NOT their customer's choice.

    Well done for removing context.

    I was talking about not having contact information on their website.
    Nothing to do with registrars.


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From R.Wieser@3:633/280.2 to All on Fri Apr 25 02:37:03 2025
    Vanguard,

    Actually, and for registrars under the GDPR's thumb, the registrars
    *must* redact the registration info. It is NOT their customer's choice.

    You *still* have no clue what you are talking about.

    .... Or you do, but that would make things even worse. :-|

    [Quote from my earlier posted link]
    In responses to domain name queries, Registrar and Registry Operator MUST treat the following Registrant fields as "redacted"
    [quote]

    *DIRECTLY FOLLOWED BY*

    [Quote from my earlier posted link]
    unless the Registered Name Holder has provided Consent to publish the Registered Name Holder's data:
    [quote]

    So no, its still the customers choice, and you're talking crap - again.

    Regards,
    Rudy Wieser



    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Trump Lost The Tariff War@3:633/280.2 to All on Fri Apr 25 03:30:00 2025
    On 24/04/2025 17:37, R.Wieser wrote:
    You *still* have no clue what you are talking about.



    For god's sake leave him alone. He is not a resident of Europe and so
    all he can do is to make up things as he goes along and hopefully
    something will hit the mark.

    None of you have any clues as to what the topic was about in the subject matter.


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: To protect and to server (3:633/280.2@fidonet)
  • From R.Wieser@3:633/280.2 to All on Fri Apr 25 05:48:18 2025
    Trump...something,something,something,

    On 24/04/2025 17:37, R.Wieser wrote:

    You *still* have no clue what you are talking about.

    For god's sake leave him alone.

    Why ?

    He is not a resident of Europe and so all he can do is to
    make up things as he goes along

    "all he can do" ? Bullshit. Just like I can look for and find (and post a link to) the relevant information, so can he. And all that it took me was about 5 minutes.

    Also, he's been getting the same "thats bullshit, bro" signal from several people. It has been his own choice to refuse to double-check his presumed facts, and instead just try to steam-roll on.

    and hopefully something will hit the mark.

    And in the mean time some poor sods will believe his crap and spread it further (and likely get laughed at) ? Yeah, thats a grand idea. Not.

    None of you have any clues as to what the topic was about in
    the subject matter.

    You mean that advertisement for yet another email provider ? One we can
    really trust ? Because they say so ?

    If you would have followed this thread you could have noticed that several people have picked up that "the subject matter" and have posted their doubts about it.

    But I take it you missed all of that...

    Kiddo, at least *try* to get your facts straight before you think about complaining about something. Being able to *that easily* point out how misguided(?) your claim is makes you look like a fool.

    Regards,
    Rudy Wieser




    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Robert@3:633/280.2 to All on Fri Apr 25 09:26:43 2025
    On 24/04/2025 11:07, VanguardLH wrote:

    "Send email to thousands within minutes". They're oriented to customers
    that want to do bulk mailing, like spammers, and marketfolk.

    BetterMail and Betterbird are not affiliated to each other.

    Ah, probably a good thing, then.

    --
    Rob
    "I have never understood why it should be necessary to become irrational
    in order to prove that you care, or, indeed, why it should be necessary
    to prove it at all." - Avon, Blake's 7


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)
  • From Philip Herlihy@3:633/280.2 to All on Fri Apr 25 21:54:07 2025
    In article <vudb2r$1j1ta$1@dont-email.me>, address@is.invalid says...

    Philip,

    No wonder look-alike domains (using UTF8 characters instead of
    ASCII) don't get killed right away.

    How does that work?

    Look-alike domains using UTF8 characters ?

    Its (too) simple. There are a lot of UTF8 characters that, to us humans, >look almost, if not completely the same as standard ASCII characters.

    Pretty-much the same as "o" and "”" in the normal ASCII range (the last one >has two dots above it), but worse.

    Regards,
    Rudy Wieser

    Helpful - thanks!

    --
    --
    Phil, London

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From John C.@3:633/280.2 to All on Fri Apr 25 22:44:55 2025
    VanguardLH wrote:
    NZ Rules OK wrote:
    Robert wrote:
    James wrote:

    You can sign up here to be on the waiting list!!!!!:
    <https://thundermail.com/>

    Maybe I'll sign up when they announce BetterMail ;-)

    It's already released :)
    <https://www.bettermail.com/>

    Not free, but then neither will be Thundermail.

    https://www.bettermail.com/pricing/

    "Send email to thousands within minutes". They're oriented to customers
    that want to do bulk mailing, like spammers, and marketfolk.

    BetterMail and Betterbird are not affiliated to each other.

    "Send email to thousands within minutes

    BetterMail is a NZ based email service provider with the easiest way to
    create, send, share and track marketing emails.
    With bulk sending, a drag and drop editor, feature rich plans and NZ
    based support you can't go wrong."

    Sounds to me like Bettermail is service designed for spammers. Am I wrong?

    --
    John C.

    I filter out all crossposts and garbage from trolls.

    Take back Microsoft from India.


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From R.Wieser@3:633/280.2 to All on Sat Apr 26 02:03:23 2025
    Philip,

    Helpful - thanks!

    You're wecome. :-)

    If you put the below in an .HTML file and open it you can see what the
    problem is - and those are just a quick grab.

    I've HTML-ed the chars for easy transport/viewing. You can also open
    'write' (the text editor) press-and-hold ALT and input one of the numbers numbers using the numeric keypad (on the right), afterwards releasing the
    ALT key.

    - - - - - - - - - - - -
    <html>
    <head>
    <meta charset="UTF-8">
    <title>A small example</title>
    </head>
    <body>

    <p> e &#8494; &#1107;</p>
    <p> K &#8490;</p>
    <p> s &#1109;</p>

    </body>
    </html>
    - - - - - - - - - - - -

    Regards,
    Rudy Wieser



    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Philip Herlihy@3:633/280.2 to All on Wed Apr 30 01:48:07 2025
    In article <vugbor$akfn$1@dont-email.me>, address@is.invalid says...
    <html>
    <head>
    <meta charset="UTF-8">
    <title>A small example</title>
    </head>
    <body>

    <p> e &#8494; &#1107;</p>
    <p> K &#8490;</p>
    <p> s &#1109;</p>

    </body>
    </html>



    Excllent demo - thanks!

    --
    --
    Phil, London

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From David@3:633/280.2 to All on Sat May 3 23:50:44 2025
    On 22/04/2025 14:58, Chris wrote:
    VanguardLH <V@nguard.LH> wrote:
    Daniel70 <daniel47@eternal-september.org> wrote:

    On 22/04/2025 2:53 am, s|b wrote:
    On Sun, 20 Apr 2025 15:49:15 -0500, VanguardLH wrote:

    Additionally, you will be able to bring your own domain on day 1 of
    the service."

    I don't own a domain, I've registered it and pay for mailhosting to a
    firm in a country that respects GDPR. Why would want to move?

    "GDPR"?? Thank you, Google and Wikipedia

    "General Data Protection Regulation"

    https://en.wikipedia.org/wiki/General_Data_Protection_Regulation

    GDPR ruined DNS lookups by requiring redaction of registrants. Trying
    to get contact info on a domain registrant to alert them to a problem
    with their web site becomes much more difficult. Yeah, they want to
    provide a publicly accessible web site, but the registrant wants to
    hide. Thanks GDPR ... not!

    A decent website will a contact option. You should not have to be forced to give out personal information via a WHOIS lookup.

    So yes, thanks GDPR.

    DO NOT FOLLOW THIS ADVICE.

    Never click links nor run software from someone you don't know
    supposedly trying to help.


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)
  • From Paul@3:633/280.2 to All on Sun May 4 04:39:20 2025
    On Sat, 5/3/2025 9:50 AM, David wrote:
    On 22/04/2025 14:58, Chris wrote:
    VanguardLH <V@nguard.LH> wrote:
    Daniel70 <daniel47@eternal-september.org> wrote:

    On 22/04/2025 2:53 am, s|b wrote:
    On Sun, 20 Apr 2025 15:49:15 -0500, VanguardLH wrote:

    Additionally, you will be able to bring your own domain on day 1 of >>>>>> the service."

    I don't own a domain, I've registered it and pay for mailhosting to a >>>>> firm in a country that respects GDPR. Why would want to move?

    "GDPR"?? Thank you, Google and Wikipedia

    "General Data Protection Regulation"

    https://en.wikipedia.org/wiki/General_Data_Protection_Regulation

    GDPR ruined DNS lookups by requiring redaction of registrants.˙ Trying
    to get contact info on a domain registrant to alert them to a problem
    with their web site becomes much more difficult.˙ Yeah, they want to
    provide a publicly accessible web site, but the registrant wants to
    hide.˙ Thanks GDPR ... not!

    A decent website will a contact option. You should not have to be forced to >> give out personal information via a WHOIS lookup.

    So yes, thanks GDPR.

    DO NOT FOLLOW THIS ADVICE.

    Never click links nor run software from someone you don't know supposedly trying to help.


    Redaction of contact information is a good thing.
    (It's a tradeoff caused by the world we live in.)

    a guy on USENET, had his computer room wiped out by ransomware.
    How was he selected ? He registered a web domain with GoDaddy,
    showing his personal information. he wasn't cloaked.

    One day, an email arrived, with a "bill" attached from GoDaddy.
    except, the email wasn't actually from GoDaddy. It was from
    a Black Hat. The Black Hat scanned GoDaddy and extracted all
    the email addresses. The attachment on the email is actually
    an executable ransomware. All you need to do is double
    click it, thinking it is a PDF. The code included a worm,
    so the code could attack all the computers.

    It took MONTHS for him to recover the computer room.
    No backups.

    However, the mental damage could not be undone.
    He no longer visits USENET.

    I have successfully reached websites using admin@ or webmaster@
    and on one occasion, they even sent an ACK. Look for
    suggested canonical forms of email addresses, for
    contacting site admin. The purpose of those channels,
    is not for "chats", it's to warn about site damage or
    server issues that perhaps the admin cannot observe.

    Paul

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Mark Lloyd@3:633/280.2 to All on Sun May 4 05:14:15 2025
    On Sat, 3 May 2025 14:39:20 -0400, Paul wrote:

    On Sat, 5/3/2025 9:50 AM, David wrote:
    On 22/04/2025 14:58, Chris wrote:
    VanguardLH <V@nguard.LH> wrote:
    Daniel70 <daniel47@eternal-september.org> wrote:

    On 22/04/2025 2:53 am, s|b wrote:
    On Sun, 20 Apr 2025 15:49:15 -0500, VanguardLH wrote:

    Additionally, you will be able to bring your own domain on day 1 >>>>>>> of the service."

    I don't own a domain, I've registered it and pay for mailhosting to >>>>>> a firm in a country that respects GDPR. Why would want to move?

    "GDPR"?? Thank you, Google and Wikipedia

    "General Data Protection Regulation"

    https://en.wikipedia.org/wiki/General_Data_Protection_Regulation

    GDPR ruined DNS lookups by requiring redaction of registrants.˙
    Trying to get contact info on a domain registrant to alert them to a
    problem with their web site becomes much more difficult.˙ Yeah, they
    want to provide a publicly accessible web site, but the registrant
    wants to hide.˙ Thanks GDPR ... not!

    A decent website will a contact option. You should not have to be
    forced to give out personal information via a WHOIS lookup.

    So yes, thanks GDPR.

    DO NOT FOLLOW THIS ADVICE.

    Never click links nor run software from someone you don't know
    supposedly trying to help.


    Redaction of contact information is a good thing.
    (It's a tradeoff caused by the world we live in.)

    a guy on USENET, had his computer room wiped out by ransomware.
    How was he selected ? He registered a web domain with GoDaddy, showing
    his personal information. he wasn't cloaked.

    One day, an email arrived, with a "bill" attached from GoDaddy.
    except, the email wasn't actually from GoDaddy. It was from a Black Hat.
    The Black Hat scanned GoDaddy and extracted all the email addresses. The attachment on the email is actually an executable ransomware. All you
    need to do is double click it, thinking it is a PDF.

    Could that attachment have had a name like:

    bill.pdf.exe

    And Windows hid the extension, making it look like:

    bill.pdf

    Windows would still know that the extension was exe even though it looked
    like a pdf. That makes it look like M$ made a bad decision.

    The code included a
    worm,
    so the code could attack all the computers.

    [snip]

    --
    Mark Lloyd
    http://notstupid.us/

    "The foolish renounce this world and pursue an imaginary world to come."
    -- Giordano Bruno (1548-1600), Italian philosopher

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)
  • From Carlos E.R.@3:633/280.2 to All on Sun May 4 07:53:17 2025
    On 2025-05-03 21:14, Mark Lloyd wrote:
    On Sat, 3 May 2025 14:39:20 -0400, Paul wrote:

    On Sat, 5/3/2025 9:50 AM, David wrote:
    On 22/04/2025 14:58, Chris wrote:
    VanguardLH <V@nguard.LH> wrote:
    Daniel70 <daniel47@eternal-september.org> wrote:

    On 22/04/2025 2:53 am, s|b wrote:
    On Sun, 20 Apr 2025 15:49:15 -0500, VanguardLH wrote:

    Additionally, you will be able to bring your own domain on day 1 >>>>>>>> of the service."

    I don't own a domain, I've registered it and pay for mailhosting to >>>>>>> a firm in a country that respects GDPR. Why would want to move?

    "GDPR"?? Thank you, Google and Wikipedia

    "General Data Protection Regulation"

    https://en.wikipedia.org/wiki/General_Data_Protection_Regulation

    GDPR ruined DNS lookups by requiring redaction of registrants.
    Trying to get contact info on a domain registrant to alert them to a >>>>> problem with their web site becomes much more difficult.˙ Yeah, they >>>>> want to provide a publicly accessible web site, but the registrant
    wants to hide.˙ Thanks GDPR ... not!

    A decent website will a contact option. You should not have to be
    forced to give out personal information via a WHOIS lookup.

    So yes, thanks GDPR.

    DO NOT FOLLOW THIS ADVICE.

    Never click links nor run software from someone you don't know
    supposedly trying to help.


    Redaction of contact information is a good thing.
    (It's a tradeoff caused by the world we live in.)

    a guy on USENET, had his computer room wiped out by ransomware.
    How was he selected ? He registered a web domain with GoDaddy, showing
    his personal information. he wasn't cloaked.

    One day, an email arrived, with a "bill" attached from GoDaddy.
    except, the email wasn't actually from GoDaddy. It was from a Black Hat.
    The Black Hat scanned GoDaddy and extracted all the email addresses. The
    attachment on the email is actually an executable ransomware. All you
    need to do is double click it, thinking it is a PDF.

    Could that attachment have had a name like:

    bill.pdf.exe

    And Windows hid the extension, making it look like:

    bill.pdf

    Windows would still know that the extension was exe even though it looked like a pdf. That makes it look like M$ made a bad decision.

    That's one of the tricks. Another is to name it

    bill.pdf .exe

    with a lot of spaces hopping to make the extension flow out of the window.


    By the way, this trick doesn't work on Linux and TB. Double click
    doesn't run an attachment, because it needs to be flagged as executable.

    Also, it is quite simple to configure a mail server to block any email
    that contain executable attachments.


    Another trick for some time was to email nice screensavers.

    --
    Cheers, Carlos.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)
  • From Chris@3:633/280.2 to All on Sun May 4 23:31:17 2025
    David <BD@invalid.now> wrote:
    On 22/04/2025 14:58, Chris wrote:
    VanguardLH <V@nguard.LH> wrote:
    Daniel70 <daniel47@eternal-september.org> wrote:

    On 22/04/2025 2:53 am, s|b wrote:
    On Sun, 20 Apr 2025 15:49:15 -0500, VanguardLH wrote:

    Additionally, you will be able to bring your own domain on day 1 of >>>>>> the service."

    I don't own a domain, I've registered it and pay for mailhosting to a >>>>> firm in a country that respects GDPR. Why would want to move?

    "GDPR"?? Thank you, Google and Wikipedia

    "General Data Protection Regulation"

    https://en.wikipedia.org/wiki/General_Data_Protection_Regulation

    GDPR ruined DNS lookups by requiring redaction of registrants. Trying
    to get contact info on a domain registrant to alert them to a problem
    with their web site becomes much more difficult. Yeah, they want to
    provide a publicly accessible web site, but the registrant wants to
    hide. Thanks GDPR ... not!

    A decent website will a contact option. You should not have to be forced to >> give out personal information via a WHOIS lookup.

    So yes, thanks GDPR.

    DO NOT FOLLOW THIS ADVICE.

    Never click links nor run software from someone you don't know
    supposedly trying to help.

    I'm glad you at least learned something today...


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Frank Slootweg@3:633/280.2 to All on Sun May 4 23:59:32 2025
    Chris <ithinkiam@gmail.com> wrote:
    David <BD@invalid.now> wrote:
    On 22/04/2025 14:58, Chris wrote:
    [...]
    A decent website will a contact option. You should not have to be forced to
    give out personal information via a WHOIS lookup.

    So yes, thanks GDPR.

    DO NOT FOLLOW THIS ADVICE.

    Never click links nor run software from someone you don't know
    supposedly trying to help.

    I'm glad you at least learned something today...

    Well, not changing nyms - to evade killfiles - all the time ('EMAK'),
    isn't something 'Boater Dave' learned, not today and probably not ever.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: NOYB (3:633/280.2@fidonet)
  • From VanguardLH@3:633/280.2 to All on Fri May 16 21:26:44 2025
    Keywords: VanguardLH,VLH

    James <invalid@invalid.invalid> wrote:

    At its core, Thundermail will primarily be a mail service provider, eventually expanding to offer a familiar browser-based experience
    similar to Gmail or Outlook. Users can send and receive email using new Thundermail accounts they sign up for. The service will also allow using your own custom domain (e.g. your.name@yourdomain.com).
    ...
    You can sign up here to be on the waiting list!!!!!: <https://thundermail.com/>

    Anyone yet get an invite? I sent my request the day this thread
    started. No response yet.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Usenet Elder (3:633/280.2@fidonet)
  • From Mr. Man-wai Chang@3:633/280.2 to All on Wed May 21 04:18:35 2025
    On 21/4/2025 3:15 am, James wrote:

    there’s at least one important quality that will distinguish Mozilla’s email service from
    competitors like Gmail: privacy. Thundermail isn’t going to use your messages to train AI, it’s not going to invade your inbox with ads, and it’s not going to harvest and sell your data.

    Sooner or later a betrayal of trust will happen suddenly... :)


    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Retirednoguilt@3:633/280.2 to All on Thu May 22 00:50:57 2025
    On 5/20/2025 2:18 PM, Mr. Man-wai Chang wrote:
    On 21/4/2025 3:15 am, James wrote:

    there’s at least one important quality that will distinguish Mozilla’s email service from
    competitors like Gmail: privacy. Thundermail isn’t going to use your
    messages to train AI, it’s not going to invade your inbox with ads, and
    it’s not going to harvest and sell your data.

    Sooner or later a betrayal of trust will happen suddenly... :)


    I can't comment on the privacy issue, but with respect to ads, when I
    use my gmail account on a win10 machine via firefox 138, using both the
    Privacy Badger and the uBlock origin add-ons, I have a gmail inbox
    entirely free of any ads whatever. Same pertains to yahoo mail.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)