An Embedded POP email Client
Allegro’s RomPOP product enables your engineering team to leverage the capabilities of receiving email on your embedded device. With the addition of SMTP and POP functionality, device manufacturers are finding creative approaches to offer specific value “add-on” services, expanding the definitions for maintenance and support, developing novel methods for secure network configuration and provisioning of equipment using standards based email.
RomPOP Basic
RomPOP Basic is a Post Office Protocol version 3 (POPv3) client for embedded devices to receive text and HTML based Internet email from any Internet POP3 mail server. Messages are processed and stored in RAM.
RomPOP Standard
RomPOP Standard adds support for attachments encoded using MIME and UUENCODED formats and support for an optional file system.
RomPOP Advanced
With RomPOP Advanced an embedded device adds Delivery Status Notification and Message Delivery Notification support.
Features |
Benefits |
|---|---|
|
Small code footprint |
More resources available for application features |
|
ANSI C Source Code Distribution |
Broad processor architecture support, eases porting and support |
|
Processor, RTOS and TCP/IP stack agnostic |
Allegro’s products will work with new or existing hardware and software designs |
|
Interface files for leading RTOS vendors provided |
Minimizes porting effort, increase time to market |
|
Shipping in millions of products worldwide |
Field proven reliability |
|
GPL Free |
No licensing or development issues related with GPL |
|
Choice of development toolkits |
Flexibility to meet your design and development needs |
|
Embedded POPv3 Client |
Ability to enable your embedded design to receive text and html based emails |
|
Support for MIME and UUENCODED attachments |
Ability to receive and interpret emails with attachments |
|
Message Disposition Notifications |
Alert sender that email has been delivered and acted upon by your embedded system |
|
Delivery Status Notification |
Easily determine if a previous message sent from your embedded system had an error |
Supported RFCs
- RFC 822 – Standard for the format of ARPA Internet text messages
- RFC 1892 – The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages
- RFC 1939 – Post Office Protocol – Version 3
- RFC 2045 – Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
- RFC 2046 – Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
- RFC 2047 – MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
- RFC 2048 – Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
- RFC 2298 – An Extensible Message Format for Message Disposition Notifications
- RFC 3464 – An Extensible Message Format for Delivery Status Notifications
System Requirements
- Processor Architecture – Agnostic to any 16-bit, 32-bit or 64-bit processor
- Operating System(OS) – Agnostic to OS vendor and will function without an OS if needed
- TCP/IP Stack – Agnostic
- Filesystem – Agnostic to vendor implementation and will function without a filesystem if needed
- Compiler – ANSI C
RomPlug Options
| Basic | Standard | Advanced | |
| Full source code |
|
|
|
| ANSI-C |
|
|
|
| Small RAM/ROM Footprint |
|
|
|
| Hardware and software abstraction layer |
|
|
|
| Ability to run without RTOS |
|
|
|
| Sample RTOS integration files |
|
|
|
| Full electronic documentation |
|
|
|
| GPL Free |
|
|
|
| Text Messages |
|
|
|
| HTML Messages |
|
|
|
| Binary Messages |
|
|
|
| Simple API |
|
|
|
| Advanced API |
|
|
|
| Receive Attachments |
|
|
|
| Memory Based Message |
|
|
|
| File Based Message |
|
|
|
| Message Preview |
|
|
|
| Advanced Header Management |
|
|
|
| Advanced Message Management |
|
|
|
| Message Delivery Notification |
|
||
| Message Status Notification |
|
