Hi there guys I
have a question not really sure why this is happening and
really this is down to my lack of knowledge of CGP (SMTP)
logs.
To explain I
used to host an email domain singlecity.co.uk I haven’t for
some years now, I noticed the other day that I’m getting a
stack of entries in the logs about the domain. SEE Below, I
don’t understand why I’m getting these, I’ve checked the
domain its DNS and there are no DNS records at all for that
domain. Presumably I’m getting these because someone has
hard coded the IP for the old mail server? The first part of
the logs I get, we don’t relay and the domain isn’t in our
domain list anymore. What I don’t understand is why the
attempt isn’t dropped straight away after all the domain
doesn’t exist and why I get what looks like mail for the
domain in the SMTP queue.
Any help reduce
my ignorance is gratefully accepted. Happy to supply more
detail, normally CGP just works (Which is why I use it) and
I only noticed this as I was checking something else. I’ve
now added a router record:
“<singlecity.co.uk> = null ; blackhole we don't host
this domain anymore” Which
I assume is the best thing to do?
00:00:39.51
5 SMTPI-44850([190.172.151.45]) inp: RCPT TO:
<info@singlecity.co.uk>
00:00:39.51
4 SMTPI-44850([190.172.151.45]) checking MX-record for
singlecity.co.uk
00:00:39.55
1 SMTPI-44850([190.172.151.45]) Recipient
info@singlecity.co.uk rejected: prohibited. We do not relay
00:00:41.55
5 SMTPI-44850([190.172.151.45]) out: 571
info@singlecity.co.uk prohibited. We do not relay\r\n
00:01:47.30
5 SMTPI-44854(117-116-231-201.fibertel.com.ar) inp: RCPT TO:
<info@singlecity.co.uk>
00:01:47.30
4 SMTPI-44854(117-116-231-201.fibertel.com.ar) checking
MX-record for singlecity.co.uk
00:01:47.34
1 SMTPI-44854(117-116-231-201.fibertel.com.ar) Recipient
info@singlecity.co.uk rejected: prohibited. We do not relay
00:01:49.34
5 SMTPI-44854(117-116-231-201.fibertel.com.ar) out: 571
info@singlecity.co.uk prohibited. We do not relay\r\n
00:02:44.81
5 SMTPI-44861([190.82.29.225]) inp: RCPT TO:
<info@singlecity.co.uk>
00:02:44.81
4 SMTPI-44861([190.82.29.225]) checking MX-record for
singlecity.co.uk
00:02:44.84
5 SMTPI-44861([190.82.29.225]) out: 250
info@singlecity.co.uk will relay to a client address\r\n
00:02:45.44
4 SMTP(singlecity.co.uk) record created
00:02:45.44
4 SMTP(singlecity.co.uk) [35846859] enqueueing (new)
00:02:45.44
5 SMTP waiting: singlecity.co.uk active:
00:02:45.44
5 SMTP(singlecity.co.uk) ready in queue
00:02:45.44
5 SMTP waiting: active: singlecity.co.uk
00:02:45.44
4 SMTP sending to singlecity.co.uk
00:02:45.44
5 SMTP waiting(get): active: singlecity.co.uk
00:02:45.44
5 SMTP-41879(singlecity.co.uk) processing
00:02:45.45
5 SMTP-41879(singlecity.co.uk) 1 relay(s)
found:mail.mydomain.com
00:02:45.45
4 SMTP-41879(singlecity.co.uk) resolving ‘mail.mydomain.com’
00:02:45.46
4 SMTP-41879(singlecity.co.uk) connecting to
[xxx.xxx.xxx.xxx]
00:03:06.46
3 SMTP-41879(singlecity.co.uk) failed to connect to
mail.2kcafe.co.uk [xxx.xxx.xxx.xxx:25]. Error Code=no
response
00:03:06.46
4 SMTP-41879(singlecity.co.uk) connecting to
[xxx.xxx.xxx.xxx]
00:03:27.46
3 SMTP-41879(singlecity.co.uk) failed to connect to
mail.2kcafe.co.uk [xxx.xxx.xxx.xxx:25]. Error Code=no
response
00:03:27.46
4 SMTP(singlecity.co.uk) re-enqueue
00:03:27.46
5 SMTP waiting: singlecity.co.uk active:
00:03:27.46
5 SMTP(singlecity.co.uk) is first in queue with 600
second(s) delay
00:03:27.46
4 SMTP-41879(singlecity.co.uk) releasing stream
00:03:27.46
5 SMTP waiting(get): singlecity.co.uk active:
00:03:27.46
5 SMTP(singlecity.co.uk) is first in queue with 600
second(s) delay
00:04:37.24
5 SMTP waiting: gmail.com singlecity.co.uk active:
00:04:37.24
5 SMTP waiting: singlecity.co.uk active: gmail.com
00:04:37.24
5 SMTP(singlecity.co.uk) is first in queue with 530
second(s) delay
00:04:37.24
5 SMTP waiting(get): singlecity.co.uk active: gmail.com
00:04:37.24
5 SMTP(singlecity.co.uk) is first in queue with 530
second(s) delay
==============================================================================================================================================================
00:03:27.46 4 SMTP(singlecity.co.uk) re-enqueue
00:03:27.46 5 SMTP waiting: singlecity.co.uk active:
00:03:27.46 5 SMTP(singlecity.co.uk) is first in queue with 600 second(s) delay
00:03:27.46 4 SMTP-41879(singlecity.co.uk) releasing stream
00:03:27.46 5 SMTP waiting(get): singlecity.co.uk active:
00:03:27.46 5 SMTP(singlecity.co.uk) is first in queue with 600 second(s) delay
00:04:37.24 5 SMTP waiting: gmail.com singlecity.co.uk active:
00:04:37.24 5 SMTP waiting: singlecity.co.uk active: gmail.com
00:04:37.24 5 SMTP(singlecity.co.uk) is first in queue with 530 second(s) delay
00:04:37.24 5 SMTP waiting(get): singlecity.co.uk active: gmail.com
00:04:37.24 5 SMTP(singlecity.co.uk) is first in queue with 530 second(s) delay
00:04:40.76 5 SMTP waiting: gmail.com singlecity.co.uk active:
00:04:40.76 5 SMTP waiting: singlecity.co.uk active: gmail.com
00:04:40.76 5 SMTP(singlecity.co.uk) is first in queue with 527 second(s) delay
00:04:40.76 5 SMTP waiting(get): singlecity.co.uk active: gmail.com
00:04:40.76 5 SMTP(singlecity.co.uk) is first in queue with 527 second(s) delay
00:05:52.42 5 SMTP waiting: gmail.com singlecity.co.uk active:
00:05:52.42 5 SMTP waiting: singlecity.co.uk active: gmail.com
00:05:52.42 5 SMTP(singlecity.co.uk) is first in queue with 455 second(s) delay