Welcome Guest. Please Login or Register  
Client Area  |  Softaculous Cloud  |  Calendar  |  Quick Links  |  
   


You are here: Index > Webuzo > General Support > Topic : SMTP dont work

Page 1 of 212>>>All


Threaded Mode | Print  

 SMTP dont work, Outlook setup (15 Replies, Read 28251 times)
bradatigad
Posted on # September 16, 2015, 7:40 pm
Group: Member
Post Group: Newbie
Posts: 2
Status:
Hallo,

i have the problem with the setup of my mail in outlook, thunderbird, osx client try to.
i have use the suggestion on the forum try with the subdomain try with the host on smtp i donty have any idea more :S

the webmail works fine :/

thx a lot
IP: --   

SMTP dont work
nikhil89
Posted on # September 18, 2015, 7:54 am | Post: 1
Group: Softaculous Team
Post Group: Elite Member
Posts: 467
Status:
Hi,

Can you please let us know the exact error you are facing? Also can you please let us know which Operating System you are using and steps followed, so that we can try to replicate the same on our test servers.
IP: --   

SMTP dont work
bradatigad
Posted on # September 18, 2015, 5:36 pm | Post: 2
Group: Member
Post Group: Newbie
Posts: 2
Status:
hello,

sure i can !

i have ubuntu on my server have delete exim and dovecot and try again ...

http://www.softaculous.com/board/index.php?tid=4595&title=Exim_not_working!!#p16113

i have follow this the webmail are ok but the 3rd party client are not and i need to finish it for my client in two days !

i am in a trouble ...
IP: --   

SMTP dont work
nikhil89
Posted on # September 19, 2015, 9:44 am | Post: 3
Group: Softaculous Team
Post Group: Elite Member
Posts: 467
Status:
Hi,

We have checked this issue and it seems that this issue was only for Ubuntu OS.

Our developers have resolved this issue and we shall release the patch soon.

For now I have emailed you the patch along with the instructions.

Please let us know if you still face the issue.
IP: --   

SMTP dont work
CosmicDebri
Posted on # November 15, 2015, 6:47 am | Post: 4
Group: Member
Post Group: Newbie
Posts: 21
Status:
I am running ubuntu 14.04 and I can receive mail with my thunderbird client, but when I try to send I get an error saying relay not allowed. Will the patch you mentioned fix this, and if so can I get it sent to me??
IP: --   

SMTP dont work
nikhil89
Posted on # November 17, 2015, 6:34 am | Post: 5
Group: Softaculous Team
Post Group: Elite Member
Posts: 467
Status:
Hi,

The patch should resolve your issue. Our developer has sent you an email of the patch and procedure to apply patch.

Please check the same and let us know if you still face the issue.
IP: --   

SMTP dont work
CosmicDebri
Posted on # November 17, 2015, 9:03 pm | Post: 6
Group: Member
Post Group: Newbie
Posts: 21
Status:
Thanks. I did as instructed and had a few issues getting dovecot to actually reinstall and stay turned on. It also wouldn't restart from Webuzo, I had to restart it from my vps terminal.

Finally got it sorted out, and deleted an email account, and added it back in Thunderbird. The smtp still comes up only on port 25, and no tls, still no encryption. I can send mail now without the relay not allowed error.

However I still can't get smtp to connect with tls, and only on port 25. Thunderbird says it detects tls on port 25, but won't actually connect or send. I've tried the usual ports for tls and ssl, nothing connects except port 25 with no encryption.

mxtoolbox tells me tls is enabled, but Tbird can't connect. What is up with that?

IP: --   

SMTP dont work
Guest
Posted on # November 18, 2015, 11:20 am | Post: 7
Group: Guest
Status:
Hi CosmicDebri,
I sent to you a Private Message, check it.

Your Issue seems to be something of similar to that topic:
http://www.softaculous.com/board/index.php?tid=8314&title=Error_installing_SSL_certificate

Maybe you need to regenerate self signed certificate for dovecot and configure the right patch on dovecot conf. file.
Read the topic I have sent.

I Am sure you will soon able to fix this issue, also I Am There for help you on that.
IP: --   

SMTP dont work
CosmicDebri
Posted on # November 18, 2015, 11:01 pm | Post: 8
Group: Member
Post Group: Newbie
Posts: 21
Status:
Thanks. I have read your thread, and might give it a try. I was also thinking of trying a reinstall on my vps and a reinstall of Webuzo and starting over. I am more familiar with Debian/Ubuntu  and would like to stick with it, although I see CentOS  seems to be the preferred OS for this panel, or at least has less issues.

I have bypassed this problem by sending my smtp through SendGrid for the moment. A free account will let you send 12,000 emails a month, and that should be fine for me and my clients. It doesn't solve this issue, and I don't like unsolved problems, but at least it works for now.
IP: --   

SMTP dont work
CosmicDebri
Posted on # November 19, 2015, 6:32 am | Post: 9
Group: Member
Post Group: Newbie
Posts: 21
Status:
Well, I had trouble adding a domain, it kept redirecting to my primary domain. Somehow I figured out it was due to a bad/corrupt ssl certificate record. I had deleted my installed certs, and the domain started working, but I guess the email was looking for them and they weren't there. I reinstalled my startssl cert, and now the email seems to connect with tls, still not with ssl, but I'll take the tls for now.

Now I get the very common issue of all mail sent from my Webuzo domains to gmail going into spam folder. I realize this is likely due to no reputation, etc, but still a major pain in the ass.

Last thing I'll try is trying to find where Webuzo puts the certs (if anyone knows, please let me know) and try editing exim configs to look for them in the right place. If I can't get that to work and stop sending emails to google's spam folders, I'll just stick with sending smtp through SendGrid, it all gets thru from there. They manage their blacklisting and reputations pretty well it looks like.
IP: --   

SMTP dont work
Guest
Posted on # November 19, 2015, 9:44 am | Post: 10
Group: Guest
Status:
Quote From : CosmicDebri November 19, 2015, 6:32 am
Well, I had trouble adding a domain, it kept redirecting to my primary domain. Somehow I figured out it was due to a bad/corrupt ssl certificate record. I had deleted my installed certs, and the domain started working, but I guess the email was looking for them and they weren't there. I reinstalled my startssl cert, and now the email seems to connect with tls, still not with ssl, but I'll take the tls for now.

Now I get the very common issue of all mail sent from my Webuzo domains to gmail going into spam folder. I realize this is likely due to no reputation, etc, but still a major pain in the ass.

Last thing I'll try is trying to find where Webuzo puts the certs (if anyone knows, please let me know) and try editing exim configs to look for them in the right place. If I can't get that to work and stop sending emails to google's spam folders, I'll just stick with sending smtp through SendGrid, it all gets thru from there. They manage their blacklisting and reputations pretty well it looks like.


Hi CosmicDebri,
you are very near the solution of your issue.

First,
if your certificate is StartSSL COM I think I have found an issue with that certificate in Webuzo.

PLEASE BACKUP ALL FILES YOU WILL EDIT following this guide. Can be user full is something go wrong. This guide is at your risk.

Please follow this step to fix this issue and let me know if you are able to find the error i Will tell you. If the reply are affirmative Wenbuzo have to work on this BUG because will sure is a problem maybe with Webuzo or START SSL COM certificate.

Your email for use your certificate need to have a valid .pem file. This .pem file are generated when you install a certificate (from Webuzo).
I have discover in my case this file is generated corrupted so that is why email not works but maybe also after this fix StartSSL COM can not be valid for email I don't know why. Let's try check and fix your generated .pem file and maybe fix it.

Please go to /etc/ssl/cert
here you should file .pem file of the domain where you setup the SSL.

If you are from SSH do this command:
vi ./yourcertificatename.pem

you will see many codes inside the certificate, use the down arrow on your keyboard for scroll down the page and continue to look into the file.

By scrolling dow check if you see a row like this:
-----END RSA PRIVATE KEY----------BEGIN CERTIFICATE-----

if you found that this is the error of the .pem file so you should press the letter I (Insert) in your keyboard and go head on the 5° (-) so the correct form of this row will be in two row like this:

-----END RSA PRIVATE KEY-----
-----BEGIN CERTIFICATE-----

so just replace the one row with this two and than save :wq

after that you need check if exim and dovecot are well configured for work with SSL.
Let's do together.

root > cd

                /etc/exim/

root > vi ./exim.conf



I suggest to copy the two row
ssl_cert = </etc/ssl/certs/cert.pem

ssl_key = </etc/ssl/private/cert.key
and past under than comment the first two row copied so edit the two pasted row so you will have

#ssl_cert = </etc/ssl/certs/cert.pem
#ssl_key = </etc/ssl/private/cert.key

ssl_cert = </etc/ssl/certs/certSSL.pem

ssl_key = </etc/ssl/private/certSSL.pem


here you have to edit the two TLS row and put your .pem file patch of the certificate
so cert.pem you have to replace in the not commented row with your file name .pem

where certSSL.pem will be your cert name file. As you can see i replaced .key file also with .pem file


after :wq for save



after that you need edit dovecot conf



you need open port 995:
Root > cd/etc/dovecot/conf.d

Root > vi./10-ssh.conf
and
change SSL/TLS from no to yes

for change that press I of Insert "on
the keybord" and edit no to yes then press esc "on the keybord", now digit

:wq and press enter


Root > service dovecot restart

Now you should check if port 995 is open, you can do it here:
http://www.infobyip.com/tcpportchecker.php
Also check if port 465 is opened.

If 465 still close please do the following command:
iptables -A INPUT -p tcp -m tcp --dport 465 -j ACCEPT

now test again and 465 will be opened, 995 should be opened without a iptables command.

Now you can test if all works fine, if not can be the STARTS SSL issue so maybe suggest to use STARTTLS and not SSL


IP: --   

SMTP dont work
Guest
Posted on # November 19, 2015, 9:48 am | Post: 11
Group: Guest
Status:
Regarding email going to SPAM you have to to the test at this address https://www.mail-tester.com/

So you will see a randoom email in this page, you have to create an email from your VPS address to that address so send an email from your email address you want be recognized and send an email to that randoom address with casual object and text

After that press the button on the page and wait for results.
Your score for be good should be 9/10

I AM sure you have not that so please check well all problem also some times the website show you the solution.

You need to set a correct SPF record on your DNS
IP: --   

SMTP dont work
CosmicDebri
Posted on # November 19, 2015, 8:21 pm | Post: 12
Group: Member
Post Group: Newbie
Posts: 21
Status:
Yeah, Webuzo saved my key and certificate in one file the same way. That was the error I was getting when added domains were going to the default/primary domain. I see it's done it again, so I would agree, it's something the devs of Webuzo need to address. As I understand it, you can combine the 2 into 1 file, but it apparently is missing a line break from one to the other when adding them.

I don't see why a StartSSL certificate is any different than a paid certificate, it's the same format and code, just a lesser known issuer, but better than self signed for sure. It doesn't bring up that 'Warning - self signed certificate' message.

I'll do the separate certs and edit the configs to match them and see how that works. All required ports are open, so it should work after that.

Thanks for the link to the spam email test. I knew about that site, but couldn't remember the link. I came up with a 6.4 score which is basically because of only 2 issues. One is no DKIM record, which shouldn't be a real issue, it helps to have one, but not having one isn't a bad thing (except in Google's eyes, we'll see).

The other issue is my IP shows up in one blacklist, Barracuda, and I have already asked them to remove it, and they have, just takes a little time to propagate through all their servers. That also prompted SpamCop to give a lower score, so just getting out of the blacklist will get me to 9/10, which still doesn't guarantee Google will accept it, but we'll see. Setting up DKIM is another series of pain in the ass steps I'd rather avoid if I don't need to so I'll leave it as a last resort.
IP: --   

SMTP dont work
CosmicDebri
Posted on # November 20, 2015, 7:17 pm | Post: 13
Group: Member
Post Group: Newbie
Posts: 21
Status:
Well, now that I'm off the blacklist I can send mail to gmail addresses and it gets received.

HOWEVER, gmail sent to my Webuzo email addresses are not being delivered. Finally got a message from gmail saying they are still trying to deliver, but:
Google tried to deliver your message, but it was rejected by the server for the recipient domain - The error that the other server returned was: 454 TLS currently unavailable.

TLS IS available as far as I can tell. When I run checks and tests, I get responses back saying tls is enabled, ports 465, 587, 995, 993 can be connected to and listening, all ports are open, no firewall, but if a program isn't listening on a port it won't connect. Email sent from my 1and1 accounts get through no problem.

I see 443 can't connect, but that https, shouldn't have anything to do with email.... but with gmail nothing is certain.....

This is getting old and tiresome. I've tried other panels that the email worked fine, they didn't use exim, most used dovecot. But they had other issues. Seems like one panel will do email fine but have issues with web serving, others email issues but web serving is fine, getting tiresome trying to resolve issue after issue after issue and still not having things work right.

Getting ready to give up and stay on shared hosting, or go back to totally standard lamp setups, which I would rather not do. I was hoping to get multiple websites running on nginx with mariadb, with working email and a control panel that helps configure things. I'm having to mess with so much stuff manually, might as well skip the control panel totally and save some memory and frustration. Or easier yet, (though more expensive) stay with shared hosting.
IP: --   

SMTP dont work
Guest
Posted on # November 20, 2015, 8:14 pm | Post: 14
Group: Guest
Status:
Hi CosmicDebri,
shared hosting are down some times and maybe they can have some issue but if you have difficulty on manage a VPS maybe is better and more safe.

I can't do many from here as i don't know your domain name for testing ports and see what i found or understand better where you are unable to ...

I think you have something of not configured correctly
https://secure.webx.net/clients/knowledgebase/91/Mail-not-deliverable-with-error-454-TLS-currently-unavailable.html

If you are Premium user you can ask help to Webuzo,
if you want I can try to help you as I sent in PM.

I understand if email are not well configured you will have issue. I have setup correctly after more than one year but now I Have learned more about Webuzo

however give access to your server to people outside of the Webuzo support can be dangerous.

Also give access to your remote PC but maybe this second option are more controllable by you.

Anyway good luck.
I Am sure you will find the rigth way for solve your issue in VPS or in shared hosting :)
If you want you can try to search me on my website www.peopleinside.it Live Chat.

       
IP: --   

« Previous    Next »

Threaded Mode | Print  

Page 1 of 212>>>All


Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is May 18, 2025, 11:55 am.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 10  |  Page Created In:0.691