Live data from Hacker News

How to use Gmail to destroy your relationship with your investors and customers

iamnotaprogrammer.com

141–150 of 159 posts

Re: How to use Gmail to destroy your relationship with your investors and customers

#141
post #133
post #117

Earlier quoted context omitted.

The goal is not to deter people from showing contempt for lack of intelligent action. (Unless that contempt is for someone who lacks intelligence because of a disability). When someone does something stupid it is fine to call them stupid. The goal is to ask people to consider using words that are not recently (even currently) used for learning disabilities. Retard has strong links with learning disabilities. Enough t…

What is the difference between being retarded due to a disability, and being stupid due to genetics? Is it just a difference of degrees? I mean both are cases of "factor outside of individuals control -> (extremely) low intelligence"

A learning disability tends to be defined by IQ (IQ less than 75 or so), rather than anything else.

Thus, someone with a chromosomal disorder, or someone who was deprived of oxygen during birth, or someone who is just stupid because of genetics all have learning disabilities. They just have different forms of learning disability.

Re: How to use Gmail to destroy your relationship with your investors and customers

#142
post #131
post #76

Earlier quoted context omitted.

> How does the appearance look? You send e-mail to foo@business.com and then funkyjizzbeats20@gmail.com replies to you! What could be more professional than that? If you configure your GMail account correctly, it will reply via the other account's own SMTP servers. There will be no evidence of your private GMail account, even in the headers. (This is not the same thing as just configuring GMail to set a particular "F…

How would I make gmail use the smtp servers?

In the "Accounts and Import" settings, you add an account and instead of choosing "Send through GMail (easier to set up)", choose "Send through 's SMTP servers".

And then you need to enter the username, server, password, etc for the other account, which can even be another GMail account.

Re: How to use Gmail to destroy your relationship with your investors and customers

#143
post #106
post #71

Earlier quoted context omitted.

There is a simple fix for this. Gmail can be configured to send via any arbitrary mail server. So you can configure your person account to send via the SMTP settings of your business account. This leaves no evidence of your personal account, even in the headers.

Not if you are sending as a @gmail account from a different @gmail account. No way to remove your `Sender:` header in that case. Ridiculous, as you can easily fix it for any other @domain.

Ah, I see. I hadn't thought about that case.

I have a lot gmail account, but only one of them is on the gmail domain name, so that hadn't come up for me.

Re: How to use Gmail to destroy your relationship with your investors and customers

#144
post #139

Earlier quoted context omitted.

What they're doing is making a very dodgey assumption. They might stop a few hundred potential spammers but they also stop millions of people who could potentially be using email more effiently and reliably (and Spam Free) by sending and/or receiving mail directly between their machines. Email could be even more decentralized than it already is in practice. This could potentially make spam far more difficult. Reading…

Your position is baffling. It's not a quote from spamhaus. It's me re-wording your text. > Why the heck aren't the millions of people on dynamic IP's using this capability? Answer: They do not know it exists. No. Millions of people have no interest in running their own email server. What benefit do most people get from running their own server? (Where most people are those who have one or two email addresses, which t…

Installing and maintaining a mail server. What OS doe you use? I'll bet there a whole host of dameons or services running and you never pay much attention to them. Someone else installed and configured them for you. And they just run all the time and you don't even pay attention to them.

What is an "mail server"? At its essence it's just a program that listens on a port for an incoming or outgoing message. Then you have programs for storing, delivering, forwarding, etc. And maybe you have perceived issues of being able to handle lots of messages. But you don't necessarily need all that if you are not providing email for other people. What if you're just a casual user who wants to send or receive a message to/from your friend? If I have an email daemon (or a "service" in Microsoft parlance) listening on a local port, I can type some text and "hit send" (or whatever method I choose to send the text to the daemon) and the mail is sent. No email provider needed. If the recipient has her email daemon listening for messages from my IP address (and only my IP address), she gets the message "immediately". There is no third party email provider. This is how email works.

There is also no spam if we do it that way. Her daemon is not open to the whole internet. It's only open to me. Why is this so baffling?

Neither third party email providers nor some rule that "no one wants to run an email server" or "no one should run their own email server" are a part of the email protocol. Those are your observations of what people have done so far and your opinions. They do not set limits on what can and cannot be done. Are we in the business of startups and trying new things or are we here to preserve status quo?

Email is internet messaging, one of the oldest forms of it. Email is a message sent in a specified format* over the internet. What could be more simple?

*Granted the format is rather rigid, but it's not too difficult for anyone to learn. It's like writing a business letter.

Millions of people have an interest in sending messages to each other over the internet. And millions of people have no interest in sending bulk email for commercial purposes. That's all I need to know. A project is born.

There is a need for an "email replacement" as many others have voiced and as pg identified in his list, but I'm afraid it's not going to come from anti-spam zealots. I appreciate what they try to do, but I do not appreciate their mindless, blunt-force methods and ideas about "good guys" and "bad guys".

There is an enormous amount of bulk email sent every minute of everyday. Just because it is "opt-out" doesn't make it any less impersonal and unwanted (or any less of a huge drain on the world's computing resources). Can we accept that some people have little interest in receiving bulk email, and that there may be a market (besides you) for email inboxes that are not open to marketers, but only to known contacts? Alas, that's not what the anti-spam zealots aim to address. They do not want to curb bulk email. They just want to stop certain senders.

This does not really move me toward my vision of email. It's just the same old thing. An inbox full of garbage.

Re: How to use Gmail to destroy your relationship with your investors and customers

#145
post #140

Earlier quoted context omitted.

Where did I claim it's not a closed ecosystem? It's starts closed and it is opened by invitation. Yep. That is exactly how it works. If you cannot understand that approach, then that just means it's not how you think. It does not mean that the approach makes no sense or has zero utility. Maybe a stupid analogy can be made if we pretend "Facebook" is the internet (of course it's not, but it does present a messaging sy…

Your posts contain a baffling mix of incompatible ideas. You argue against block listing, but then suggest blocking the entire Internet except the few people you want to send you email. You say that only people who you have given your email address to should be able to send you email, and then you say there should be a lookup system to get email addresses. (But what's the point of the email directory system if you ca…

I never said there should be a lookup system. Where are you seeing that? I said there isn't one and people still manage to get by. The other commenter was suggesting looking up addresses was some sort of problem. I'm saying it's a non-issue. If not having a public name-to-email lookup was a show stopper, then we would not be having this discussion because email would not be popular. People get by just fine without lookup. They exchange addresses and store addresses on their own.

Discussion is great. But you have to read carefully to understand what's being said. (If I am not being clear, then I apologize.) But if your mind is closed then there's no point reading what I'm typing because I am not regurgitating the usual ideas on email.

Anwyay, discussion is irrelevent when juxtaposed against running code. I'm interested in stuff that works more than getting approval from people in online forums.

This is not some new thing. Anyone can use email this way now. We all have good connections and bandwidth. There is no need for store and forward. What has stood in the way of using email as direct communication is people who can only see email being used one way: daemons that accept commands from any connection, spoofed IP's and all, and email as a service run by someone else, not a small program on the client's machine. If it was impossible to authenticate connections based on any other means besides real-time challenge-response, or DNS run by someone else, then how would people manage to run ssh daemons without the same problems as email?

Re: How to use Gmail to destroy your relationship with your investors and customers

#146

Earlier quoted context omitted.

Gmail allows you to send from your other email addresses through the web interface. It is nice having multiple accounts in the same mailbox so they can share labels. I don't think it's a violation of trust to have mail forwarded from one account to another account on the same provider. Email does not have an implied amount of security or privacy. Sending email is like sending a postcard--Anyone involved in its transi…

I'd say it is more analogous to regular first-class mail in an envelope. There is some expectation of privacy, but no guarantee.

I would agree with the envelope analogy if the message was not encoded in plain text. Say base64--an intermediate has to go through a slight process to read it, like opening an envelope.

Mostly, it's worse than a postcard. It'd be like if every letter carrier makes a copy of the postcard, then is supposed to discard theirs once the next person has their copy. There is zero guarantee that any of the several copies were actually discarded, and it's highly improbable that they were erased securely by any of the intermediates.

Knowing that the messages are transmitted in plain text across at least two mail servers (often more), and across several intermediate ISPs, it is ... unlikely... for an informed person to have an expectation of privacy in email.

Encryption solves all these problems, but we all know that's not in mainstream use. Not even signing!

Re: How to use Gmail to destroy your relationship with your investors and customers

#147
post #119

Earlier quoted context omitted.

I wish we could get these anti-spam zealots to apply the same effort to stopping junk postal mail. The history of direct mail is interesting and perhaps instructive. It has been kept alive by those who do the delivery (cf. those who do the sending). I have sometimes wondered if the same might be true for email. If your emplyer knows its recipients (e.g. business partners) and can coordinate with them to run an SMTP s…

If his employer knows the recipient the employer can ask the recipient to either stop using the block list, or to poke a whole in it and whitelist their email.

Are you suggesting his employer doesn't know the recipients? Hmm, if true, I wonder what sort of email that might be.

Not the type I'm interested in.

Re: How to use Gmail to destroy your relationship with your investors and customers

#148
post #119

Earlier quoted context omitted.

If his employer knows the recipient the employer can ask the recipient to either stop using the block list, or to poke a whole in it and whitelist their email.

Are you suggesting his employer doesn't know the recipients? Hmm, if true, I wonder what sort of email that might be. Not the type I'm interested in.

Read the thread again.

> For example my employer's mail server--which has been sending legitimate person-to-person emails for years (no bulk)--has ended up on blacklists several times because some blacklist operator decided to black-hole an entire netblock at our ISP.

You replied:

> If your emplyer knows its recipients (e.g. business partners) and can coordinate with them to run an SMTP service for recieving and sending messages on a different port, would that solve the problem?

That solution introduces a bunch of problems: you're running more software that's open to the Internet and thus introducing insecurity; you're asking people (who might not be technical) to install and run software and use a different mechanism when they want to communicate with a subset of users.

The other solution is to just ask the people that you're sending email to, but who are using a whitelist / block list to add you to the white list or exclude you from the block list.

Re: How to use Gmail to destroy your relationship with your investors and customers

#149
post #148

Earlier quoted context omitted.

Are you suggesting his employer doesn't know the recipients? Hmm, if true, I wonder what sort of email that might be. Not the type I'm interested in.

Read the thread again. > For example my employer's mail server--which has been sending legitimate person-to-person emails for years (no bulk)--has ended up on blacklists several times because some blacklist operator decided to black-hole an entire netblock at our ISP. You replied: > If your emplyer knows its recipients (e.g. business partners) and can coordinate with them to run an SMTP service for recieving and send…

You're making assumptions. About how things would work and about users and what they can and cannot do. Typical online discussion. Lots and lots of assumptions.

I do not understand your last sentence. Didn't he say his ISP is blocking outgoing mail? The recipients are powerless to unilaterally change that situation.

Think about this for a moment. Forget the corporate example. Imagine one user has a daemon listening for mail (no setup, it's all been set up for him:- it's "built-in" to his OS). Imagine there is an authentication method e.g. a shared secret and perhaps even some obfuscation like port knocking to hide the open port. Even assuming a determined spammer can get past this, is it worth his time? He will reach a grand total of one user.

We can even use a small overlay, where the IP addresses are private, not routable on the internet. The spammer needs to get into the overlay network first, again defeating things like shared secrets or perhaps private keys to identify machines before he can even get a shot a access to a listening mail daemon. That's not easy to do if the users stay logged in. And again, if the network is small, with a few hundred users or less, maybe only a handful, is it worth his time?

Re: How to use Gmail to destroy your relationship with your investors and customers

#150

Earlier quoted context omitted.

Blacklists are run by anti-spam zealots who really don't care about what is fair or a smart idea. For example my employer's mail server--which has been sending legitimate person-to-person emails for years (no bulk)--has ended up on blacklists several times because some blacklist operator decided to black-hole an entire netblock at our ISP. From the blacklist operator's perspective, the broad effect of the block is in…

I wish we could get these anti-spam zealots to apply the same effort to stopping junk postal mail. The history of direct mail is interesting and perhaps instructive. It has been kept alive by those who do the delivery (cf. those who do the sending). I have sometimes wondered if the same might be true for email. If your emplyer knows its recipients (e.g. business partners) and can coordinate with them to run an SMTP s…

This is not a workable solution because the problem is not based on what port SMTP is running on. Organizations and ISPs voluntarily subscribe to email blacklists because they are desperate for any help in reducing spam volumes. They would filter email coming from blacklisted IPs regardless of what port it came in on.

You're basically proposing a whitelist solution, which has many known problems: it does not scale well; it does not handle new or unexpected email partners; it relies on the simultaneous cooperation of all parties; etc. In this particular case it also relies on spammers remaining ignorant of the new port for SMTP--which seems unlikely.

Post reply on HN