Koozali.org: home of the SME Server

determine the the exact time the server

Offline partsgaw

  • **
  • 35
  • +0/-0
determine the the exact time the server
« on: January 05, 2010, 09:28:50 AM »
hi Good day,
   can u help me determine whats the exact time the emails has been sent by the email server (Qmail) after being qued.

thanks,

« Last Edit: January 05, 2010, 09:34:57 AM by ethan_chien »

Offline Jáder

  • *
  • 1,099
  • +0/-0
    • LinuxFacil
Re: determine the the exact time the server
« Reply #1 on: January 05, 2010, 01:38:08 PM »
That information is on header of each message.
Choose to see headers of messages (CTRL+U on Thunderbird) ... there are all information you will ever need about that message.
Eg. each server where server was routed and time.

What´s your problem... delivery delay ?

Jáder
...

Offline partsgaw

  • **
  • 35
  • +0/-0
Re: determine the the exact time the server
« Reply #2 on: January 06, 2010, 01:49:38 AM »
hi jader,
 
   yeah it takes hours that recipient will received my email when i send email to this email address only (mspcagde@info.com.ph).
Can determine this log error :

2010-01-04 08:25:39.417075500 info msg 19139792: bytes 4266 from <mspcagde@info.com.ph> qp id 400
2010-01-04 10:45:30.612418500 starting delivery 7754: msg 19139792 to remote mspcagde@info.
2010-01-04 10:55:31.716867500 info msg 19139792: bytes 2022 from <mspcagde@info.com.ph> qp d 453
2010-01-04 10:55:31.745816500 info msg 19139585: bytes 2142 from <mspcagde@info.com.ph> qp d 400
2010-01-04 11:21:40.310023500 info msg 19139792: bytes 1870 from <mspcagde@info.com.ph> qp d 453
2010-01-04 11:21:40.345004500 info msg 19139585: bytes 1990 from <mspcagde@info.com.ph> qp d 400
2010-01-04 11:34:21.833529500 starting delivery 7893: msg 19139792 to remote mspcagde@info.
2010-01-04 11:40:41.558303500 info msg 19139792: bytes 2048 from <mspcagde@info.com.ph> qp d 453
2010-01-04 11:40:41.587287500 info msg 19139354: bytes 2168 from <mspcagde@info.com.ph> qp d 400
2010-01-04 11:41:39.120903500 info msg 19139792: bytes 2582 from <mspcagde@info.com.ph> qp d 453
2010-01-04 11:41:39.144896500 info msg 19139354: bytes 2702 from <mspcagde@info.com.ph> qp d 400
2010-01-04 11:48:01.265989500 starting delivery 7947: msg 19139587 to remote mspcagde@info.
2010-01-04 12:09:23.170073500 starting delivery 8025: msg 19139587 to remote mspcagde@info.
2010-01-04 12:41:38.557650500 info msg 19139792: bytes 2143 from <mspcagde@info.com.ph> qp id 453
2010-01-04 12:41:38.584634500 info msg 19139354: bytes 2264 from <mspcagde@info.com.ph> qp id 400
2010-01-04 13:09:14.681004500 info msg 19139792: bytes 3650 from <mspcagde@info.           id 453
2010-01-04 13:09:14.709983500 info msg 19139587: bytes 3771 from <mspcagde@info.           id 400
2010-01-04 13:22:12.651959500 starting delivery 8256: msg 19139792 to remote msp
2010-01-04 13:42:22.597629500 starting delivery 8325: msg 19139792 to remote msp
2010-01-04 14:10:49.800324500 starting delivery 8392: msg 19139792 to remote msp
2010-01-04 14:19:58.733452500 starting delivery 8396: msg 19139927 to remote msp
2010-01-04 14:26:39.876253500 starting delivery 8429: msg 19139927 to remote msp
2010-01-04 14:46:39.688801500 starting delivery 8523: msg 19139927 to remote msp
2010-01-04 14:53:29.517259500 starting delivery 8528: msg 19139792 to remote msp
2010-01-04 15:19:59.908046500 starting delivery 8645: msg 19139927 to remote msp
2010-01-04 15:49:29.334124500 starting delivery 8813: msg 19139792 to remote msp
2010-01-04 16:06:39.837069500 starting delivery 9091: msg 19139927 to remote msp
2010-01-04 16:12:51.158524500 info msg 19139847: bytes 2235 from <mspcagde@info.           id 453
2010-01-04 16:12:51.188492500 info msg 19139354: bytes 2356 from <mspcagde@info.           id 400
2010-01-04 16:58:49.327629500 starting delivery 9426: msg 19139792 to remote msp
2010-01-05 08:27:44.268862500 info msg 19139850: bytes 2052 from <mspcagde@info.           id 453
2010-01-05 08:27:44.296847500 info msg 19139319: bytes 2173 from <mspcagde@info.           id 400


thanks
« Last Edit: January 06, 2010, 01:52:41 AM by ethan_chien »

Offline Jáder

  • *
  • 1,099
  • +0/-0
    • LinuxFacil
Re: determine the the exact time the server
« Reply #3 on: January 06, 2010, 02:06:55 AM »
I'm not sure howto discover your problem using that  log
What I do?
I see the header of one message looking for info like this:
Code: [Select]
Return-Path: <jader@linuxfacil.net>
Delivered-To: jader@pantera.roan.com.br
Received: (qmail 8793 invoked by alias); 2 Jan 2010 10:19:15 -0000
Delivered-To: alias-localdelivery-jader@roan.com.br
Received: (qmail 8790 invoked by uid 453); 2 Jan 2010 10:19:15 -0000
X-Virus-Checked: Checked by ClamAV on roan.com.br
X-Spam-Status: No, hits=0.0 required=5.0
tests=BAYES_50,SPF_PASS
X-Spam-Check-By: roan.com.br
Received: from outbound-mail-24.bluehost.com (HELO outbound-mail-24.bluehost.com) (69.89.21.19)
    by roan.com.br (qpsmtpd/0.40) with SMTP; Sat, 02 Jan 2010 08:19:09 -0200
Received: (qmail 7645 invoked by uid 0); 2 Jan 2010 10:19:03 -0000
Received: from unknown (HELO box544.bluehost.com) (74.220.219.144)
  by outboundproxy2.bluehost.com with SMTP; 2 Jan 2010 10:19:03 -0000
Received: from 189.27.174.221.dynamic.adsl.gvt.net.br ([189.27.174.221] helo=lobo.linuxfacil.net)
by box544.bluehost.com with esmtpa (Exim 4.69)
(envelope-from <jader@linuxfacil.net>)
id 1NR14Z-0003sQ-2P
for jader@roan.com.br; Sat, 02 Jan 2010 03:19:03 -0700
Received: (qmail 13442 invoked by uid 453); 2 Jan 2010 10:18:56 -0000
X-Virus-Checked: Checked by ClamAV on linuxfacil.net
Received: from localhost (HELO localhost) (127.0.0.1)
    by linuxfacil.net (qpsmtpd/0.40) with ESMTP; Sat, 02 Jan 2010 08:18:55 -0200
Received: from macmini.linuxfacil.net (macmini.linuxfacil.net
 [192.168.13.204]) by lobo (Horde Framework) with HTTP; Sat,  2 Jan 2010
 08:18:53 -0200
Message-ID: <20100102081853.16424v6jtirseyec@lobo>
Date: Sat,  2 Jan 2010 08:18:53 -0200

I do this to discover if the problem was internal to my server (delay to try to delivery) or something else (like antispam rules on ISP or target server).

If your problem is just for one destination... I bet on spam (or antispam) rules.
What a header of one delivered message searching for this info and watch your smtp log to see an delay caused by antispam rules (like a tarpit).

I setup two autoreply accounts (on inside my country, in an account on biggest ISP here) and another on a hosting service I use inside USA. I use them to diagnose e-mail problems.
You can try them: respostaautomatica@terra.com.br and respostaautomatica@abandonemicrosoft.net
but try BOTH of them in EACH message... if you get no answer... that's a bad signal.

BTW: the  autoreply messages are in portuguese... try google translate them if you're curious!

...

Offline partsgaw

  • **
  • 35
  • +0/-0
Re: determine the the exact time the server
« Reply #4 on: January 06, 2010, 02:33:38 AM »
thanks for the info,  ill just contact first the email admins for the target email server to check there antispam rules and then ill try sending to that autoreply mails.

  then what does bad signal means? network or routing problems?

thanks

Offline Jáder

  • *
  • 1,099
  • +0/-0
    • LinuxFacil
Re: determine the the exact time the server
« Reply #5 on: January 06, 2010, 12:28:18 PM »
You can use the autoreply addrress to get familiar with e-mail headers... there´re no harm in use those addressess.

Bad signal : if you cannot get a quick answer from at least ONE of those... it´s  probable the problem is on your side... network... server configuration... firewall port redirect... dns misconfiguration...

When I change ANYTHING on my servers I do 3 tests:
1) external remote access
2) e-mails being received  (using those autoreply accounts)
3) web navigation from inside network

it this is working... on this order... everything else I can fix later because is a minor problem! :D

Jáder
...