User:marketing.btw Size:2904 Dest:/var/mail/marketing.btw Mode:None
I can actually see test messages I've sent to the email address using the 'Read User Mail' in Virtualmin however Outlook isn't collecting it now for some reason. There are no errors Outlook seems to check the mailbox OK however no mail is actually being downloaded.
This is odd as tests I ran much earlier prior to getting the outgoing SMTP working were collected by Outlook so something must have changed/be different now.
How can I fix/troubleshoot this?
So, your email is being delivered, but to the wrong place.
Virtualmin will read email from anywhere, but since it's being delivered incorrectly, it's not accessible from Outlook.
What does your /etc/procmailrc file contain?
Also, to fix the "fatal: open database /etc/aliases.db: No such file or directory" error, you can run the command "newaliases".
Here's the contents of /etc/procmailrc.....
* ?/usr/bin/test "$EXITCODE" = "73"
* ?/usr/bin/test "$VIRTUALMIN" != ""
I did add a new mail user so do I have to run the newaliases command everytime I add an alias?
It looks like some incorrect lines got in there somehow... try replacing these 5 lines at the end:
With these 3 lines:
And no, you don't need to run newaliases each time.
Thanks Eric, just sent a test and received it from the pop box so I think that this has solved it! Thank you very much for the help you have given me.
Further to this old issue I have just seen this reoccur again we updated packages on the server and procmailrc was overwritten again as described above, what can I do to stop this from happening in the future?
Do you happen to know what package caused the update?
Or do you have a list of packages that were updated recently?
And can you remind me what distro you're using?
Is there a log somewhere I can view showing packages that have been updated?
Operating system CentOS Linux 5.6
Virtualmin version 3.96.gpl GPL
Webmin version 1.600
Kernel and CPU Linux 126.96.36.199-rscloud on x86_64
You can see the packages updated on a CentOS system by looking in /var/log/yum.log.