Clayton wrote:
Running a mailserver on a dynamic IP-address is difficult at best, but I guess it could work if your dyndns stuff is working.
Nothing like starting on the harder side of things :-) In theory, that is what DynDNS is supposed to "help" with. They provide a fixed point for the mail to be received and relay it to me.
A few years ago I already gave up on using a dynamic ip even for a private server to tinker with. You are facing two problems with a dynamic ip: - receiving: you have to rely on dyndns to switch fast enough to your current address AND rely on external clients not to cache the dns results too long. - sending: if you don't use your isp mailserver as relay you might as well stop here. Most mailservers do not accept mails from clients with dynamic ip. Additionally, your reverse dns record does not match your dyndns name.
Buried in the mail bounce is: Diagnostic-Code: X-Postfix; unknown user: $USERNAME (where $USERNAME is the alias name I set in /etc/aliases, and attempted to use mailx to send a test message to)
As Per already mentioned, you edit the source file /etc/aliases and build the database /etc/aliases.db with the command "newaliases". If Postfix discovers that the sourcefile is more recent than the database it will log a warning.
Also... in the mail headers I'm seeing, wherever the server name is mentioned: hostname.domainname.com
eg: linux-tily.mydomain.com
where I want it to read just mydomain.com... or would like it to.
Please show output of "postconf -n". If you don't use fully qualified domain names in the addresses then Postfix will qualify the username with the value of $myorigin. Change it to the value you desire: "postconf myorigin" shows what is currently configured.
External mail - are you using your ISPs mailserver to relay through or are you sending directly? I.e. have you set relayhost in your postfix config? Do you see the mail being delivered? (check your log).
I do not want to use my ISPs mailserver (various reasons, including all their support info is in German, and my German skills are pathetic at best)... so I'm hoping to use my own setup/server.
That will only work as desired if your server has a fixed ip. Nothing else will be worth the trouble.
I've set my relayhost to my own domain... and checked the logs again. Hmmmm... I think this has put me on to the problem... now (after setting my relayhost), I'm seeing a nice helpful bounce error:
Remote-MTA: dns; mx1.mailhop.org Diagnostic-Code: smtp; 550 Sender verify failed
So... I need to sort out that part... which I should be able to do... I hope (the remote MTA is the one DynDNS provides).
Haven't used it but that message tells you the domain you were using in your sender address does not exist in DNS. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org