Hi, Here's the watchlog from yesterday and I extracted a few entries. It didn't include the mail size though, but certainly it's slow when the mail size is over hundred K bytes.The Linux server looks normal, just don't understand where the problem is. Here's one of the incoming message still in the incoming queue at this moment: [root@mailgate2 incoming]# ls -l 5F5007F3F-rw------- 1 postfix postfix 10059776 Jan 15 22:27 5F5007F3F [root@mailgate2 incoming]# grep 5F5007F3F /var/log/maillogJan 15 21:37:22 mailgate2 postfix/smtpd[25122]: 5F5007F3F: client=ttsenmta4.ttasia.com[210.17.183.10]Jan 15 21:37:22 mailgate2 postfix/cleanup[25123]: 5F5007F3F: message-id=<001d01cdf2fa$a49caed0$edd60c70$@com> [root@mailgate2 incoming]# postcat 5F5007F3F|more*** ENVELOPE RECORDS 5F5007F3F ***message_size: 0 0 0 0 0message_arrival_time: Tue Jan 15 21:37:22 2013create_time: Tue Jan 15 21:37:22 2013named_attribute: rewrite_context=remotesender: [email protected]_attribute: log_client_name=ttsenmta4.ttasia.comnamed_attribute: log_client_address=210.17.183.10named_attribute: log_client_port=53984named_attribute: log_message_origin=ttsenmta4.ttasia.com[210.17.183.10]named_attribute: log_helo_name=ttsenmta4.ttasia.comnamed_attribute: log_protocol_name=ESMTPnamed_attribute: client_name=ttsenmta4.ttasia.comnamed_attribute: reverse_client_name=ttsenmta4.ttasia.comnamed_attribute: client_address=210.17.183.10named_attribute: client_port=53984named_attribute: helo_name=ttsenmta4.ttasia.comnamed_attribute: client_address_type=2named_attribute: dsn_orig_rcpt=rfc822;[email protected]_recipient: [email protected]: [email protected]*** MESSAGE CONTENTS 5F5007F3F ***Received: from ttsenmta4.ttasia.com (ttsenmta4.ttasia.com [210.17.183.10]) by mailgate2.ss-intl.com (Postfix) with ESMTP id 5F5007F3F for <[email protected]>; Tue, 15 Jan 2013 21:37:22 +0800 (HKT)Received: from mail.whitexgarments.com ([218.111.30.246]) by ttsenmta4.ttasia.com with Microsoft SMTPSVC(7.5.7601.17514); Tue, 15 Jan 2013 16:35:16 +0800Received: from WHITEXPC by mail.whitexgarments.com (MDaemon PRO v11.0.3) with ESMTP id md50002467920.msg for <[email protected]>; Tue, 15 Jan 2013 16:34:50 +0800X-Spam-Processed: mail.whitexgarments.com, Tue, 15 Jan 2013 16:34:50 +0800 (not processed: message size (14788353) exceeds spam filter configured max size of (102400))X-Authenticated-Sender: [email protected]: 202.79.28.102.... Any ideas where to find the root cause is welcome. Many thanks.
373357F0D: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=16369, delays=16369/0/0/0.51, dsn=2.0.0, status=sent (250 Mail queued for delivery) E20B37F04: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=0.16, delays=0.07/0/0/0.08, dsn=2.0.0, status=sent (250 Mail queued for delivery) statistics: max connection rate 1/60s for (smtp:202.181.174.145) at Jan 14 00:02:48 statistics: max connection count 1 for (smtp:202.181.174.145) at Jan 14 00:02:48 statistics: max cache size 1 at Jan 14 00:02:48 A352F7F04: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=2.1, delays=0.08/0/0.01/2, dsn=2.0.0, status=sent (250 Mail queued for delivery) 674D27F04: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=0.09, delays=0.06/0/0/0.02, dsn=2.0.0, status=sent (250 Mail queued for delivery) statistics: max connection rate 1/60s for (smtp:59.188.18.158) at Jan 14 00:15:44 statistics: max connection count 1 for (smtp:59.188.18.158) at Jan 14 00:15:44 statistics: max cache size 1 at Jan 14 00:15:44 D504D7F04: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=186, delays=185/0/0/0.61, dsn=2.0.0, status=sent (250 Mail queued for delivery) 6D5467F04: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=1.7, delays=1.2/0/0/0.5, dsn=2.0.0, status=sent (250 Mail queued for delivery) statistics: max connection rate 1/60s for (smtp:210.17.183.8) at Jan 14 00:27:45 statistics: max connection count 1 for (smtp:210.17.183.8) at Jan 14 00:27:45 statistics: max cache size 2 at Jan 14 00:31:21 7CE747F04: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=0.07, delays=0.05/0/0/0.02, dsn=2.0.0, status=sent (250 Mail queued for delivery) statistics: max connection rate 1/60s for (smtp:210.17.183.10) at Jan 14 00:40:51 statistics: max connection count 1 for (smtp:210.17.183.10) at Jan 14 00:40:51 statistics: max cache size 1 at Jan 14 00:40:51 ... statistics: max connection rate 1/60s for (smtp:210.17.183.10) at Jan 14 08:53:46 statistics: max connection count 1 for (smtp:210.17.183.10) at Jan 14 08:53:46 statistics: max cache size 2 at Jan 14 08:55:56 A34747F07: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=1.4, delays=1/0/0/0.41, dsn=2.0.0, status=sent (250 Mail queued for delivery) 12F867F04: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=112, delays=111/0/0/0.77, dsn=2.0.0, status=sent (250 Mail queued for delivery) 12F867F04: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=112, delays=111/0/0/0.77, dsn=2.0.0, status=sent (250 Mail queued for delivery) B321B7F04: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=0.13, delays=0.07/0/0/0.06, dsn=2.0.0, status=sent (250 Mail queued for delivery) ... 4DE897F1D: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=4.1, delays=3.2/0/0/0.92, dsn=2.0.0, status=sent (250 Mail queued for delivery) CAF9E7F0D: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=1163, delays=1160/0/0/3.4, dsn=2.0.0, status=sent (250 Mail queued for delivery) statistics: max connection rate 3/60s for (smtp:210.17.183.8) at Jan 14 10:27:04 statistics: max connection count 6 for (smtp:210.17.183.8) at Jan 14 10:25:18 statistics: max cache size 4 at Jan 14 10:30:25 2E2527F0D: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=0.23, delays=0.16/0/0/0.06, dsn=2.0.0, status=sent (250 Mail queued for delivery) 2E2527F0D: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=0.23, delays=0.16/0/0/0.06, dsn=2.0.0, status=sent (250 Mail queued for delivery) 2E2527F0D: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=0.23, delays=0.16/0/0/0.06, dsn=2.0.0, status=sent (250 Mail queued for delivery) D43787F1D: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=0.07, delays=0.06/0/0/0.01, dsn=2.0.0, status=sent (250 Mail queued for delivery) E7CDF7F15: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=412, delays=411/0/0/0.62, dsn=2.0.0, status=sent (250 Mail queued for delivery) E7CDF7F15: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=412, delays=411/0/0/0.62, dsn=2.0.0, status=sent (250 Mail queued for delivery) E7CDF7F15: to=<[email protected]>, relay=192.168.1.21[192.168.1.21]:25, delay=412, delays=411/0/0/0.62, dsn=2.0.0, status=sent (250 Mail queued for delivery) Regards,Fred​ On Tue, 01/15/2013 10:14 PM, Wietse Venema <[email protected]> wrote: > Fred Ho: > > Hi, > > This is the external mail gateway which direct the incoming messages > > to the backend mail server which do the actual delivery. This is > > defined in the transport file as:ss-intl.com smtp:[192.168.1.21] > > What are the typical data rates for small and for large messages? > You get this from the postfix logfile records. > > postfix/smtpd client=x.x.x.x gives the approximate start of transmission. > > qmgr size=xxx gives the message size and approximate end of transmission. > > Combining these gives you the data rates. > > Wietse > >
