Koozali.org: home of the SME Server

Sending email to an e-smith server

Spencer Fornaciari

Sending email to an e-smith server
« on: November 01, 2001, 08:42:34 AM »
Hey,
I've got webmail up and working, with everything apparently setup as its supposed to be.  I have my e-smith server up and running.  The website works, I have the DNS working and people can reach my website via it.  I can email out from webmail but none of the mail I send to my server is reaching the system…any idea what is causing this?  Any help would be appreciated.  Thanks.

schwiers

Re: Sending email to an e-smith server
« Reply #1 on: November 01, 2001, 04:16:55 PM »
I'm having the same problem.  Things were working then two days ago somthing changed.  The error message received when sending email to the mail server says that the recipient could not be reached. Diagnostic-code: smtp;550 5.1.1   ... User Unknown
What does that mean/indicate?  Any help would be appreciated. thanks. sls

Spencer Fornaciari

Re: Sending email to an e-smith server
« Reply #2 on: November 01, 2001, 11:02:27 PM »
Nevermind...it just took like 12 hours to receive it for whatever reason.  Thanks anyway.

enigma

Re: Sending email to an e-smith server
« Reply #3 on: November 02, 2001, 12:18:22 AM »
I have a simliar problem with version 5 - all mail services worked on 4.1.2, a clean install of 5 and installation of updated blades....... no mail?

??anyone??

sage

Re: Sending email to an e-smith server
« Reply #4 on: November 02, 2001, 02:27:45 AM »
enigma

Have you logginto admin to check the mail?  I was not receving mail until I checked there.  Everything was bouncing and going there.

enigma

Re: Sending email to an e-smith server
« Reply #5 on: November 02, 2001, 03:07:04 PM »
Hi Sage

yes i did :) - :( no mail :(   ?:{

but still no mail, it looks as though my server is not holding the retrieval settings to my isp... cant work out for teh life of me why - all was well till i moved to v5

any ideas?

Steve Schwier

Re: Sending email to an e-smith server
« Reply #6 on: November 03, 2001, 05:47:47 PM »
Problem solved.  My ISP had made some incorrect DNS changes.  Originally they denied they had created the problem.  It only took three for them to admit and fix it.