Evolution mail client & remote SMTP server = can't send

[bubba]

Steps to reproduce the problem:
1. Create account IMAP (receive) SMTP (send),
both require authentication

2. Send mail to user not at remote SMTP
server

3. Evolution asks for SMTP password, enter it

4. Error from Evolution: "RCPT TO response
error: Requested action not taken: mailbox
unavailable: mail not sent"

However, Error from debug:

sending : MAIL FROM:
<koralesky@xxxxxxxxx.edu>
received: 250 2.5.0 Address Ok.
sending : RCPT TO: <barron@xxxx.xxxx.edu>
received: 550 5.7.1 Relaying prohibited:
barron@xxxx.xxxx.edu
sending : QUIT
received: 221 2.3.0 Bye received. Goodbye.


I would expect this if relaying was not allowed (it is allowed, but only for authenticated users). Mail sent in the same manner through the SMTP server using Mozilla Mail or Mulberry work fine and are sent to other servers. It seems that only Evolution does not send.



Anyone seen this? Anyone have any ideas about how to get around it?

 

[rahvin]

I've never used evolution but there is something definately wrong with one of your addresses. If you get that error from the mail server than the server 1. Thinks you are outside its block of valid IP's for relaying or 2. Using a From field that does not match the accepted from field of the server.

This "barron@xxxx.xxxx.edu" leads me to believe it is number 2, Evolution appears to be saying your email is barron@xxx.xxxx.edu, when in fact the server probably only accepts email from fields of the form barron@xxxx.edu.

 

[bubba]

The same configuration works for two other mail clients (Mozilla and Mulberry) to the same set of servers, so it is not that the server doesn't allow it....