SMTP email cannot send (only receive)

[afterda3]

I'm using cloudflare and have pointed the DNS record of "mx" to :
xo4.x10hosting.com

Now I'm getting an exclamation mark on cloudflare where previously I wasn't.

I can receive emails to the created email accounts via x10hosting webmail horde, but sending via webmail or replying to test emails aren't working at all.

In the "Email Deliverability" app it says:
--------------------
“DKIM” is properly configured for this domain.
“SPF” is properly configured for this domain.
“PTR” is properly configured for this domain.

The system uses an alternate HELO of “xo4.x10hosting.com” when sending mail from the “mywhateverhostname.com” domain.

---------------------

What have I done wrong?

 

[spacresx]

i had a similar issue when i first tried "cloudbric" for my paid website.
(cloudbric was an alternative to cloudflare)
but the issue i had was similar to your issue, here is what worked for me,
it may or may not work for you.

change your ftp/email to your x10host default settings.
dont try changing it to cloudflares.
and only change the dns for your website mx entry (for http/https)

keep in mind your email isnt on, or setup through cloudflare.
you are only forwarding requests for your x10 site through cloudflare.
also remember changes to dns settings can take a few hours up to 3 or
4 days to complete. thats a normal when changing dns settings.
also remember it might or might not work for you.
im just saying what worked for me when i tried cloudbric.

 

[afterda3]

Thank you for your reply spaceresx, very much appreciated!

Here is the following information:
I have my own domain name: mydomainname.com
with the x10hosting hostname version : mydomainname.x10.bz

mydomainname.com is an alias of mydomainname.x10.bz

Nameservers point to cloudflare.

Using cloudflare I have activated http with SSL for mydomainname.com, this works fine.
I had tried to use mydomainname.x10.bz for SSL but I had problems that I couldn't fix so I just removed that.

ftp isn't in the DNS for the cloudflare DNS settings, it is on the x10hosting dns setup due to connecting via x10hosting domain.
ftp does work via ftp client via the
ftp.mydomainname.x10.bz

I haven't tried to setup:
ftp.mydomainname.com
as it already connects fine the x10 name for basic file transfers.

Please explain how to "change your ftp/email to your x10host default settings".
Is this a combination of using cloudflare DNS and/or x10hosting DNS settings?
I was understanding that wherever the nameservers point they have full DNS control, so that would be cloudflare?

What are the email default settings in the DNS setup?
If no mx is included in the DNS does it try and use mail.mydomainname.com or something?

This is where I'm a bit confused, the mx setting.

Under cloudflare DNS settings:
Type Name Content Priority TTL Proxy Status
MX mydomainname.com xo4.x10hosting.com 10 Auto DNS only

"Change the dns for your website mx entry (for http/https)" = ???

Please help!

 

[spacresx]

from what i understand the "free" x10hosting doesnt support https.
but using cloudflare you should be able to over ride that anyway.
(my cloudbric allowed me force http requests to https)

the email should work ok IF you did not make changes for the email.
i had difficulty at first on cloudbric as i didnt understand much of it.
and i was sending/receiving emails at cloudbric instead of my website.
(which was an issue of course, same as your issue)

i just created a new test email for Thunderbird email client.
everything works ok on my x10 account. sending and receiving are ok.
here is what i used:

test@website.x10.bz
your password for email.
ports:
pop = 995
smtp = 465

note: in some cases the user name is only whats is before the @
so with my test the user is just test not test@website.x10.bz
Thunderbird is funky that way but try your full name with the @ also
if it dont work just use your name in the settings.
some people can use mail.website.x10.bz also.
if it dont work use test@website.x10.bz

but change the @website.x10.bz to @your website link

i can confirm it works for me, i can send and receive just fine.

and just leave your cloudflare settings as is if that part works ok.

 

[afterda3]

Thanks for replying!

x10hosting includes the cloudflare in the cpanel.
SSL is supported for free accounts.
I can see both web addresses in cloudflare app.

Logging into cloudflare.com shows me the same info as it should in x10hosting.

It's not desirable to use the x10hosting web address for email.

Regardless for testing purposes I made a test@mydomainname.x10.bz email account.

The webmail produces same results, can receive but not send.
Even though it says sent successfully, its gone into the void.

Using Thunderbird it tries to configure auto with the following:

IMAP mail.mydomainname.x10.bz 143 STARTTLS normal pw
SMTP mail.mydomainname.x10.bz 587 STARTTLS normal pw
username : test

Now clicking "Get Certificate" :

Clicking cancel produces this popup in the corner:

Now this points to an issue with the auth method.

 

[spacresx]

sorry i thought it would be easy for you to set up the email.
i showed you what worked for me without a problem.
and i can tell you didnt understand what i wrote.

for openers, i pointed out its pop settings not imap.
and given the fact you didnt notice that, im assuming you may also
be using the wrong address, unless your website also ends in x10.bz
and as you never gave the link to your site i couldnt formulate it.
thats why i said before you may need to change it.

the settings example was only based for pop mail not imap
which works differently, and i dont use imap for any emails.

you can try whatever email you want to,
but i cant help if your using imap as i use pop email

 

[afterda3]

I was referring to the above instructions from x10hosting.
I require IMAP as POP3 is not adequate as there will be multi devices connected to the email account.

I still cant get the email system to work, either in webmail or client. Only receive is working, never send.

I have done a combination of usernames with and without the @ address and prefix. Along with the various security auth options.

Something is blatently missing here.....!