Existing services may be SOAP, POX/REST services over HTTP/S, as well as SOAP or legacy services over JMS, Apache VFS file systems (e.g. s/ftp, file, zip/tar/gz, webdav, cifs etc.), Mail systems (e.g. pop3, imap, smtp), Financial Information eXchange (FIX), Hessian, AMQP etc.
GSi uses SMTP as mail transport protocol, and the conversion from the then prevalent X.400 email facilities to SMTP proved for many departments an improvement in reliability and speed.
Since the SMTP and NNTP protocols (used to deliver e-mail and Usenet, respectively) were formerly only able to transmit 7-bits, it was then the convention to use ISO-2022-JP for sending e-mail in Japanese.
Examples of application layer protocols include the File Transfer Protocol (FTP), the Simple Mail Transfer Protocol (SMTP), and Dynamic Host Configuration Protocol (DHCP).
Any of the well known Internet protocols may be found in an intranet, such as HTTP (web services), SMTP (e-mail), and FTP (file transfer protocol).
MHS was a very 'open' system, and this, with Novell's encouragement, made it popular in the early 1990s as a 'glue' between not only the proprietary email systems of the day such as PROFS, SNADS, MCI, 3+Mail, cc:Mail, Para-Mail and Microsoft Mail, but also the competing standards-based SMTP and X.400.
System services demand (including SSH, FTP, ProFTPD, Vsftpd, Pure-FTPd, Telnet, Samba, Fax, CUPS, Fail2ban, IMAP, POP3, SMTP, VirusMail and Spam, and supporting log files from xinetd, Sendmail, Postfix, Dovecot, UW-IMAP, Qpopper, HylaFAX, MailScanner and CommuniGate).
In order to transport these files, Niklas supports FTP/SFTP, HTTP/HTTPS, POP3, SMTP, IMAP, SOAP, MQ and JMS.
PHPMailer sends an SMTP extension command with the sent emails as below which can be used to get the usage report of PHPMailer on the ESPs(Email Service Providers):
Because SMTP Proxies can be implemented using lighter-weight programming techniques such as asynchronous IO (for example nginx, Node.js, Netty and Libevent), thousands of connections can be juggled using the same resources as a much smaller number of connections in the context of a full-blown store and forward email server.
It relies on XML Information Set for its message format, and usually relies on other Application Layer protocols, most notably Hypertext Transfer Protocol (HTTP) or Simple Mail Transfer Protocol (SMTP), for message negotiation and transmission.
For xCBL message transport, Commerce One created an envelope messaging standard called MML (Marketsite Messaging Layer) based on the SMTP MIME format to provide both payload (xCBL) and attachment support.