I used amazon SES as a sender-dependent-transport. I apply this manually to domains as I need to verify each individually in AWS. I’m doing this to get around spam/block issues with Outlook/Microsoft mostly.
I also use simple-login but when I try to use their reverse-alias feature to reply to an email without revealing my real email address it will fail as follows:
An attempt to send an email from your alias firstname.lastname@example.org using email@example.com is blocked.
I cannot add
firstname.lastname@example.org to the simplelogin whitelist. Well, I can, but since it changes for every email, it is not suitable.
So right now every time I want to reply to one of these emails I have to manually disable the sender-dependent-transport on my domain, send the email, then re-enable it.
I was hoping to use a Transport Map to overcome this limitation. I want to be able to say emails going to “simplelogin.co” should not use AWS but rather postfix or whatever to send the mail. Is this possible?
Furthest I got was to se
[172.22.1.1] as the next hop but of course this doesn’t make sense and it errors with “mail for [172.22.1.1] loops back to myself”
Is it possible to achieve a reasonable integration with simplelogin?