Hello,
I am having a problem with returned mail. I don't have something configured correctly.
I have 6 virtual hosts on one machine and mail sent from these host is being returned. This is the transcript:
The original message was received at Tue, 11 Apr 2006 07:30:19 -0400 from localhost.localdomain [127.0.0.1]
----- The following addresses had permanent fatal errors ----- f5loar@charter.net (reason: 553 #5.1.8 Domain of sender address apache@localhost.localdomain does not resolve)
----- Transcript of session follows ----- ... while talking to mail.charter.net.:
MAIL From:apache@localhost.localdomain SIZE=1618
<<< 553 #5.1.8 Domain of sender address apache@localhost.localdomain does not resolve 501 5.6.0 Data format error
I think this has something to with outgoing address mappings but not sure how to fix it. All virtual hosts are included in the local domains file.
TIA
Am Di, den 11.04.2006 schrieb Thomas E Dukes um 14:17:
I am having a problem with returned mail. I don't have something configured correctly.
I have 6 virtual hosts on one machine and mail sent from these host is being returned. This is the transcript:
The original message was received at Tue, 11 Apr 2006 07:30:19 -0400 from localhost.localdomain [127.0.0.1]
----- The following addresses had permanent fatal errors ----- f5loar@charter.net (reason: 553 #5.1.8 Domain of sender address apache@localhost.localdomain does not resolve)
----- Transcript of session follows ----- ... while talking to mail.charter.net.:
MAIL From:apache@localhost.localdomain SIZE=1618
<<< 553 #5.1.8 Domain of sender address apache@localhost.localdomain does not resolve 501 5.6.0 Data format error
I think this has something to with outgoing address mappings but not sure how to fix it. All virtual hosts are included in the local domains file.
localhost.localdomain is no valid public FQDN. Either give your host a valid FQDN (which is recommended for a networked host anyway) or use masquerarding / generics feature.
Alexander
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Alexander Dalloz Sent: Tuesday, April 11, 2006 8:41 AM To: CentOS mailing list Subject: Re: [CentOS] Sendmail problem
Am Di, den 11.04.2006 schrieb Thomas E Dukes um 14:17:
I am having a problem with returned mail. I don't have something configured correctly.
I have 6 virtual hosts on one machine and mail sent from
these host is
being returned. This is the transcript:
The original message was received at Tue, 11 Apr 2006
07:30:19 -0400
from localhost.localdomain [127.0.0.1]
----- The following addresses had permanent fatal errors ----- f5loar@charter.net (reason: 553 #5.1.8 Domain of sender address apache@localhost.localdomain does not resolve)
----- Transcript of session follows ----- ... while talking to mail.charter.net.:
MAIL From:apache@localhost.localdomain SIZE=1618
<<< 553 #5.1.8 Domain of sender address
does not resolve 501 5.6.0 Data format error
I think this has something to with outgoing address
mappings but not
sure how to fix it. All virtual hosts are included in the
local domains file.
localhost.localdomain is no valid public FQDN. Either give your host a valid FQDN (which is recommended for a networked host anyway) or use masquerarding / generics feature.
Alexander
Hello Alexander,
As far as I know, I have my FQDN set. It may not be done so correctly in sendmail.
Here's a portion of my sendmail.mc file:
LOCAL_DOMAIN(`localhost.localdomain')dnl <---- do I need to change this to my FDQN? dnl # dnl # The following example makes mail from this host and any additional dnl # specified domains appear to be sent from mydomain.com dnl # dnl # masquerade not just the headers, but the envelope as well dnl # dnl FEATURE(masquerade_envelope)dnl dnl # dnl # masquerade not just @mydomainalias.com, but @*.mydomainalias.com as well dnl # dnl FEATURE(masquerade_entire_domain)dnl dnl # dnl MASQUERADE_DOMAIN(localhost)dnl dnl MASQUERADE_DOMAIN(localhost.localdomain)dnl <------ How about this? dnl # MASQUERADE_DOMAIN(mydomainalias.com)dnl dnl # MASQUERADE_DOMAIN(mydomain.lan)dnl MAILER(smtp)dnl MAILER(`procmail')
What masquerade feature do I need to setup so that mail sent from domain1, domain2, domain3, etc., is sent from the respective domains?
Any help would be really appreciated!!!
TIA
Am Di, den 11.04.2006 schrieb Thomas E Dukes um 19:34:
Hello Alexander,
As far as I know, I have my FQDN set. It may not be done so correctly in sendmail.
hostname
/usr/lib/sendmail -bt -d0.6 < /dev/null
Here's a portion of my sendmail.mc file:
LOCAL_DOMAIN(`localhost.localdomain')dnl <---- do I need to change this to my FDQN?
No. From /usr/share/doc/sendmail/README.cf:
+-----------------------------------+ | ACCEPTING MAIL FOR MULTIPLE NAMES | +-----------------------------------+
If your host is known by several different names, you need to augment class {w}. This is a list of names by which your host is known, and anything sent to an address using a host name in this list will be treated as local mail. You can do this in two ways: either create the file /etc/mail/local-host-names containing a list of your aliases (one per line), and use ``FEATURE(`use_cw_file')'' in the .mc file, or add ``LOCAL_DOMAIN(`alias.host.name')''. Be sure you use the fully-qualified name of the host, rather than a short name.
If you want to have different address in different domains, take a look at the virtusertable feature, which is also explained at http://www.sendmail.org/virtual-hosting.html
dnl # dnl # The following example makes mail from this host and any additional dnl # specified domains appear to be sent from mydomain.com dnl # dnl # masquerade not just the headers, but the envelope as well dnl # dnl FEATURE(masquerade_envelope)dnl dnl # dnl # masquerade not just @mydomainalias.com, but @*.mydomainalias.com as well dnl # dnl FEATURE(masquerade_entire_domain)dnl dnl # dnl MASQUERADE_DOMAIN(localhost)dnl dnl MASQUERADE_DOMAIN(localhost.localdomain)dnl <------ How about this? dnl # MASQUERADE_DOMAIN(mydomainalias.com)dnl dnl # MASQUERADE_DOMAIN(mydomain.lan)dnl MAILER(smtp)dnl MAILER(`procmail')
What masquerade feature do I need to setup so that mail sent from domain1, domain2, domain3, etc., is sent from the respective domains?
If you have multiple domains to host you probably don't want to use the masquerade feature as that causes Sendmail to always rewrite to just a single domain name (MASQUERADE_AS).
From DSN report we see that it was your Apache to send the mail out. Typically it is submitting, so you could use "sendmail -f realuser@domain.tld" to change the sender. If you run PHP you should have a close look at http://phpmailer.sourceforge.net/ instead of using the mail() function.
Alexander
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Alexander Dalloz Sent: Tuesday, April 11, 2006 2:05 PM To: CentOS mailing list Subject: RE: [CentOS] Sendmail problem
Am Di, den 11.04.2006 schrieb Thomas E Dukes um 19:34:
Hello Alexander,
As far as I know, I have my FQDN set. It may not be done
so correctly
in sendmail.
hostname
/usr/lib/sendmail -bt -d0.6 < /dev/null
Here's a portion of my sendmail.mc file:
LOCAL_DOMAIN(`localhost.localdomain')dnl <---- do I need to change this to my FDQN?
No. From /usr/share/doc/sendmail/README.cf:
+-----------------------------------+ | ACCEPTING MAIL FOR MULTIPLE NAMES | +-----------------------------------+
If your host is known by several different names, you need to augment class {w}. This is a list of names by which your host is known, and anything sent to an address using a host name in this list will be treated as local mail. You can do this in two ways: either create the file /etc/mail/local-host-names containing a list of your aliases (one per line), and use ``FEATURE(`use_cw_file')'' in the .mc file, or add ``LOCAL_DOMAIN(`alias.host.name')''. Be sure you use the fully-qualified name of the host, rather than a short name.
If you want to have different address in different domains, take a look at the virtusertable feature, which is also explained at http://www.sendmail.org/virtual-hosting.html
dnl # dnl # The following example makes mail from this host and any additional dnl # specified domains appear to be sent from
mydomain.com
dnl # dnl # masquerade not just the headers, but the
envelope as well
dnl # dnl FEATURE(masquerade_envelope)dnl dnl # dnl #
masquerade not
just @mydomainalias.com, but @*.mydomainalias.com as well dnl # dnl FEATURE(masquerade_entire_domain)dnl dnl # dnl MASQUERADE_DOMAIN(localhost)dnl dnl MASQUERADE_DOMAIN(localhost.localdomain)dnl <------
How about this?
dnl # MASQUERADE_DOMAIN(mydomainalias.com)dnl dnl # MASQUERADE_DOMAIN(mydomain.lan)dnl MAILER(smtp)dnl MAILER(`procmail')
What masquerade feature do I need to setup so that mail sent from domain1, domain2, domain3, etc., is sent from the
respective domains?
If you have multiple domains to host you probably don't want to use the masquerade feature as that causes Sendmail to always rewrite to just a single domain name (MASQUERADE_AS).
From DSN report we see that it was your Apache to send the mail out. Typically it is submitting, so you could use "sendmail -f realuser@domain.tld" to change the sender. If you run PHP you should have a close look at http://phpmailer.sourceforge.net/ instead of using the mail() function.
Alexander
The domains are listed in /etc/mail/local-host-names. My sendmail.mc also has the FEATURE(`use_cw_file'). From what I understand this is for accepting mail for these domains. The problem maybe related but the correct 'sent from' address is not being applied to outgoing mail. The scripts sending the outgoing mail are set to use a valid user in the domain.
I have no problem getting mail - just the outgoing.
TIA
Am Mi, den 12.04.2006 schrieb Thomas E Dukes um 1:02:
The domains are listed in /etc/mail/local-host-names. My sendmail.mc also has the FEATURE(`use_cw_file'). From what I understand this is for accepting mail for these domains. The problem maybe related but the correct 'sent from' address is not being applied to outgoing mail. The scripts sending the outgoing mail are set to use a valid user in the domain.
I have no problem getting mail - just the outgoing.
There seems to be a misunderstanding between us. I just tried to explain to you what LOCAL_DOMAIN would be for. Not that it should be any help. Set a FQDN hostname. Yours is actually localhost.localdomain. Hint: HOSTNAME in /etc/sysconfig/network.
Alexander
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Alexander Dalloz Sent: Tuesday, April 11, 2006 7:10 PM To: CentOS mailing list Subject: RE: [CentOS] Sendmail problem
Am Mi, den 12.04.2006 schrieb Thomas E Dukes um 1:02:
The domains are listed in /etc/mail/local-host-names. My
sendmail.mc
also has the FEATURE(`use_cw_file'). From what I
understand this is
for accepting mail for these domains. The problem maybe
related but
the correct 'sent from' address is not being applied to
outgoing mail.
The scripts sending the outgoing mail are set to use a
valid user in the domain.
I have no problem getting mail - just the outgoing.
There seems to be a misunderstanding between us. I just tried to explain to you what LOCAL_DOMAIN would be for. Not that it should be any help. Set a FQDN hostname. Yours is actually localhost.localdomain. Hint: HOSTNAME in /etc/sysconfig/network.
Alexander
The contents of my /etc/sysconfig/network:
NETWORKING=yes HOSTNAME=palmettodomains.com
This really has me stumped. I recently upgraded my server with a fresh install of CentOS 4.2 then upgrade to 4.3 when it was released. I never had this problem on my old server which had been upgraded numerous time since Redhat 8.0, Fedora, White Box. I copied all the config files for mail and bind/named. I must have missed something.
Thanks!!!!!!!!
Here'sanother bounce email:
The original message was received at Tue, 11 Apr 2006 19:16:44 -0400 from localhost.localdomain [127.0.0.1]
----- The following addresses had permanent fatal errors ----- xxxxxx@comcast.net (reason: 521-EHLO/HELO from sender 71.31.91.127 does not map to localhost.localdomain in DNS)
----- Transcript of session follows ----- ... while talking to gateway-s.comcast.net.:
MAIL From:apache@localhost.localdomain SIZE=2176
<<< 521-EHLO/HELO from sender 71.31.91.127 does not map to localhost.localdomain in DNS <<< 521-sending machine name must be provided as a fully <<< 521-qualified domain via EHLO/HELO command. <<< 521-see section 4.1.1.1 and 4.1.4 of RFC 2821 <<< 521 521: Comcast requires that all mail servers must have a PTR record with a valid Reverse DNS entry. Currently your mailserver does not fill that requirement. For more information, refer to: http://www.comcast.net/help/faq/index.jsp?faq=Email118405 554 5.0.0 Service unavailable
Am Mi, den 12.04.2006 schrieb Thomas E Dukes um 2:23:
Here'sanother bounce email:
The original message was received at Tue, 11 Apr 2006 19:16:44 -0400 from localhost.localdomain [127.0.0.1]
----- The following addresses had permanent fatal errors ----- xxxxxx@comcast.net (reason: 521-EHLO/HELO from sender 71.31.91.127 does not map to localhost.localdomain in DNS)
----- Transcript of session follows ----- ... while talking to gateway-s.comcast.net.:
MAIL From:apache@localhost.localdomain SIZE=2176
<<< 521-EHLO/HELO from sender 71.31.91.127 does not map to localhost.localdomain in DNS <<< 521-sending machine name must be provided as a fully <<< 521-qualified domain via EHLO/HELO command. <<< 521-see section 4.1.1.1 and 4.1.4 of RFC 2821 <<< 521 521: Comcast requires that all mail servers must have a PTR record with a valid Reverse DNS entry. Currently your mailserver does not fill that requirement. For more information, refer to: http://www.comcast.net/help/faq/index.jsp?faq=Email118405 554 5.0.0 Service unavailable
2 things:
1) Your mail host at that time of the mail had the hostname localhost.localdomain, thus your Sendmail used it for EHLO/HELO. You fixed that meanwhile
2) The remote side requires not only a valid forward DNS record (palmettodomains.com points to that IP) but too a matching reverse one. From here I can't judge whether the named IP is static and thus assigned by your ISP. If that is the case then you really should take care for both types of DNS entries. If not (you are on an dynamic line) you should use your ISP's mail host as SMART_HOST within your Sendmail configuration. DynDNS is a very bad base for reliable mail services.
Alexander
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Alexander Dalloz Sent: Wednesday, April 12, 2006 7:06 AM To: CentOS mailing list Subject: RE: [CentOS] Sendmail problem
Am Mi, den 12.04.2006 schrieb Thomas E Dukes um 2:23:
Here'sanother bounce email:
The original message was received at Tue, 11 Apr 2006
19:16:44 -0400
from localhost.localdomain [127.0.0.1]
----- The following addresses had permanent fatal errors ----- xxxxxx@comcast.net (reason: 521-EHLO/HELO from sender 71.31.91.127 does not map to localhost.localdomain in DNS)
----- Transcript of session follows ----- ... while talking to gateway-s.comcast.net.:
MAIL From:apache@localhost.localdomain SIZE=2176
<<< 521-EHLO/HELO from sender 71.31.91.127 does not map to localhost.localdomain in DNS <<< 521-sending machine name must be provided as a fully <<< 521-qualified domain via EHLO/HELO command. <<< 521-see section 4.1.1.1 and 4.1.4 of RFC 2821 <<< 521
521: Comcast
requires that all mail servers must have a PTR record with a valid Reverse DNS entry. Currently your mailserver does not fill that requirement. For more information, refer to: http://www.comcast.net/help/faq/index.jsp?faq=Email118405 554 5.0.0 Service unavailable
2 things:
- Your mail host at that time of the mail had the hostname
localhost.localdomain, thus your Sendmail used it for EHLO/HELO. You fixed that meanwhile
- The remote side requires not only a valid forward DNS
record (palmettodomains.com points to that IP) but too a matching reverse one. From here I can't judge whether the named IP is static and thus assigned by your ISP. If that is the case then you really should take care for both types of DNS entries. If not (you are on an dynamic line) you should use your ISP's mail host as SMART_HOST within your Sendmail configuration. DynDNS is a very bad base for reliable mail services.
Alexander
Hello Alexander,
Yes, I have a dynamic IP address. If I use my ISPs mail host as the SMART_HOST, would that cause relaying problems? I tried that on the mail client end a while back and got errors about relaying.
Thanks, I'll give it a try.
Eddie
On Wed, 2006-04-12 at 07:13 -0400, Thomas E Dukes wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Alexander Dalloz Sent: Wednesday, April 12, 2006 7:06 AM To: CentOS mailing list Subject: RE: [CentOS] Sendmail problem
Am Mi, den 12.04.2006 schrieb Thomas E Dukes um 2:23:
Here'sanother bounce email:
The original message was received at Tue, 11 Apr 2006
19:16:44 -0400
from localhost.localdomain [127.0.0.1]
----- The following addresses had permanent fatal errors ----- xxxxxx@comcast.net (reason: 521-EHLO/HELO from sender 71.31.91.127 does not map to localhost.localdomain in DNS)
----- Transcript of session follows ----- ... while talking to gateway-s.comcast.net.:
MAIL From:apache@localhost.localdomain SIZE=2176
<<< 521-EHLO/HELO from sender 71.31.91.127 does not map to localhost.localdomain in DNS <<< 521-sending machine name must be provided as a fully <<< 521-qualified domain via EHLO/HELO command. <<< 521-see section 4.1.1.1 and 4.1.4 of RFC 2821 <<< 521
521: Comcast
requires that all mail servers must have a PTR record with a valid Reverse DNS entry. Currently your mailserver does not fill that requirement. For more information, refer to: http://www.comcast.net/help/faq/index.jsp?faq=Email118405 554 5.0.0 Service unavailable
2 things:
- Your mail host at that time of the mail had the hostname
localhost.localdomain, thus your Sendmail used it for EHLO/HELO. You fixed that meanwhile
- The remote side requires not only a valid forward DNS
record (palmettodomains.com points to that IP) but too a matching reverse one. From here I can't judge whether the named IP is static and thus assigned by your ISP. If that is the case then you really should take care for both types of DNS entries. If not (you are on an dynamic line) you should use your ISP's mail host as SMART_HOST within your Sendmail configuration. DynDNS is a very bad base for reliable mail services.
Alexander
Hello Alexander,
Yes, I have a dynamic IP address. If I use my ISPs mail host as the SMART_HOST, would that cause relaying problems? I tried that on the mail client end a while back and got errors about relaying.
Thanks, I'll give it a try.
Just as a side note here ... the majority of mail servers now use a technique called Realtime Blackhole List (RBL).
Many of the new lists contain the IPs of all dynamic Cable/DSL providers as a huge amount of spam is sent via broadband PC's that have been compromised.
It is a losing proposition to use dynamic machines to send reliable e- mail as a server ... at least that has been my experience.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Johnny Hughes Sent: Wednesday, April 12, 2006 7:28 AM To: CentOS ML Subject: RE: [CentOS] Sendmail problem
On Wed, 2006-04-12 at 07:13 -0400, Thomas E Dukes wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Alexander Dalloz Sent: Wednesday, April 12, 2006 7:06 AM To: CentOS mailing list Subject: RE: [CentOS] Sendmail problem
Am Mi, den 12.04.2006 schrieb Thomas E Dukes um 2:23:
Here'sanother bounce email:
The original message was received at Tue, 11 Apr 2006
19:16:44 -0400
from localhost.localdomain [127.0.0.1]
----- The following addresses had permanent fatal
errors -----
xxxxxx@comcast.net (reason: 521-EHLO/HELO from sender 71.31.91.127
does not map
to localhost.localdomain in DNS)
----- Transcript of session follows ----- ... while
talking to
gateway-s.comcast.net.:
> MAIL From:apache@localhost.localdomain SIZE=2176
<<< 521-EHLO/HELO from sender 71.31.91.127 does not map to localhost.localdomain in DNS <<< 521-sending machine
name must be
provided as a fully <<< 521-qualified domain via
EHLO/HELO command.
<<< 521-see section 4.1.1.1 and 4.1.4 of RFC 2821 <<< 521
521: Comcast
requires that all mail servers must have a PTR record
with a valid
Reverse DNS entry. Currently your mailserver does not fill that requirement. For more information, refer to: http://www.comcast.net/help/faq/index.jsp?faq=Email118405 554 5.0.0 Service unavailable
2 things:
- Your mail host at that time of the mail had the hostname
localhost.localdomain, thus your Sendmail used it for
EHLO/HELO. You
fixed that meanwhile
- The remote side requires not only a valid forward DNS record
(palmettodomains.com points to that IP) but too a
matching reverse
one. From here I can't judge whether the named IP is static and thus assigned by your ISP. If that is the case then you really should take care for both types of DNS entries. If not (you are on an dynamic line) you should use your ISP's mail host as SMART_HOST within your Sendmail configuration. DynDNS is a very bad base for reliable mail services.
Alexander
Hello Alexander,
Yes, I have a dynamic IP address. If I use my ISPs mail
host as the
SMART_HOST, would that cause relaying problems? I tried
that on the
mail client end a while back and got errors about relaying.
Thanks, I'll give it a try.
Just as a side note here ... the majority of mail servers now use a technique called Realtime Blackhole List (RBL).
Many of the new lists contain the IPs of all dynamic Cable/DSL providers as a huge amount of spam is sent via broadband PC's that have been compromised.
It is a losing proposition to use dynamic machines to send reliable e- mail as a server ... at least that has been my experience.
Hey Johnny,
Yes, I know. I have that problem sending mail to AOL (that's ironic) and RoadRunner accounts. If my ISP hadn't lost its mind for what they charge ($180/month) for a static/business DSL account, I would be on that.
Thanks!!
Thomas E Dukes spake the following on 4/12/2006 4:42 AM:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Johnny Hughes Sent: Wednesday, April 12, 2006 7:28 AM To: CentOS ML Subject: RE: [CentOS] Sendmail problem
On Wed, 2006-04-12 at 07:13 -0400, Thomas E Dukes wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Alexander Dalloz Sent: Wednesday, April 12, 2006 7:06 AM To: CentOS mailing list Subject: RE: [CentOS] Sendmail problem
Am Mi, den 12.04.2006 schrieb Thomas E Dukes um 2:23:
Here'sanother bounce email:
The original message was received at Tue, 11 Apr 2006
19:16:44 -0400
from localhost.localdomain [127.0.0.1]
----- The following addresses had permanent fatal
errors -----
xxxxxx@comcast.net (reason: 521-EHLO/HELO from sender 71.31.91.127
does not map
to localhost.localdomain in DNS)
----- Transcript of session follows ----- ... while
talking to
gateway-s.comcast.net.:
>> MAIL From:apache@localhost.localdomain SIZE=2176
<<< 521-EHLO/HELO from sender 71.31.91.127 does not map to localhost.localdomain in DNS <<< 521-sending machine
name must be
provided as a fully <<< 521-qualified domain via
EHLO/HELO command.
<<< 521-see section 4.1.1.1 and 4.1.4 of RFC 2821 <<< 521
521: Comcast
requires that all mail servers must have a PTR record
with a valid
Reverse DNS entry. Currently your mailserver does not fill that requirement. For more information, refer to: http://www.comcast.net/help/faq/index.jsp?faq=Email118405 554 5.0.0 Service unavailable
2 things:
- Your mail host at that time of the mail had the hostname
localhost.localdomain, thus your Sendmail used it for
EHLO/HELO. You
fixed that meanwhile
- The remote side requires not only a valid forward DNS record
(palmettodomains.com points to that IP) but too a
matching reverse
one. From here I can't judge whether the named IP is static and thus assigned by your ISP. If that is the case then you really should take care for both types of DNS entries. If not (you are on an dynamic line) you should use your ISP's mail host as SMART_HOST within your Sendmail configuration. DynDNS is a very bad base for reliable mail services.
Alexander
Hello Alexander,
Yes, I have a dynamic IP address. If I use my ISPs mail
host as the
SMART_HOST, would that cause relaying problems? I tried
that on the
mail client end a while back and got errors about relaying.
Thanks, I'll give it a try.
Just as a side note here ... the majority of mail servers now use a technique called Realtime Blackhole List (RBL).
Many of the new lists contain the IPs of all dynamic Cable/DSL providers as a huge amount of spam is sent via broadband PC's that have been compromised.
It is a losing proposition to use dynamic machines to send reliable e- mail as a server ... at least that has been my experience.
Hey Johnny,
Yes, I know. I have that problem sending mail to AOL (that's ironic) and RoadRunner accounts. If my ISP hadn't lost its mind for what they charge ($180/month) for a static/business DSL account, I would be on that.
Thanks!!
AOL only wants to send spam, not receive it. You will need to make arrangements to use a smart host somewhere on a fixed ip with good reverse mapping. They will need to be contacted to set your domain up as an authorized relay. You might be able to rent such service monthly, and it should be much cheaper.
Am Mi, den 12.04.2006 schrieb Thomas E Dukes um 13:13:
Hello Alexander,
Yes, I have a dynamic IP address. If I use my ISPs mail host as the SMART_HOST, would that cause relaying problems? I tried that on the mail client end a while back and got errors about relaying.
Thanks, I'll give it a try.
Eddie
If your mail setup for posting to this list uses the same setup / infrastructure, then you are not sending through your ISP's MTA. And from quoted DSN it seems that you didn't use the ISP's relay in that case neither. Something to check?
Alexander
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Alexander Dalloz Sent: Wednesday, April 12, 2006 7:06 AM To: CentOS mailing list Subject: RE: [CentOS] Sendmail problem
Am Mi, den 12.04.2006 schrieb Thomas E Dukes um 2:23:
Here'sanother bounce email:
The original message was received at Tue, 11 Apr 2006
19:16:44 -0400
from localhost.localdomain [127.0.0.1]
----- The following addresses had permanent fatal errors ----- xxxxxx@comcast.net (reason: 521-EHLO/HELO from sender 71.31.91.127 does not map to localhost.localdomain in DNS)
----- Transcript of session follows ----- ... while talking to gateway-s.comcast.net.:
MAIL From:apache@localhost.localdomain SIZE=2176
<<< 521-EHLO/HELO from sender 71.31.91.127 does not map to localhost.localdomain in DNS <<< 521-sending machine name must be provided as a fully <<< 521-qualified domain via EHLO/HELO command. <<< 521-see section 4.1.1.1 and 4.1.4 of RFC 2821 <<< 521
521: Comcast
requires that all mail servers must have a PTR record with a valid Reverse DNS entry. Currently your mailserver does not fill that requirement. For more information, refer to: http://www.comcast.net/help/faq/index.jsp?faq=Email118405 554 5.0.0 Service unavailable
2 things:
- Your mail host at that time of the mail had the hostname
localhost.localdomain, thus your Sendmail used it for EHLO/HELO. You fixed that meanwhile
- The remote side requires not only a valid forward DNS
record (palmettodomains.com points to that IP) but too a matching reverse one. From here I can't judge whether the named IP is static and thus assigned by your ISP. If that is the case then you really should take care for both types of DNS entries. If not (you are on an dynamic line) you should use your ISP's mail host as SMART_HOST within your Sendmail configuration. DynDNS is a very bad base for reliable mail services.
One thing I should mention is that I use MailScanner. Don't know if that is part of the problem but when installed, sendmail service is turned off but I think is controlled by MailScanner.
-
Alexander Dalloz -
Johnny Hughes -
Scott Silva -
Thomas E Dukes