j256 / mailgw Goto Github PK

I suggest you add tooltips to Mailgw. For example, I think "Del" and "Mail" would benefit from tooltips.

I suppose the tooltips might be:

1. "Click on this to delete this email address. Don't worry, even if you confirm deletion of this email you will have the ability to undelete this email address for 365 days (a whole year)."
2. "Click on this to send an email from this email address.

Assuming they don't expire, I suggest you add something like...

"Mailgw provides a free anti-spam-mail service to help you take control over your email. With your Mailgw account, you can give out a separate email address to every company which asks you for one. Unlike many of our competitors, email addresses you create on Mailgw last indefinitely (they don't expire)."

to

https://mailgw.com/

I would like the ability to create a disposable email on the fly without needing to login.

Other's have mentioned this. Mailgw does have a auto-create feature but you need to confirm the creation.

Like the title of this issue asks: how does one use Mailgw's auto-create feature?

I liked the ability to create an email such as...
[email protected]

I think that this is possible given the 3 periods.

Sure. That's what I figured.

I initially was worried that folks would create email addresses on your behalf

It happened to me a dozen or so times on Spamgourmet: maybe once every year or two. It was notable but barely annoying compared to the very welcome "handiness" (usefulness) of being able to create a new disposable email address "on the fly" as I was signing up for a user name and password on a new website.

When signing up on www.foo.com I would simply—essentially although not precisely—type something like "[email protected]" where...

1. foo = website name, and
2. the number "2"= number of email messages to receive, and
3. [email protected] = the "root" of my spamgourmet.com email addresses.

Actually, precisely, I normally used "recursor.net" instead of "spamgourmet.com" because "recursor.net"—one of the domains owned by Spamgourmet—presumably would seem innocuous to any person who happened to glance at it, whereas "spamgourmet.com" would presumably seem suspicious.

and then send you spam but they would need to know your original email in which case why bother.

As I indicated above, once every year or two, I guess some spammer "messed up" their spambot and did send a message to one of my Spamgourmet disposable email addresses. But I presume they did so inadvertently (due to their own incompetence).

Here's an analogy for you: people injure themselves—and even die—walking up and down stairs. But stairs are commonly used because, of course, their benefits far outweigh the detriments.

Obviously you would need to send mail from one of the emails on your account for this to be triggered

As I indicated above, that's not how it works on Spamgourmet.

If you wanted to error on the side of caution, I suppose you might do the following. The very first time Mailgw were to send a user an email from a "non-extant Mailgw disposable email address" you might send the user the actual email (that, say, Amazon.com or eBay.com had presumably sent to the user) as well as a second email message (a "safety email") with a "one-click confirmation" by which I mean, the second email message might have the user click on something such as,

"We assume you probably created the following email address...

[email protected]

when, for example, you recently signed up for a new account on a new website. However, in the extremely unlikely event that, for example, a bot is sending spam to you using [email protected] then please click on...

"This is spam! I don't want to receive messages which are sent to [email protected]."

I'll be blunt: trying to create 100% secure products often leads engineers to make bad choices. No, I don't want a bridge to collapse. But a 99.99966% secure bridge for half the price is a almost always a better deal than a 99.99999% secure bridge which costs twice the price of the "vulnerable" bridge.

http://www.mailgw.com/ is difficult for me to remember. On the other hand, http://www.mail123456.com/ is easy for me to remember.

Sorry about that.

No problem. I've worked with many engineers. They have all been terrible at UI/UX (user interface/user experience).

When I used Spamgourmet.com I rarely used that email. I used one of their other domains "recursor.net" so that I might create an email address such as...

There are other domains that map to mailgw.com. spam86.com is one of them. mnull.com is another.

I see.

Is that what you want

No.

I want mail123456.com.

Bad design makes people learn new stuff unnecessarily. Because I presume all users of Mailgw.com know how to count from one to ten, then something like mail123456 would almost certainly be easier for them to remember than domains spam86.com and mnull.com.

I am thinking of the following use case...

1. I am signing up for a new website.
2. I need to enter an email address.
3. I am creating a new email address "on the fly" (to avoid being spammed in the future).
4. I can more remember to type in "mail123456.com" at the end of, for example, [email protected] (to receive a free chocolate chip cookie in the mail) more easily than [email protected]

And yeah, of course, that's a feature request. Mailgw obviously should allow users to include capital letters, underscores, and dashes in email addresses. Please don't take offense but disallowing them is obviously bad practice. If your code "breaks" because of that, well, then, ummm, hmmmm... I suggest you update your code. It's not 1996 any longer!

Please see... https://i.imgur.com/NsLas79.png.

Github allows creating more than one type of issue. I suggest you have at least two types of issues: bug reports and feature requests, just like the flameshot github.