OmniMix • Tutorial • Nyms • Sending Nym Messages

With an activated nym account sending nym messages is quite easy. Simply define the address of your nym as the sender of the message (in our example 'From: whopper@nym.panta-rhei.eu.org') and deliver it through OmniMix, which will recognize it as nym related and pass it on to the nym server, from where the final delivery takes place.

So a nym message coming from the client application should look like

--------------------------------------------------------------------------------
From: whopper@nym.mixmin.net
To: John Doe <john.doe@domain.net>
Subject: A Question
Nym-Commands: +acksend -signsend
O-Nym: Yes

Hi John,

how are you?

Greetings

Jack the Whopper
--------------------------------------------------------------------------------

or, as a MIME encoded message

--------------------------------------------------------------------------------
From: whopper@nym.mixmin.net
To: =?UTF-8?Q?Lieschen M=C3=BCller?= <jmueller@home.example>
Subject: =?UTF-8?Q?R=C3=BCckfrage?=
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Nym-Commands: +acksend -signsend
O-Nym: Yes

Hallo Lieschen,

wie geht's?

Gr=C3=BC=C3=9Fe

Jack the Whopper
--------------------------------------------------------------------------------

where the 'Nym-Commands:' and 'O-Nym:' header are optional to override OmniMix's internal settings. Of course OmniMix removes the 'O-Nym:' header before processing the message.

As nyms are only valid for specific users, don't forget to assign your nym account to the corresponding OmniMix user account. Otherwise outgoing messages with your nym's address in the 'From:' header are rejected.

Confirmation messages you have to send to activate your newly created nym account or any later account modifications are recognized as such and trimmed down to the destination's address before they are handed over to Mixmaster.

Here's what the 'Raw Data' log list shows in the course of that process:

--------------------------------------------------------------------------------
==================== [14:56:59.052 - 0] Getting from SMTP Client:
Received: from localhost[127.0.0.1] (helo=[127.0.0.1]) by localhost[127.0.0.1] with esmtp (OmniMix SMTP Server)
Message-ID: <55631C18.30006@domain.invalid>
Date: Mon, 25 May 2015 14:56:56 +0200
From: Anonymous <anon@domain.invalid>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: confirm+30dcb911435d759d@nym.mixmin.net
Subject: Re:
References: <--jtcNK4vK2FD7@nym.mixmin.net>
In-Reply-To: <--jtcNK4vK2FD7@nym.mixmin.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 5/25/2015 4:52 AM, config@nym.mixmin.net wrote:
> Your configuration request completed successfully.
>
> A new reply block has been received for your mail alias, but has not
> yet been activated.  In order to start receiving mail with your new
> reply block, you must confirm it by sending an (anonymous) E-mail
> message to the following address:
>
>    confirm+30dcb911435d759d@nym.mixmin.net
>
> The contents of the message can be anything.  Any message delivered to
> this address will activate your reply block.
>
>

==================== [14:56:59.072 - 0] Getting from Hashcash Minter:
To: confirm+30dcb911435d759d@nym.mixmin.net

==================== [14:56:59.082 - 0] Getting from Header Filter:
To: confirm+30dcb911435d759d@nym.mixmin.net

==================== [14:57:01.595 - 0] Getting from Message Converter:
Mode: Anon mail

To: confirm+30dcb911435d759d@nym.mixmin.net
--------------------------------------------------------------------------------

As you can see, with a confirmation reply the 'From:' address is irrelevant, as it's sent as a normal anonymous message without any reference to a specific nym account.