When you receive files sent via HTTP, you cannot observe the file transfer(s) on the server but you can see summary information about the transfers in the Log window of the MassTransit Administrator application. In addition, you can designate services and/or actions that you have configured on the server, to be performed on the received files in the Files window of the MassTransit Administrator application.
Please note that using a secured connection may slow down the transmission speed. When you encrypt the files, the file transfers are more secure but that increases the time for the transmission.
The transferred files are being received in the Received folder of the contact's mailbox.
MassTransit 6.0.2 and later support transfers of files and folders with Unicode characters in TCP/IP, TCP/IP Secure, and UDT file transfers. By default, MassTransit will queue and transfer files and folders with high Unicode (>0xFF) successfully across the MassTransit protocol (TCP/IP, TCP/IP Secure, and UDT connections).
See the Transferring Files page for more information on the MassTransit Unicode support.
Ad hoc file transfer allows Web client contacts to send files to users designated by email addresses that may or may not already have accounts in MassTransit. After logging in to the MassTransit Web (MTWeb) site, Web client users are allowed to send files to any valid email address. When the Web client clicks on the "Send" button, the files are sent to the MassTransit server. If the entered email address does not belong to an existing contact on the server, an account with that address is automatically created. If you have a limited Web client contact licenses, the automatically created contact will be an Ad hoc contact. Otherwise, the created contact will be a Web client contact.
See the Ad Hoc Delivery page for more information and configuration instructions.
MassTransit 7 provides a new feature called Request Files. It allows Web client users to request files to be sent to them from other users designated by email addresses. After logging in to the MassTransit Web (MTWeb) site, the web client users are allowed to send a request to any valid email address. If the entered email address does not belong to an existing contact on the server, an account with that address is automatically created.
See the Request Files page for more information and configuration instructions.
Configuring Request Files
The configuration of the Request Files feature consists of three principal steps:
Configuring the Ad Hoc Delivery Feature
Before configuring the request files feature, you need to configure the ad hoc delivery feature first. You can find detailed instructions about how to do that on the Ad Hoc Delivery page.
If you have already configured the ad hoc delivery feature, continue with the instructions below.
Creating an Email Action
To enable the Request Files feature, you need to add an email action in MassTransit which will notify the contacts of the file request.
$${{Subject}}
The token that will contain an HTTP link, allowing the contact to click the link and send files from the MassTransit server is:
$${{HTTPLink_passkey}}
The following 3 tokens are also available with the Files Requested action:
Here is an example text for the email action Message area:
$${{ContactName}},
$${{OriginatingContactName}} ($${{OriginatingEmailAddress}}) is requesting files from you:
$${{Subject}}
$${{Note}}
Click the link below to be automatically logged in and to send files.
$${{HTTPLink_passkey}}
This automatic login link is good for $${{PasskeyTTLHours}} hours.
The used tokens in the example text of the e-mail notification do the following:
$${{ContactName}} - name of the person receiving the email
$${{OriginatingContactName}} - displays the contact name of the originating user who is requesting the files
$${{OriginatingEmailAddress}} - displays the email address of the originating user
$${{PasskeyTTLHours}} - displays the validity time of the passkey link set in the MassTransitEngine.cfg file
Note: The complete list with the available tokens and detailed information about them can be found on the Email Notification Tokens page.
Configuring Contacts to Use Request Files
The last step for configuring the request files feature is to set the desired individual users who will be able to send files to other contacts and arbitrary e-mail addresses. This configuration is per user only and you need to set it for each Web client contact that you want to use the feature. To do this, edit an existing Web client contact or add a new one from the Contacts window of the MassTransit Administrator.
Note: For more information about contact privileges, see Contact Privileges on the Contacts page.
Now, the request files feature is fully configured and the chosen Web client contacts should be able to send file requests to arbitrary email addresses.
Using the Request Files Feature
The request files feature can be used by Web client contacts only. They can find detailed information on how to send requests for files on the Requesting Files page from the Web Client User Guide.
MassTransit web users may be repeatedly prompted to Enter Network Password when attempting to access a MassTransit file transfer website hosted by Microsoft IIS. This dialog may appear prior to the display of any MassTransit web content, and may repeatedly appear throughout the user’s MassTransit web session.
Users attempting to access a MassTransit file transfer website hosted on Microsoft IIS may be prompted with a Windows authentication dialog if the MassTransit website permissions have not been configured to allow Anonymous access. As a result, a dialog box asking "Enter Network Password" may appear throughout the web session.
To resolve this behavior, Microsoft IIS must be configured to allow Anonymous access.
Follow the steps below for enabling Anonymous access on IIS depending on the IIS version you have.
To enable Anonymous access on IIS 6:
Note: The Internet Guest User account begins with "IUSR_" and may also need to be enabled within the Users and Groups Management Console.
The Anonymous access should be enabled and the web client users (Web client and Ad hoc contacts) should not be prompted to Enter Network Password.
To enable Anonymous access on IIS 7:
Note: The Internet Guest User account begins with "IUSR_" and may also need to be enabled within the Users and Groups Management Console.
The Anonymous access should be enabled and the web client users (Web client and Ad hoc contacts) should not be prompted to Enter Network Password.