Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Not applicable

550 5.1.1 USER UNKNOWN

Linux webserver behind fg60: A few users complain that people that used to be able to e-mail them can' t. I requested one of the returned messages as follows: +++++++++++++++++ From: System Administrator Sent: Thursday, April 30, 2009 3:53 PM To: Judy Borgerson Cc: ' kevin@wildrowspump.com' Subject: Undeliverable: email Your message did not reach some or all of the intended recipients. Subject: FW: email Sent: 4/30/2009 3:53 PM The following recipient(s) could not be reached: ' kevin@theirdomain.com' on 4/30/2009 3:53 PM 550 5.1.1 <kevin@wildrowspump.com>... User unknown +++++++++++++++++ and another: +++++++++++++++++ > The message could not be sent because one of the recipients was rejected = > by the server. The rejected e-mail address was = > ' alyson@wildrowspump.com' . Subject ' FSR Proof' , Account: = > ' mail.imagepress.ca' , Server: ' smtp.imagepress.ca' , Protocol: SMTP, = > Server Response: ' 550 5.1.1 <alyson@wildrowspump.com>... User unknown' , = > Port: 25, Secure(SSL): No, Server Error: 550, Error Number: 0x800CCC79 +++++++++++++++ their dns is setup at EasyDNS, consulting with them they say all is ok. don' t know what to do, they are valid users, most outside people can e-mail them, but more and more can' t. thanks in advance for any help/
2 REPLIES 2
abelio
SuperUser
SuperUser

Hello, it seems not to be fortigate related.. in your shoes, i' ll re-check /etc/resolv.conf entries in the linux server and test those listed dns servers to determine if it can be able to resolve wildrowspump.com domain... a worst situation could be that wildrowspump.com domain be defined as local domain in that linux server.... but this is really off topic for this forum.

regards




/ Abel

regards / Abel
Not applicable

Abel
Sorry Abel , I did not intend to step outside the forum topic/generosity of knowledge etc. As it turned out the domain was previously hosted at TELUS. When the client decided to host internally, TELUS had not purged their dns cache/records, so any sender on the TELUS netowk was not getting through. Thanks, maybe this will help someone in the future, Dan
Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors