2524: email is no response
- WontFix
- Review Board
| Bill*****@gmai***** (Google Code) (Is this you? Claim this profile.) | |
| March 12, 2012 |
What version are you running? 1.6-bate2 What's the URL of the page containing the problem? na What steps will reproduce the problem? 1.E-mail setting :port:587 use TLS What is the expected output? What do you see instead? expected output: send e-mails for review requests and views instead: if the user who login in and whose mail address is the Sender e-mail address in E-mail Setting, then the reviewboard will send the mail after some perating. But if the user who login in and whose mail address is not the Sender e-mail address in E-mail Setting, then reviewboard will not send the mail anyway after some perating. why ? What operating system are you using? What browser? win xp and ie8 Please provide any additional information below.
I'm afraid I don't understand. I think you'll need to dig into your mail server logs to see what's happening. I also highly suggest upgrading. 1.6 beta 2 is pretty old code.
-
+ NeedInfo
http error log： SMTPDataError: (550, '5.7.1 Client does not have permissions to send as this sender') ERROR:root:Error sending e-mail notification with subject 'Re: Review Request: test mail1' on behalf of '"yangsq" <yangsq@neusoft.com>' to '"admin admin" <admin@neusoft.com>,"yangsq" <yangsq@neusoft.com>': (550, '5.7.1 Client does not have permissions to send as this sender') Probably because our e-mail system do not support "behalf of sender". Can you tell me which code I could change and remove the "behalf of sender" and all mails send from the mail which address set in E-mail Setting and without "behalf of sender".
The from/sender addresses are all set in reviewboard/notifications/email.py We're pretty set in our ways as far as the way we send email (our current configuration is more likely to get through than anything else), and we highly recommend fixing your SMTP server configuration rather than trying to hack reviewboard.
-
- NeedInfo + WontFix
I see, but fixing our SMTP server configuration is difficult for me, Because fixing the SMTP configuration is the behavior of our company, the scope of influence is large, the SMTP server configuration is one of the security policy of our company. And More trouble, We must use our company mail system, We can not use other mail system at company. So I am sorry I think whethor I can change the code . Can you help me ? we hope use reviewboard very much.
Try upgrading. It's possible this was fixed in a point release. I don't think we were sending the right headers in the 1.6 betas.
:( I upgrade to 1.6.4.1, but the problem is not solved.
Did you run any version prior to the 1.6 beta? I need to know exactly what header it's upset about. We've always overridden the From: header.
I may load ReviewBoard-1.5.5-py2.5.egg and just see see and not run it ,and then, I update to 1.6 beta, and test it. before our company mail system upgrade, the mail send is ok, after the mail system upgrade, the mail send is not ok, and then, I upgrade it to 1.6.4.1 now.
：） I change the code "SpiffyEmailMessage": "headers['From'] = from_email" to "headers['From'] = sender" , then the problem is solved.
I have another question，The bugs can add mantis ? We use mantis to manage bugs.
:) I find the bug setting. I can use the mantis now.
i am facing the same problem ,and i tried to change headers['From'] = from_email" to "headers['From'] = sender",but it still not work,the error log still shows that "SMTPDataError: (550, '5.7.1 Client does not have permissions to send as this sender')" but the default user can send the email successfully and others can not. i remember that everyone can send the request email before the email server upgrate,and now we login in email server with username like "username" rather than "username@example.com" before
I have tested the method which is supplied by Bill, it works well, thanks. I think your way is to cheat the outlook mail server :) But I think it is better to apply generic mailbox(all users can send mail on behalf of this mailbox) to solve this problem. @fuye: maybe you should try to restart your apache server after you modify the code.