Some requestors not getting correspondence

Hi All,

A small number of requestors are not getting email from RT. Usually the
requestors are from the same domain - eg bob@domain.net.nz or
peter@domain.net.nz and effects a couple of domains.

We have RT installed on a Redhat 8 box. The box sits behind a firewall on a
intranet using a public address. We us fetchmail to pull incoming emails
from a mail server in our DMZ. Email is sent directly through the firewall
from our RT box using sendmail.

I was thinking that maybe the mailserver on these domains is putting these
emails into a black hole thinking they are spam - we don’t get any ‘can not
deliver’ responses.

Below is an example of the the autogenerated reply that doesn’t get to
requestors. I though a couple of things might cause problems but not sure -
generic return-path, mydomain.co.nz isn’t a real domain (ie no reverse
lookup). I changed the Precedence to Normal but this doesn’t seem to make
any differenct.

Any help appreciated. Greg.

Return-Path: mail@localhost.localdomain
Delivered-To: elisara@world-net.co.nz
Received: (qmail 30754 invoked from network); 5 Feb 2003 01:13:41 -0000
Received: from 210-54-18-149.iprolink.co.nz (HELO mailserver.mydomain.co.nz)
(210.54.18.149)
by 0 with SMTP; 5 Feb 2003 01:13:41 -0000
Received: from mailserver.mydomain.co.nz (mailserver [127.0.0.1])
by mailserver.mydomain.co.nz (8.12.5/8.12.5) with ESMTP id
h151OaE7006319
for elisara@world-net.co.nz; Wed, 5 Feb 2003 14:24:36 +1300
Received: (from mail@localhost)
by mailserver.mydomain.co.nz (8.12.5/8.12.5/Submit) id h151Oa0X006315;
Wed, 5 Feb 2003 14:24:36 +1300Date: Wed, 5 Feb 2003 14:24:36 +1300
Subject: [realgroovy.co.nz #1696] AutoReply: Another Test from Greg
From: “orders” orders@realgroovy.co.nz
Reply-To: orders@realgroovy.co.nz
In-Reply-To: rt-1696@realgroovy.co.nz
Message-ID: rt-1696-7450.10.1945318512567@realgroovy.co.nz
Precedence: Normal
X-RT-Loop-Prevention: realgroovy.co.nz
RT-Ticket: realgroovy.co.nz #1696
Managed-by: RT 2.0.15 (Request Tracker — Best Practical Solutions)
RT-Originator: elisara@world-net.co.nz
To: elisara@world-net.co.nz

Welcome to Real Groovy Customer Support. This message has been automatically
generated in response to your enquiry regarding:

        "Another Test from Greg",

a summary of which appears below. We have registered your enquiry and will
be in touch soon. There is no need to reply to this message.

Our normal hours of operation are NZDT 8.30am to 5.30pm Monday to Friday.
Your enquiry has been assigned an ID of

     [realgroovy.co.nz #1696].

Thank you,
Real Groovy

Testing, 1, 2, 3.

Hi All,

A small number of requestors are not getting email from RT. Usually the
requestors are from the same domain - eg bob@domain.net.nz or
peter@domain.net.nz and effects a couple of domains.

We have RT installed on a Redhat 8 box. The box sits behind a firewall on a
intranet using a public address. We us fetchmail to pull incoming emails
from a mail server in our DMZ. Email is sent directly through the firewall
from our RT box using sendmail.

I was thinking that maybe the mailserver on these domains is putting these
emails into a black hole thinking they are spam - we don’t get any ‘can not
deliver’ responses.

Below is an example of the the autogenerated reply that doesn’t get to
requestors. I though a couple of things might cause problems but not sure -
generic return-path, mydomain.co.nz isn’t a real domain (ie no reverse
lookup). I changed the Precedence to Normal but this doesn’t seem to make
any differenct.

Any help appreciated. Greg.

Return-Path: mail@localhost.localdomain
Delivered-To: elisara@world-net.co.nz
Received: (qmail 30754 invoked from network); 5 Feb 2003 01:13:41 -0000
Received: from 210-54-18-149.iprolink.co.nz (HELO mailserver.mydomain.co.nz)
(210.54.18.149)
by 0 with SMTP; 5 Feb 2003 01:13:41 -0000
Received: from mailserver.mydomain.co.nz (mailserver [127.0.0.1])
by mailserver.mydomain.co.nz (8.12.5/8.12.5) with ESMTP id
h151OaE7006319
for elisara@world-net.co.nz; Wed, 5 Feb 2003 14:24:36 +1300
Received: (from mail@localhost)
by mailserver.mydomain.co.nz (8.12.5/8.12.5/Submit) id h151Oa0X006315;
Wed, 5 Feb 2003 14:24:36 +1300Date: Wed, 5 Feb 2003 14:24:36 +1300
Subject: [realgroovy.co.nz #1696] AutoReply: Another Test from Greg
From: “orders” orders@realgroovy.co.nz
Reply-To: orders@realgroovy.co.nz
In-Reply-To: rt-1696@realgroovy.co.nz
Message-ID: rt-1696-7450.10.1945318512567@realgroovy.co.nz
Precedence: Normal
X-RT-Loop-Prevention: realgroovy.co.nz
RT-Ticket: realgroovy.co.nz #1696
Managed-by: RT 2.0.15 (Request Tracker — Best Practical Solutions)
RT-Originator: elisara@world-net.co.nz
To: elisara@world-net.co.nz

Welcome to Real Groovy Customer Support. This message has been automatically
generated in response to your enquiry regarding:

        "Another Test from Greg",

a summary of which appears below. We have registered your enquiry and will
be in touch soon. There is no need to reply to this message.

Our normal hours of operation are NZDT 8.30am to 5.30pm Monday to Friday.
Your enquiry has been assigned an ID of

     [realgroovy.co.nz #1696].

Thank you,
Real Groovy

Testing, 1, 2, 3.

Hi All,

A small number of requestors are not getting email from RT. Usually the
requestors are from the same domain - eg bob@domain.net.nz or
peter@domain.net.nz and effects a couple of domains.

We have RT installed on a Redhat 8 box. The box sits behind a firewall on a
intranet using a public address. We us fetchmail to pull incoming emails
from a mail server in our DMZ. Email is sent directly through the firewall
from our RT box using sendmail.

I was thinking that maybe the mailserver on these domains is putting these
emails into a black hole thinking they are spam - we don’t get any ‘can not
deliver’ responses.

Below is an example of the the autogenerated reply that doesn’t get to
requestors. I though a couple of things might cause problems but not sure -
generic return-path, mydomain.co.nz isn’t a real domain (ie no reverse
lookup). I changed the Precedence to Normal but this doesn’t seem to make
any differenct.

Any help appreciated. Greg.

Return-Path: mail@localhost.localdomain
Delivered-To: elisara@world-net.co.nz
Received: (qmail 30754 invoked from network); 5 Feb 2003 01:13:41 -0000
Received: from 210-54-18-149.iprolink.co.nz (HELO mailserver.mydomain.co.nz)
(210.54.18.149)
by 0 with SMTP; 5 Feb 2003 01:13:41 -0000
Received: from mailserver.mydomain.co.nz (mailserver [127.0.0.1])
by mailserver.mydomain.co.nz (8.12.5/8.12.5) with ESMTP id
h151OaE7006319
for elisara@world-net.co.nz; Wed, 5 Feb 2003 14:24:36 +1300
Received: (from mail@localhost)
by mailserver.mydomain.co.nz (8.12.5/8.12.5/Submit) id h151Oa0X006315;
Wed, 5 Feb 2003 14:24:36 +1300Date: Wed, 5 Feb 2003 14:24:36 +1300
Subject: [realgroovy.co.nz #1696] AutoReply: Another Test from Greg
From: “orders” orders@realgroovy.co.nz
Reply-To: orders@realgroovy.co.nz
In-Reply-To: rt-1696@realgroovy.co.nz
Message-ID: rt-1696-7450.10.1945318512567@realgroovy.co.nz
Precedence: Normal
X-RT-Loop-Prevention: realgroovy.co.nz
RT-Ticket: realgroovy.co.nz #1696
Managed-by: RT 2.0.15 (Request Tracker — Best Practical Solutions)
RT-Originator: elisara@world-net.co.nz
To: elisara@world-net.co.nz

Welcome to Real Groovy Customer Support. This message has been automatically
generated in response to your enquiry regarding:

        "Another Test from Greg",

a summary of which appears below. We have registered your enquiry and will
be in touch soon. There is no need to reply to this message.

Our normal hours of operation are NZDT 8.30am to 5.30pm Monday to Friday.
Your enquiry has been assigned an ID of

     [realgroovy.co.nz #1696].

Thank you,
Real Groovy

Testing, 1, 2, 3.

A small number of requestors are not getting email from RT. Usually the
requestors are from the same domain - eg bob@domain.net.nz or
peter@domain.net.nz and effects a couple of domains.

Email is sent directly through the firewall from our RT box using
sendmail.

I was thinking that maybe the mailserver on these domains is putting these
emails into a black hole thinking they are spam - we don’t get any ‘can not
deliver’ responses.

sounds plausible. I’d run tcpflow on the rt box, and see if you can
capture RT sending mail to them. Either you’ll be able to, in which
case there’s not much you can do to fix it, or there’ll be some more
serious problem with your rt setup.

seph