Recent Posts

Pages: [1] 2 3 ... 10
1
News & Announcements / Re: Roundcube 1.4 beta released
« Last post by ElasticUser on Today at 03:21:21 PM »
The login page for Elastic looks bad on my phone and computer browsers, and Elastic hardly runs on any of my phone browsers.  it appears like it could be awhile before Elastic is stable.   8)
2
API Based Plugins / Re: Calendar Plugin 3.2.19 Uncaught Error
« Last post by hermawan-fsi on Today at 11:10:33 AM »
i have got the same too, install with iredmail and ubuntu 16, rouncube 1.3.8 show this error

this erros  page isn’t working  is currently unable to handle this request. HTTP ERROR 500

from maillog this

mail roundcube: PHP Fatal error:  Uncaught Error: Class 'kolab_attachments_handler' not found in /opt/www/roundcubemail-1.3.8/plugins/calendar/lib/calendar_ui.php:103#012Stack trace:#012#0 /opt/www/roundcubemail-1.3.8/plugins/calendar/calendar.php(313): calendar_ui->init_templates()#012#1 /opt/www/roundcubemail-1.3.8/program/lib/Roundcube/rcube_plugin_api.php(493): calendar->calendar_view()#012#2 /opt/www/roundcubemail-1.3.8/index.php(295): rcube_plugin_api->exec_action('calendar.index')#012#3 {main}#012  thrown in /opt/www/roundcubemail-1.3.8/plugins/calendar/lib/calendar_ui.php on line 103

3
Pending Issues / Re: Search doesn't seem to work on the android app
« Last post by SKaero on November 13, 2018, 09:36:27 AM »
The "roundcube" Android app isn't build or maintained by the official Roundcube project or team. I'd suggest reaching out to the developer of the Android app directly.
4
Pending Issues / Search doesn't seem to work on the android app
« Last post by josephmaher on November 12, 2018, 10:29:48 PM »
Search works fine for me in a browser, but when I use it in th roundcube android app it doesnt' work.  I've appended the output from Send Application Log below if that is of any help.

Any advice much appreciated!

Joseph

APP_VERSION_CODE=20180920
APP_VERSION_NAME=2018.09.20
ANDROID_VERSION=7.1.2
PHONE_MODEL=GT-I9505
CUSTOM_DATA=Settings.url = https://maher.org.uk/roundcube/

STACK_TRACE=java.lang.Exception: Report requested by developer
        at org.acra.ErrorReporter.a(SourceFile:552)
        at org.acra.ErrorReporter.handleSilentException(SourceFile:350)
        at smalltownboys.rc.roundcubeActivity.onOptionsItemSelected(SourceFile:964)
        at android.app.Activity.onMenuItemSelected(Activity.java:3208)
        at com.android.internal.policy.PhoneWindow.onMenuItemSelected(PhoneWindow.java:1215)
        at com.android.internal.view.menu.MenuBuilder.dispatchMenuItemSelected(MenuBuilder.java:761)
        at com.android.internal.view.menu.MenuItemImpl.invoke(MenuItemImpl.java:152)
        at com.android.internal.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:904)
        at com.android.internal.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:894)
        at com.android.internal.view.menu.MenuPopup.onItemClick(MenuPopup.java:128)
        at android.widget.AdapterView.performItemClick(AdapterView.java:310)
        at android.widget.AbsListView.performItemClick(AbsListView.java:1164)
        at android.widget.AbsListView$PerformClick.run(AbsListView.java:3139)
        at android.widget.AbsListView$3.run(AbsListView.java:4054)
        at android.os.Handler.handleCallback(Handler.java:751)
        at android.os.Handler.dispatchMessage(Handler.java:95)
        at android.os.Looper.loop(Looper.java:154)
        at android.app.ActivityThread.main(ActivityThread.java:6186)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)

LOGCAT=--------- beginning of system
--------- beginning of main
11-12 22:02:01.000 D/roundcube(15756): ---------- START-UP ----------
11-12 22:02:02.204 D/roundcube(15756): web1.onReceivedSslError
11-12 22:02:02.395 D/roundcube(15756): Facebook Ad Error: No fill. We are not able to serve ads to this person. Please refer to https://developers.facebook.com/docs/audience-network/faq#a12. If you are integrating Audience Network for the first time, you can use test ads https://developers.facebook.com/docs/audience-network/testing.
11-12 22:02:02.579 D/roundcube(15756): web1.onReceivedTitle.Roundcube Webmail :: Welcome to Roundcube Webmail
11-12 22:02:09.597 D/roundcube(15756): web1.onPageFinished.LOGIN_FORM.https://maher.org.uk/roundcube/
11-12 22:02:09.600 D/roundcube(15756): web1.Cookie.roundcube_sessid=1f72qkjcluiiaeu5u9hcf6f6l6
11-12 22:02:09.753 D/roundcube(15756): MyJavaScriptInterface.setLoginType.0
11-12 22:02:09.755 D/roundcube(15756): MyJavaScriptInterface.sendBroadcast.android.intent.action.MAIN.login_submit
11-12 22:02:09.759 D/roundcube(15756): onReceive.login_submit
11-12 22:02:09.760 D/roundcube(15756): MyJavaScriptInterface.showToast.--- Logging in ---
11-12 22:02:10.406 D/roundcube(15756): web1.onReceivedTitle.Roundcube Webmail :: Inbox
11-12 22:02:13.855 D/roundcube(15756): web1.onPageFinished.LOGIN_SUBMIT.https://maher.org.uk/roundcube/?_task=mail&_mbox=INBOX
11-12 22:02:13.856 D/roundcube(15756): web1.Cookie.roundcube_sessid=kagq9664ags6kvj8barcnpsrn7; roundcube_sessauth=d8kT2TZhv1oE68vVd4IPirN5iV-1542078000; mailviewsplitter=276; mailviewsplitterv=206
11-12 22:02:14.178 D/roundcube(15756): MyJavaScriptInterface.sendBroadcast.android.intent.action.MAIN.update_mailboxes
11-12 22:02:14.181 D/roundcube(15756): MyJavaScriptInterface.setLoginForm.0
11-12 22:02:14.188 D/roundcube(15756): onReceive.update_mailboxes
11-12 22:02:17.700 D/roundcube(15756): MyJavaScriptInterface.log.getMessages setHtml(messagelistcontainer,6)
11-12 22:02:17.735 D/roundcube(15756): MyJavaScriptInterface.log.getMessageList mes_cnt=6,td.length=48,row_count=8
11-12 22:02:17.772 D/roundcube(15756): MyJavaScriptInterface.sendBroadcast.android.intent.action.MAIN.refresh
11-12 22:02:17.775 D/roundcube(15756): onReceive.refresh
11-12 22:02:18.696 D/roundcube(15756): web2.onPageFinished
11-12 22:02:24.759 D/roundcube(15756): onReceive.search
11-12 22:02:24.798 D/roundcube(15756): web1.onConsoleMessage.Uncaught ReferenceError: rcmail_ui is not defined
5
Pending Issues / Re: Add support for IMAPS on Dovecot
« Last post by SKaero on November 12, 2018, 04:39:53 PM »
The "auto_create_user" setting only creates the user record in the Roundcube database which is used to store user preferences and and contacts. If you don't see any email that likely means your mail server isn't returning any email. Enable imap_debug to see what your mail server is telling Roundcube.
6
Pending Issues / Re: Add support for IMAPS on Dovecot
« Last post by chris01 on November 12, 2018, 03:40:52 PM »
Well. I can finally login against a setting of:
Code: [Select]
$config['default_host'] = 'ssl://<FQDN>';
$config['default_port'] = 993;
$config['username_domain'] = null;
$config['auto_create_user'] = true;
But, while all my folders show up. NONE of them have anything in them.
My guess is that RC is confused about logging into a FQDN, but everything is coming from localhost.
Which also probably accounts for the fact that I had to switch auto_create_user to TRUE.

I'm not sure RC is going to work for us. Well, I suppose it could. But it's clearly going to need many
configuration changes.  :-\

Thank you again, JohnDoh, for taking the time to give me the necessary "clues". :)

--Chris
7
Pending Issues / Re: Add support for IMAPS on Dovecot
« Last post by chris01 on November 12, 2018, 02:08:33 PM »
Flipping brilliant, JohnDoh!
Thanks for the reply. These were just the clues I think I needed to make this work!

BUT, using:

RC (relevant) settings:
Code: [Select]
$config['default_host'] = 'ssl://myvalid.domain';
$config['default_port'] = 993;
$config['username_domain'] = null;
// automatically create a new Roundcube user when log-in the first time.
// a new user will be created once the IMAP login succeeds.
// set to false if only registered users can use this service
$config['auto_create_user'] = false;

DC log:
Code: [Select]
Nov 12 10:28:15 imap-login: Debug: SSL alert: close notify [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x10, ret=1: before/accept initialization [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: before/accept initialization [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv2/v3 read client hello A [000.111.222.333]
Nov 12 10:29:34 auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth
Nov 12 10:29:34 auth: Debug: Module loaded: /usr/local/lib/dovecot/auth/lib20_auth_var_expand_crypt.so
Nov 12 10:29:34 auth: Debug: Read auth token secret from /var/run/dovecot/auth-token-secret.dat
Nov 12 10:29:34 auth: Debug: auth client connected (pid=63360)
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client hello A [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server hello A [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write certificate A [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write key exchange A [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server done A [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client certificate A [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client key exchange A [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client key exchange A [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client key exchange A [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read certificate verify A [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read finished A [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write session ticket A [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write change cipher spec A [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write finished A [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [000.111.222.333]
Nov 12 10:29:34 auth: Debug: client in: AUTH 1 PLAIN service=imap secured no-penalty session=NhT/4Xt6QvgYcSlR lip=000.111.222.333 rip=000.111.222.333 lport=993 rport=63554 local_name=myvalid.domain resp=AGNocmlzLmgAMDkwNDU3YXNY (previous base64 data may contain sensitive data)
Nov 12 10:29:34 auth-worker(63363): Debug: Loading modules from directory: /usr/local/lib/dovecot/auth
Nov 12 10:29:34 auth-worker(63363): Debug: Module loaded: /usr/local/lib/dovecot/auth/lib20_auth_var_expand_crypt.so
Nov 12 10:29:34 auth-worker(63363): Debug: pam(MYUSERNAME,000.111.222.333,<NhT/4Xt6QvgYcSlR>): lookup service=dovecot
Nov 12 10:29:34 auth-worker(63363): Debug: pam(MYUSERNAME,000.111.222.333,<NhT/4Xt6QvgYcSlR>): #1/1 style=1 msg=Password for MYUSERNAME@host.myvalid.domain:
Nov 12 10:29:34 auth: Debug: client passdb out: OK 1 user=MYUSERNAME
Nov 12 10:29:34 auth: Debug: master in: REQUEST 3761897473 63360 1 b3d176ad969d7c342e65320d9730ca24 session_pid=63364 request_auth_token
Nov 12 10:29:34 auth-worker(63363): Debug: passwd(MYUSERNAME,000.111.222.333,<NhT/4Xt6QvgYcSlR>): lookup
Nov 12 10:29:34 auth: Debug: master userdb out: USER 3761897473 MYUSERNAME system_groups_user=MYUSERNAME uid=1001 gid=0 home=/home/MYUSERNAME auth_token=27bdba3943c0939976aba5045ebb1d3a32c294cf
Nov 12 10:29:34 imap-login: Info: Login: user=<MYUSERNAME>, method=PLAIN, rip=000.111.222.333, lip=000.111.222.333, mpid=63364, TLS, session=<NhT/4Xt6QvgYcSlR>
Nov 12 10:29:34 imap(MYUSERNAME): Info: Logged out in=29 out=522
Nov 12 10:29:34 imap-login: Debug: SSL alert: close notify [000.111.222.333]
Nov 12 10:29:34 imap-login: Debug: SSL alert: close notify [000.111.222.333]

RC imap log:
Code: [Select]
[12-Nov-2018 10:29:34 -0800]: <h5mljn9a> [6A5C] S: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] IMAPS ready.
[12-Nov-2018 10:29:34 -0800]: <h5mljn9a> [6A5C] C: A0001 ID ("name" "Roundcube" "version" "1.3.8" "php" "7.2.3" "os" "FreeBSD" "command" "/?_task=login")
[12-Nov-2018 10:29:34 -0800]: <h5mljn9a> [6A5C] S: * ID ("name" "Dovecot")
[12-Nov-2018 10:29:34 -0800]: <h5mljn9a> [6A5C] S: A0001 OK ID completed.
[12-Nov-2018 10:29:34 -0800]: <h5mljn9a> [6A5C] C: A0002 AUTHENTICATE PLAIN ****** [25]
[12-Nov-2018 10:29:34 -0800]: <h5mljn9a> [6A5C] S: A0002 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY SPECIAL-USE] Logged in
[12-Nov-2018 10:29:34 -0800]: <h5mljn9a> [6A5C] C: A0003 NAMESPACE
[12-Nov-2018 10:29:34 -0800]: <h5mljn9a> [6A5C] S: * NAMESPACE (("" "/")) NIL NIL
[12-Nov-2018 10:29:34 -0800]: <h5mljn9a> [6A5C] S: A0003 OK Namespace completed (0.001 + 0.000 secs).
[12-Nov-2018 10:29:34 -0800]: <h5mljn9a> [6A5C] C: A0004 LOGOUT
[12-Nov-2018 10:29:34 -0800]: <h5mljn9a> [6A5C] S: * BYE Logging out
[12-Nov-2018 10:29:34 -0800]: <h5mljn9a> [6A5C] S: A0004 OK Logout completed (0.001 + 0.000 secs).

RC error log:
Code: [Select]
[12-Nov-2018 10:29:34 -0800]: <h5mljn9a> PHP Error: Access denied for new user MYUSERNAME. 'auto_create_user' is disabled in /usr/local/www/rc138/program/include/rcmail.php on line 662 (POST /?_task=login&_action=login)
Based on $config['auto_create_user'] = false; (above). I would have guessed this to mean
NOT to tell the SYSTEM to create a user. But to only permit LOGIN if the USER already existed in
the SYSTEM. Am I wrong?

OH, and yes using a CERT against localhost / an IMAP(s) server authenticating against
a local system, is overkill. But it has proven to (better) thwart / confound the
repeated attempts to undermine, or otherwise abuse the IMAPS/MX, and it hasn't resulted in
any troubles using other webmail applications. ;)

Thanks again!

--Chris
8
Pending Issues / Re: Add support for IMAPS on Dovecot
« Last post by JohnDoh on November 12, 2018, 02:45:32 AM »
PHP has had certificate validation enabled by default since version 5.6. You can use the `imap_conn_options` in Roundcube to disable this. Something like:
Code: [Select]
$config['imap_conn_options'] = array(
  'ssl' => array(
    'verify_peer' => false,
  ),
);
You could also use this option to tell PHP how to correctly validate the cert. Using encrypted connections when connecting to localhost is overkill though so you should also consider allowing plain IMAP connections this way.

As for the username, IIRC Roundcube only adds a domain automatically if the config option `username_domain`is set.
9
Pending Issues / Re: Add support for IMAPS on Dovecot
« Last post by chris01 on November 11, 2018, 11:52:33 PM »
Looks like I'll need to get a valid cert for localhost
Does anyone know of a Certificate Authority that will grant a CSR for localhost?

Thanks! :)

--Chris
10
Pending Issues / Re: Add support for IMAPS on Dovecot
« Last post by chris01 on November 11, 2018, 10:47:14 PM »
OK, appears I've already had to deal with this before. The suggested solution was to use:
Code: [Select]
$config['default_host'] = 'ssl://<FQDN>:993';
But this doesn't seem to work. As it (RC) sends <USERNAME>@<FQDN>
which fails. Because our system (and Dovecot) expect <USERNAME> only.
Yet RC insists on having a valid cert.
Any possibilities for RC under these circumstances?

Thanks!

--Chris
Pages: [1] 2 3 ... 10