Amoss

I think it might be related to my IP, it happened after that restart which initialized my VPS settings of exim and it took time until we figured out all the changes that were made and fixed them. But that is only a guess as Gmail doesn't share anything about the reason, moreover, the message say as if my server is the problem as it doesn't deliver, it doesn't say Gmail doesn't accept it. An exim test say something about failing the spam test and then it say I pass it so it's confusing as well. Unless there is something hidden in the logs, I have no idea what else needs to be done. Posting this again for @Krydos I have also been asked this "I noticed there is no reverse lookup for 216.218.228.90. I'm also concerned about what it might mean that the IP address is the same for both names. Also, it is important for deliverability that the sending server is authorized to send messages on behalf of your domain." and this You might improve deliverability by adding a reverse lookup record If only someone from Gmail could check this issue and tell me why this happens only with gmail, but that will be naive to think it will happen. I posted on their support forum/community (where "regular" people reply) but they are clueless as well.

Thanks, and do you have a problem sending emails to gmail? :-)

Adding this here as well I have also been asked this "I noticed there is no reverse lookup for 216.218.228.90. I'm also concerned about what it might mean that the IP address is the same for both names. Also, it is important for deliverability that the sending server is authorized to send messages on behalf of your domain." and this You might improve deliverability by adding a reverse lookup record

Gmail Issue, I saw the following here https://amp.ipaddress.com/websites/stockdiv.com - what is this heliohost2.gmail.com thing? SOA Record stockdiv.com IN SOA ns1.heliohost.org. heliohost2.gmail.com. ( 2019051110 ; serial 3600 ; refresh : 1 hour 7200 ; retry : 2 hours 1209600 ; expiry : 14 days 86400 ; minttl : 1 day ) I have also been asked this "I noticed there is no reverse lookup for 216.218.228.90. I'm also concerned about what it might mean that the IP address is the same for both names. Also, it is important for deliverability that the sending server is authorized to send messages on behalf of your domain." and this You might improve deliverability by adding a reverse lookup record

Works like a charm - thanks --- Gmail issue: Is it officially a voodoo or is there anything else that can be done? or maybe somewhere else i can check things? --- Any idea what's the thing with the java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens? from the web it is related to https/http stuff, in apache logs I didn't see anything suspicious.

Thanks, I hope Krydos will take care of it the next time he will be online. I wonder why I (and maybe others) get this error and the people here didn't. Now other users started reporting me that they have this problem as well so it's not only me. Do you have an idea how can I fix this? Assuming I can ofcourse. --- regarding the email, my account is defined inside gmail itself (what a joke, ah? ), pop3 server is stockdiv.com and it works, if I change it to mail.stockdiv.com then it says: Unable to establish secure SSL connection to mail.stockdiv.com. SMTP on the other hand, was changed successfully to mail.... so I emailed again to the panther email... and after 24 hours or so I got a delivery error email --- I see several errors of the following: 12-Jul-2019 19:21:45.076 INFO [http-nio-8080-exec-21] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level. java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens from the web it is related to https/http stuff, in apache logs I didn't see anything suspicious. ----

See in my previous reply (previous page) what happens when I test with exim.

Thanks, email sent. This is what I get from bitdefender (computer) and from the rest client (mobile) I did the following using ssh $ exim -v ...@gmail.com from: support@stockdiv.com subject: testing gmail this is a test, did you receive it? LOG: MAIN <= amoss@mail.stockdiv.com U=amoss P=local S=362 amoss@mail:~$ delivering 1hldYm-000Wx3-A7 LOG: retry_defer MAIN == ...@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host for 'gmail.com'

I emailed 2 people after the fix. I asked one person and he told me he didn't. I still didn't ask the other one. On the other hand, I still didn't receive any delivery error email back...

Thank you wolstech for updating, I'll give it some time to propagate and try again later when I'm home

I'm at work so I can't upload images, when I'm home I will upload both images from my mobile and my browser. The browser is actually my antivirus (bitdefender) who is warning me. This didn't happen before the latest changes Krydos did but I'm glad to know it's not a general issue. Maybe it needs time to propagate.

Thanks but what do you see when browsing to https://www.stockdiv.com ? I get a certificate warning in my browser (from my antivirus). I also have a rest client on my mobile that also get the same error about the certificate

That's what happens when someone who understands what he is doing is doing things - things get resolve quickly and professionally - thanks a lot, I emailed someone, waiting for his response to make sure it works. One last thing - www.stockdiv.com does not work because of the new certificate thing.

I followed these steps https://forum.vestacp.com/viewtopic.php?t=14331 and I'm now back in step 1 where only cert fails I did notice that under /etc/exim4/domains/ there is only stockdiv.com, not sure if mail.stockdiv.com should also be there I do see a lot of these in exim mainlog: dovecot_login authenticator failed for (stockdiv.com) [ip, not mine]: 535 Incorrect authentication data (set_id=<name varies>@stockdiv.com) -> is it someone who is trying to (ab)use my server? I continued with the steps and reached here: Now go to your EXIM.conf, probably located in /etc/exim/exim.conf... Where can I find exim? It's not under etc... I did see exim4 under etc but there is no exim.conf file there. sudo find . -name "exim*.conf" found several occurrences but none seem to be an exim folder. I've found update-exim4.conf.conf but it doesn't seem to have what the guide says. Also, in vestacp -> mail section -> domain it says stockdiv.com (disabled for editing). Should it also be mail.stockdiv.com?

I went to the web.conf file and when editing it, I noticed that mail.stockdiv.com alias was already there. I checked vesta panel and it was also there. Not sure how. At this point, I went to this site https://www.checktls.com/TestReceiver (entered both stockdiv.com and mail.stockdiv.com) and it looks worse than before, now there are 3 failures, not just one as before, including TLS itself (+cert + secure). Previously, only cert was failing. Can you please take a look at this? Thanks

I will try and update, I also tried this one https://www.checktls.com/TestReceiver and saw there is a cert problem. I wonder if it's all related. update: well, the first step is to add an alias mail.stockdiv.com, there's already a www.stockdiv.com alias so I added another one to it but when saving, it fails with error code 3. any idea?

I've found this https://forum.vestacp.com/viewtopic.php?t=17151 May I follow the instructions there to accomplish that? I'm asking so I won't break things. Thanks

I did: https://support.google.com/mail/thread/8130059?hl=en The guy there told me to check the PTR/reverse dns etc... and if it still fails, talk to my sysadmin/mail hoster/seek help outside. When I asked him specifically about the errors, he wrote this: Please check with your domain hoster re traffic filtering; otherwise I am not sure that we can give any further advice. If you have another way to contact gmail or ask about this kind of error, do let me know and I'll do it.

My question is about the errors I get when sending to Gmail, I don't receive those when sending to other providers: H=gmail-smtp-in.l.google.com [74.125.197.27] TLS error on connection (recv): Resource temporarily unavailable, try again. H=gmail-smtp-in.l.google.com [74.125.197.27]: Remote host closed connection in response to EHLO mail.stockdiv.com H=alt1.gmail-smtp-in.l.google.com [209.85.200.27] TLS error on connection (recv): Resource temporarily unavailable, try again. H=alt1.gmail-smtp-in.l.google.com [209.85.200.27]: alt1.gmail-smtp-in.l.google.com [209.85.200.27]: No such file or directory == ...@gmail.com R=dnslookup T=remote_smtp defer (2): No such file or directory H=alt1.gmail-smtp-in.l.google.com [209.85.200.27]: alt1.gmail-smtp-in.l.google.com [209.85.200.27] ** ...@gmail.com: retry timeout exceeded

Thanks for updating, what about the errors I posted in my previous message? When sending emails to other providers everything is smooth, when sending to gmail I get those errors... I guess my next question would be if vesta is going to support ubuntu 19 anytime soon?

I will try it, thanks. Changing the dns to GoDaddy + A record leading to my vps, will change anything the fact of not being able to send to gmail? --- I tried sending an email from exim itself and got the following and here is someone who had the same issue: https://www.mail-archive.com/exim-users%40exim.org/msg53129.html ... SMTP>> STARTTLS SMTP<< 220 2.0.0 Ready to start TLS SMTP>> EHLO mail.stockdiv.com LOG: MAIN H=gmail-smtp-in.l.google.com [74.125.197.27] TLS error on connection (recv): Resource temporarily unavailable, try again. SMTP(close)>> LOG: MAIN H=gmail-smtp-in.l.google.com [74.125.197.27]: Remote host closed connection in response to EHLO mail.stockdiv.com H=alt1.gmail-smtp-in.l.google.com [209.85.200.27] TLS error on connection (recv): Resource temporarily unavailable, try again. SMTP(close)>> H=alt1.gmail-smtp-in.l.google.com [209.85.200.27]: alt1.gmail-smtp-in.l.google.com [209.85.200.27]: No such file or directory LOG: MAIN == ...@gmail.com R=dnslookup T=remote_smtp defer (2): No such file or directory H=alt1.gmail-smtp-in.l.google.com [209.85.200.27]: alt1.gmail-smtp-in.l.google.com [209.85.200.27] ** ...@gmail.com: retry timeout exceeded I was told to "Please check with your domain hoster regarding traffic filtering"

My domain is pointed to your servers because everything is there, site and war. If I'll change it to GoDaddy's/cloudflare's servers, won't it fail everything? I was wondering: changing my VPS IP is something that can be done easily? I think that one of the problems is that my IP got backlisted because of those dns/ptr issues, maybe getting a new IP will fix this. Assuming it won't have other effects on the VPS itself.

Mmmm... Let's try mail.stockdiv.com? Also read here, also the comments: https://serverfault.com/questions/713426/reverse-dns-is-not-a-valid-hostname How were your other VPSs configured? I read in other posts that Gmail can be picky about this reverse DNS thing... Do you see any errors in the exim logs when it tries to send an email to Gmail? I tried again this morning but failed. I've also been asked this: do you have a valid rDNS entry for your mailserver/domain? And another test I did: http://multirbl.valli.org/email-test/1aa7b6e88a261b5cdddaef889c941b60393d97ce.html there are some failures there Thanks

Thank you for the link, it says "Most systems won't care that it is a domain" and since gmail is still not working, I wonder if it is one of the systems that does not like it. Is it something you can change as the RFC guidelines suggests or if you think otherwise, please share your thoughts. Regarding the logs, thanks a lot! I saw some errors in the tomcat that I'm going to investigate.

Thanks, it looks like the restart reset the vps name along other things. In vesta i was able to rename back the hostname but I understand that exim was also reset. Still not working with Gmail. While mail-tester is ok https://www.mail-tester.com/test-af8vw&reloaded=4 , I checked again (3 times) mxtoolbox and saw this: smtp: Reverse DNS is not a valid Hostname: Your Reverse DNS Record (PTR) is not a valid host name. According to email sending best practices, a PTR Record should be a valid host name. If the PTR Record is not a valid hostname, there is a likelihood that you will experience email delivery issues with anti-spam services. smtp: 5.794 seconds - Warning on Connection time (3 tests show above 5) smtp: 8.214 seconds - Not good! on Transaction Time (3 tests show above 8) dns: Only on the second try, I got this about dns: At least one name server failed to respond in a timely manner. A 3rd check did not show this problem so maybe it was temporarily. ----- Another issue: I redeployed my war and it behaved weird. Only a tomcat restart made it work again, please let me know if you see an error around 6:15pm (gmt+3) in the tomcat/apache logs. Thanks