In TAW 3.0 the email & messaging system has been completely reworked. In this blog post we’ll go over some of the major features that the TAW 3.0 email & messaging system brings.

Internal Messaging

Sending messages to other TAW members will work very similar to the current system. You will be able to easily send messages to other TAW members on the website. The major difference with the current system is the ability to start a conversation with multiple members at the same time. The ability to add members to the CC or BCC of a message will also be included at launch.

Integrated email client

TAW 3.0 offers the ability to send emails to any email address straight from the TAW website. This will be seamlessly integrated with the internal messaging system. If you send a message to TAW members it will just be sent straight to their inbox on the TAW website. Whilst if you send a message to any external email address it will send an email to that address. You can of course send a message to both TAW members and external email addresses at the same time.

This wouldn’t be very useful if we weren’t able to receive emails so if someone were to send an email to VeryCoolUsername@taw.net, VeryCoolUsername would receive that email in his inbox on the TAW website.

In the images below you can see an example of an exchange between the TAW website and gmail. The first image shows the messages in gmail and the second image shows the same messages in TAW 3.0. Note that the TAW 3.0 image is still a work in progress and may still change significantly.

Unit inbox

With the old system it can be a bit of a hassle to send official requests between different units. An example of this would be transfers between Army and Ops. If VeryCoolUsername would want to transfer from War Thunder to the Communication Division, the DC of WAR would have to send an email to the COMMS DC and the COMMS DO and include 1CC, 1CLC, AC, ALC, OC, OLC, MRC CC, MRC CLC in the CC of the email. The callsigns for all 10 of these people would have to be looked up and correctly spelled to be able to properly send the transfer request. As you can probably imagine manually typing 10 different callsigns can be quite time error prone and time consuming. 

As an intermediate solution we will be introducing unit inboxes. Unit inboxes will be accessible by the commanders of a unit so for a division the DC and DO would have access. They would then be able to send and receive emails and messages. So for internal communication you can just type the name of the unit(s) you would like to message and the staff of that unit will be able to respond. This removes the need to look up and type the names of individual people in the CoC.

Minor features

Attachments

TAW 3.0 will support email attachments so you will be able to send emails with any type of file attached.

Spam protection

Since TAW 3.0 will allow you to receive emails from external parties, spam protection is essential.

Auto completion of callsigns, units and email addresses

To minimise the risk of mistyping a callsign, unit name or email address when sending a message we have added autocompletion. This can be seen in action in the videos below.

Video 1

Video 2

Formatting

To make your emails look just that little bit better TAW 3.0 will support email formatting.

Notification settings

You will be able to configure whether or not you want emails sent to your @taw.net to be forwarded to your personal email.

The End.

If you have any questions, suggestions or concerns feel free to reach out to me(FlyingDutchMan [CC SEC]) via Discord, the website, carrier pigeon or email.