E-mail & Instant Messaging

Page Table of Contents


Security Notice (2014.04)

EMN's primary services were never vulnerable.

For a description of the issue see heartbleed.com.

As for EMN specifically: The primary host runs a Long Term Support OS which means bug-fixes and security-patches are applied by default but new versions with new features aren't. It was never upgraded to support the feature which introduced the vulnerability.

While there is no evidence to suggest that passwords for EMN were ever exposed and the jabber/mail servers were never vulnerable; the possibility remains. You're encouraged to set a new password by the normal method.

Please ensure that your password for EMN is not the same for any other service.

Certificate Change (2014.01.14)

Replaced the expired StartSSL CA Cert with a self-signed one. This should alleviate "certificate expired" warnings; replaced with a one-time "self signed, can't automatically verify identity" warning.

Please see the Certificates page for further details.

Recent Service Outages

Update 2014.01.02: Services should be recovering as DNS updates propagate.

The hosting provider for EMN had a migration planned for the new year (poor timing indeed). All preparations which could be reasonably expected were made, and we double-checked our disaster recovery, etc. It should have been nearly seemless (there are always a few that are getting stale DNS info).

Ultimately it's our responsibility to see that EMN's services are available. Regardless of the performance of any one provider. The donations made to EMN for the purpose of funding hosting should be put to good use. Please keep that context in mind for the following rant.

Our provider comprehensively dropped the ball.

Actually not just 'the' ball. If they managed to locate any one of a number of different balls and managed to elevate it even just slightly services would have been operating normally far sooner.

Part of our own preparations that could have avoided much of this pain were prevented because they went and broke key services days in advance of the announced changeover. And then went through with the changeover with them still broken (but not until it was already a day late). And not only failed to restore them during the changeover, or within a dozen hours after the changeover, but also failed to act on any one of a littany of requested workarounds which were given before the changeover date.

We're in the process of moving our Domain registration and DNS hosting away from this provider. We'll be reviewing options for hosting of services.

API Code Migration

Update 2013.09.13: Eve-Mail.Net (this service) no longer supports Legacy API Keys.

Most of you have already updated to modern keys. The rest of you can use the normal form to re-submit with a modern key: https://eve-mail.net/api.py

If you've had issues recently it's possible submitting a modern key with more access will resolve them. This may also help if you spontaneously lose access some time after this message (I'll be doing a forced-refresh of all accounts).

And the usual disclaimer: an API key is not required to use EMN's basic services, only those features which require API functionality (like automatically managed corp and alliance chats).

As for "why now?": I had planned to support legacy keys as long as CCP did, but their 2013.06.26 update to the API broke error handling rather spectacularly. I've worked around this in most features but I'm not willing to rework how I handle legacy keys as they've been deprecated for some time now. More Info: https://forums.eveonline.com/default.aspx?g=posts&m=3423701#post3423701


Update 2012.10.06: The web-based account creation/update page is now converted. It only refers to vCodes but will still accept Legacy keys (though I haven't tested that option extensively and I'm not sure why you would use it).


Access Mask Options

How to Update

You can use web-based account creation/update page (the same is if you wereupdating your password).
or
You can use The Postmaster bot on Jabber. Simply open a conversation and send apikey [keyID] [vCode](obviously without the brackets).


About the Service

There is additional information in eve-online forum threads

So what's this all about? It's not 'just another e-mail address'.

Basic IM Service Features

IM Features With a Limited API Key Basic Mail Service Features Features With a Full API Key

The addressis useful. It's a nice easy to remember e-mail address to use for dealing with other EVE players,without having to give out your normal address. And because everyone's e-mail address is tied to their in-gamecharacter name, people can be confident that it's really you e-mailing them.

The interesting thing is the Jabber (aka XMPP) Server. It's an Instant Message server. Unlike MSN or AIManyone (with some basic technical skills) can set one up and people using different servers can communicate by justusing user_name@eve-mail.net or user_name@gmail.com (for G-Talk) addresses.

The most compelling feature of Jabber is the ability to setup shared contact lists (or 'groups'). For thisserver it's handled through a bot (the user named "The Postmaster"). Just tell The Postmaster to add you to a groupand then (after you reconnect) your contact list will automatically show a new group with all of the existingmembers of that group (and they'll see you after a reconnect too). No more adding each member of your corp or alliance one address at a time. No moretrying to remember who PJohnson3874@MSN.com is in game.

If you provide an API key, you and all of your corp mates are automatically added to your own 'locked' groupwith only your corp members and another for your alliance.

Setting your API information also creates and sets permissions for member-restricted chat rooms for your corp andalliance.

You can also easily broadcast messages to your entire corporation or alliance group. Simply send a message to[ticker]@broadcast.eve-mail.net.

You can use "The Postmaster" bot to manage your API info, join/leave additional groups, and so on.


Donate

One time or recurring via paypal (More Details).


Account Creation

There are two methods of creating an account:

Password Reset

Password resets can be done by simply repeating either account creation method, regardless of which method you originally used to creat your account.


User Names

Your user name is your in game character name with two changes. Any spaces are converted to a _ (underscore) and any ' (apostrophe) are converted to a . (period).

Example: First La'st would turn into first_la.st.


Mail Setup

You can use your Google Mail account to send and receive messages with your eve-mail.net address (Google's Instructions). Onegmail login for both addresses.

OR

You can use a traditional e-mail client on your computer or phone (both the normal POP3 and IMAP access are supported).

Server Details:


IM (Jabber/XMPP) Setup

Some clients will just ask for your full address (user_name@eve-mail.net), others may ask for your screenname (user_name), domain (eve-mail.net), and server (eve-mail.net) separately.

Ports are default and SSL is again optional (certificate is self-signed).

There are a huge variety of clients, many of which support AIM/MSN/Yahoo/etc protocols as well (multi-protocolclients denoted with a *).

Windows: Trillian Pro*, Pidgin*, Spark, Psi,more...

Mac: iChat*, Adium*, Psi, more...

Unix: Pidgin*, Spark,Psi, more...


Contact, Support, Suggestions, and just generally saying Hi

You can mail "The Postmaster" (at eve-mail.net) with questions, suggestions, comments, issues, etc.

I (Lake) am virtually always on the IM server. I'm not always available but feel free to leave a message and I'llget back to you when I'm so inclined.

Thanks

A particular thanks to Entity for his EVE API Library for python, upon which I've built a multitude of EVEAPI projects, including this site.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.