안녕하세요 다람쥐메일과 큐메일을 설치했습니다.
작성자 정보
- raemianserver 작성
- 작성일
컨텐츠 정보
- 2,635 조회
- 2 댓글
- 0 추천
- 목록
본문
SquirrelMail configtest
This script will try to check some aspects of your SquirrelMail configuration and point you to errors whereever it can find them. You need to go run conf.pl in the config/ directory first before you run this script.
SquirrelMail version: | 1.4.22 |
Config file version: | 1.4.0 |
Config file last modified: | 02 June 2015 13:44:15 |
PHP version 5.3.3 OK.
Running as N/A(N/A) / N/A(N/A)
display_errors:
error_reporting: 22527
variables_order OK: GPCS.
PHP extensions OK. Dynamic loading is disabled.
ERROR: You have configured PHP not to allow short tags (short_open_tag=off). This shouldn't be a problem with SquirrelMail or any plugin coded coded according to the SquirrelMail Coding Guidelines, but if you experience problems with PHP code being displayed in some of the pages and changing setting to "on" solves the problem, please file a bug report against the failing plugin. The correct contact information is most likely to be found in the plugin documentation.
Checking paths...Data dir OK.
Attachment dir OK.
Plugins are not enabled in config.
Themes OK.
Default language OK.
Base URL detected as: http://www.dhsquare.net/squirrelmail/src (location base autodetected)
Checking outgoing mail service....
SMTP server OK ()
Checking IMAP service....
ERROR: ERROR: Error connecting to IMAP server "xxx.xx.xx.xxx:110".Server error: (110) Connection timed out
그래서 110번 포트도 열고 다 했는데도 여전히 접속이 안됩니다.
다람쥐메일 로그인 페이지에서 로그인 하면
아래와 같은 메시지가 뜹니다.
ERROR |
Error connecting to IMAP server: 117.52.74.109. 110 : Connection timed out
|
관련자료
-
이전
-
다음
지유파파님의 댓글
- 지유파파
- 작성일
Luatic님의 댓글
- Luatic
- 작성일
PHP extensions OK. Dynamic loading is disabled.
ERROR: You have configured PHP not to allow short tags (short_open_tag=off). This shouldn't be a problem with SquirrelMail or any plugin coded coded according to the SquirrelMail Coding Guidelines, but if you experience problems with PHP code being displayed in some of the pages and changing setting to "on" solves the problem, please file a bug report against the failing plugin. The correct contact information is most likely to be found in the plugin documentation.