Hi,
i am a little bit confused; while almost any email accounts work; some of them doesn’t.
I have checked various posts here, and yes, the line “myorigin=” has been removed from main.cf The problem, in fact is, that with one specific virtual server, i won’t be able to receive postmaster@ webmaster@ emails.
Standard User Mail is working; but the system’s mail aliases don’t work. I will always get:
Recipient address rejected: User unknown in virtual mailbox table
This is driving me nuts. I have forwarded the emails for postmaster@ to an external email-address, although this is working with other virtual servers, it won’t work with this one specific server.
hostname -f returns a FQDN neither Postfix or Apache claim about missing FQDN. I have set the hosts files like this:
A hostname would typically be an FQDN format – host.example.com. It looks like you just mentioned “example.com” though.
If your hostname is just a domain name, and also happens to be a Virtual Server, that can sometimes cause problems.
I’d recommend making sure that your hostname is in the format host.example.com, and that there’s no Virtual Server with the same name as your hostname.
I will probably need to have also an virtual host like example.com; so i will have to change hostname in something different.
What would you suggest to use? And how could i achieve this without having to reinstall everything?
But anyway, although normal emailusers under example1.com work, the systemaliases won’t, so any mail to webmaster, postmaster etc. will bounce.
Thanks for help.
Problem is, that i want to issue certificates for example1.com, and i will need to receive an confirmation code on one of the system accounts in order to continue, so i will have to get it working somehow.
Btw, when i wanted to copy newly created certificates over to Webmin Virtualmin died with an errormessage, like could not find PID, and then wasn’t available anymore. I restarted the system but webmin didn’t work. Afterwards i found out, that he said, that he couldn’t open the certificates file, although it had all the rights and user/group settings like one on a another server i compared it to, but it kept nagging. So i commented the line with the named cert file and changed the line of the keyfile back to the standard .pem file and was able to get it up again.
I also encountered missing Mailbox Dirs, also with an missing PID error…
I poked around a bit and compared the settings for the virtual servers, with which it is working, and i found out, that there doesn’t seem to be a difference. So if anyone could point me in the right direction, i’d appreciate it very much.
I will probably need to have also an virtual host like example.com; so i will have to change hostname in something different. What would you suggest to use? And how could i achieve this without having to reinstall everything?
Well, if you’d like to use example.com sometime as a Virtual Server, it might make this a good time to change your hostname.
It’s simple to do though, and does not require reinstalling.
You can do that by going into Webmin -> Networking -> Network Config -> Hostname and DNS Client, and change your hostname there.
When you’re done, try restarting Webmin, as that may resolve the PID errors you received. You can do that with this command:
/etc/init.d/webmin restart
When you’ve completed that, see if that resolves your email issue.
If not – one place to start would be to go into System Settings -> Re-Check Config, and make sure it doesn’t notice any problems.
warning: dict_nis_init: NIS domain name not set - NIS lookups disabled
But it looks like there is a server in Taiwan, where someone tried to use the mailserver as relay.
Also freshclam seems to have a problem:
freshclam[19137]: segfault at 13d2000 ip 00007f35348c0e78 sp 00007fff57c65160 error 4 in libclamav.so.6.1.7[7f353468e000+907000]
But it does not show anything about the message, which was bounced. Weird, huh?
The message is bounced with Err 550; but the alias is available, and whether i set it to forward it to an external mail account, the admin user of the virtual domain or the admin user’s email, nothing works at all.