On 2011-01-03 14:06, stevebragg wrote:
>
> Carlos
>
> Thank you for your reply.
>
> You know I DID start this thread off by saying I am not a Linux
> expert…
>
> Sorry it was not the file postfix.cnf - it was main.cnf in the Postfix
> folder, but I am sure you knew that :-)?
Not unless I see at least a bit of the file and I recognize the lines 
>
> I did read your previous thread but did not understand it all, nor a
> lot of the entries in the log.
>
> One thing you said:-
>
>
> Code:
> --------------------
> > Jan 2 16:39:59 webserver postfix/cleanup[26040]: warning: database /etc/postfix/sender_canonical.db is older than source file /etc/postfix/sender_canonical
> > Jan 2 16:39:59 webserver postfix/cleanup[26040]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
>
> Ah, this is very important: it means that you have made changes to the
> configuration that were not applied.
> --------------------
>
>
> I have no idea what these changes are and I did not make them, if
> anything, I guess, they were done in an update?
Ok, every time the file /etc/postfix/virtual is changed, a corresponding
/etc/postfix/virtual.db file has to be created or updated. Postfix does not
read the “virtual” file, only the “virtual.db” file. However, it notice
that the file was changed and complains. There are several files in that
directory, map files, that need this.
To do that “compilation”, you need to do:
Code:
su -
cd /etc/postfix
postmap virtual
postmap sender_canonical
for all the files that postfix is complaining about.
To automate this, I have a file named /etc/postfix/Makefile:
Code:
all: access.db relay_ccerts.db sasl_passwd.db
transport.db canonical.db relocated.db
sender_canonical.db virtual.db
ehlo_discard_words.db sender_relayhost.db
generic.db
transport.db: transport
postmap transport
sender_relayhost.db: sender_relayhost
postmap sender_relayhost
virtual.db: virtual
postmap virtual
generic.db: generic
postmap generic
canonical.db: canonical
postmap canonical
sender_canonical.db: sender_canonical
postmap sender_canonical
sasl_passwd.db: sasl_passwd
postmap sasl_passwd
/etc/aliases.db: /etc/aliases
postalias /etc/aliases
access.db: access
postmap access
relocated.db: relocated
postmap relocated
ehlo_discard_words.db: ehlo_discard_words
postmap ehlo_discard_words
(notice that the blank spaces at the start of each line are tabs, not
spaces. That’s important).
So that now I do:
Code:
su -
cd /etc/postfix
make
Try correcting all that before doing any more tests, the results are confusing.
>
> Code:
> --------------------
> You can send mail directly provided you have a fixed internet IP and a
> domain name with an MX entry (and reversal DNS if possible). That’s the
> starting point.
> --------------------
>
>
> We do have a domain with an MX entry AND we have a fixed IP address
> (well 4 actually) and the web server itself has been allocated one of
> these: 80.175.232.147.
No, there is no MX entry.
Code:
cer@Telcontar:~> host -t MX mail.dsgmservices.com
mail.dsgmservices.com has no MX record
cer@Telcontar:~> host -t MX mail.dynamicsystems.gb.com
mail.dynamicsystems.gb.com has no MX record
I don’t know how important that will be in your case, but there isn’t one.
The problem the log shows is that postfix is thinking both names resolve to
the same machine and that he is that machine, so it can not relay to itself
as that would be a loop. You could have a problem with your local dns
resolution.
The other possibility is that the machine “mail.dynamicsystems.gb.com” in
the greeting says it is “mail.dsgmservices.com” instead of
mail.dynamicsystems.gb.com, ie, its mailserver is misconfigured.
webserver → sends to → mailserver
mail.dsgmservices.com mail.dynamicsystems.gb.com
You have more problems, in fact. See:
Code:
That might cause problems with some spam filters.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
