Hi. I'm not very techy so I might not explain this super well. I have a website that has an online form that sends me the details that the customer fills in and sends them a message saying 'thanks for getting touch and I'll get back to them'. Both of these messages get sent out as emails and go out with 'no-reply@domain.co.uk as the sender email address. The emails on my Exchange server are myname@domain.co.uk. There seems to be a problem with Exchange accepting the no-reply emails. Is there a setting I can alter so Exchange can accept them? Will I need to change the website so the domain part of the email doesn't match my server emails? Should I set up 'no-reply' as an actual email address within Exchange? Thanks, Michael

So the webform sends out the email to the customer as no-reply@domain.co.uk and relays to your exchange server but your exchange server is not accepting it? There is no rfc restriction prohibiting the use of no-reply in the local part of the smtp address.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

The webform does send out an email to the customer but I don't think it relays that one to my exchange server, that's just a thank you for your enquiry type email. The webform sends out a second email to me that contains the information that was entered in the fields of the webform (customer name, phone no, their email), and it is this second one that exchange doesn't seem to like. If I alter my email address within the website settings area to be a web based yahoo type email address that I have then I do get the email, but if I try to have that second email sent to my exchange email address it doesn't come through. I was wondering if it was because the domain part of the the webform email is the same as the domain part my email adresses set up on exchange. And even if that's not the root of the problem I still want the webform email to get sent to my work email address if possible. I want to get the no-reply email to come through exchange, I suppose I'm guessing that the same domain part is causing the problem. Maybe my GFI spam filter is catching it??? I'll have a look there.

Right, problem solved. i had forgotten that some of the spam filter rules just delete incoming emails, it is only ones that fail on a certain couple of rules that get sent to spam quarantine for inspection. When I looked at the list of all email being checked for spam the no-reply emails were being blocked because my own domain was in the block list. So it wasn't an exchange problem at all. @ Jamestechman - thanks for answering though. Cheers

The webform does send out an email to the customer but I don't think it relays that one to my exchange server, that's just a thank you for your enquiry type email. The webform sends out a second email to me that contains the information that was entered in the fields of the webform (customer name, phone no, their email), and it is this second one that exchange doesn't seem to like. If I alter my email address within the website settings area to be a web based yahoo type email address that I have then I do get the email, but if I try to have that second email sent to my exchange email address it doesn't come through. I was wondering if it was because the domain part of the the webform email is the same as the domain part my email adresses set up on exchange. And even if that's not the root of the problem I still want the webform email to get sent to my work email address if possible. I want to get the no-reply email to come through exchange, I suppose I'm guessing that the same domain part is causing the problem. Maybe my GFI spam filter is catching it??? I'll have a look there. GFI is probably blocking inbound messages that are sent FROM: your own domain to mitigate spoofing.

Right, problem solved. i had forgotten that some of the spam filter rules just delete incoming emails, it is only ones that fail on a certain couple of rules that get sent to spam quarantine for inspection. When I looked at the list of all email being checked for spam the no-reply emails were being blocked because my own domain was in the block list. So it wasn't an exchange problem at all. @ Jamestechman - thanks for answering though. Cheers