Opened 20 years ago
Closed 20 years ago
#1873 closed defect (invalid)
Notification Error
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.8.4 |
| Severity: | minor | Keywords: | notification email |
| Cc: | sekhargs@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
When I enable Notify option, I am getting the below error.
Python traceback
Traceback (most recent call last):
File "C:\PYTHON23\Lib\site-packages\trac\core.py", line 531, in cgi_start
real_cgi_start()
File "C:\PYTHON23\Lib\site-packages\trac\core.py", line 526, in real_cgi_start
dispatch_request(path_info, args, req, env)
File "C:\PYTHON23\Lib\site-packages\trac\core.py", line 441, in dispatch_request
module.run()
File "C:\PYTHON23\Lib\site-packages\trac\Module.py", line 44, in run
self.render()
File "C:\PYTHON23\Lib\site-packages\trac\Ticket.py", line 450, in render
self.save_changes (id)
File "C:\PYTHON23\Lib\site-packages\trac\Ticket.py", line 379, in save_changes
tn.notify(ticket, newticket=0, modtime=now)
File "C:\PYTHON23\Lib\site-packages\trac\Notify.py", line 228, in notify
NotifyEmail.notify(self, ticket['id'], subject)
File "C:\PYTHON23\Lib\site-packages\trac\Notify.py", line 131, in notify
Notify.notify(self, resid)
File "C:\PYTHON23\Lib\site-packages\trac\Notify.py", line 79, in notify
self.begin_send()
File "C:\PYTHON23\Lib\site-packages\trac\Notify.py", line 139, in begin_send
self.server = smtplib.SMTP(self.smtp_server)
File "C:\Python23\lib\smtplib.py", line 240, in __init__
(code, msg) = self.connect(host, port)
File "C:\Python23\lib\smtplib.py", line 288, in connect
for res in socket.getaddrinfo(host, port, 0, socket.SOCK_STREAM):
gaierror: (7, 'getaddrinfo failed')
The trac.ini Settings are as follows:
[notification] smtp_enabled = TRUE smtp_replyto = sekhargs@medicomsoft.com smtp_always_cc = smtp_server = medicomsoft.com smtp_from = ravi@medicomsoft.com always_notify_reporter = FALSE
Attachments (0)
Change History (4)
comment:1 by , 20 years ago
| Description: | modified (diff) |
|---|---|
| Milestone: | 0.8.3 |
comment:2 by , 20 years ago
It seems the smtp host used is perfectly resolvable, I'm not sure what is causing this error.
You do seem to be using medicomsoft.com as the smtp host, while you should be using smtp.medicomsoft.com instead. Maybe that will help?
comment:3 by , 20 years ago
| Keywords: | notification email added; Notify removed |
|---|
comment:4 by , 20 years ago
| Priority: | high → normal |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
medicomsoft.com is a domain.
- The default name resolution leads to
204.174.223.150, which does not serve SMTP requests. - The STMP service for this domain seems to be available on
smtp.medicomsoft.com(204.174.223.198):nslookup > set query=MX > medicomsoft.com medicomsoft.com mail exchanger = 10 smtp.medicomsoft.com.
MXmeans "Mail Exchanger" for the DNS request
However, the trace log seems to show that there is an additional error, as the expected error message with a invalid SMTP server would be something like
"Connection refused". You may experience a name resolution error as well.
You can use "nslookup" - available on any platform (Windows, Unix, Mac, …) - to double check that your system is able to resolve 'smtp.medicomsoft.com' into a valid IP address.
Feel free to reopen this ticket if you still experience a problem with a valid SMTP server.



Improved readability of description