For EMail, Robo supports UUE, Base64, BinHex and LCMCODE attachments. The notes with file attachments must be sent to either robo@robomaster.ca or fallback@robomaster.ca, sending them anywhere else will not get them included. Beware of notes from other functions of Robo. Robo will send confirmations with a different return address. This is so that auto-responders do not cause infinite email loops. The Robo Postings and New Bulletin are also sent with a different return address. Responding to any of these notes with a TRN file is a sure way to miss a turn.

The fallback@robomaster.ca address is intended for those players whose email service encounters frequent delays. A while ago I was asked to implement something where a partial TRN could be sent and not trigger HOST. Since then the fallback address has been used by allies to put in a conditional TRN, just in case their ally is not able to submit a real TRN on his own (possibly out of town). It has also been used to ensure the schedule when a player knows they are going to be away, but can make their TRNs according to the schedule, only if the game does not run early.

Unless an authorization list has been specified, and as long as authorization has not been blocked, anyone who has received an RST, or a copy of the RST, for a game at Robo can submit a TRN for that game. If the authorization has been blocked, then only the email address of record, or any alternate addresses, can submit a TRN. If there is an authorization list, then only addresses on that authorization list can submit TRN files (in addition to the address of record and any alternates). One method of bypassing the authorization list is to specify the ROBOUSER: and CODEWORD: parameters in the body of the email note. This is primarily for players who are travelling and are using a Cyber Cafe, or relatives EMail, to submit their TRN files, or for any situation where the return address is unknown.

The syntax is either:

  ROBOUSER: <Email> <Codeword>

or

  ROBOUSER: <Email>
  CODEWORD: <Codeword>