Turn an email attachment into an AS2 transmission
Send an email to your DocEvent address and its attachment is signed, encrypted and delivered to your trading partner over AS2, with the MDN receipt tracked. The whole AS2 stack sits behind an email address.
From
Email
To
AS2
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Servers & protocols
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How Email to AS2 routing works
SourceEmail
Email attachments are captured automatically via inbound email (Amazon SES).
DocEvent Channel
routes · retries · logs
Destination
AS2
Files are delivered to an AS2 trading partner — signed, encrypted, and tracked until the MDN receipt comes back.
1
File arrives via Email
Inbound email processed via Amazon SES. Attachments extracted and routed through the channel.
2
Channel routes it
DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3
Delivered to AS2
Outbound AS2 (RFC 4130) delivery to your partner's AS2 URL. Messages are signed (SHA-256, SHA-384 or SHA-512) and encrypted (AES-256, AES-192, AES-128 or 3DES for legacy partners) using the partner's certificate, and can be compressed. Ask for a synchronous MDN, an asynchronous MDN, or none at all — signed receipts are verified and recorded, and a message whose receipt never arrives is parked for reprocessing instead of being quietly lost. Re-sends carry the same Message-ID, so a partner's duplicate detection suppresses them.
Common use cases
Real workflows that teams automate with a Email → AS2 channel.
- Let a department send EDI to a partner by emailing an attachment
- Bridge a manual, mailbox-driven process to a compliant AS2 channel
- Give a legacy system that can only email an AS2 outbound path
- Send documents to a trading partner without any integration work
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the Email or AS2 side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
Email
Inbound email processed via Amazon SES. Attachments extracted and routed through the channel.
Email attachments are captured automatically via inbound email (Amazon SES).Destination:
AS2
Outbound AS2 (RFC 4130) delivery to your partner's AS2 URL. Messages are signed (SHA-256, SHA-384 or SHA-512) and encrypted (AES-256, AES-192, AES-128 or 3DES for legacy partners) using the partner's certificate, and can be compressed. Ask for a synchronous MDN, an asynchronous MDN, or none at all — signed receipts are verified and recorded, and a message whose receipt never arrives is parked for reprocessing instead of being quietly lost. Re-sends carry the same Message-ID, so a partner's duplicate detection suppresses them.
Files are delivered to an AS2 trading partner — signed, encrypted, and tracked until the MDN receipt comes back.Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages