[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: sendmail or bind problems



Check!

Are you a victim of linuxconf?
It has used different tables to the standard sendmail distribution generated
configuration.
It's left me configuring the files in multiple files in /etc/mail.  Perhaps
you've done your config, in a file you're not using.

Have you tried using the IP address, as a number rather than symbolically?
The DNS PTR lookup may not be resolving quite how you expect.

Rob

----- Original Message -----
From: "R. W. Rodolico" <rodo@dailydatainc.com>
To: <debian-isp@lists.debian.org>
Sent: Tuesday, October 24, 2000 3:36 AM
Subject: RE: sendmail or bind problems


> Thanks for all the suggestions. I do have brion-enterprises.com and
> their ISP listed in /etc/mail/relay-domains and have brion-
> enterprises.com in /etc/mail/local-host-names.
>
> I believe the problem is with the target SMTP server, and I'd rather
> look like a fool here than with them. Attached is a transcript if
> anyone has time to look at it.
>
> Thanks for all the suggestions before.
>
> Rod
>
> > > -----Original Message-----
> > > From: R. W. Rodolico [mailto:rodo@dailydatainc.com]
> > > Sent: Monday, October 23, 2000 2:15 AM
> > > To: debian-isp@lists.debian.org
> > > Subject: sendmail or bind problems
> > >
> > >
> > > I am running sendmail 8.9.3-23. I host several small web sites. One
> of
> > > my clients is sending mail and the receiving server denies it
> because
> > > it says "Relaying Denied," I assume because my client is coming
> from my
> > > mail server (tully.dailydatainc.com) but has their return address
> > > (brion-enterprises.com) in the "From" field.
> > >
> > > I am using one IP address for everyone.
> > >
> > > Any ideas?
> > >
> > > I can send the headers if necessary.
> > >
> > > Thanks,
> > >
> > > Rod
> > >
> > >
> > > --
> > > To UNSUBSCRIBE, email to debian-isp-request@lists.debian.org
> > > with a subject of "unsubscribe". Trouble? Contact
> > > listmaster@lists.debian.org
> > >
> >
> >
>
> R. W. Rodolico
> Daily Data, Inc.
> POB 140465
> Dallas  TX  75214-0465
> 214.827.2170
>
> It appears I could be pursuing an untamed ornithoid to no purpose.
>             --Brent Spiner as Data, Star Trek: The Next Generation
>


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


> Received: by tully (mbox stargazer)
>  (with Cubic Circle's cucipop (v1.31 1998/05/13) Thu Oct 12 06:15:26 2000)
> X-From_: MAILER-DAEMON  Thu Oct 12 06:03:11 2000
> Return-Path: <MAILER-DAEMON>
> Received: from localhost (localhost)
> by tully.dailydatainc.com (8.9.3/8.9.3/Debian 8.9.3-21) with internal id
GAA22667;
> Thu, 12 Oct 2000 06:03:11 -0500
> Date: Thu, 12 Oct 2000 06:03:11 -0500
> From: Mail Delivery Subsystem <MAILER-DAEMON>
> Message-Id: <200010121103.GAA22667@tully.dailydatainc.com>
> To: <stargazer@brion-enterprises.com>
> MIME-Version: 1.0
> Content-Type: multipart/report; report-type=delivery-status;
> boundary="GAA22667.971348591/tully.dailydatainc.com"
> Subject: Returned mail: User unknown
> Auto-Submitted: auto-generated (failure)
> X-Mozilla-Status2: 00000000
>
> This is a MIME-encapsulated message
>
> --GAA22667.971348591/tully.dailydatainc.com
>
> The original message was received at Thu, 12 Oct 2000 06:03:09 -0500
> from [209.30.224.148]
>
>    ----- The following addresses had permanent fatal errors -----
> <jrs@directv.com>
>
>    ----- Transcript of session follows -----
> ... while talking to smtp1.san.cerf.net.:
> >>> RCPT To:<jrs@directv.com>
> <<< 550 <jrs@directv.com>... Relaying denied
> 550 <jrs@directv.com>... User unknown
>
> --GAA22667.971348591/tully.dailydatainc.com
> Content-Type: message/delivery-status
>
> Reporting-MTA: dns; tully.dailydatainc.com
> Received-From-MTA: DNS; [209.30.224.148]
> Arrival-Date: Thu, 12 Oct 2000 06:03:09 -0500
>
> Final-Recipient: RFC822; jrs@directv.com
> Action: failed
> Status: 5.1.1
> Remote-MTA: DNS; smtp1.san.cerf.net
> Diagnostic-Code: SMTP; 550 <jrs@directv.com>... Relaying denied
> Last-Attempt-Date: Thu, 12 Oct 2000 06:03:11 -0500
>
> --GAA22667.971348591/tully.dailydatainc.com
> Content-Type: message/rfc822
>
> Return-Path: <stargazer@brion-enterprises.com>
> Received: from brion-enterprises.com ([209.30.224.148])
> by tully.dailydatainc.com (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id
GAA22665
> for <jrs@directv.com>; Thu, 12 Oct 2000 06:03:09 -0500
> X-Authentication-Warning: tully.dailydatainc.com: Host [209.30.224.148]
claimed to be brion-enterprises.com
> Message-ID: <39E59B27.BD411976@brion-enterprises.com>
> Date: Thu, 12 Oct 2000 06:06:15 -0500
> From: bart brion <stargazer@brion-enterprises.com>
> Organization: B&H Commercial Services
> X-Mailer: Mozilla 4.72 [en] (Win98; U)
> X-Accept-Language: en
> MIME-Version: 1.0
> To: "Swindal, James R" <jrs@directv.com>
> Subject: Re: B&H Leads.xls
> References: <4FD5D5BC751CD411B2D30008C7A489C9011391D4@libra.directv.com>
> Content-Type: multipart/alternative;
>  boundary="------------7FE492F2DE626B4B01F4FCF3"
>
>
> --------------7FE492F2DE626B4B01F4FCF3
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> I'm glad that you sent again, I didn't get the first one.
> Bart
>
> "Swindal, James R" wrote:
>
> >
> >
> >                I may have sent this yesterday, but I want to make sure
> >                you received it.
> >                <<B&H Leads.xls>>
> >
>
> --------------7FE492F2DE626B4B01F4FCF3
> Content-Type: text/html; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
> <html>
> I'm glad that you sent again, I didn't get the first one.
> <br>Bart
> <p>"Swindal, James R" wrote:
> <blockquote TYPE=CITE>&nbsp;
> <ul>
> <ul>
> <ul><font face="Arial">I may have sent this yesterday, but I want to make
> sure you received it.</font>
> <br><font face="Arial"><font color="#000000"><font size=-1>&lt;&lt;B&amp;H
> Leads.xls>></font></font></font></ul>
> </ul>
> </ul>
> </blockquote>
> </html>
>
> --------------7FE492F2DE626B4B01F4FCF3--
>
>
> --GAA22667.971348591/tully.dailydatainc.com--
>
>
>



Reply to: