Google Answers Logo
View Question
 
Q: Issues with Secondary SMTP (sendmail) Server ( No Answer,   0 Comments )
Question  
Subject: Issues with Secondary SMTP (sendmail) Server
Category: Computers > Programming
Asked by: jbulow-ga
List Price: $25.00
Posted: 15 Jun 2006 19:37 PDT
Expires: 03 Jul 2006 05:55 PDT
Question ID: 738577
I'm having some trouble with our web-generated emails (like
newsletters, contact forms, etc.) are not valid due to some issues
with sendmail, so they are being filtered out my spam filters. Our
company's mail is handled by ElectricMail (MX records are set to
inbound.electric.net). However, we need to be able to send -valid-
messages from our web server (www.thedomain.com) (which runs on Fedora
Core 3).

Here are the problems that the spam filters identify in the messages...

- HELO doesn't use FQDN 
- Sending IP's PTR record doesn't match HELO 
- Sending IP's PTR record is full of numbers (so is probably bogus as
far as spam filters see the world)
- Message ID illegal (no FQDN)

Here are the headers of the message.....

Return-Path: <apache@localhost.localdomain>
Received: from localhost.localdomain
(customer-reverse-entry.111.222.333.444 [111.222.333.444] (may be
forged))
 by receiver-domain.com (4.13.10/4.13.10) with ESMTP id k5CFra3R024823
 for <user@receiver-domain.com>; Mon, 12 Jun 2006 11:53:38 -0400
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
 by localhost.localdomain (4.13.10/4.13.10) with ESMTP id k5D0vpHV000975
 for <user@receiver-domain.com>; Mon, 12 Jun 2006 17:57:51 -0700
Received: (from apache@localhost)
 by localhost.localdomain (4.13.10/4.13.10/Submit) id k5D0vdmM000973;
 Mon, 12 Jun 2006 17:57:39 -0700
Date: Mon, 12 Jun 2006 17:57:39 -0700
Message-Id: <200606130057.k5D0vdmM000973@localhost.localdomain>
To: user@receiver-domain.com
Subject: Message from 1
From: user@somedomain.com
Content-type: text/html

I imagined that many of these problems might be able to be fixed by
changing the hostname, and perhaps a few headers in PHP. But
basically, when I change the /etc/hosts file on the web server to
say...

111.222.333.444     www.thedomain.com

it starts sending any emails that are to something@thedomain.com to
itself, instead of using the MX record indicated in thedomain.com
(which is inbound.electric.net). This obviously is not very helpful,
since nobody connects to the web server (www.thedomain.com) to
retrieve their mail. I can fix this problem by taking out that line.
However, the first set of problems still exists (which is what I'm
looking to fix, primarily).

Some of these problems can be fixed, to a limited extent by changing
headers in PHP, but many of these headers refuse to change, probably
due to configuration settings. Perhaps reverse DNS is required? I'm
not sure (and I'm not sure where to start with that regarding
sendmail).

I've taken a look at the sendmail.cf and sendmail.mc files, but don't
know where to begin on that issue, or if changing those files is part
of the solution. I'm more of a web developer than a sys admin. If
someone could give a few suggestions on where to start (or more detail
would be -very- welcome :), it would certainly be greatly appreciated.

Thanks very much. I certainly appreciate any help.

- Jonathan
Answer  
There is no answer at this time.

Comments  
There are no comments at this time.

Important Disclaimer: Answers and comments provided on Google Answers are general information, and are not intended to substitute for informed professional medical, psychiatric, psychological, tax, legal, investment, accounting, or other professional advice. Google does not endorse, and expressly disclaims liability for any product, manufacturer, distributor, service or service provider mentioned or any opinion expressed in answers or comments. Please read carefully the Google Answers Terms of Service.

If you feel that you have found inappropriate content, please let us know by emailing us at answers-support@google.com with the question ID listed above. Thank you.
Search Google Answers for
Google Answers  


Google Home - Answers FAQ - Terms of Service - Privacy Policy