Delivery Confirmation

Purpose

Inform the sender of a transfer that a transfer has been received.

Details

Users can choose to request a delivery confirmation (also known as acknowledgement) per transfer. If enabled, the server will inform the sender of a transfer that it has been received by sending a delivery report notification email.

Image

A transfer is transitioning from unread to received state when:

  • it is currently unread
  • the download for one of its files is started by someone other than the sender, or
  • the transfer is copied to the receiver's drive, or
  • the transfer has been forwarded to other receivers

If the transfer has been deleted (through expiration or an action by the receiver/sender/admin), the sender will receive a no-delivery report notification email:

Image

The transfer's unread/received state is visible in the web portal of the sender, in section Sent:

Image

Note

  • Downloads performed by the sender (within an authenticated session) will not trigger the notification emails.
  • Unless recipient authentication is enabled, the notification email does not guarantee that the transfer download was actually performed by the intended recipient. Instead is is possible that another user, having somehow obtained the transfer URL, accessed the transfer.
  • An upload to multiple recipients gets split into individual transfers per recipient. As a result, the sender will receive delivery or non-delivery reports for each individual recipient.

Configuration

  • Scope: configurable per transfer
  • Privileges: user-privileges required
  • Default: enabled

The delivery confirmation is requested when sending a transfer:

Image

Dependencies

none

Conflicts

none