[{"data":1,"prerenderedAt":12},["ShallowReactive",2],{"$fw3iAKqzTh7C1yo0AhcOW0_QnsVZ9HSe5hE1pI5bvPG4":3},{"title":4,"slug":5,"excerpt":6,"category":7,"order":8,"screens":9,"html":11},"Understanding alias options","alias-options-explained","Learn about attachment processing and envelope data options for email aliases","configuration",4,[10],"aliases","\u003Cp>When creating or editing an alias in EmailConnect, you&#39;ll find two important options that control how email data is processed and delivered to your webhooks.\u003C\u002Fp>\n\u003Ch2>Process attachments\u003C\u002Fh2>\n\u003Cp>This option determines how EmailConnect handles file attachments in incoming emails.\u003C\u002Fp>\n\u003Ch3>Option 1: Inline (default)\u003C\u002Fh3>\n\u003Cp>When set to &quot;Inline&quot;, attachments are:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Converted to Base64 encoding\u003C\u002Fli>\n\u003Cli>Included directly in the webhook JSON payload\u003C\u002Fli>\n\u003Cli>Immediately available for processing\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Example payload with inline attachment:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-json\">{\n  &quot;subject&quot;: &quot;Invoice for March&quot;,\n  &quot;attachments&quot;: [\n    {\n      &quot;filename&quot;: &quot;invoice-march.pdf&quot;,\n      &quot;contentType&quot;: &quot;application\u002Fpdf&quot;,\n      &quot;size&quot;: 125840,\n      &quot;content&quot;: &quot;JVBERi0xLjQKJeHp69MKMSAwIG9iago8PC9Ue...&quot; \u002F\u002F Base64 encoded content\n    }\n  ]\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Best for:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Small to medium attachments (under 10MB)\u003C\u002Fli>\n\u003Cli>When you need immediate access to file contents\u003C\u002Fli>\n\u003Cli>Simple architectures without external storage\u003C\u002Fli>\n\u003Cli>Quick prototypes and MVPs\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Option 2: Managed S3 storage\u003C\u002Fh3>\n\u003Cp>When set to &quot;Managed S3 storage&quot;, attachments are:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Uploaded to Amazon S3 (or compatible storage)\u003C\u002Fli>\n\u003Cli>Webhook receives URLs instead of file contents\u003C\u002Fli>\n\u003Cli>Files accessible via secure, time-limited URLs\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Example payload with Managed S3 storage:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-json\">{\n  &quot;subject&quot;: &quot;Invoice for March&quot;,\n  &quot;attachments&quot;: [\n    {\n      &quot;filename&quot;: &quot;invoice-march.pdf&quot;,\n      &quot;contentType&quot;: &quot;application\u002Fpdf&quot;,\n      &quot;size&quot;: 125840,\n      &quot;url&quot;: &quot;https:\u002F\u002Fstatic.emailconnect.eu\u002Fattachments\u002Fuuid...&quot;\n    }\n  ]\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Best for:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Large attachments (over 10MB)\u003C\u002Fli>\n\u003Cli>High-volume email processing\u003C\u002Fli>\n\u003Cli>When webhooks have size limits\u003C\u002Fli>\n\u003Cli>Long-term file storage needs\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Option 3: Custom S3 storage\u003C\u002Fh3>\n\u003Cp>Configure your own S3-compatible bucket for attachment storage:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Full control over file retention\u003C\u002Fli>\n\u003Cli>Keep files in your own infrastructure\u003C\u002Fli>\n\u003Cli>Custom access policies\u003C\u002Fli>\n\u003Cli>Cost optimization for high volumes\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Configuration required:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Bucket name and region\u003C\u002Fli>\n\u003Cli>Access key and secret key\u003C\u002Fli>\n\u003Cli>Optional: custom endpoint for S3-compatible services (MinIO, Backblaze B2, etc.)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Email content format\u003C\u002Fh2>\n\u003Cp>This option controls which email body formats are included in your webhook payload.\u003C\u002Fp>\n\u003Ch3>Option 1: Both HTML and text (default)\u003C\u002Fh3>\n\u003Cp>When set to &quot;Both&quot;, your webhook receives:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>html\u003C\u002Fcode>: The HTML version of the email body\u003C\u002Fli>\n\u003Cli>\u003Ccode>text\u003C\u002Fcode>: The plain text version of the email body\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Example payload:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-json\">{\n  &quot;subject&quot;: &quot;Welcome to our service&quot;,\n  &quot;html&quot;: &quot;&lt;h1&gt;Welcome!&lt;\u002Fh1&gt;&lt;p&gt;Thanks for signing up.&lt;\u002Fp&gt;&quot;,\n  &quot;text&quot;: &quot;Welcome!\\n\\nThanks for signing up.&quot;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Best for:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Applications that need to display emails in different contexts\u003C\u002Fli>\n\u003Cli>When you want fallback options for rendering\u003C\u002Fli>\n\u003Cli>Maximum flexibility in processing\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Option 2: HTML only\u003C\u002Fh3>\n\u003Cp>When set to &quot;HTML only&quot;, your webhook receives only the \u003Ccode>html\u003C\u002Fcode> field.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Best for:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Applications that only render HTML content\u003C\u002Fli>\n\u003Cli>When you want to reduce payload size\u003C\u002Fli>\n\u003Cli>Web-based email viewers\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Option 3: Text only\u003C\u002Fh3>\n\u003Cp>When set to &quot;Text only&quot;, your webhook receives only the \u003Ccode>text\u003C\u002Fcode> field.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Best for:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Text processing and analysis\u003C\u002Fli>\n\u003Cli>Logging and archival systems\u003C\u002Fli>\n\u003Cli>When HTML formatting isn&#39;t needed\u003C\u002Fli>\n\u003Cli>Simpler parsing requirements\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Include envelope data\u003C\u002Fh2>\n\u003Cp>This option adds technical email routing information to your webhook payload.\u003C\u002Fp>\n\u003Ch3>What is envelope data?\u003C\u002Fh3>\n\u003Cp>Envelope data includes:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>MAIL FROM\u003C\u002Fstrong>: The actual sender address (may differ from &quot;From&quot; header)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>RCPT TO\u003C\u002Fstrong>: The actual recipient address (may differ from &quot;To&quot; header)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SMTP transaction details\u003C\u002Fstrong>: Routing and delivery information\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>When enabled\u003C\u002Fh3>\n\u003Cp>Your webhook receives additional fields:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-json\">{\n  &quot;subject&quot;: &quot;Order confirmation&quot;,\n  &quot;from&quot;: &quot;orders@shop.com&quot;,\n  &quot;to&quot;: &quot;customer@example.com&quot;,\n  &quot;envelope&quot;: {\n    &quot;mailFrom&quot;: &quot;bounces@shop.com&quot;,\n    &quot;rcptTo&quot;: [&quot;automation@in.myapp.com&quot;],\n    &quot;remoteAddress&quot;: &quot;192.168.1.50&quot;,\n    &quot;clientHostname&quot;: &quot;mail.shop.com&quot;\n  }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Why envelope data matters\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Email forwarding detection:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>See the original recipient when emails are forwarded\u003C\u002Fli>\n\u003Cli>Track the actual delivery path\u003C\u002Fli>\n\u003Cli>Identify automated forwards\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Bounce handling:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The MAIL FROM address receives bounce notifications\u003C\u002Fli>\n\u003Cli>Different from the visible &quot;From&quot; address\u003C\u002Fli>\n\u003Cli>Critical for email deliverability tracking\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Security and validation:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Verify the sending server\u003C\u002Fli>\n\u003Cli>Detect spoofed emails\u003C\u002Fli>\n\u003Cli>Implement SPF\u002FDKIM validation\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>When to enable envelope data\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Enable for:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Email analytics applications\u003C\u002Fli>\n\u003Cli>Bounce processing systems\u003C\u002Fli>\n\u003Cli>Security-focused applications\u003C\u002Fli>\n\u003Cli>When debugging delivery issues\u003C\u002Fli>\n\u003Cli>Multi-tenant applications needing routing info\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Skip for:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Simple email-to-webhook conversions\u003C\u002Fli>\n\u003Cli>When you only need message content\u003C\u002Fli>\n\u003Cli>Applications that don&#39;t process technical headers\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Common configurations\u003C\u002Fh2>\n\u003Ch3>Support ticket system\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Process attachments\u003C\u002Fstrong>: Inline (customers attach screenshots)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Include envelope\u003C\u002Fstrong>: No (not needed for tickets)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Document processing system\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Process attachments\u003C\u002Fstrong>: Managed S3 storage (large PDFs)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Include envelope\u003C\u002Fstrong>: No (focus on content)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Email analytics platform\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Process attachments\u003C\u002Fstrong>: Managed S3 storage (preserve originals)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Include envelope\u003C\u002Fstrong>: Yes (track routing)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Simple notification system\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Process attachments\u003C\u002Fstrong>: Inline (if any)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Include envelope\u003C\u002Fstrong>: No (keep it simple)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Performance considerations\u003C\u002Fh2>\n\u003Ch3>Inline attachments\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Increases webhook payload size\u003C\u002Fli>\n\u003Cli>May hit size limits on receiving endpoints\u003C\u002Fli>\n\u003Cli>Faster for small files\u003C\u002Fli>\n\u003Cli>No additional API calls needed\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Managed S3 storage\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Keeps webhook payloads small\u003C\u002Fli>\n\u003Cli>Requires additional HTTP requests to fetch files\u003C\u002Fli>\n\u003Cli>Better for large files\u003C\u002Fli>\n\u003Cli>Adds slight processing delay\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Envelope data\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Minimal impact on payload size\u003C\u002Fli>\n\u003Cli>No performance impact\u003C\u002Fli>\n\u003Cli>Useful debugging information\u003C\u002Fli>\n\u003Cli>Can be ignored if not needed\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Choose the configuration that best matches your use case and architectural requirements.\u003C\u002Fp>\n",1781207681465]