# Possibility to transport emails via API

**URL:** <https://meta.discourse.org/t/possibility-to-transport-emails-via-api/75243>\
**Category:** Product Support\
**Created:** [December 2, 2017, 5:08pm UTC](https://meta.discourse.org/t/possibility-to-transport-emails-via-api/75243 "2017-12-02T17:08:21Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [December 2, 2017, 9:24pm UTC](https://meta.discourse.org/t/possibility-to-transport-emails-via-api/75243/3 "2017-12-02T21:24:07Z")

</div>

Mailgun support are talking out their rear end. They could just as easily strip this purported “originating IP” information from the headers when relaying via SMTP as via API, and nobody with two braincells to rub together trusts any information added by relaying systems, because (a) it’s all so trivial to forge, and (b) the WHOLE POINT of relaying through a service like mailgun is _because the originating system isn’t properly configured for SMTP_.

---

_[View the full topic](https://meta.discourse.org/t/possibility-to-transport-emails-via-api/75243)._