that_guy_iain

I bet someone returned that security camera.

> 1. Email didn’t arrive in his inbox of his Google workspace

> 2. He checked workspace email logs (with admin you can do this on gsuite)

But it didn't arrive, so how was it in his email logs!?!?!?! Are you tech literate? Isn't this the second time you've been asked or was I rate limited at that point?

Dude, you keep on just believing a blog post even though it makes no technical sense. That's why none of the hardcore nerds are even approaching this and why Viva are going to sue.

An email bouncing means it was rejected because it did not find an inbox or a recipient. You AI to question if that is true. So if the email service provider says we don't know who that belongs to, why would they provide logs.

And what email service provider is rejecting an email over a RFC thing when millions of emails a day because most devs don't care about the RFCs and only an idiot would have two different mail infrastructure and code versions running for gmail and workspaces. Especially on the sending and receiving part.

So are you going to apologies for being confidently wrong? Because I'm technically and confidently right. Again, which is why the hardcore nerds are leaving this the fuck alone because they saw me wreck the post in minutes of it being posted.

> You don't have the right to complain to random websites without punishment. And nobody punished you. And "ability to redress" is something you still have. And there are no damages.

Well, you see Dang aka Daniel edited the settings on my account to stop me replying, or that's what I've heard, and pointing out the absolute lie that the blog post is. And that did hamper my ability to redress and people have been lying about me so there are damages. But even if it's just rate limiting that hampers my ability especially since it's been optimised heavily for high traffic so there is no technical reason for it since it's a file-based datastore.

> You brought it up. Though it's pretty obvious you're a liar.

I said someone there should know. I didn't say everyone should know. I clearly made it quite clear it was insider knowledge. This is what is known as a flex. I want to tell you my tagline because it's awesome but you can just call me a keyboard warrior.

The email landed in the spam folder. A bounced email means it didn't find the inbox. If it didn't find an inbox there would be no log for him to check. Technical knowledge of emails and what the terms mean out him instantly as a liar. The fact this is still up on the front page is an embarrassment for the tech community in my opinion.

Would you mind looking into what an email bouncing is?

WTF you talking about? Rene, this is defamation and I'm probably going to take action because honestly, enough is enough. I'm fed up of folk like you who lack basic technical knowledge or any knowledge making up bullshit. Your hourly rate makes me like you have money to take.

It's called the right to redress. Read up on EU laws.

It's a if you know you, you know. If you don't you're not in the know. :D

It amazes me people read that in this community and don't know for an email to bounce it means it didn't find an inbox. If it didn't find an inbox how did he check the logs?

What that is liable? That is a very small claim.

A log that clearly was from them and not the service provider. It amazes me you think you're so smart but haven't realised he doesn't have access to the logs you think he is showing.

Comments like this are why he's just landed himself with a major liability and I bet he'll be getting sued over this.

So you think he had access to Viva's email servers to see the response? No, he clearly tested it himself and used his credentials to send it.

My takeaway is there is no bug. My takeaway is that his test email bounced because he didn't have the reputation Viva does. Emails are handled on a reputation basis, this is why we use email service providers like Sendgrid, Mailgun, Postmark, etc.

> Viva.com, one of Europe's largest payment processors, sends verification emails without a Message-ID header — a basic requirement of RFC 5322 since 2008. Google Workspace rejects them outright. Their support team's response to my detailed bug report: "your account has a verified email, so there's no problem."

Their emails do arrive tho? It was your email that didn't arrive? I find it unbelievable that a payment provider ignored customer complaining about no emails being delivered since it would breach their SLAs with their customers and their customers' customers would have complained. Especially since at the top you say Google says you got the verified email.

Dude, you may be liable for damages on this. This is an extremely serious allegation to be making in my opinion. I would delete this asap.

Edit: I think Ycombinator needs to realise they're liable for spreading this too. Holy crap, it's bad. They're lying through their teeth saying an email bounced but ended up in their logs. That's not now emails bounce is it? They bounce because it wasn't found. How was he able to verify his email if he didn't get the code?

Interesting subjects? A 30(?) year old programming language that has been on here repeatedly is not an interesting subject. New programming languages are. Cool things written in obscure languages is also interesting.

The content marketing that is pushed by sock accounts is wank and generally drops pretty quickly and called out like this. But you just complain about content marketing because you're one of those people who think you should make money but no one else.

I'm not sure how I'm being harsh. It's literally a somewhat well known programming language being reposted for the 100th time or something silly like that. I'm literally just pointing out the truth and it's almost certainly the main poster downvoting things.

> Do you know the joke with "I'll repeat the joke to you until you understand it?".

Nope. That's not a joke. That's not funny.

> That's why some things get reposted and upvoted. In hope of getting someone else to understand them.

No, they get reposted and upvoted by sock accounts in hope that someone will finally be interested in a 30 year old programming language.

> By the way, do you complain about sock accounts when yet another "Here is this problem, and by the way we sell a product that claims to solve it" gets upvoted?

What does content marketing have to do with sock accounts?

I'm honestly not sure what point you thought was getting made. Do you honestly think people don't understand D? It's been looked at repeatedly and still nothing cool is built in it.

All seriousness, do you honestly think this site has 10,000 new users a day? How many people do you think are on here that aren't very well informed? Honestly, I'm just wondering?

Also, do you know it only gets to front page if the hardcore that go to new upvote it? How many hardcore people don't know what D is?

Let's be serious, most people are regulars and this has been on the front page multiple times like constantly. And it was upvoted 4 times on new to get to the front page rapidly. It's not something new that we're all "Oh that's cool".

We also know there are tons of sock accounts.

And no half of the posts on front page can't be put in that since they aren't constantly reposted like this.

So, while there are a few people who will have learnt about this for the first time. Most of you know what it is and somehow feel like this is your chance to go look I'm smarter than Iain. And I think you've failed again.

> Formal verification is a hardcore approach. It is difficult and it is the holy grail of software engineering.

My first question is, what is formal verification? Since I am a hardcore nerd, I'm confused since this blog post basically says tests aren't good enough.

Serious question, how is this on the front page? We all know of the language and chosen not to use it.

Edit: Instead of downvoting, just answer the question if you've upvoted it. But I'm guessing it's the same sock accounts that upvoted it.

How often do issues break? And how is waiting a few minutes breaking the process?

It does? Do you know git is a dvcs? And therefore you're able to continue working without an internet connection or a service provider being up? It delays the code review process but doesn't break it.

I get it that you want it to be 100% up, but let's be serious your FLOSS projects probably break more stuff than GitHub being down does.

Dude, you need to stay on script! Over here you're saying it's an anti-trust issue [1]. It's literally the thread above this.

[1] https://news.ycombinator.com/item?id=46946827#46946914

What someone saying to me privately via other channels that it was them when I asked them. It was some dude at Google so maybe complain to Google but I don't think this site has rules about what you do off the site. I don't think you understand rules and laws and stuff to be fair. And I'm pretty sure it was you because it's weird if someone was pretending to be you.

Didn't you just privately tell me it was 4 accounts? Maybe that was someone else hating on Windows 95. But you need an active reason not what they did 20 years ago.