<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Reason: AGED MESSAGE in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/reason-aged-message/m-p/3888653#M25802</link>
    <description>As it says, the message is aged... i.e. old.&lt;BR /&gt;&lt;BR /&gt;Look at the dates in the message header.&lt;BR /&gt;The original message was sent on Oct 08, but the error message is generated on Oct 30. This message has apparently been stuck in a queue somewhere for more than three weeks.&lt;BR /&gt;&lt;BR /&gt;It's a fairly common tactic of junk emailers to send mail with a forged date, to make their ads either first or last in the receiver's mailbox. Looks like someone at amosconnect.com has decided to block emails that are older than some specified amount of time.&lt;BR /&gt;&lt;BR /&gt;If amosconnect.com's mail server has had problems, the people at amosconnect.com may lose some email because of their aggressive filtering. If you are not the postmaster@amosconnect.com, there is very little you can do about it. &lt;BR /&gt;&lt;BR /&gt;If the message was important, it might be appropriate to try and call someone at amosconnect.com and ensure they know their email service has been unreliable.&lt;BR /&gt;&lt;BR /&gt;But it looks like your original message was sent on a list of recipients, and master.endless4@amosconnect.com was only one of them. Many automated mailing list administration systems have a feature that unsubscribes any addresses that repeatedly produce error messages. If this error message repeats, you might consider removing this recipient from your mailing list.</description>
    <pubDate>Mon, 30 Oct 2006 03:56:05 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2006-10-30T03:56:05Z</dc:date>
    <item>
      <title>Reason: AGED MESSAGE</title>
      <link>https://community.hpe.com/t5/operating-system-linux/reason-aged-message/m-p/3888652#M25801</link>
      <description>Dear All,&lt;BR /&gt;&lt;BR /&gt;Good Day!&lt;BR /&gt;&lt;BR /&gt;there are failure delivery from Postmaster@amosconnect.com&lt;BR /&gt;on my mail server.The delivery was as following&lt;BR /&gt;*********************************************&lt;BR /&gt;Your message&lt;BR /&gt;&lt;BR /&gt;    To:      NewsLinkServices@mail.newslinkservices.net&lt;BR /&gt;    Subject: NewsLink Philippines (Zip) 10/08/2006&lt;BR /&gt;    Date:    Sun Oct 08 15:10:48 2006&lt;BR /&gt;&lt;BR /&gt;could not be delivered to the following destination(s):&lt;BR /&gt;&lt;BR /&gt;    Bcc:    master.endless4@amosconnect.com &lt;ADMIN&gt;&lt;BR /&gt;    Reason: AGED MESSAGE&lt;BR /&gt;    Date:   Mon Oct 30 01:15:11 2006 UTC&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Received: from NLBUMR01 (localhost.xantic.priv [127.0.0.1]) by mailrelay1.xantic.net (Postfix) with ESMTP id A92845D345 for &lt;MASTER.ENDLESS4&gt;; Sun,  8 Oct 2006 16:16:07 +0000 (UTC)&lt;BR /&gt;Received: from mailrelay1.xantic.net ([212.165.122.18]) by localhost (mailrelay1.xantic.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A8ueEQFMUdt4 for &lt;MASTER.ENDLESS4&gt;; Sun,  8 Oct 2006 16:16:03 +0000 (UTC)&lt;BR /&gt;Received: from mail.newslinkservices.net (unknown [59.144.173.101]) by mailrelay1.xantic.net (Postfix) with ESMTP id 34F135CB30 for &lt;MASTER.ENDLESS4&gt;; Sun,  8 Oct 2006 15:09:50 +0000 (UTC)&lt;BR /&gt;Received: from 192.168.0.2 ([192.168.0.10]) by mail.newslinkservices.net (8.12.10/8.12.10) with ESMTP id k98F6HWF005749 for &lt;MASTER.ENDLESS4&gt;; Sun, 8 Oct 2006 20:37:22 +0530&lt;BR /&gt;Message-Id: &amp;lt;200610081507.k98F6HWF005749@mail.newslinkservices.net&amp;gt;&lt;BR /&gt;From: NewsLink &lt;TRANSMISSION&gt;&lt;BR /&gt;To: NewsLinkServices@mail.newslinkservices.net&lt;BR /&gt;Subject: NewsLink Philippines (Zip) 10/08/2006&lt;BR /&gt;Date: 08 Oct 2006 20:40:48 +0530&lt;BR /&gt;X-Priority: 5&lt;BR /&gt;X-MSMail-Priority: Low&lt;BR /&gt;Mime-Version: 1.0&lt;BR /&gt;Content-Type: multipart/mixed; boundary="----=_TZXCuJBc~ucL2q9vt-MM"&lt;BR /&gt;X-Anti-Virus: Kaspersky Anti-Virus for MailServers 5.5.10/RELEASE, bases: 08102006 #216663, status: clean&lt;BR /&gt;********************************************&lt;BR /&gt;&lt;BR /&gt;Plz suggest where is the problems.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Manoj&lt;/TRANSMISSION&gt;&lt;/MASTER.ENDLESS4&gt;&lt;/MASTER.ENDLESS4&gt;&lt;/MASTER.ENDLESS4&gt;&lt;/MASTER.ENDLESS4&gt;&lt;/ADMIN&gt;</description>
      <pubDate>Sun, 29 Oct 2006 22:45:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/reason-aged-message/m-p/3888652#M25801</guid>
      <dc:creator>monu_1</dc:creator>
      <dc:date>2006-10-29T22:45:54Z</dc:date>
    </item>
    <item>
      <title>Re: Reason: AGED MESSAGE</title>
      <link>https://community.hpe.com/t5/operating-system-linux/reason-aged-message/m-p/3888653#M25802</link>
      <description>As it says, the message is aged... i.e. old.&lt;BR /&gt;&lt;BR /&gt;Look at the dates in the message header.&lt;BR /&gt;The original message was sent on Oct 08, but the error message is generated on Oct 30. This message has apparently been stuck in a queue somewhere for more than three weeks.&lt;BR /&gt;&lt;BR /&gt;It's a fairly common tactic of junk emailers to send mail with a forged date, to make their ads either first or last in the receiver's mailbox. Looks like someone at amosconnect.com has decided to block emails that are older than some specified amount of time.&lt;BR /&gt;&lt;BR /&gt;If amosconnect.com's mail server has had problems, the people at amosconnect.com may lose some email because of their aggressive filtering. If you are not the postmaster@amosconnect.com, there is very little you can do about it. &lt;BR /&gt;&lt;BR /&gt;If the message was important, it might be appropriate to try and call someone at amosconnect.com and ensure they know their email service has been unreliable.&lt;BR /&gt;&lt;BR /&gt;But it looks like your original message was sent on a list of recipients, and master.endless4@amosconnect.com was only one of them. Many automated mailing list administration systems have a feature that unsubscribes any addresses that repeatedly produce error messages. If this error message repeats, you might consider removing this recipient from your mailing list.</description>
      <pubDate>Mon, 30 Oct 2006 03:56:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/reason-aged-message/m-p/3888653#M25802</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2006-10-30T03:56:05Z</dc:date>
    </item>
    <item>
      <title>Re: Reason: AGED MESSAGE</title>
      <link>https://community.hpe.com/t5/operating-system-linux/reason-aged-message/m-p/3888654#M25803</link>
      <description>Hi Matti,&lt;BR /&gt;&lt;BR /&gt;Good Day!&lt;BR /&gt;&lt;BR /&gt;A very thanks for your suggetion.So It means that, this is not my end problem.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;With Regards,&lt;BR /&gt;Manoj</description>
      <pubDate>Mon, 30 Oct 2006 05:19:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/reason-aged-message/m-p/3888654#M25803</guid>
      <dc:creator>monu_1</dc:creator>
      <dc:date>2006-10-30T05:19:52Z</dc:date>
    </item>
  </channel>
</rss>

