Link to home
Start Free TrialLog in
Avatar of Zabulon777
Zabulon777

asked on

553 Terminating connection as the sender is spoofed. issue

I am having an issue where a user that is using Taleo ( http://www.taleo.com ) is getting the following error:
 553 Terminating connection as the sender is spoofed.
while trying to send an email through Taleo.  It kicks back to Outlook 2003 and I verified that the msg isn't even getting to the exchange server.  The user is internal so maybe it is a relay issue where Exchange isn't allowing the client machine to relay?

Any help would be appreciated.
Avatar of Ludovick Lagrevol
Ludovick Lagrevol
Flag of France image

try to add the machine ip to the relay permited computes  on SMTP connector in the exchange server manager.
Avatar of Zabulon777
Zabulon777

ASKER

Ok just added it, now I have to wait until the user gets back and tests tomorrow! I will let you know what happens in the morning. Thanks!
ASKER CERTIFIED SOLUTION
Avatar of mvvinod
mvvinod

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Also check what the from address on the e-mail is going out as. If user uses "from" other than their own and they dont have send as permission for that mailbox, exchange responds back with similar message.

I dont know if the "from" is generated by taleo. You might want to check that also to see what the from is set as if its set in taleo.

Vinod.
Here is the exact error msg that shows up in the users mailbox (outlook 2003) after trying to send a mail through Taleo applicaiton.

       The e-mail system was unable to deliver the message, but did not report a specific reason.  Check the address and try again.  If it still fails, contact your system administrator.
            < nyrelay.taleo.com #5.0.0 X-Postfix; host mail.enerplus.com[208.38.44.211] said: 553    Terminating connection as the sender is spoofed. (in reply to MAIL FROM    command)>

It looks likes its trying to relay it from the client machine... and doesnt look like it ever hits the Exchange box.