Mailing List Message #97602
From: Tim Pickard <>
Subject: Re: "we refuse to relay" and mailman
Date: Mon, 23 Mar 2009 14:00:20 -0400
To: CommuniGate Pro Discussions <>
I replied earlier but did not see it hit the list.  So I added the log as a link:

Hi and thanks for the reply,

Below are the sanitized log entries to protect the innocent and not so innocent.  Coworkers volunteered to get mail from the testlist to their accounts and personal outside emails.

I tried to keep all the relevant entries.  I cut out the LOCAL deliveries as they are not part of the problem.

One other wrinkle that may or may not impact this issue is that we do use Postini service for our incoming mail.  Thus, our MX records point to their service and not back to our own outgoing IP.


Lyle Giese wrote:
'We refuse to relay' means the remote host thinks you are asking it to
relay (redirect or trying to send email via them to a remote host they
are not responsible for).  Not that they think you relayed the message.

You are missing some other detail here yet.  Relaying has nothing to do
really with SPF and if they thought it was an SPF failure most hosts
just silently drop the incoming email.  So I think you can eliminate SPF

You have Mailman setup to use your CGPro server as a smart host from
what info you are showing.

I think there is something else that is wrong that is not shown here
yet.   I would set the smtp sending log level to low level and you could
trace the message via the id (13608339 in this example) to get more
detail.  And in between the Queued and Dequerer message should be some
detail(not referenced by the message id unfortunately) that will be
helpful.  But you get a tight time frame based on timestamps and will
have a good idea where to look.

Lyle wrote:
Hello all,

I have a problem with my email list messages being rejected by remote
20:37:18.994 1 DEQUEUER [13608339] SMTP(
failed: we refuse to relay

Initially, I thought this might be an SPF issue and updated our SPF
record in the DNS.  No change.

Perhaps it was the way the headers appeared.
"Received: from [] (HELO localhost.localdomain)
  by (CommuniGate Pro SMTP 5.2.10)
  with ESMTP id 13607978; Sat, 21 Mar 2009 17:51:36 -0400"

Editing the hosts file to put the server IP and name in the first line
did not change the behavior.
"Received: from [] (HELO
  by (CommuniGate Pro SMTP 5.2.10)
  with ESMTP id 13608028; Sat, 21 Mar 2009 18:12:55 -0400"

I changed Mailman to force it to use the host instead of the loopback.
Still rejected.
Finally I reconfigured Mailman to use SMTP_AUTH and port 587 to send
out mail.  Still it appears to remote hosts as if they are relayed

I am stumped here.  Users do not have this problem sending messages
directly to the users in the list.

The last failed message headers:
Return-Path: <>
Received: from [] (account mailmansend HELO
  by (CommuniGate Pro SMTP 5.2.10)
  with ESMTPA id 13608338; Sat, 21 Mar 2009 20:37:18 -0400
Received: from [] (account
    by (CommuniGate Pro WEBUSER 5.2.10)
    with HTTP id 13608337 for;
    Sat, 21 Mar 2009 20:37:07 -0400
From: <>
X-Mailer: CommuniGate Pro WebUser v5.2.10
Date: Sat, 21 Mar 2009 20:37:07 -0400
Message-ID: <>

The IP's are Client IP ranged.

What is making this appear to be a relayed message to the remote host?

Thanks for your help


This message is sent to you because you are subscribed to
  the mailing list <>.
To unsubscribe, E-mail to: <>
To switch to the DIGEST mode, E-mail to <>
To switch to the INDEX mode, E-mail to <>
Send administrative queries to  <>

Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster