Hi,
I'm looking into OTRS 5s to replace our current limited Osticket system.
However I'm running into several issues concerning mailing with the new OTRS installation.
In the system log is telling me that we can't connect to our Exchange server true Imap.
When I use telnet to connect op port 993 it just answers like it fine.
Any idea's how to troubleshoot this further? I'm read several topics on this and other forums but I can't find the cause of this problem.
I need to fix this asap if we want to use OTRS as our new ticket solution, everything els is clear and setup, only mailing seems to be an issue.
I restated the server and re-installed fetchmail but I still have these errors comming:
There was an error executing /usr/bin/fetchmail -a: The run control file had bad permissions.
Best regards,
Kristof Loos
OTRS 5s IMAP Exchange 365 - Fetchmail
Moderator: crythias
Re: OTRS 5s IMAP Exchange 365 - Fetchmail
Hi,
first you should check if all modules are installed correctly ($OTRSHOME/bin/otrs.CheckModules.pl)
You don't need fetchmail. You can configure POP3(S)/IMAP(S)/IMAPTLS in Admin -> Postmaster Mail Accounts.
This should work fine. The OTRS Daemon will take care about fetching the mails.
Check here for more infos
http://doc.otrs.com/doc/manual/admin/st ... p3-account
Sending is configured in Sysconfig Core::Sendmail
the recommended solution is, to set up a local MTA on your machine, configure it to use procmail
http://doc.otrs.com/doc/manual/admin/st ... eiving-cmd
Regards
Florian
first you should check if all modules are installed correctly ($OTRSHOME/bin/otrs.CheckModules.pl)
You don't need fetchmail. You can configure POP3(S)/IMAP(S)/IMAPTLS in Admin -> Postmaster Mail Accounts.
This should work fine. The OTRS Daemon will take care about fetching the mails.
Check here for more infos
http://doc.otrs.com/doc/manual/admin/st ... p3-account
Sending is configured in Sysconfig Core::Sendmail
the recommended solution is, to set up a local MTA on your machine, configure it to use procmail
http://doc.otrs.com/doc/manual/admin/st ... eiving-cmd
Regards
Florian
OTRS 8 SILVER (Prod)
OTRS 8 auf Debian 11 (Test)
Znuny 7.x latest version testing auf Debian 11
-- Ich beantworte keine Forums-Fragen PN - No PN please
I won't answer to unfriendly users any more. A greeting and regards are just polite.
OTRS 8 auf Debian 11 (Test)
Znuny 7.x latest version testing auf Debian 11
-- Ich beantworte keine Forums-Fragen PN - No PN please
I won't answer to unfriendly users any more. A greeting and regards are just polite.
-
- Znuny newbie
- Posts: 11
- Joined: 05 Jul 2017, 21:17
- Znuny Version: 5.0.20
- Real Name: Kristoffel Loos
- Company: Telecom IT
Re: OTRS 5s IMAP Exchange 365 - Fetchmail
Hi,
Thanks for the repsonse!
All perl modules are installed, that's no issue, smtp works on our domain only pulling or fetching the mails by de Deamon fails every 10 minutes.
MTA like sendmail is only to send out, that's no issue or I'm I worng?
Kristof
Thanks for the repsonse!
All perl modules are installed, that's no issue, smtp works on our domain only pulling or fetching the mails by de Deamon fails every 10 minutes.
MTA like sendmail is only to send out, that's no issue or I'm I worng?
Kristof
Re: OTRS 5s IMAP Exchange 365 - Fetchmail
Hi,
MTA is for sending/receiving (local sendmail/postfix/exim/...)
If you are using the Admin -> Postmaster Mailbox setting (POP3/IMAP) you don't need to have fetchmail configured.
Florian
MTA is for sending/receiving (local sendmail/postfix/exim/...)
If you are using the Admin -> Postmaster Mailbox setting (POP3/IMAP) you don't need to have fetchmail configured.
what about the logs?pulling or fetching the mails by de Deamon fails every 10 minutes
Florian
OTRS 8 SILVER (Prod)
OTRS 8 auf Debian 11 (Test)
Znuny 7.x latest version testing auf Debian 11
-- Ich beantworte keine Forums-Fragen PN - No PN please
I won't answer to unfriendly users any more. A greeting and regards are just polite.
OTRS 8 auf Debian 11 (Test)
Znuny 7.x latest version testing auf Debian 11
-- Ich beantworte keine Forums-Fragen PN - No PN please
I won't answer to unfriendly users any more. A greeting and regards are just polite.
-
- Znuny newbie
- Posts: 11
- Joined: 05 Jul 2017, 21:17
- Znuny Version: 5.0.20
- Real Name: Kristoffel Loos
- Company: Telecom IT
Re: OTRS 5s IMAP Exchange 365 - Fetchmail
hi,
We can mail true our exchange 2013 smtp on port 25 without authentication, we are white listed.
I made also de mistake to forget add the email adress so it wasn't allowed to relay, but that's sloved now.
I think the mail issue is at the side of the Exchange server, our Admin is looking into that right now.
--
Br,
Kristof Loos
We can mail true our exchange 2013 smtp on port 25 without authentication, we are white listed.
I made also de mistake to forget add the email adress so it wasn't allowed to relay, but that's sloved now.
I think the mail issue is at the side of the Exchange server, our Admin is looking into that right now.
--
Br,
Kristof Loos
-
- Znuny newbie
- Posts: 11
- Joined: 05 Jul 2017, 21:17
- Znuny Version: 5.0.20
- Real Name: Kristoffel Loos
- Company: Telecom IT
Re: OTRS 5s IMAP Exchange 365 - Fetchmail
Since there should be a certificate in place on the Exchange server for IMAPS on 993 I came accross the tool: sslscan.
So if you run this on like: sslscan mail.server.com:933 you should get results like:
Accepted TLSv1 256 bits ECDHE-RSA-AES256-SHA
But I only get Failed for all. Could this mean that the Exchange isn't setup with an valid certificate, and this is the reason why OTRS can't get mail true the IMAPS??
Br,
Kristof Loos
So if you run this on like: sslscan mail.server.com:933 you should get results like:
Accepted TLSv1 256 bits ECDHE-RSA-AES256-SHA
But I only get Failed for all. Could this mean that the Exchange isn't setup with an valid certificate, and this is the reason why OTRS can't get mail true the IMAPS??
Br,
Kristof Loos
-
- Znuny newbie
- Posts: 11
- Joined: 05 Jul 2017, 21:17
- Znuny Version: 5.0.20
- Real Name: Kristoffel Loos
- Company: Telecom IT
Re: OTRS 5s IMAP Exchange 365 - Fetchmail
Hi,
The problem has been resolved, finally it seemed to be an issue on the Exchange server side!
br,
The problem has been resolved, finally it seemed to be an issue on the Exchange server side!
br,