Sending files to RealNetworks employees:

Files can be delivered to RealNetworks employees using the following CGI: https://tobor2.prognet.com/cgi-bin/incoming.cgi .

Either drag and drop the file you would like to send into the first box, or click the "Browse" button to bring up a file selection window.

In the second box, indicate the name of the user to whom you would like to send a file. This must be a RealNetworks employee email account, and not an alias or list of any type.

In the text area below, you can specify additional information that will be given to the recipient in the email notice they receive. It is a good idea to provide your name and email address in this field as a signature for your file transfer.

When you are finished, click the button labeled "Send File". If there are any errors, you will be notified. Otherwise, the program will report success with a message like:
The file product.pdf was successfully delivered to jdoe.

In this example, the user "jdoe" would receive an email notice that he'd been sent a file. It would look something like the following:
From:Tobor File Transfer Service <null@real.com>
To:jdoe@real.com
Subject:File transfer notice
Date:22 Apr 2014 12:24:29 -0700
You have received the file product.pdf from 172.20.112.159.

Please pick it up as soon as possible from \\TOBOR2\HOMES\incoming

The sender said:
Please review the document before our meeting.

John Doe - jdoe@real.com
Please do not reply to this message.

Sending files to users outside RealNetworks:

Files can be delivered to users outside of RealNetworks by employees using the following CGI: https://tobor2.prognet.com/cgi-bin/private/outgoing.cgi .

In order to access the CGI, you must log in with your RN username and password.

In the first text area, you can specify the email addresses of the people who should be told about the location of this file. Please, list only one address per line.

Optionally, you may specify a username and password which must be used to retrieve this file. If you leave these boxes blank, no authentication will be required for remote persons to download the file that you are uploading to tobor. If you choose to protect the document with a username/password, follow these guidelines: In the final text area, you can specify additional information that will be given to the recipients in the email notice they receive.

When you are finished, click the button labeled "Send File". If there are any errors, you will be notified. Otherwise, the program will report success with a message like:
Your outgoing directory was created successfully. Save your files in \\TOBOR2\HOMES\public_html\0011432.39225 and they will be accessible to the users you listed.

The location listed will be a link that you can click, or enter the location in to the "Run" item on your Start menu. Any files that you copy to this folder will be available to the users you listed initially. This makes it simple to upload a small group of files for distribution. However, if you have a large group of files, or a complex folder structure, you should probably "Zip" the files first, and upload the .zip file to the server.

NOTE: Users who download files from tobor2 using https will be warned that the security certificate is not signed by a recognized authority. The certificate on tobor2 is self-signed. If the certificate is accepted, all of the session (including the location of the file, the username/password, and the file transferred) will still be encrypted.

In this example, the remote users would receive an email notice that they'd been sent a file by "jdoe". It would look something like the following:
From:Tobor File Transfer Service <null@real.com>
To:Undisclosed <null@real.com>
Subject:File transfer notice
Date:22 Apr 2014 12:24:29 -0700
You were sent the file https://tobor2.prognet.com/~jdoe/1019510625.65.6511/product.pdf from 172.20.112.159 by jdoe@real.com.

Please pick it up as soon as possible.

You will be asked for the following:
Username: ThisFile
Password: IsProtected

The sender said:
Don't let anyone else see the contents of this file!
Please do not reply to this message.
RealNetworks Bubble Logo

John Doe <jdoe@realnetworks.com>
Last modified: Mon Apr 22 15:01:12 PDT 2014