Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Deferred: Connection refused by conservus.ca

Posted on 2006-06-21
1
1,029 Views
Last Modified: 2013-12-17
Hello

I have a mail server that we call Discovery 192.168.1.30.
Our MX record point to mail.montrealinfo.com 192.168.1.30.
We don't have an MX record for conciergeinfo.com and conservus.ca even though we own these domains.

Then we have a faxserver that we call FAXSERVER 192.168.1.40
That server is used exclusively to send our weekly publication by FAX throught hylafax and by EMAIL through SENDMAIL.  The email is sent with the address infolettre@conservus.ca  (not @montrealinfo.com which is our primary email).

*** All info about SENDMAIL configuration on both server are at the end ***

  The problem is that the FAXSERVER doesn't seem to know "conservus.ca" at all.  I noticed that because, each week, there are many bouncing emails coming back to the FAXSERVER for the email infolettre@conservus.ca, but the server doesn't know what to do with @conservus.ca emails, so i received a Postmaster notify: see transcript for details from postmaster@faxserver.montrealinfo.com saying this :

----------------------------------------------------------------

To: postmaster@faxserver.montrealinfo.com
Subject: Postmaster notify: see transcript for details

The original message was received at Thu, 15 Jun 2006 19:40:42 -0400
from localhost
with id k5FNOgAE019426

   ----- The following addresses had permanent fatal errors -----
<infolettre@conservus.ca>

   ----- Transcript of session follows -----
<infolettre@conservus.ca>... Deferred: Connection refused by conservus.ca.
Message could not be delivered for 5 days
Message will be deleted from queue

Reporting-MTA: dns; faxserver.montrealinfo.com
Arrival-Date: Thu, 15 Jun 2006 19:40:42 -0400

Final-Recipient: RFC822; infolettre@conservus.ca
Action: failed
Status: 4.4.7
Remote-MTA: DNS; conservus.ca
Last-Attempt-Date: Tue, 20 Jun 2006 20:33:32 -0400

Return-Path: <MAILER-DAEMON>
Received: from localhost (localhost)
      by faxserver.montrealinfo.com (8.12.8/8.12.8) id k5FNOgAE019426;
      Thu, 15 Jun 2006 19:40:42 -0400
Date: Thu, 15 Jun 2006 19:40:42 -0400
From: Mail Delivery Subsystem <MAILER-DAEMON>
Message-Id: <200606152340.k5FNOgAE019426@faxserver.montrealinfo.com>
To: <infolettre@conservus.ca>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
      boundary="k5FNOgAE019426.1150414842/faxserver.montrealinfo.com"
Subject: Warning: could not send message for past 4 hours
Auto-Submitted: auto-generated (warning-timeout)

    **********************************************
    **      THIS IS A WARNING MESSAGE ONLY      **
    **  YOU DO NOT NEED TO RESEND YOUR MESSAGE  **
    **********************************************

The original message was received at Thu, 15 Jun 2006 15:13:45 -0400
from [192.168.1.129]

   ----- Transcript of session follows -----
451 navgolfexpress.com: Name server timeout
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old

Reporting-MTA: dns; faxserver.montrealinfo.com
Arrival-Date: Thu, 15 Jun 2006 15:13:45 -0400

Final-Recipient: RFC822; info@navgolfexpress.com
Action: delayed
Status: 4.4.3
Last-Attempt-Date: Thu, 15 Jun 2006 19:40:42 -0400
Will-Retry-Until: Tue, 20 Jun 2006 15:13:45 -0400

Return-Path: <infolettre@conservus.ca>
Received: from [ATLAS] ([192.168.1.129])
      by faxserver.montrealinfo.com (8.12.8/8.12.8) with ESMTP id k5FJD7AB003022
      for <info@navgolfexpress.com>; Thu, 15 Jun 2006 15:13:45 -0400
Message-Id: <200606151913.k5FJD7AB003022@faxserver.montrealinfo.com>
From: "Infoletter Team" <infolettre@conservus.ca>
To: "Stephen St-Pierre" <info@navgolfexpress.com>
Subject: Infolettre no. 539
Date: Thu, 15 Jun 2006 15:14:50 -400
MIME-Version: 1.0
Content-Type: multipart/mixed;
      boundary="----=_123X456_000_05B23C6E"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Dacons mail.it 2 (PC)

Good day,
...

------------------------------------------

Here is the info and config about sendmail on Discovery

• file "access"

localhost                      RELAY
127.0.0.1                     RELAY
192.168                       RELAY
montrealinfo.com         RELAY
conciergeinfo.com        RELAY
10.0.18                       RELAY
conservus.ca               RELAY

*** montrealinfo.com - conciergeinfo.com - conservus.ca are our company websites.

• file "local-host-names"

discovery.montrealinfo.com
mail.montrealinfo.com
mail.conciergeinfo.com
mail.conservus.ca
montrealinfo.com
conciergeinfo.com
conservus.ca

• file "relay-domains"

192.168
montrealinfo.com
conciergeinfo.com
10.0.18
10.0.19
conservus.ca
faxserver.montrealinfo.com


----------------------------------

Here is the info and config about sendmail on Discovery

• file "access"

localhost                       RELAY
127.0.0.1                       RELAY
192.168                         RELAY
montrealinfo.com                RELAY
conciergeinfo.com               RELAY
conservus.ca                    RELAY

• file "local-host-names"

faxserver.montrealinfo.com

• file "relay-domains"

192.168
montrealinfo.com
conciergeinfo.com
conservus.ca

-----------------------

Have any clue???

Thanks,
Martin
0
Comment
Question by:mlegros
1 Comment
 
LVL 27

Accepted Solution

by:
Nopius earned 500 total points
ID: 17006129
faxserver.montrealinfo.com doesn't know _WHERE_ to relay mail to domain conservus.ca (I suppose it uses address 66.38.180.26).

You may either point conservus.ca to Discovery in /etc/hosts on faxserver:
/etc/hosts:
192.168.1.30 conservus.ca

OR
to change mailertable rules on faxserver like this
probably it's a 'mailertable' file:

conserver.ca                 smtp:192.168.1.30
0

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
As tax season makes its return, so does the increase in cyber crime and tax refund phishing that comes with it
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question