![]() It gets more complex though when you consider the same user with multiple contexts: "I'll call Bob" at home might easily be a totally different person than "I'll call Bob" in the workplace. People who already know 49985189215 as "Bobby Smith" would see that pop up on their screen instead, and the rare few which have a conflicting "Bob Smith" would see it rendered differently, making it obvious I don't mean their Bob Smith. When I publish something for other people to see and add a special reference to Bob Smith, it contains "". When I ask the software to contact "Bob Smith", it knows who I mean from that mapping. We can take inspiration from how our meat-space society functions, where everybody maintains their own contextual aliases as metadata, something that can be personalized or shared.įor example, imagine we have a big global commenting site, and my own metadata says "Terr_ believes ID 49985189215 is Bob Smith." I disagree, there is a solution out there, it's just more work because the client-software has to be smarter. > I think of likely reasons this happens is username exhaustion. I get the sense that the relative lack of trouble I have maintaining a mail server is more to do with being effectively grandfathered in and worry that if I ever have to shift away from my current provider that email sending is going to become a lot harder since I won’t have my IP reputation any more. If someone sets up a server and it has never sent mail for their domain before-or, worse, they get a radioactive IP address-it may be hard to become accepted by other email providers. IP/domain reputation is also probably an issue I’ve been using the same IP address and domain names for over a decade so services like Talos are reasonably satisfied I’m harmless. ![]() They don’t seem to care that blocking a whole IPv4 netrange of a reputable VPS provider because some other customer was sending junk mail will cause collateral damage. I manage to get blacklisted a couple times per year by Hotmail, who still only support IPv4, despite SNDS always saying everything is fine. Gmail, but this isn't always desirable, because then that email provider gains access to the messages you redirect, and those messages might contain sensitive information.IP range is definitely a problem. As a workaround you can also redirect your messages through another email provider, e.g. You can point them to this add-on, bug 12916, or RFC2822 section 3.6.6. If you run into issues with an email provider not supporting redirection of messages, please contact them and see if you can make them change their policy. I think they do this in error, and also reported this to Microsoft, but unfortunately they haven't changed their policy yet. Most notably Microsoft does not support it at the moment, probably as a measure against SPAM. The extension is an answer for bug 12916 Not all email providers support redirection of messages. The feature of email redirecting is also known as remailing or resending. ![]() The Mailredirect extension for Mozilla Thunderbird and Mozilla SeaMonkey adds the ability to redirect one or more email messages to one or more recipients. If you depend on this functionality, please don't upgrade to Thunderbird 78, but stay on version 68 and disable updates, until a compatible version of Mail Redirect is released. ![]() ![]() I'm still working on a new version that works with Thunderbird 78.*. At the moment Mail Redirect is not yet compatible with Thunderbird 78.*. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |