Aspose.Email系列產(chǎn)品

Aspose.Email for .NET

目標Windows窗體，ASP.NET，WPF，WCF或基于.NET Framework 2.0或更高版本的任何類型的應用程序

Aspose.Email for Java

用于基于Java SE或EE的桌面，Web或任何類型的應用程序的Native Java API

Aspose.Email for C++

在C ++應用程序中創(chuàng)建，操作或轉(zhuǎn)換電子郵件消息。

Aspose.Email for Android via Java

在移動應用程序中處理Outlook電子郵件,適用于Android OS 2.3或更高版本

Aspose.Email for SharePoint

在SharePoint 2010中轉(zhuǎn)換電子郵件并將文件同步到FTP或Dropbox

支持的格式

主要特點

一個完整的電子郵件處理解決方案 

Aspose.Email。NET用短短的兩行代碼便可快速通過SMTP服務(wù)器輕松發(fā)送電子郵件，并且可在在郵件中添加附件，包括文本和/或HTML郵件正文；郵件合并從模板中創(chuàng)建的郵件；發(fā)送大量的電子郵件以及創(chuàng)建自定義郵件標題。Aspose.Email for .NET也允許您使用用戶名和密碼或者APOP認證登錄到POP3服務(wù)器，以便查看郵箱大小和郵件計數(shù)，獲取完整的信息或郵件標題，刪除來自服務(wù)器的郵件以及基本的POP3命令。Aspose.Email for .NET支持IMAP協(xié)議，其中包括認證，創(chuàng)建，刪除，選擇，查詢文件夾，獲取，刪除和保存郵件，更改信息和基本的IMAP命令。對于SMTP，POP3和IMAP，SSL也同樣支持。

所支持的信息文件格式

Aspose.Email for .NET同樣支持讀取EML, MSG 或者 MHT格式的電子郵件，并且能夠提取電子郵件的標題和段落，檢索附件和嵌入的對象。它還支持文件更改，例如添加或刪除附件，主題，正文內(nèi)容，然后將其保存為EML、MSG或MHT格式的郵件。它也可以讀取Outlook PST文件格式，并從PST文件中提取信息以及聯(lián)系人資料信息以MSG格式存儲到磁盤中。

支持Microsoft Exchange服務(wù)器

Aspose.Email for .NET支持訪問來自Microsoft Exchange服務(wù)器的郵件。你可以從收件箱，草稿箱，下載消息文件夾中查詢消息，并把它們保存為EML, MDG 或者 MHT格式。使用Exchange Server，也可以發(fā)送電子郵件和會議邀請。 WebDAV和Exchange Web服務(wù)（Exchange Server 2007或更高版本）可用于連接到Exchange服務(wù)器。

完整的循環(huán)模式解決方案

使用Aspose.Email for .NET您可以輕松、可靠地計算發(fā)生的日期和時間，即使是最復雜的循環(huán)模式。Aspose.Email for .NET能讓你使用每年，每月，每周，每天，每小時，每分鐘和每秒循環(huán)模式，并且代表了你的Windows，Web或移動設(shè)備應用程序中的循環(huán)模式。

Key Features

A Complete Email Processing Solution

Aspose.Emailallows you to quickly send emails using just two lines of code. With Aspose.Emailyou can easily create and send emails through SMTP Servers, attach embedded objects and add attachments to emails, include text and/or HTML mail body, mail merge for creating emails from a template, send bulk emails, and send iCalendar compliant appointments or meetings as well as create customized mail headers. Aspose.Emailalso allows you to log into POP3 servers by user and password or APOP authentication, view mailbox size and messages count, retrieve the full message or its header, delete messages from server as well as basic POP3 commands. Aspose.Emailhas support for the IMAP protocol including authentication, create, delete, select, query folders, get, delete and save messages, change message flags and basic IMAP commands. For SMTP, POP3 and IMAP, SSL is also supported. 。

Message File Format Support

Aspose.Emailalso allows you to read email message from file or stream in EML, MSG or MHT format, extract email headers and bodies, retrieve attachments and embedded objects. It also supports making changes to files, for example the addition or removal of attachments, change to, from, subject, body elements and then save emails as EML, Microsoft Outlook Message file (MSG) or MHT format. 　　It can also read the popular Outlook PST file format, read folders and message information and extract messages from the PST file to disk or stream in MSG format. 　　Contacts information can also be read from the Outlook PST file and each contact can be saved to disk in MSG format。

Microsoft Exchange Server Support

Aspose.Emailsupports accessing emails from Microsoft Exchange Servers. You can list messages from a folder, for example inbox, drafts, download messages and save them as EML, MDG or MHT format. Emails and meeting invitations can also be sent using the Exchange Server. Both WebDav and Exchange Web Services (for Exchange Server 2007 or later) can be used to connect to the Exchange Server.

Complete Recurrence Pattern Solution

With Aspose.Emailyou can easily and reliably calculate occurrence dates and times for even the most complex recurrence patterns, consume and produce recurrence patterns in the iCalendar (RFC 2445) format and create recurrence patterns programmatically via an intuitive object model. Aspose.Emailfurther allows you to use yearly, monthly, weekly, daily, hourly, minutely and secondly recurrence patterns, and represent recurrence patterns in your windows, web or mobile applications. The recurrence patterns implemented by Aspose.Emailare coherent with schedule related elements of the iCalendar RFC (2445)