# Introducing Automatic e-mail Address Porting (AEAP)

**URL:** <https://forum.delta.chat/t/introducing-automatic-e-mail-address-porting-aeap/2236>\
**Category:** Uncategorized\
**Created:** [September 21, 2022, 8:47am UTC](https://forum.delta.chat/t/introducing-automatic-e-mail-address-porting-aeap/2236 "2022-09-21T08:47:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hpk](https://forum.delta.chat/user_avatar/forum.delta.chat/hpk/32/9_2.png) [@hpk](https://forum.delta.chat/u/hpk)\
**Post date:** [September 21, 2022, 8:47am UTC](https://forum.delta.chat/t/introducing-automatic-e-mail-address-porting-aeap/2236/1 "2022-09-21T08:47:17Z")

</div>

Over on Mastodon and Twitter we published about [our introduction of e-mail account porting to a new provider](https://delta.chat/en/2022-09-14-aeap). If you have any questions or remarks, leave them here 🙂

---

<div class="post-metadata">

**Author:** ![Raiden](https://forum.delta.chat/user_avatar/forum.delta.chat/raiden/32/2544_2.png) [@Raiden](https://forum.delta.chat/u/Raiden)\
**Post date:** [September 21, 2022, 12:10pm UTC](https://forum.delta.chat/t/introducing-automatic-e-mail-address-porting-aeap/2236/2 "2022-09-21T12:10:01Z")

</div>

DC just keeps getting better! 👍

---

<div class="post-metadata">

**Author:** ![bencan](https://forum.delta.chat/letter_avatar_proxy/v4/letter/b/eb9ed0/32.png) [@bencan](https://forum.delta.chat/u/bencan)\
**Post date:** [March 21, 2025, 11:08pm UTC](https://forum.delta.chat/t/introducing-automatic-e-mail-address-porting-aeap/2236/3 "2025-03-21T23:08:31Z")

</div>

This sounds like a great, underrated feature. I would like to try it out in the future and tell others about this feature, but I hesitate to use it knowing that it takes time for all contacts to be notified of the address change, and there is the risk that some messages will be missed, especially if you haven’t set up email forwarding.

I’m not aware that chatmail even supports email forwarding at all, which means that porting a chatmail address creates a big risk of missing some messages.

I would feel more comofrtable using this feature if I know Delta Chat continues to check for messages sent to the old address until either all contacts have acknowledged the change of address or I manually choose to delete the old address.

Since Delta Chat has great multi-account support, maybe Delta Chat could automatically clone the account whenever AEAP is used and give the account with the old address a profile description such as “ex-account” (or add some other way to visually distinguish it, such as formatting the account name with strikethrough)? This seems like a natural and intuitive way to guarantee that no message will be missed when porting an address.

> [@Multiple Instances of the same account: AEAP & Testing vs easy updating of credentials with DCLOGIN](https://support.delta.chat/t/multiple-instances-of-the-same-account-aeap-testing-vs-easy-updating-of-credentials-with-dclogin/2890):
>
> We currently allow multiple instances/account with the same email address. This is both useful for testing and for testing an AEAP setup. We also already had some ideas regarding cloning accounts. BTW: Not sure if this use case of testing AEAP will still work with improved multi device synchronisation. Against this stands the idea of using a DCLOGIN qr code to replace the current password and other settings for an address. Sure we can say it does that when scanned from the account configure …

---

<div class="post-metadata">

**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\
**Post date:** [October 6, 2026, 3:19pm UTC](https://forum.delta.chat/t/introducing-automatic-e-mail-address-porting-aeap/2236/4 "2026-10-06T15:19:59Z")

</div>


