# Status of AEAP and possible workarounds

**URL:** <https://forum.delta.chat/t/status-of-aeap-and-possible-workarounds/3762>\
**Category:** Mutual Help\
**Created:** [May 4, 2025, 7:38pm UTC](https://forum.delta.chat/t/status-of-aeap-and-possible-workarounds/3762 "2025-05-04T19:38:13Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![gardenerik](https://forum.delta.chat/user_avatar/forum.delta.chat/gardenerik/32/2580_2.png) [@gardenerik](https://forum.delta.chat/u/gardenerik)\
**Post date:** [May 4, 2025, 7:38pm UTC](https://forum.delta.chat/t/status-of-aeap-and-possible-workarounds/3762/1 "2025-05-04T19:38:13Z")

</div>

Hello,

I noticed that AEAP was disabled some time ago, presumably temporarily, as seen [here](https://github.com/chatmail/core/commit/4a2bfe03dab3c8a7f3297cb47719d0f3392c7201).

I was wondering if there are any plans for it to return in the near future. If not, is there a recommended workaround? For example, would it be possible to import existing messages into a new account, or something like that?

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![link2xt](https://forum.delta.chat/user_avatar/forum.delta.chat/link2xt/32/1971_2.png) [@link2xt](https://forum.delta.chat/u/link2xt)\
**Post date:** [May 4, 2025, 8:17pm UTC](https://forum.delta.chat/t/status-of-aeap-and-possible-workarounds/3762/2 "2025-05-04T20:17:31Z")

</div>

It is going to be reimplemented. Change [WIP: PGP contacts by link2xt · Pull Request #6796 · chatmail/core · GitHub](https://github.com/chatmail/core/pull/6796) makes it possible to port 1:1 chats (which is not possible with existing AEAP implementation) and then there is a plan to allow doing AEAP by configuring an additional provider instead of reconfiguring the current one.

---

<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:** [May 5, 2025, 10:33pm UTC](https://forum.delta.chat/t/status-of-aeap-and-possible-workarounds/3762/3 "2025-05-05T22:33:35Z")

</div>

Great to hear you are working to improve this feature.

> [@link2xt](#):
>
> Change [WIP: PGP contacts by link2xt · Pull Request #6796 · chatmail/core · GitHub](https://github.com/chatmail/core/pull/6796) makes it possible to port 1:1 chats (which is not possible with existing AEAP implementation)

I didn’t read about this limitation before. So the existing implementation won’t let you use AEAP if there is only one identity assigned to your email address? That seems like the majority of cases! Maybe I misunderstood what you meant here.

> [@link2xt](#):
>
> then there is a plan to allow doing AEAP by configuring an additional provider instead of reconfiguring the current one

Would this eventually lead to the possibility of cloning an account and keeping the old address active parallel to the newer one, to catch any messages still sent to the old address, as I described [here](https://support.delta.chat/t/introducing-automatic-e-mail-address-porting-aeap/2236/3)? Or could this even be laying groundwork for multihoming in future?

---

<div class="post-metadata">

**Author:** ![gardenerik](https://forum.delta.chat/user_avatar/forum.delta.chat/gardenerik/32/2580_2.png) [@gardenerik](https://forum.delta.chat/u/gardenerik)\
**Post date:** [May 6, 2025, 5:00pm UTC](https://forum.delta.chat/t/status-of-aeap-and-possible-workarounds/3762/4 "2025-05-06T17:00:56Z")

</div>

> [@bencan](#):
>
> I didn’t read about this limitation before. So the existing implementation won’t let you use AEAP if there is only one identity assigned to your email address? That seems like the majority of cases! Maybe I misunderstood what you meant here.

I think @link2xt under “porting 1:1 chats” means that chats between two people will be properly handled after AEAP. I think the current implementation creates another chat in the app for your contacts, so they have “you before AEAP” and “you after AEAP” as separate chat histories.

---

<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:** [May 6, 2025, 10:09pm UTC](https://forum.delta.chat/t/status-of-aeap-and-possible-workarounds/3762/5 "2025-05-06T22:09:42Z")

</div>

I see, that makes sense. I got confused where the github PR mentions “1:1 chat assignment … multiple PGP-contacts with the same email address”.

I would not have guessed that this limitation with 1:1 chats existed just from reading the available posts about AEAP. At least I didn’t see it mentioned anywhere. I always imagine that the 1:1 chats are more simple to implement than the group chats, so my assumption was that if it was already working seamlessly for the group chats, it is also working seamlessly for the 1:1 chats!

---

<div class="post-metadata">

**Author:** ![Seth](https://forum.delta.chat/letter_avatar_proxy/v4/letter/s/f14d63/32.png) [@Seth](https://forum.delta.chat/u/Seth)\
**Post date:** [August 9, 2025, 3:20pm UTC](https://forum.delta.chat/t/status-of-aeap-and-possible-workarounds/3762/6 "2025-08-09T15:20:48Z")

</div>

Is AEAP still disabled? Have some friends on the same email provider that went down and need to migrate them to a chatmail server.

---

<div class="post-metadata">

**Author:** ![cr0nbeirut](https://forum.delta.chat/letter_avatar_proxy/v4/letter/c/b77776/32.png) [@cr0nbeirut](https://forum.delta.chat/u/cr0nbeirut)\
**Post date:** [October 4, 2025, 12:58am UTC](https://forum.delta.chat/t/status-of-aeap-and-possible-workarounds/3762/7 "2025-10-04T00:58:39Z")

</div>

Yes, I’m curious if there is any place to track the status of this change and when it may be possible to change providers without deleting & creating a new account.

It also would be good to know if will be possible to completely remove any reference to the old email address when changing servers with the new implementation, I understand from reading thru other threads that in the old implementation, the original address was still visible somewhere (I guess because it was part of the PGP identity) after the user changed servers.

---

<div class="post-metadata">

**Author:** ![ueen](https://forum.delta.chat/user_avatar/forum.delta.chat/ueen/32/3324_2.png) [@ueen](https://forum.delta.chat/u/ueen)\
**Post date:** [April 2, 2026, 4:30pm UTC](https://forum.delta.chat/t/status-of-aeap-and-possible-workarounds/3762/8 "2026-04-02T16:30:44Z")

</div>

Any updates yet? (:

---

<div class="post-metadata">

**Author:** ![link2xt](https://forum.delta.chat/user_avatar/forum.delta.chat/link2xt/32/1971_2.png) [@link2xt](https://forum.delta.chat/u/link2xt)\
**Post date:** [April 2, 2026, 5:28pm UTC](https://forum.delta.chat/t/status-of-aeap-and-possible-workarounds/3762/9 "2026-04-02T17:28:20Z")

</div>

AEAP is replaced with multi-relay. You can now add another relay and switch to it: [How to migrate your profile to another relay (version 2.33)](https://support.delta.chat/t/how-to-migrate-your-profile-to-another-relay-version-2-33/4441)

With 2.48+ releases you can hide old relay afterwards so you continue receiving messages there from contacts that don’t know yet that you have moved your profile.

---

<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:41pm UTC](https://forum.delta.chat/t/status-of-aeap-and-possible-workarounds/3762/10 "2026-10-06T15:41:20Z")

</div>


