|0||Virtual paths are not used, physical paths themselves are placed in URIs (e.g. <IMG SRC="C:\Inetpub\wwwroot\picture.gif">).|
|1||Virtual paths are used instead of physical paths (e.g. <IMG SRC="http://www.domain.com/picture.gif">). The message files must be stored in a location visible from the web.|
|2||The virtual path must point to a downloader script. MailBee.NET will also supply message_id and file_id parameters in URI. The downloader script can use them to locate the file to be downloaded to the client. The message files can be stored in a location which can be accessed by the downloader script but is not directly visible from the web (for better security). See GetHtmlAndSaveRelatedFiles(String, VirtualMappingType, MessageFolderBehavior) method documentation for more information.|
|3||Virtual path is ignored, all embedded objects are base64 encoded within the HTML. Nothing is saved into a temporary location, no temporary folder is created. GetHtmlWithBase64EncodedRelatedFiles method uses this mode.|
|4||The virtual path must be a prefix. To make the resulting virtual path, MailBee will append a suffix ("1", "2", etc) to each inline attachment referenced in the body. No files will actually be saved (although SavedAs property will be set to the resulting virtual path), the application needs to save files itself. Useful if you need to host these inline attachments on external storage (e.g. Amazon S3). GetHtmlAndRelatedFilesInMemory(String) method uses this mode.|
These modes specify how physical paths to embedded pictures (and other inline attachments related in HTML body and saved into temporary location by GetHtmlAndSaveRelatedFiles(String, VirtualMappingType, MessageFolderBehavior) method) are mapped into URIs placed into SRC elements of corresponding HTML tags.
|URI is a synonym of an URL.|