Postfix on SuSE 9.0 Server - results in no MX host

This is a discussion on Postfix on SuSE 9.0 Server - results in no MX host within the alt.comp.mail.postfix forums, part of the Mail Servers and Related category; Hello all, I've just subscribed, and am amazed at the number of posts in this newsgroup! Anyway.... I've ...


Go Back   Usenet Forums > Mail Servers and Related > alt.comp.mail.postfix

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 03-28-2005
Ronald MacDonald
 
Posts: n/a
Default Postfix on SuSE 9.0 Server - results in no MX host

Hello all,
I've just subscribed, and am amazed at the number of posts in
this newsgroup!
Anyway.... I've had a look at recent posts, and on some forums, and
can't find a logical explanation for my problem, anywhere.
Basically, emails are not being sent or recieved. I am on SuSE linux 9.0
(Server) and the log file is returning with the error:

Name service error for name=*.* type=MX: Host not found, try again

(Note - I changed the domain to *.*; it depends on the domain I put in
outgoing mail.)

Now, I know that the typical error is found in /etc/resolv.conf - but
I've spent a reasonably long time seaching Google for the appropriate
syntax, checking it, checking it again etc etc... this is simply illogical
from my point of view.
It was working fine before - the only thing that stopped it working was
a power cut. I don't believe any data was corrupted as a result, but
obviously there must be some file that was modified during startup, after
the blackout.
I know this a very broad question, but what other files, apart from
resolv.conf, could be stopping the mail server from functioning?

My /etc/resolv.conf is as follows;

nameserver 192.168.0.1 # IP address of router
nameserver 192.168.0.1
nameserver 192.168.0.1
search musdev.net ronkymac.com ronkymac.co.uk

#======= END RESOLV.CONF===========

Personally, I find the syntax very suspicious, but anyway - multipule
sources say it's correct.

I am behind a firewall also - do you think that would cause the mail server
to function incorrectly? All packets except those through port 80, 25, and
443 are blocked.

Anyway, I look forward to hearing your opinions.

Thank you all very much.

Ronald MacDonald (-- and yes, that IS my real name, lol)


Reply With Quote
  #2 (permalink)  
Old 03-28-2005
Julia Thorne
 
Posts: n/a
Default Re: Postfix on SuSE 9.0 Server - results in no MX host

On Mon, 28 Mar 2005 16:17:14 +0100, Ronald MacDonald wrote:

> Basically, emails are not being sent or recieved. I am on SuSE linux
> 9.0 (Server) and the log file is returning with the error:
>
> Name service error for name=*.* type=MX: Host not found, try again


> I know this a very broad question, but what other files, apart from
> resolv.conf, could be stopping the mail server from functioning?
>
> My /etc/resolv.conf is as follows;
>
> nameserver 192.168.0.1 # IP address of router
> nameserver 192.168.0.1
> nameserver 192.168.0.1
> search musdev.net ronkymac.com ronkymac.co.uk
>
> #======= END RESOLV.CONF===========
>
> Personally, I find the syntax very suspicious, but anyway - multipule
> sources say it's correct.


Sounds suspicious to me too. resolv.conf is to tell the system how
to resolve names to IP addresses. My resolv.conf is very simple:

nameserver 65.104.xx.xx
nameserver 65.106.x.xxx
nameserver 65.106.x.xxx

The first line is the DNS server here, the other two are the DNS
servers at the upstream provider, as alternates.

> I am behind a firewall also - do you think that would cause the mail server
> to function incorrectly? All packets except those through port 80, 25, and
> 443 are blocked.


If you have POP3 access to mail, you'll need port 110.
The main thing is, you need to specify a nameserver to the system,
and you need to open firewall access to port 53 at that nameserver,
or Postfix can't lookup any hosts.

That blocks outgoing email. If you have any UCE checks in effect
that do reverse-DNS lookups on incoming SMTP connections, then all
incoming mail will also fail, because the DNS lookups will fail.
Reply With Quote
  #3 (permalink)  
Old 03-28-2005
Ronald MacDonald
 
Posts: n/a
Default Re: Postfix on SuSE 9.0 Server - results in no MX host

Aha! It works!
I changed /etc/resolv.conf to
nameserver [IP address]
nameserver [IP address]
nameserver [IP address]

and it seems to be successfully sending mail to everyone, apart from local
mailboxes (which recieve log files).

The log file returns with this error;

Mar 28 19:53:59 server postfix/smtpd[5548]: 8BDB712E64: reject: RCPT from
unknown[212.159.14.212]: 554 < [user] @musdev.net>: Relay access denied;
from=< [ address] > to=< [user] @musdev.net> proto=ESMTP
helo=<ptb-relay01.plus.net>


Any ideas??

Cheers,
Ronald.


Reply With Quote
  #4 (permalink)  
Old 03-29-2005
Simon Powell
 
Posts: n/a
Default Re: Postfix on SuSE 9.0 Server - results in no MX host

Allow for relaying by local domain/subnet and this will work fine (in
main.cf look under the section relay/trusted hosts)

"Ronald MacDonald" <ronkymac@macdonald100.force9.co.uk> wrote in message
news:424854d5$0$83081$ed2619ec@ptn-nntp-reader03.plus.net...
> Aha! It works!
> I changed /etc/resolv.conf to
> nameserver [IP address]
> nameserver [IP address]
> nameserver [IP address]
>
> and it seems to be successfully sending mail to everyone, apart from local
> mailboxes (which recieve log files).
>
> The log file returns with this error;
>
> Mar 28 19:53:59 server postfix/smtpd[5548]: 8BDB712E64: reject: RCPT from
> unknown[212.159.14.212]: 554 < [user] @musdev.net>: Relay access denied;
> from=< [ address] > to=< [user] @musdev.net> proto=ESMTP
> helo=<ptb-relay01.plus.net>
>
>
> Any ideas??
>
> Cheers,
> Ronald.
>



Reply With Quote
  #5 (permalink)  
Old 03-29-2005
Ronald MacDonald
 
Posts: n/a
Default Re: Postfix on SuSE 9.0 Server - results in no MX host

Hey,

I know this sounds silly, but I don't know what part to change.
The IP address of the server is 84.92.57.161.

I know this is rather ridiculous, but I've posted up the part of the main.cf
which seems to be stopping the connection taking place.
This is the present state of the main.cf;


###############################BEGIN EXTRACT###############################

# RECEIVING MAIL

# Note: you need to stop/start Postfix when this parameter changes.
#
inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost

# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4

# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
#
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
#
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# sample-smtpd.cf).
#
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
#
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
#
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#
#mydestination = $myhostname, localhost.$mydomain
#mydestination = $myhostname, localhost.$mydomain $mydomain
#mydestination = $myhostname, localhost.$mydomain, $mydomain,
mydestination = $myhostname localhost.$mydomain www.$mydomain ftp.$mydomain
# mail.$mydomain, www.$mydomain, ftp.$mydomain

# REJECTING MAIL FOR UNKNOWN LOCAL USERS
#
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination and $inet_interfaces.
#
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
#
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery.
#
# Details are described in the LOCAL_RECIPIENT_README file.
#
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
#
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =

# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# $inet_interfaces, while $local_recipient_maps is non-empty and the
# recipient address or address local-part is not found.
#
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
#
#unknown_local_recipient_reject_code = 550
unknown_local_recipient_reject_code = 450

# TRUST AND RELAY CONTROL

# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
#
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in file sample-smtpd.cf.
#
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
#
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
#
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
#
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host

# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
#
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
#
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#
mynetworks = 192.168.0.4/28, 127.0.0.0/8, 84.92.57.161
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table

# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions restriction in the
# file sample-smtpd.cf for detailed information.
#
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any
destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
#
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
#
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
#
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction in the file sample-smtpd.cf.
#
#relay_domains = $mydestination
###############################END EXTRACT###############################









"Simon Powell" <si_powell@blueyonder.co.uk> wrote in message
news:vEd2e.24530$4%3.17229@fe2.news.blueyonder.co. uk...
> Allow for relaying by local domain/subnet and this will work fine (in
> main.cf look under the section relay/trusted hosts)
>
> "Ronald MacDonald" <ronkymac@macdonald100.force9.co.uk> wrote in message
> news:424854d5$0$83081$ed2619ec@ptn-nntp-reader03.plus.net...
>> Aha! It works!
>> I changed /etc/resolv.conf to
>> nameserver [IP address]
>> nameserver [IP address]
>> nameserver [IP address]
>>
>> and it seems to be successfully sending mail to everyone, apart from
>> local
>> mailboxes (which recieve log files).
>>
>> The log file returns with this error;
>>
>> Mar 28 19:53:59 server postfix/smtpd[5548]: 8BDB712E64: reject: RCPT from
>> unknown[212.159.14.212]: 554 < [user] @musdev.net>: Relay access denied;
>> from=< [ address] > to=< [user] @musdev.net> proto=ESMTP
>> helo=<ptb-relay01.plus.net>
>>
>>
>> Any ideas??
>>
>> Cheers,
>> Ronald.
>>

>
>



Reply With Quote
  #6 (permalink)  
Old 03-29-2005
Julia Thorne
 
Posts: n/a
Default Re: Postfix on SuSE 9.0 Server - results in no MX host

On Tue, 29 Mar 2005 15:55:25 +0100, Ronald MacDonald wrote:

> I know this sounds silly, but I don't know what part to change.
> The IP address of the server is 84.92.57.161.
> This is the present state of the main.cf;
> <snip>
> #mydestination = $myhostname, localhost.$mydomain
> #mydestination = $myhostname, localhost.$mydomain $mydomain
> #mydestination = $myhostname, localhost.$mydomain, $mydomain,
> mydestination = $myhostname localhost.$mydomain www.$mydomain ftp.$mydomain
> # mail.$mydomain, www.$mydomain, ftp.$mydomain


The uncommented line is the only one Postfix uses, but I left the
other lines for comparison- there is a missing comma which would
keep Postfix from recognizing localhost as part of mydestnation.

"," was invented by the devil to torture programmers. :-)

> #local_recipient_maps = unix:passwd.byname $alias_maps
> #local_recipient_maps = proxy:unix:passwd.byname $alias_maps
> #local_recipient_maps =


No local recipient maps? One is not required, but the first line
above is the configuration most often used. This will allow email
sent to/from system users, and addresses in $alias_maps, which usually
will include users in the virtual domains (if any) and alises like
"postmaster" etc.

> #relay_domains = $mydestination


I think this should be uncommented too.
Reply With Quote
  #7 (permalink)  
Old 04-12-2005
Ronald MacDonald
 
Posts: n/a
Default Re: Postfix on SuSE 9.0 Server - results in no MX host

Hey all,

Finally got it working a coule of days ago - decided to simply uninstall and
get a default config for SuSE off the Postfix website. Worked a gem with a
few simple changes.

Thanks everyone.


"Julia Thorne" <rimbaldi@nospam.tld> wrote in message
news:tck2e.6613064$f47.1219310@news.easynews.com.. .
> On Tue, 29 Mar 2005 15:55:25 +0100, Ronald MacDonald wrote:
>
>> I know this sounds silly, but I don't know what part to change.
>> The IP address of the server is 84.92.57.161.
>> This is the present state of the main.cf;
>> <snip>
>> #mydestination = $myhostname, localhost.$mydomain
>> #mydestination = $myhostname, localhost.$mydomain $mydomain
>> #mydestination = $myhostname, localhost.$mydomain, $mydomain,
>> mydestination = $myhostname localhost.$mydomain www.$mydomain
>> ftp.$mydomain
>> # mail.$mydomain, www.$mydomain, ftp.$mydomain

>
> The uncommented line is the only one Postfix uses, but I left the
> other lines for comparison- there is a missing comma which would
> keep Postfix from recognizing localhost as part of mydestnation.
>
> "," was invented by the devil to torture programmers. :-)
>
>> #local_recipient_maps = unix:passwd.byname $alias_maps
>> #local_recipient_maps = proxy:unix:passwd.byname $alias_maps
>> #local_recipient_maps =

>
> No local recipient maps? One is not required, but the first line
> above is the configuration most often used. This will allow email
> sent to/from system users, and addresses in $alias_maps, which usually
> will include users in the virtual domains (if any) and alises like
> "postmaster" etc.
>
>> #relay_domains = $mydestination

>
> I think this should be uncommented too.



Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 10:10 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0