Rouncube Http

Discuss according roundcube product has the main webmail managed by artica

Rouncube Http

New postby zetar » Wed Aug 14, 2013 8:25 pm

Hello, after a long long time. here I am.
I have a problem with Roundcube, it was three but two I resolved, I have made ​​progress.
Until two days ago, it was configured to be reached on port 80, now on port 449, I should return to port 80, as I do.
""correction: Starting......: [INIT]: RoundCube Web disabled (RoundCubeHTTPEngineEnabled)..
Stopping......: [INIT]: RoundCube Web DB: [roundcubemail]: All are ok, nothing to do...
Starting......: Roundcube password Enabled
Starting......: Roundcube jqueryui Enabled
Starting......: Roundcube fail2ban Enabled
Starting......: Roundcube dkimstatus Enabled
Starting......: Roundcube msglistcols Enabled
Starting......: Roundcube calendar Enabled
Starting......: Roundcube sieverules Enabled
Starting......: [INIT]: RoundCube Web `plugins/sieverules/config.inc.php`
Starting......: Roundcube (php) sieverules_port (4190)
Starting......: [INIT]: RoundCube Web `/usr/share/roundcube/config/db.inc.php`
Starting......: [INIT]: RoundCube Web `/etc/roundcube/debian-db.php`
Starting......: [INIT]: Artica Web service PHP-FPM is enabled
Starting......: [INIT]: RoundCube Web Listen port 449
Stopping......: [INIT]: RoundCube Web already stopped...
/etc/init.d/roundcube restart
restart Please wait....

"14-Aug-2013 22:19:53 PHP Error Failed to load plugin file /usr/share/roundcube/plugins/fail2ban/fail2ban.php in /usr/share/roundcube/program/lib/Roundcube/rcube_plugin_api.php on line 223 (POST /?_task=login&_action=login)"
Thank you very much.
Attachments
Immage_5042 Aug. 14 22.38.jpg
Immage_5042 Aug. 14 22.38.jpg (158.53 KiB) Viewed 8189 times
zetar
 
Posts: 345
Joined: Sat Dec 11, 2010 9:31 am
Artica servers number: 1
Linux System: Ubuntu
Technical skills: A newbee

Re: Rouncube Http

New postby zetar » Thu Aug 15, 2013 11:55 am

updated:
To make it work again I had to reinstall the version: 1.7.073120.
More later I was not able to start it
Thanks...
zetar
 
Posts: 345
Joined: Sat Dec 11, 2010 9:31 am
Artica servers number: 1
Linux System: Ubuntu
Technical skills: A newbee

Re: Rouncube Http

New postby admin » Thu Aug 15, 2013 6:37 pm

Corrigé en 1.7.081519 nightlybuild
User avatar
admin
Site Admin
 
Posts: 11942
Joined: Wed Oct 17, 2007 7:59 am
Location: France

Re: Rouncube Http

New postby zetar » Thu Aug 15, 2013 9:55 pm

Thanks David.
zetar
 
Posts: 345
Joined: Sat Dec 11, 2010 9:31 am
Artica servers number: 1
Linux System: Ubuntu
Technical skills: A newbee

Re: Rouncube Http

New postby zetar » Fri Aug 16, 2013 11:17 am

Updated to version as you suggested, the problem has not changed.
Does not start.
Downgraded it all works ...
Thank you ..
zetar
 
Posts: 345
Joined: Sat Dec 11, 2010 9:31 am
Artica servers number: 1
Linux System: Ubuntu
Technical skills: A newbee

Re: Rouncube Http

New postby zetar » Sat Sep 21, 2013 6:58 pm

Hello.
Same problem, updated to the current version after a period that does not update anything.
The usual problem, Roundcube does not start, even the Milter-Greylist not start.
What can I do to be able to update the system.
Thank you.
zetar
 
Posts: 345
Joined: Sat Dec 11, 2010 9:31 am
Artica servers number: 1
Linux System: Ubuntu
Technical skills: A newbee

Re: Rouncube Http

New postby admin » Sun Sep 22, 2013 7:08 am

which version ?
User avatar
admin
Site Admin
 
Posts: 11942
Joined: Wed Oct 17, 2007 7:59 am
Location: France

Re: Rouncube Http

New postby zetar » Sun Sep 22, 2013 11:40 am

They stopped at 1.7.073120.
Any later version does not start Roundcube and Milter.
Thank you.
zetar
 
Posts: 345
Joined: Sat Dec 11, 2010 9:31 am
Artica servers number: 1
Linux System: Ubuntu
Technical skills: A newbee

Re: Rouncube Http

New postby admin » Sun Sep 22, 2013 3:53 pm

what is the result of

Code: Select all
php5 /usr/share/artica-postfix/exec.milter-greylist.php --start --verbose
User avatar
admin
Site Admin
 
Posts: 11942
Joined: Wed Oct 17, 2007 7:59 am
Location: France

Re: Rouncube Http

New postby zetar » Mon Sep 23, 2013 10:44 am

OK
Or removing the ACL to shorten the file.
thanks

Starting......: artica-executor instantiate instantiate class class.ini-frame.inc...
Starting......: artica-executor instantiate instantiate classes done...
parsecmdlines ou= hostname= STOP= START=1
Starting......: [INIT]: Milter Greylist Daemon single instance execute exec.white-black-central.php
[9077] [DAEMON]::::milter_greylist/LoadConfig:: Loading GreyListConf ->GET_INFO('GreyListConf') in class.milter.greylist.inc line

77
[9077] [DAEMON]::::milter_greylist/ParseConfig:: Parsing start in class.milter.greylist.inc line 145
[9077] [DAEMON]::::milter_greylist/regconf:: greylist=1m in class.milter.greylist.inc
[9077] [DAEMON]::::milter_greylist/regconfBool:: return 0 for lazyaw in class.milter.greylist.inc
[9077] [DAEMON]::::milter_greylist/regconf:: autowhite=3d in class.milter.greylist.inc
[9077] [DAEMON]::::milter_greylist/regconf:: timeout=7d in class.milter.greylist.inc
[9077] [DAEMON]::::milter_greylist/regconfBool:: return 0 for syncaddr in class.milter.greylist.inc
->Parsepeer()
->Parse_Acls()
Parsing acls in 9493 bytes data
Starting......: milter-greylist::DEBUG::Parse_Acls::SELECT COUNT(ID) as tcount FROM miltergreylist_acls WHERE instance='master'
[9077] [DAEMON]::::milter_greylist/__Parse_DNSBL:: Parsing DNSBL 0 rows in class.milter.greylist.inc
Starting......: milter-greylist::this->BuildDefault() in ParseConfig
[9077] [DAEMON]::::milter_greylist/ParseConfig:: Parsing end in class.milter.greylist.inc
Starting......: milter-greylist master 0 objects
Starting......: milter-greylist master 55 rules
Starting......: milter-greylist master cleaning 58 rules
Starting......: milter-greylist master building 57 rules
Starting......: milter-greylist sync port is not enabled
Starting......: milter-greylist timeout:7d
Starting......: milter-greylist greylist:1m
Starting......: milter-greylist master adding array_acl2=57 rules
Starting......: [INIT]: Milter Greylist Daemon single instance /etc/mail/greylist.conf
Starting......: [INIT]: Milter Greylist Daemon cleaning /etc/mail/greylist.conf with 243 lines
Starting......: [INIT]: Milter Greylist Daemon writing /etc/mail/greylist.conf (204 lines)
Starting......: [INIT]: Milter Greylist Daemon Testing /etc/mail/greylist.conf
Starting......: [INIT]: Milter Greylist Daemon config file "/etc/mail/greylist.conf" is okay
Starting......: [INIT]: Milter Greylist Daemon notify administrator
Milter-greylist has been reconfigured
By daemon
Settings:
# Greylisting config file with a lot of options explained
#
# $Id: greylist2.conf,v 1.1 2006/08/20 04:49:49 manu Exp $
#
# Uncomment this to enable debug output.
# Note that options appearing before the "verbose" option in this
# file will not be treated verbosely.
# May be overridden by the "-v" command line argument.
#verbose
# If you work with multiple MXs, list them with
# peer entries to enable greylist sync among the MXs.
#peer 192.0.2.17
#peer 192.0.2.18
# You may wish to use a specific local address or port for
# syncing between MXs. Of course one of your interfaces
# must have the address assigned. An '*' for the address
# means any address.
#syncaddr *
#syncaddr * port 7689
#syncaddr 192.0.2.2
#syncaddr 192.0.2.2 port 9785
#syncaddr 2001:db8::1:c3b5:123
#syncaddr 2001:db8::1:c3b5:123 port 1234
# Specific IP-Address for outbound sync-connections
# between MXs. If blank, system selects an ip.
# syncsrcaddr 123.45.678.9
# Greylisting your own MTA is a very bad idea: never
# comment this line, except for testing purposes.
acl whitelist addr 127.0.0.0/8
# If you use IPv6, uncomment this.
#acl whitelist addr ::1/128
# You will want to avoid greylisting your own clients
# as well, by filtering out your IP address blocks.
# Here is an example if you use 192.0.2.0/16.
#acl whitelist addr 192.0.2.0/16
# You can avoid greylisting by filtering on the sender
# envelope address, but this is not a good idea: it
# can be trivially forged.
#acl whitelist from friendly@example.com
# Some of your users do not get any spam because
# their addresses have never been collected by
# spammers. They will want to avoid the extra delivery
# delay caused by grey listing. You can filter on the
# recipient envelope address to achieve that.
#acl whitelist rcpt John.Doe@example.net
# It is possible to use regular expressions in domain, from
# and rcpt lines. The expression must be enclosed by
# slashes (/). Note that no escaping is available to
# provide slashes inside the regular expression.
#acl whitelist rcpt /.*@example\.net/
# This option tells milter-greylist when it should
# add an X-Greylist header. Default is all, which
# causes a header to always be added. Other possible
# values are none, delays and nodelays
report all
# This option attempts to make milter-greylist more
# friendly with sender callback systems. When the
# message is from <>, it will be temporarily
# rejected at the DATA stage instead of the RCPT
# stage of the SMTP transaction. In the case of a
# multi recipient DSN, whitelisted recipient will
# not be honoured.
#delayedreject
# Uncomment if you want auto-whitelist to work for
# the IP rather than for the (IP, sender, receiver)
# tuple.
#lazyaw
# How often should we dump to the dumpfile (0: on each change, -1: never).
#dumpfreq 10m
# This option disables the conversion of the time specified in the
# integer format to humanly readable format in the comment of each
# line in the dumpfile.
# Time needed in order to dump large dumpfiles (several milion
# entries/few 100's of MB) can be significantly improved.
dump_no_time_translation
# This option causes greylist entries that expire to be logged via
# syslog. This allows you to collect the IP addresses and sender
# names and use them for blacklisting, SPAM scoring, etc.
logexpired
# How long will the greylist database retain tuples.
timeout 7d
# Do not use ${greylist} macros from sendmail's access DB.
#noaccessdb
# Use extended regular expressions instead of basic
# regular expressions.
#extendedregex
#
# All of the following options have command-line equivalents.
# See greylist.conf(5) for the exact equivalences.
#
# How long a client has to wait before we accept
# the messages it retries to send. Here, 1 hour.
# May be overridden by the "-w greylist_delay" command line argument.
greylist 1m
# How long does auto-whitelisting last (set it to 0
# to disable auto-whitelisting). Here, 3 days.
# May be overridden by the "-a autowhite_delay" command line argument.
autowhite 3d
# Specify the netmask to be used when checking IPv4 addresses
# in the greylist.
# May be overridden by the "-L cidrmask" command line argument.
#subnetmatch /24
# Specify the netmask to be used when checking IPv6 addresses
# in the greylist.
# May be overridden by the "-M prefixlen" command line argument.
#subnetmatch6 /64
# Normally, clients that succeed SMTP AUTH are not
# greylisted. Uncomment this if you want to
# greylist them regardless of SMTP AUTH.
# May be overridden by the "-A" command line argument.
#noauth
# If milter-greylist was built with SPF support, then
# SPF-compliant senders are not greylisted. Uncomment
# this to greylist them regardless of SPF compliance.
# May be overridden by the "-S" command line argument.
#nospf
# If milter-greylist was built with DRAC support,
# then DRAC DB location can be specified here
#drac db "/usr/local/etc/drac.db"
# Uncomment this to disable DRAC
#nodrac
# Uncomment if you want milter-greylist to remain
# in the foreground (no daemon).
# May be overridden by the "-D" command line argument.
#nodetach
# Uncomment this if you do not want milter-greylist
# to tell its clients how long they are greylisted.
# May be overridden by the "-q" command line argument.
#quiet
# You can specify a file where milter-greylist will
# store its PID.
# May be overridden by the "-P pidfile" command line argument.
pidfile "/var/run/milter-greylist.pid"
# You can specify the socket file used to communicate
# with sendmail.
# May be overridden by the "-p socket" command line argument.
socket "/var/run/milter-greylist/milter-greylist.sock"
# The dumpfile location.
# May be overridden by the "-d dumpfile" command line argument.
#dumpfile "/opt/artica/var/milter-greylist/greylist.db"
# The user the milter should run as.
# May be overridden by the "-u username" command line argument.
#user "greylist"
geoipdb "/usr/share/GeoIP/GeoIP.dat"
#ACLS Rules
acl whitelist addr 127.0.0.1/8 #ID:1 local network

stat "|logger -t milter-greylist -p mail.info" "MGREYSTATS:master,%i,%f,%r,%a,%A
,%S,%C\n"

20072 bytes file /var/log/artica-postfix/events/1c8052c5c931ed7fc80aaff8ee8c0274
text
Starting......: [INIT]: Milter Greylist Daemon done.
root@mail1-fel1:~# clear
root@mail1-fel1:~# php5 /usr/share/artica-postfix/exec.milter-greylist.php --sta
rt --verbose | less

[1]+ Stopped php5 /usr/share/artica-postfix/exec.milter-greylist.php --start --verbose | less
root@mail1-fel1:~# clear
root@mail1-fel1:~# php5 /usr/share/artica-postfix/exec.milter-greylist.php --start --verbose | less
#syncaddr *
#syncaddr * port 7689
#syncaddr 192.0.2.2
#syncaddr 192.0.2.2 port 9785
#syncaddr 2001:db8::1:c3b5:123
#syncaddr 2001:db8::1:c3b5:123 port 1234
# Specific IP-Address for outbound sync-connections
# between MXs. If blank, system selects an ip.
# syncsrcaddr 123.45.678.9
# Greylisting your own MTA is a very bad idea: never
# comment this line, except for testing purposes.
acl whitelist addr 127.0.0.0/8
# If you use IPv6, uncomment this.
#acl whitelist addr ::1/128
# You will want to avoid greylisting your own clients
# as well, by filtering out your IP address blocks.
# Here is an example if you use 192.0.2.0/16.
#acl whitelist addr 192.0.2.0/16
# You can avoid greylisting by filtering on the sender
# envelope address, but this is not a good idea: it
# can be trivially forged.
#acl whitelist from friendly@example.com
# Some of your users do not get any spam because
# their addresses have never been collected by
# spammers. They will want to avoid the extra delivery
# delay caused by grey listing. You can filter on the
# recipient envelope address to achieve that.
#acl whitelist rcpt John.Doe@example.net
# It is possible to use regular expressions in domain, from
# and rcpt lines. The expression must be enclosed by
# slashes (/). Note that no escaping is available to
# provide slashes inside the regular expression.
#acl whitelist rcpt /.*@example\.net/
# This option tells milter-greylist when it should
# add an X-Greylist header. Default is all, which
# causes a header to always be added. Other possible
# values are none, delays and nodelays
report all
# This option attempts to make milter-greylist more
# friendly with sender callback systems. When the
# message is from <>, it will be temporarily
# rejected at the DATA stage instead of the RCPT
# stage of the SMTP transaction. In the case of a
# multi recipient DSN, whitelisted recipient will
# not be honoured.
#delayedreject
# Uncomment if you want auto-whitelist to work for
# the IP rather than for the (IP, sender, receiver)
# tuple.
#lazyaw
# How often should we dump to the dumpfile (0: on each change, -1: never).
#dumpfreq 10m
# This option disables the conversion of the time specified in the
# integer format to humanly readable format in the comment of each
# line in the dumpfile.
# Time needed in order to dump large dumpfiles (several milion
# entries/few 100's of MB) can be significantly improved.
dump_no_time_translation
# This option causes greylist entries that expire to be logged via
# syslog. This allows you to collect the IP addresses and sender
# names and use them for blacklisting, SPAM scoring, etc.
logexpired
# How long will the greylist database retain tuples.
timeout 7d
# Do not use ${greylist} macros from sendmail's access DB.
#noaccessdb
# Use extended regular expressions instead of basic
# regular expressions.
#extendedregex
#
# All of the following options have command-line equivalents.
# See greylist.conf(5) for the exact equivalences.
#
# How long a client has to wait before we accept
# the messages it retries to send. Here, 1 hour.
# May be overridden by the "-w greylist_delay" command line argument.
greylist 1m
# How long does auto-whitelisting last (set it to 0
# to disable auto-whitelisting). Here, 3 days.
# May be overridden by the "-a autowhite_delay" command line argument.
autowhite 3d
# Specify the netmask to be used when checking IPv4 addresses
# in the greylist.
# May be overridden by the "-L cidrmask" command line argument.
#subnetmatch /24
# Specify the netmask to be used when checking IPv6 addresses
# in the greylist.
# May be overridden by the "-M prefixlen" command line argument.
#subnetmatch6 /64
# Normally, clients that succeed SMTP AUTH are not
# greylisted. Uncomment this if you want to
# greylist them regardless of SMTP AUTH.
# May be overridden by the "-A" command line argument.
#noauth
# If milter-greylist was built with SPF support, then
# SPF-compliant senders are not greylisted. Uncomment
# this to greylist them regardless of SPF compliance.
# May be overridden by the "-S" command line argument.
#nospf
# If milter-greylist was built with DRAC support,
# then DRAC DB location can be specified here
#drac db "/usr/local/etc/drac.db"
# Uncomment this to disable DRAC
#nodrac
# Uncomment if you want milter-greylist to remain
# in the foreground (no daemon).
# May be overridden by the "-D" command line argument.
#nodetach
# Uncomment this if you do not want milter-greylist
# to tell its clients how long they are greylisted.
# May be overridden by the "-q" command line argument.
#quiet
# You can specify a file where milter-greylist will
# store its PID.
# May be overridden by the "-P pidfile" command line argument.
pidfile "/var/run/milter-greylist.pid"
# You can specify the socket file used to communicate
# with sendmail.
# May be overridden by the "-p socket" command line argument.
socket "/var/run/milter-greylist/milter-greylist.sock"
# The dumpfile location.
# May be overridden by the "-d dumpfile" command line argument.
#dumpfile "/opt/artica/var/milter-greylist/greylist.db"
# The user the milter should run as.
# May be overridden by the "-u username" command line argument.
#user "greylist"
geoipdb "/usr/share/GeoIP/GeoIP.dat"
#ACLS Rules
acl whitelist addr 127.0.0.1/8 #ID:1 local network

stat "|logger -t milter-greylist -p mail.info" "MGREYSTATS:master,%i,%f,%r,%a,%A
,%S,%C\n"

20072 bytes file /var/log/artica-postfix/events/1c8052c5c931ed7fc80aaff8ee8c0274
text
Starting......: [INIT]: Milter Greylist Daemon done.
root@mail1-fel1:~# clear
root@mail1-fel1:~# php5 /usr/share/artica-postfix/exec.milter-greylist.php --sta
rt --verbose | less

[1]+ Stopped php5 /usr/share/artica-postfix/exec.milter-greylist.php --start --verbose | less
root@mail1-fel1:~# clear
root@mail1-fel1:~# php5 /usr/share/artica-postfix/exec.milter-greylist.php --start --verbose | less
# This option disables the conversion of the time specified in the
# integer format to humanly readable format in the comment of each
# line in the dumpfile.
# Time needed in order to dump large dumpfiles (several milion
# entries/few 100's of MB) can be significantly improved.
dump_no_time_translation
# This option causes greylist entries that expire to be logged via
# syslog. This allows you to collect the IP addresses and sender
# names and use them for blacklisting, SPAM scoring, etc.
logexpired
# How long will the greylist database retain tuples.
timeout 7d
# Do not use ${greylist} macros from sendmail's access DB.
#noaccessdb
# Use extended regular expressions instead of basic
# regular expressions.
#extendedregex
#
# All of the following options have command-line equivalents.
# See greylist.conf(5) for the exact equivalences.
#
# How long a client has to wait before we accept
# the messages it retries to send. Here, 1 hour.
# May be overridden by the "-w greylist_delay" command line argument.
greylist 1m
# How long does auto-whitelisting last (set it to 0
# to disable auto-whitelisting). Here, 3 days.
# May be overridden by the "-a autowhite_delay" command line argument.
autowhite 3d
# Specify the netmask to be used when checking IPv4 addresses
# in the greylist.
# May be overridden by the "-L cidrmask" command line argument.
#subnetmatch /24
# Specify the netmask to be used when checking IPv6 addresses
# in the greylist.
# May be overridden by the "-M prefixlen" command line argument.
#subnetmatch6 /64
# Normally, clients that succeed SMTP AUTH are not
# greylisted. Uncomment this if you want to
# greylist them regardless of SMTP AUTH.
# May be overridden by the "-A" command line argument.
#noauth
# If milter-greylist was built with SPF support, then
# SPF-compliant senders are not greylisted. Uncomment
# this to greylist them regardless of SPF compliance.
# May be overridden by the "-S" command line argument.
#nospf
# If milter-greylist was built with DRAC support,
# then DRAC DB location can be specified here
#drac db "/usr/local/etc/drac.db"
# Uncomment this to disable DRAC
#nodrac
# Uncomment if you want milter-greylist to remain
# in the foreground (no daemon).
# May be overridden by the "-D" command line argument.
#nodetach
# Uncomment this if you do not want milter-greylist
# to tell its clients how long they are greylisted.
# May be overridden by the "-q" command line argument.
#quiet
# You can specify a file where milter-greylist will
# store its PID.
# May be overridden by the "-P pidfile" command line argument.
pidfile "/var/run/milter-greylist.pid"
# You can specify the socket file used to communicate
# with sendmail.
# May be overridden by the "-p socket" command line argument.
socket "/var/run/milter-greylist/milter-greylist.sock"
# The dumpfile location.
# May be overridden by the "-d dumpfile" command line argument.
#dumpfile "/opt/artica/var/milter-greylist/greylist.db"
# The user the milter should run as.
# May be overridden by the "-u username" command line argument.
#user "greylist"
geoipdb "/usr/share/GeoIP/GeoIP.dat"
#ACLS Rules
acl whitelist addr 127.0.0.1/8 #ID:1 local network

acl whitelist addr 37.130.152.0/24 #mynetworks array2
stat "|logger -t milter-greylist -p mail.info" "MGREYSTATS:master,%i,%f,%r,%a,%A
,%S,%C\n"

20072 bytes file /var/log/artica-postfix/events/1c8052c5c931ed7fc80aaff8ee8c0274
text
Starting......: [INIT]: Milter Greylist Daemon done.
root@mail1-fel1:~# clear
root@mail1-fel1:~# php5 /usr/share/artica-postfix/exec.milter-greylist.php --sta
rt --verbose | less

[1]+ Stopped php5 /usr/share/artica-postfix/exec.milter-greylist.php --start --verbose | less
root@mail1-fel1:~# clear
root@mail1-fel1:~# php5 /usr/share/artica-postfix/exec.milter-greylist.php --start --verbose | less
# Uncomment if you want milter-greylist to remain
# in the foreground (no daemon).
# May be overridden by the "-D" command line argument.
#nodetach
# Uncomment this if you do not want milter-greylist
# to tell its clients how long they are greylisted.
# May be overridden by the "-q" command line argument.
#quiet
# You can specify a file where milter-greylist will
# store its PID.
# May be overridden by the "-P pidfile" command line argument.
pidfile "/var/run/milter-greylist.pid"
# You can specify the socket file used to communicate
# with sendmail.
# May be overridden by the "-p socket" command line argument.
socket "/var/run/milter-greylist/milter-greylist.sock"
# The dumpfile location.
# May be overridden by the "-d dumpfile" command line argument.
#dumpfile "/opt/artica/var/milter-greylist/greylist.db"
# The user the milter should run as.
# May be overridden by the "-u username" command line argument.
#user "greylist"
geoipdb "/usr/share/GeoIP/GeoIP.dat"
#ACLS Rules
acl whitelist addr 127.0.0.1/8 #ID:1 local network
acl whitelist addr 66.218.66.0/23 #ID:28 Yahoo Groups servers (common pool)
stat "|logger -t milter-greylist -p mail.info" "MGREYSTATS:master,%i,%f,%r,%a,%A,%S,%C\n"
20072 bytes file /var/log/artica-postfix/events/f667b5d2cec09f3f6b64ca2b53d5acfe text
Starting......: [INIT]: Milter Greylist Daemon done.

Screenshot add.
Roundcube was set on port 80 is now on the 449 and you can not change.
Attachments
Immage_5074 Sep. 23 13.03.jpg
Immage_5074 Sep. 23 13.03.jpg (46.11 KiB) Viewed 8113 times
Immage_5073 Sep. 23 13.01.jpg
Immage_5073 Sep. 23 13.01.jpg (148.17 KiB) Viewed 8113 times
Immage_5072 Sep. 23 12.56.jpg
Immage_5072 Sep. 23 12.56.jpg (150.34 KiB) Viewed 8113 times
zetar
 
Posts: 345
Joined: Sat Dec 11, 2010 9:31 am
Artica servers number: 1
Linux System: Ubuntu
Technical skills: A newbee

Next

Return to RoundCube

Who is online

Users browsing this forum: No registered users and 1 guest

cron