Re: Re: Newsgroups beef (was Stock inflaters?)

"Mike Easter" <[email protected]>
Newsgroups gmane.mail.spam.spamcop.help
Organization SpamCop
Message-ID <[email protected]>
[email protected] wrote:
> Mike the problem we are having is that 2 of our partners, 1 of whom is
> listed in the email, have been receiving this 5.4.7 error message
> whenever they send email to us.

But I'm still not 'getting it'.  Partner1 tries to email you.  If we
were looking at the headers of the DSN message which partner1 receives,
we would be able to tell if partner1 were receiving that message from
his own provider or if partner1 were receiving a newmail generated by
the recipient server, perhaps namely yours.

> This started happening over the past
> two weeks. We have check our settings on our Surf SMTP server, our
> firewall, our DNS and there is nothing blocking these accounts.  We
> are trying to find out what else may be causing the problem why just
> these 2 are not able to reach us and thousands of others are just
> fine.

How did you conclude that your server was generating these reports?  You
haven't shown me that part in a way which I understand yet.

> This is from our vendor Inovis

I don't know who vendor Inovis is.

> From: Mail Delivery System [mailto:[email protected]]

I have seen that strange nonrouting domainname before in an earlier
thread here.  Whichever mailerdaemons you post are 'non-existent' from a
routing point of view.

From: [email protected]
Newsgroups: spamcop.help
Subject: Mail not delivered
Date: Mon, 3 Oct 2005 09:24:24 -0500
Message-ID: <[email protected]>

> Subject: Delivery Status Notification (Failure)
>
> The following message to was undeliverable.
> The reason for the problem:
> 5.4.7 - Delivery expired (message too old) ''

You are pasting a body of something or other when you need to be pasting
its headers to aid in its understanding.

-- 
Mike Easter
kibitzer, not SC admin
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.