#4243 closed defect (worksforme)
Can't get notifications using Exchange
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | 0.10.2 |
Severity: | normal | Keywords: | notification msexchange |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I can't configure trac to use exchange as a server.
Attachments (0)
Change History (6)
comment:1 by , 18 years ago
Keywords: | notification needinfo added |
---|
follow-up: 3 comment:2 by , 18 years ago
The error I get in trac.log using Exchange is:
2006-12-06 14:07:59,736 Trac[web_ui] ERROR: Failure sending notification on change to ticket #26: Connection unexpectedly closed Traceback (most recent call last): File "C:\Python24\Lib\site-packages\trac\ticket\web_ui.py", line 551, in _do_save tn.notify(ticket, newticket=False, modtime=now) File "C:\Python24\Lib\site-packages\trac\ticket\notification.py", line 127, in notify NotifyEmail.notify(self, ticket.id, subject) File "C:\Python24\Lib\site-packages\trac\notification.py", line 216, in notify Notify.notify(self, resid) File "C:\Python24\Lib\site-packages\trac\notification.py", line 114, in notify self.begin_send() File "C:\Python24\Lib\site-packages\trac\notification.py", line 278, in begin_send self.server = smtplib.SMTP(self.smtp_server, self.smtp_port) File "C:\Python24\lib\smtplib.py", line 244, in __init__ (code, msg) = self.connect(host, port) File "C:\Python24\lib\smtplib.py", line 307, in connect (code, msg) = self.getreply() File "C:\Python24\lib\smtplib.py", line 351, in getreply raise SMTPServerDisconnected("Connection unexpectedly closed") SMTPServerDisconnected: Connection unexpectedly closed
I get it whether I set a username and password or not, whether I use TLS or not, whether I have the default domain set or not.
When I telnet to the exchange server and proper port, it seems that a connection is established, and then when you hit any key, it is dropped. The telnet log file has no data. Telnetting to port 80 on the server and hitting a bunch of keys results in an HTTP/1.1 bad request. (I'm sophisticated ;) )
I'll check with the Exchange admin to see if it accepts SMTP inbound connections. I don't know about TLS, but turning it in trac.ini on doesn't fix the issue.
comment:3 by , 18 years ago
Replying to anonymous:
When I telnet to the exchange server and proper port, it seems that a connection is established, and then when you hit any key, it is dropped.
I assume you meant port 25?
If you cannot at least type 'HELO' (or 'EHLO') and get a valid reply from the server, Trac will not be able to use this server. Maybe the connection is encrypted (SSL), in such a case the usual port is 465 (ssmtp), not 25. Be aware that Trac does not support SSL connections for now - whatever the port number.
comment:4 by , 18 years ago
Yeah it was connecting to port 25, not using an SSL connection, and the issue was resolved when the sysadmin adjusted some Exchange settings, though he didn't let me know what he did. Basically, Exchange was refusing my connection and he configured it to allow it then the Trac bits worked just fine. Prior to and after his adjustments my Outlook connected just fine, which made me unsure about the source of the problem. Thanks for your quick reply.
comment:5 by , 18 years ago
Keywords: | needinfo removed |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
comment:6 by , 8 years ago
Keywords: | msexchange added |
---|
Well, I would say that as for any installation issue, you'd better first to ask for help in the MailingList or over #IRC.
Anyway, can you provide more information, as it's hard to help you with so few pieces of information.
trac.ini
file)