Yes I do, (SEND to INTELLIGENT BSV)
Call me old fashioned but I've always stuck with dedicated servers with full root access so I've no experience with Upcloud.
I suppose this just goes to show how little I know about the flow mechanism for mail in and out of AIM. We create mail, We press send, AIM sends it to the designated SMTP server. Does it then wait for a callback to say it's been received? - Dunno - but maybe that's where the delay comes in
The only other things I can come up with (and it happened to me a few years ago,) is a bad sender reputation. The previous user of the IP address I inherited when upgrading servers had a reputation as a spammer. I had to use MXTools to check which blacklists I was on and take the necessary steps to get removed. I even found that 1and1 themselves were blacklisted on one list and had to report it to them. So maybe Upcloud themselves are the problem.
Might be worth Dan spinning up an AWS instance for a few hours, install a demo AIM and load up his project and test. Looks like you've already done it with CRM but there's nothing like creating a like for like scenario for proving a point. If the identical bsv using identical mail services works on AWS but not on Upcloud then the issue has to be with Upcloud hasn't it? .
Hope this helps
