

![]() | Start a set with this search |
![]() | Include this search in one of my sets |
![]() | Exclude this search from one of my sets |
![]() | Permalink to these results Paste this link in email or IM: |
| Atom feed for tracking future search results Paste this URL into your reader: |
4 messages in net.sourceforge.lists.courier-users[courier-users] How can I track conne...| From | Sent On | Attachments |
|---|---|---|
| Peter Ford | Jul 28, 2004 2:09 am | |
| m...@rtij.nl | Jul 28, 2004 2:54 am | |
| Phillip Hutchings | Jul 28, 2004 3:17 am | |
| Sam Varshavchik | Jul 28, 2004 4:13 am |

![]() | Permalink for this message Paste this link in email or IM: |
![]() | Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | [courier-users] How can I track connections to my courier server? | Actions... |
|---|---|---|
| From: | Peter Ford (pfo...@justcroft.com) | |
| Date: | Jul 28, 2004 2:09:44 am | |
| List: | net.sourceforge.lists.courier-users | |
Hi,
I'm trying to work out how to get more info into my logs, in order to track a
problem one of our
customers is having when sending mail to us.
I have his log output (which is more than I usually get :-) ), and a fleeting
glimpse of it in my log.
His log says:
--- Session Transcript --- Tue 2004-07-27 22:00:54: Parsing Message <xxxxxxxxxxxxxxxxxxxxxxxx\pd90000001178.msg> Tue 2004-07-27 22:00:54: From: dlos...@isispetroleum.com.au Tue 2004-07-27 22:00:54: To: rwij...@justcroft.com Tue 2004-07-27 22:00:54: Subject: RE: Kingdom in Houston Tue 2004-07-27 22:00:54: Message-ID: <HGEK...@isispetroleum.com.au> Tue 2004-07-27 22:00:54: MX-record resolution of [justcroft.com] in progress (DNS Server: 127.0.0.1)... Tue 2004-07-27 22:00:55: P=020 D=justcroft.com TTL=(120) MX=[alien.justcroft.com] {81.144.249.133} Tue 2004-07-27 22:00:55: P=015 D=justcroft.com TTL=(120) MX= [alien.justcroft.co.uk] {192.168.1.7} Tue 2004-07-27 22:00:55: P=010 D=justcroft.com TTL=(120) MX=[mail.justcroft.com] {81.144.249.133} Tue 2004-07-27 22:00:55: Attempting MX: P=010 D=justcroft.com TTL=(120) MX= [mail.justcroft.com] {81.144.249.133} Tue 2004-07-27 22:00:55: Attempting SMTP connection to [81.144.249.133 : 25] Tue 2004-07-27 22:00:55: Waiting for socket connection... Tue 2004-07-27 22:00:55: Socket connection established (10.0.0.20 : 4137 ->
81.144.249.133 : 25) Tue 2004-07-27 22:00:55: Waiting for protocol initiation... Tue 2004-07-27 22:01:25: 30 second wait for protocol timeout exceeded. Tue 2004-07-27 22:01:46: Attempting MX: P=020 D=justcroft.com TTL=(120) MX= [alien.justcroft.com] {81.144.249.133} Tue 2004-07-27 22:01:46: Attempting SMTP connection to [81.144.249.133 : 25] Tue 2004-07-27 22:01:46: Waiting for socket connection... Tue 2004-07-27 22:01:49: Socket connection established (10.0.0.20 : 4156 ->
81.144.249.133 : 25) Tue 2004-07-27 22:01:49: Waiting for protocol initiation... Tue 2004-07-27 22:02:19: 30 second wait for protocol timeout exceeded. Tue 2004-07-27 22:02:19: This message is 0 days old; it has 2 days left to get delivered --- End Transcript ---
I found the MX for his domain and got the IP address of his mail server, then
grepped that in my
maillog, and all I have is lots of instances of
Jul 27 11:00:05 alien courieresmtpd: started,ip=[::ffff:203.59.129.54]
(His server is in australia, mine in the UK, so this particular log entry
corresponds to the log he
sent...)
There's no follow-up to this "started" entry - which I suppose matches the
timeout in his log.
Is there anyway to have more information logged about connections? I can't see
any configurations
which affect logging levels.
I really want to be able to demonstrate that this problem is out of my control -
I suspect a
misconfiguration on the remote end, since most people manage to send us mail
perfectly well.
-- Peter Ford phone: 01580 893333 Developer fax: 01580 893399 Justcroft International Ltd., Staplehurst, Kent







