You can check headers. There you can find information does it uses SPF-record properly.

I would also setup PTR record for reverse lookup if you didn’t already.
To do it, login to Control Panel and change your Droplet name to your domain name (e.g. to example.com).
You can verify that it’s created under Networking -> PTR records.

After it’s setup successfully, you can try sending mail again. I’m not sure do you have to wait little before PTR records come in effect, but you will see yourself :)

Edit: Saw your comment, SPF-record looks OK, just verify you have PTR record (name your Droplet mydomain.co.uk)

thanks for the reply…
yep everything is properly setup and i can receive message in inbox only in aol.gmail spam outlook not receiving

and can i post my domain name and ip openly?

If everything is setup correctly, there could be trust issues.

It happens that mails sent from new IPs (IPs that never sent mails) have delivery issues. For some providers it will work absolutely normal, yet for some it will finish in spam or not delivered.

In case of Outlook.com, they’re know to absolutely block mails from new IP addresses.
For them, there is article on Outlook.com Postmaster.
Especially take at look at Are you sending email from new IPs?:

IPs not previously used to send email typically don't have any reputation built up in our systems. As a result, emails from new IPs are more likely to experience deliverability issues. Once the IP has built a reputation for not sending spam, Outlook.com will typically allow for a better email delivery experience.

Take a look at note too:

Note: don't forget to update your Junk Email Reporting Program (JMRP) account with the new IPs. To update or set up a JMRP account, click here.

For GMail spam issue, you need to wait until trust you. If users whitelist your email address, that process can be speed up.