Scam report against | /user/1641925-vaping/ | $42.99

[Vaping]

Problem fixed, awaiting on customer's side response.

[Vaping]

@Lucas Waiting to get this closed since the problem's fixed.

[Lucas]

Please do it.

News? 

[BobsDaddy]

So far im able to send emails out (went to spam but its ok) but still got problems with receiving mails

[Lucas]

@Lucas Waiting to get this closed since the problem's fixed.

News? He's saying he didn't get what he paid for yet

[Lucas]

@Lucas Waiting to get this closed since the problem's fixed.

News about this? 

[Vaping]

News about this?

The service is working in its full performances, the only problem I had been able to identify was the email sending issue, it's either given by the signature, since trust score is 100%, or by the ports of SMTP, I'll check personally with cPanel today and get this fixed.

[AZATEJ]

removed.

[Lucas]

The service is working in its full performances, the only problem I had been able to identify was the email sending issue, it's either given by the signature, since trust score is 100%, or by the ports of SMTP, I'll check personally with cPanel today and get this fixed.

Fixed now? 

[Vaping]

Fixed now? 

Issue's fixed, tested in various sceniaros, emails are being sent without errors, here's a log:
 

2019-03-28 18:40:10 1h9Zwg-006juG-VC <= [email protected] H=(evaporate.vapehost.cc) [::1]:56328 P=esmtpsa X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no A=dovecot_plain:[email protected] S=771 id=20190328184010.Horde.gcXkmTOImn4B2Yl6ERQU15m@evaporate.vapehost.cc T="test email" for [email protected]
2019-03-28 18:40:11 1h9Zwg-006juG-VC SMTP connection outbound 1553798411 1h9Zwg-006juG-VC vapehost.cc [email protected]
2019-03-28 18:41:14 1h9Zwg-006juG-VC => [email protected] R=dkim_lookuphost T=dkim_remote_smtp H=gmail-smtp-in.l.google.com [173.194.76.26] X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=yes C="250 2.0.0 OK 1553798474 v6si8433556wro.213 - gsmtp"

The emails appeared not to be sent just because Gmail was responding to our old server's requests, here's a log as an example:

<destinationemail>

host gmail-smtp-in.l.google.com [74.125.140.27]
SMTP error from remote mail server after end of data:
550-5.7.1 [136.243.44.194 1] Our system has detected an unusual rate of
550-5.7.1 unsolicited mail originating from your IP address. To protect our
550-5.7.1 users from spam, mail sent from your IP address has been blocked.
550-5.7.1 Please visit
550-5.7.1 https://support.goog...olicitedIPError to review our
550 5.7.1 Bulk Email Senders Guidelines. k32si5616003wre.32 - gsmtp

 

As you can see the IP in the gmail response is not our current one, instead it's from our old Germany's node.

With the accounts having been transferred over from our old server with that IP address, it is likely the initial message was sent from the old server and when the bounce back returned the site in question was then pointed to/resolving to this new server.

The common factor would be DNS in which a domain or mail record would now be pointed to the new server opposed to the old and Gmail would return the message based on DNS opposed to the server of origin.

The new server does have messages in the queue waiting to be sent. The messages date back to the 25th. The old server had a similar condition in which messages have been queued for some time, they are being sent out.

That's what happened after the accounts were transferred and DNS updated, messages still in the queue on the old server finally are getting sent out, and when Gmail returns to the sender, they see the sender now resolves to the new server.