Unable to recieve email

I had virtualmin up and functioning for over a year. Last night I deleted two of my virtual servers and now I am unable to receive email. Any help would be appreciated. Thanks

Status: 
Closed (fixed)

Comments

Could you explain further what is going wrong? Do email senders get bounces, or does mail just disappear?

Also, what gets logged to /var/log/mail.log when someone tries to send you email?

Outside email gets bounced with a 554 error. Here is the bounce message.

Hi. This is the qmail-send program at gateway11.websitewelcome.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out.

info@scrapbookmate.com: 62.41.49.156 does not like recipient. Remote host said: 554 5.7.1 info@scrapbookmate.com: Relay access denied Giving up on 62.41.49.156.

Here's an entry in the /var/log/maillog of an email that I tried to send:

Jul 15 03:36:04 sawgrass postfix/qmgr[30264]: 37C222D8369: removed Jul 15 03:37:11 sawgrass postfix/smtpd[31870]: connect from gateway14.websitewel come.com[67.18.72.130] Jul 15 03:37:11 sawgrass postfix/smtpd[31870]: NOQUEUE: reject: RCPT from gatewa y14.websitewelcome.com[67.18.72.130]: 554 5.7.1 info@scrapbookmate.com: Relay access denied; from=sunfleming@sonomawatereng.com to=info@scrapbookmate.com proto=SMTP helo=<gateway14.websitewelcome.com> Jul 15 03:37:11 sawgrass postfix/smtpd[31870]: disconnect from gateway14.website welcome.com[67.18.72.130]

Thanks for your help

In Virtualmin, go to Limits and Validation -> Validate Virtual Servers, select the scrapbookmate.com domain and run a validation of all features. Let us know if that reports any errors ..

Running the validation of scrapbookmate reported that email for scrapbookmate.com wasn't enabled. However under edit server, the checkbox was checked. I disabled mail and saved the settings and then re-enabled mail and saved it. It is now working. Yay it is now working.

Thanks for your help

Cool .. let me know if you see this problem re-occur, as it may indicate a bug.

Automatically closed -- issue fixed for 2 weeks with no activity.