Apple Mail Desktop no SMTP via mobileconfig

[NicolaiSchmid]

Hello,
I've setup wildduck and added an account via the mobile config feature to both my iPhone and my Apple Mail for desktop. On the phone, everything works well, however, on the desktop there seems to be an issue with configuring the SMTP server. Fetching emails via IMAP works fine, but the mobileconfig (the same as for the phone) doesn't seem to register the SMTP server.
Looking inside the file, the server and its configuration are present, and of course it's too working on the phone.
I'm quite struggling with this issue because I don't know how to debug it.
The server works fine with other clients (Thunderbird, Outlook, iPhone Apple Mail)

Do you have any ideas where I should look, what logs I should monitor to narrow this issue down?

I appreciate any ideas you might have!

[andris9]

Can you add the same server settings manually? Does it work then?

[NicolaiSchmid]

Adding it manually (without ports, just the domains) leads to a very long load and an eventual error "Unable to verify account name or password".

Adding ports lets it verify immediately (successfully) only to not save the credentials and display the server as offline in the account settings.
When I add the username back in the settings, it verifies immediately, but returns the same credential error as above.

So, when only looking at Apple mail, with the mobile config, it adds it quickly and only IMAP works (on desktop), adding it manually doesn't work at all

[github-actions]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 15 days.

[NicolaiSchmid]

?

[NicolaiSchmid]

you'll see the Outgoing Mail Server is localhost and the port is 2587
For me, that's not the issue. It sets theOutgoingMailServerHostName correctly, but my described issue above still persists

[louis-lau]

@msimerson You haven't posted the mobileconfig configuration of wildduck that you say you've set correctly. No way for us to know if it is. Wildduck webmail wouldn't use the mobileconfig settings to display that page.

@NicolaiSchmid Sorry, but I don't think we can help from a distance. It sounds like an issue with your apple mail instance, not wildduck or zonemta. Look at the zonemta logs or debug the client instead of the server.

[louis-lau]

Wildduck webmail just uses the wildduck api, it's a seperate application and an example of what you can build on top of wildduck.

[NicolaiSchmid]

Sorry, but I don't think we can help from a distance. It sounds like an issue with your apple mail instance, not wildduck or zonemta. Look at the zonemta logs or debug the client instead of the server.

I can confirm the issue also persists on the webmail.wildduck.email instance (i just signed up and downloaded the configuration profile), not only on my Mac (and for the last two years, across software updates) but also on a friend's macbook

[msimerson]

Since my issue was not related this this thread and felt a little like issue hijacking, I've deleted my posts.

[louis-lau]

I can confirm the issue also persists on the webmail.wildduck.email instance

SMTP doesn't seem exposed on the demo instance. If you try to telnet wildduck.email 587 you'll see that you're not able to connect.

@andris9 The banner says "Messages from SMTP and webmail are queued but not delivered". Should this be updated, or should smtp submission be exposed?

This doesn't explain why something is not working on your instance, if you were to provide some more info that would be very helpful! Apple mail has a built-in connection doctor for example. Or perhaps provide the generated mobileconfig file with the app password redacted? Otherwise, screenshots of your manual settings? What about the mobileconfig toml configuration in wildduck?

The reason this has gone unanswered for so long is because it's not easily reproducible on a properly set up server, and there isn't enough information provided for us to be of any help. I do understand you asked for debugging steps, but it's hard for open source maintainers to play free support monkey if you understand what I mean :). Hopefully going over the things I mentioned above help you debug the issue.

[NicolaiSchmid]

Thanks for your reply!
I will post all of the above within the next week or two!
I appreciate your help! 🙏