#4871 closed defect (wontfix)
Notification is failing
Reported by: | ashish | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | notification | Version: | 0.10.4 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 387, in dispatch_request dispatcher.dispatch(req) File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 237, in dispatch resp = chosen_handler.process_request(req) File "build/bdist.linux-i686/egg/tracdiscussion/core.py", line 72, in process_request File "build/bdist.linux-i686/egg/tracdiscussion/api.py", line 33, in render_discussion File "build/bdist.linux-i686/egg/tracdiscussion/api.py", line 503, in _do_action File "build/bdist.linux-i686/egg/tracdiscussion/notification.py", line 91, in notify File "/usr/lib/python2.4/site-packages/trac/notification.py", line 216, in notify Notify.notify(self, resid) File "/usr/lib/python2.4/site-packages/trac/notification.py", line 114, in notify self.begin_send() File "/usr/lib/python2.4/site-packages/trac/notification.py", line 287, in begin_send self.server.login(self.user_name, self.password) File "/usr/lib/python2.4/smtplib.py", line 587, in login raise SMTPAuthenticationError(code, resp) SMTPAuthenticationError: (535, 'authentication failed (#5.7.1)')
Attachments (0)
Change History (9)
comment:1 by , 18 years ago
Description: | modified (diff) |
---|---|
Keywords: | needinfo added |
Milestone: | 0.10.4 |
Severity: | blocker → major |
comment:2 by , 18 years ago
comment:4 by , 18 years ago
Component: | general → notification |
---|---|
Keywords: | needinfo removed |
comment:5 by , 17 years ago
Resolution: | wontfix |
---|---|
Severity: | major → normal |
Status: | closed → reopened |
Version: | 0.10.3 → 0.10.4 |
I'm experiencing the same error. Here's the output of my error log…
Trac[web_ui] ERROR: Failure sending notification on change to ticket #22: (535, '5.7.0 authentication failed') Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/trac/ticket/web_ui.py", line 562, in _do_save tn.notify(ticket, newticket=False, modtime=now) File "/usr/lib/python2.3/site-packages/trac/ticket/notification.py", line 129, in notify NotifyEmail.notify(self, ticket.id, subject) File "/usr/lib/python2.3/site-packages/trac/notification.py", line 216, in notify Notify.notify(self, resid) File "/usr/lib/python2.3/site-packages/trac/notification.py", line 114, in notify self.begin_send() File "/usr/lib/python2.3/site-packages/trac/notification.py", line 287, in begin_send self.server.login(self.user_name, self.password) File "/usr/lib/python2.3/smtplib.py", line 583, in login raise SMTPAuthenticationError(code, resp) SMTPAuthenticationError: (535, '5.7.0 authentication failed')
and here is the notification section
[notification] smtp_enabled = true smtp_server = localhost smtp_from = trac@naivepixel.net smtp_port = 25 smtp_replyto = trac@naivepixel.net smtp_user =trac@naivepixel.net smtp_password ={encripted}
comment:6 by , 17 years ago
Sorry, I put my wrong email address instead of .net is .com, but in the app we use the .net address
comment:7 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | reopened → closed |
Well, if SMTP authentication is failing, I don't think there's much Trac can do here:
You either used the wrong settings, or used a SMTP server that do not support these settings. A quick look at your settings shows that you're using the machine where Trac runs (localhost) with an unusual user name (as the username contains a domain). Are you sure about this?
comment:8 by , 17 years ago
Resolution: | wontfix |
---|---|
Status: | closed → reopened |
Yes I'm shure. I have setup mail services with other applications on my webserver this way. What I found out in my Hosting Service is this
'''Authentication''': The server uses pop-before-smtp authentication, so the settings for sending mail should not include any authentication. What this means is that the mail server will rely on a recent successful POP authentication result in order to send outgoing mail. If you find that you are sometimes being challenged for authentication, or encountering authentication issues when sending mail, change your mail client setting for "check for new messages" to a smaller time interval, say 2 or 3 minutes.
Here is the url to check out how to configure email settings on my provider. Eapps My question would be, does SMTPAuth uses pop first then smtp?
comment:9 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | reopened → closed |
So here it is: the POP-before-SMTP hack is not supported by Trac.
There is a ticket about this feature, but I doubt it is ever implemented in Trac core, maybe some day as a plugin.
SMTP AUTH uses well SMTP authentication, TLS is also supported. POP-before-SMTP is not.
From the error message, this error seems related to an authentication issue on the SMTP server, not to a blocker error in Trac.
Please post the
[notification]
section of yourtrac.ini
file.btw: please be fair with the severity field: this is not a blocking issue.