Re: [RCU] feature request

[Webert de Souza Lima]

I was looking at Roundcube listing settings and I saw the Sorting Columns
option "Received Date". I think this is equivalent to what I'm requesting.


Regards,

Webert Lima
DevOps Engineer at MAV Tecnologia
*Belo Horizonte - Brasil*
*IRC NICK - WebertRLZ*

On Tue, Apr 3, 2018 at 10:28 AM, Webert de Souza Lima  wrote:

> Hah, I didn't know you had a script for that. I actually wrote one on my
> own.
>
> Thanks for replying, but what I'm actually proposing is to have this
> option in the UI for the user himself to click, like he does with the other
> columns.
>
>
> Regards,
>
> Webert Lima
> DevOps Engineer at MAV Tecnologia
> *Belo Horizonte - Brasil*
> *IRC NICK - WebertRLZ*
>
> On Tue, Apr 3, 2018 at 2:58 AM, A.L.E.C  wrote:
>
>> On 02.04.2018 20:48, Webert de Souza Lima wrote:
>> > Because of the problem I have described recently in the email entitled:
>> >
>> > "Unable to send command: A0007 FETCH 1:* (UID BODY.PEEK[HEADER.FIELDS
>> > (FROM)])"
>> >
>> > I would like to request a feature: clear ordering preference.
>> > That would make the sort as the default again.
>> >
>> > How is that likely to be done? I'm not sure I can request any features.
>>
>> bin/moduserprefs.sh --delete message_sort_col
>>
>> --
>> Aleksander 'A.L.E.C' Machniak
>> Kolab Groupware Developer [http://kolab.org]
>> Roundcube Webmail Developer   [http://roundcube.net]
>> 
>> PGP: 19359DC1 # Blog: https://kolabian.wordpress.com
>> ___
>> Roundcube Users mailing list
>> users@lists.roundcube.net
>> http://lists.roundcube.net/mailman/listinfo/users
>>
>
>
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

Re: [RCU] feature request

[Webert de Souza Lima]

Hah, I didn't know you had a script for that. I actually wrote one on my
own.

Thanks for replying, but what I'm actually proposing is to have this option
in the UI for the user himself to click, like he does with the other
columns.


Regards,

Webert Lima
DevOps Engineer at MAV Tecnologia
*Belo Horizonte - Brasil*
*IRC NICK - WebertRLZ*

On Tue, Apr 3, 2018 at 2:58 AM, A.L.E.C  wrote:

> On 02.04.2018 20:48, Webert de Souza Lima wrote:
> > Because of the problem I have described recently in the email entitled:
> >
> > "Unable to send command: A0007 FETCH 1:* (UID BODY.PEEK[HEADER.FIELDS
> > (FROM)])"
> >
> > I would like to request a feature: clear ordering preference.
> > That would make the sort as the default again.
> >
> > How is that likely to be done? I'm not sure I can request any features.
>
> bin/moduserprefs.sh --delete message_sort_col
>
> --
> Aleksander 'A.L.E.C' Machniak
> Kolab Groupware Developer [http://kolab.org]
> Roundcube Webmail Developer   [http://roundcube.net]
> 
> PGP: 19359DC1 # Blog: https://kolabian.wordpress.com
> ___
> Roundcube Users mailing list
> users@lists.roundcube.net
> http://lists.roundcube.net/mailman/listinfo/users
>
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

Re: [RCU] feature request

[A.L.E.C]

On 02.04.2018 20:48, Webert de Souza Lima wrote:
> Because of the problem I have described recently in the email entitled:
> 
> "Unable to send command: A0007 FETCH 1:* (UID BODY.PEEK[HEADER.FIELDS
> (FROM)])"
> 
> I would like to request a feature: clear ordering preference.
> That would make the sort as the default again.
> 
> How is that likely to be done? I'm not sure I can request any features.

bin/moduserprefs.sh --delete message_sort_col

-- 
Aleksander 'A.L.E.C' Machniak
Kolab Groupware Developer [http://kolab.org]
Roundcube Webmail Developer   [http://roundcube.net]

PGP: 19359DC1 # Blog: https://kolabian.wordpress.com
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

[RCU] feature request

[Webert de Souza Lima]

Because of the problem I have described recently in the email entitled:

"Unable to send command: A0007 FETCH 1:* (UID BODY.PEEK[HEADER.FIELDS
(FROM)])"

I would like to request a feature: clear ordering preference.
That would make the sort as the default again.

How is that likely to be done? I'm not sure I can request any features.

Regards,

Webert Lima
DevOps Engineer at MAV Tecnologia
*Belo Horizonte - Brasil*
*IRC NICK - WebertRLZ*
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

Re: [RCU] feature request: set identity per recipient

[Ralph Seichter]

On 16.10.16 10:33, Jari Fredriksson wrote:

> I have multiple identities, and for example mailing lists like this
> I use this iki.fi identity, because my primary identity has strick
> dkim/dmarc -policies which will cause fail when received from a
> mailing list of an email forwarding service (like iki.fi).

DMARC policies are enforced by MTAs, but Roundcube is a MUA, so I'm not
sure I understand what exactly you are asking for? Are you thinking of
identity support in Thunderbird fashion, which allows for different SMTP
server / sender address combinations?

-Ralph
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

[RCU] feature request: set identity per recipient

[Jari Fredriksson]

I don't know if this already is somehow possible, but would be very cool
this. 

I have multiple identities, and for example mailing lists like this I
use this iki.fi identity,  because my primary identity has strick
dkim/dmarc -policies which will cause fail when received from a mailing
list of an email forwarding service (like iki.fi). 

--
ja...@iki.fi

signature.asc
Description: OpenPGP digital signature
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

Re: [RCU] Feature Request: Independent owncloud plugin

[A.L.E.C]

On 09/16/2012 07:07 PM, Tobias Hachmer wrote:

 Is here anybody who knows how to get the auto-authentication working?
 (with same user credentials used for roundcube(imap) login)

As I know authentication against IMAP was planned for ownCloud 4.5. So,
if they implemented it, an integration with Roundcube should be quite
simple now.

-- 
Aleksander 'A.L.E.C' Machniak
LAN Management System Developer [http://lms.org.pl]
Roundcube Webmail Developer  [http://roundcube.net]
---
PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

Re: [RCU] Feature Request: Independent owncloud plugin

[Tobias Hachmer]

Am 17.09.2012 11:41, schrieb A.L.E.C:

On 09/16/2012 07:07 PM, Tobias Hachmer wrote:
Is here anybody who knows how to get the auto-authentication 
working?

(with same user credentials used for roundcube(imap) login)


As I know authentication against IMAP was planned for ownCloud 4.5. 
So,

if they implemented it, an integration with Roundcube should be quite
simple now.


Thanks A.L.E.C for your response! The Feature list on github doesn't 
list this feature. 
(https://github.com/owncloud/core/wiki/ownCloud-4.5-Features)


I'm interested in how the owncloud authentication works when using this 
plugin with kolab. What kind of authentication is used in combination 
with kolab and why the authentication doesn#T work with my 
modifications?


For now in my test setup I have setup rouncube and owncloud. Roundcube 
is using imap authentication (dovecot uses ldap authentication). 
Owncloud is using integrated ldap authentication. The usernames and 
passwords are the same for roundcube and owncloud login.


Regards,
Tobias Hachmer
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

Re: [RCU] Feature Request: Independent owncloud plugin

[A.L.E.C]

On 09/17/2012 12:10 PM, Tobias Hachmer wrote:

 What kind of modification does the owncloud plugin need if the new
 owncloud release will support imap authentication?

I don't know. The plugin was written for some pre-4.0 version of
ownCloud, so a lot of things might have changed. I didn't check yet how
the new auth possibilities in ownCloud look like.

-- 
Aleksander 'A.L.E.C' Machniak
LAN Management System Developer [http://lms.org.pl]
Roundcube Webmail Developer  [http://roundcube.net]
---
PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

Re: [RCU] Feature Request: Independent owncloud plugin

[Tobias Hachmer]

Am 10.09.2012 15:24, schrieb Tobias Hachmer:

Honestly, is someone able to patch this plugin to use native imap
authentication or ldap_auth.
I have seen this plugin uses the plugin kolab_auth. Can I use this
plugin and configure it to authenticate against a non kolab openldap
server? This would be a great workaround!


For now did the following modifications to owncloud.php:

--- a/owncloud.php  2012-09-16 18:59:22.962792771 +0200
+++ b/owncloud.php  2012-09-16 19:01:52.284938898 +0200
@@ -21,15 +21,10 @@

 function init()
 {
 $rcmail = rcmail::get_instance();

-// requires kolab_auth plugin
-if (empty($_SESSION['kolab_uid'])) {
-return;
-}
-
 $this-add_texts('localization/', false);

 // register task
 $this-register_task('owncloud');

@@ -64,11 +59,11 @@
 $rcmail = rcmail::get_instance();

 $this-load_config();

 $src  = $rcmail-config-get('owncloud_url');
-$user = $_SESSION['kolab_uid']; // requires kolab_auth plugin
+$user = $_SESSION['username'];
 $pass = $rcmail-decrypt($_SESSION['password']);

 $src = preg_replace('/^(https?:\/\/)/',
 '\\1' . urlencode($user) . ':' . urlencode($pass) . '@', 
$src);


I see now by clicking on Files the owncloud login page. The 
auto-authentication did not work for now.
Is here anybody who knows how to get the auto-authentication working? 
(with same user credentials used for roundcube(imap) login)


Thanks in advance,
Tobias Hachmer
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

[RCU] feature request

[Jim Pazarena]

I just learned about a cool feature which last pass uses...
restrict login to a specific country or countries

It would certainly be a benefit to me to be able to
restrict logins (in my case) to canada  us from the
individual setup screen per client.

I have seen multiple instances of spam injection into
roundcube via a hacked client. Always by a foreign
country 'hacker'.

Limiting to certain countries by IP would not eliminate
those hackers which are proxied somehow into CA/US, but
it would sure help.
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

Re: [RCU] feature request

[Paul Hartman]

On Tue, Sep 11, 2012 at 3:00 PM, Jim Pazarena roundc...@paz.bz wrote:
 I just learned about a cool feature which last pass uses...
 restrict login to a specific country or countries

 It would certainly be a benefit to me to be able to
 restrict logins (in my case) to canada  us from the
 individual setup screen per client.

 I have seen multiple instances of spam injection into
 roundcube via a hacked client. Always by a foreign
 country 'hacker'.

 Limiting to certain countries by IP would not eliminate
 those hackers which are proxied somehow into CA/US, but
 it would sure help.

Unless you want per-user allowable countries at the RC level, this can
otherwise be implemented pretty easily in your http server using
existing geoip modules.
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

Re: [RCU] feature request

[Tache Madalin]

I personally recommend a firewall using geoip functions. They work like a 
charm. 

Sent from my iPhone

On 11.09.2012, at 23:07, Paul Hartman paul.hart...@gmail.com wrote:

 On Tue, Sep 11, 2012 at 3:00 PM, Jim Pazarena roundc...@paz.bz wrote:
 I just learned about a cool feature which last pass uses...
 restrict login to a specific country or countries
 
 It would certainly be a benefit to me to be able to
 restrict logins (in my case) to canada  us from the
 individual setup screen per client.
 
 I have seen multiple instances of spam injection into
 roundcube via a hacked client. Always by a foreign
 country 'hacker'.
 
 Limiting to certain countries by IP would not eliminate
 those hackers which are proxied somehow into CA/US, but
 it would sure help.
 
 Unless you want per-user allowable countries at the RC level, this can
 otherwise be implemented pretty easily in your http server using
 existing geoip modules.
 ___
 Roundcube Users mailing list
 users@lists.roundcube.net
 http://lists.roundcube.net/mailman/listinfo/users
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

Re: [RCU] feature request

[Kaz Kylheku]

On Tue, 11 Sep 2012 13:00:41 -0700, Jim Pazarena roundc...@paz.bz
wrote:
 I just learned about a cool feature which last pass uses...
 restrict login to a specific country or countries
 
 It would certainly be a benefit to me to be able to
 restrict logins (in my case) to canada  us from the
 individual setup screen per client.
 
 I have seen multiple instances of spam injection into
 roundcube via a hacked client. Always by a foreign
 country 'hacker'.

RoundCube is the wrong place to implement host controls.
If you want to do this at the HTTP level, you can
do it in Apache. Certain originating IP's can be blocked
from accessing the application entirely. You can redirect
them to a static page which informs the user that
access is not allowed from that place of origin.

More strongly than that, you can do the filtering in
iptables right in your kernel, so that the connection
requests can reach your machine, but are never seen
by Apache. Or right in your network's router, so that
the offenders are stopped right at your doorstep.

I have a whole ton of iptables rules that ban various
IP blocks. Many of them in China and other places.
The server simply appears as a black hole for all
packets.

Here is an example entry in my iptables save/restore
file which blocks a range of IP addresses:

-A INPUT -m iprange --src-range 125.64.0.0-125.71.255.255 -i eth0 -p
tcp -m tcp
 --dport 25 -j DROP

That particular netblock has been a source of spam
connections to my mail server. I don't block everything, just
TCP port 25. But of course everything could be blocked like this:

-A INPUT -m iprange --src-range 125.64.0.0-125.71.255.255 -i eth0 -j
DROP

___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

Re: [RCU] Feature Request: Independent owncloud plugin

[Tobias Hachmer]

Am 10.09.2012 13:21, schrieb Torsten Grote:

On Friday 07 September 2012 19:31:06 Tobias Hachmer wrote:

Just to make the owncloud plugin useable for people don't running
kolab.


There's still people not running Kolab? ;)


:-))

Honestly, is someone able to patch this plugin to use native imap 
authentication or ldap_auth.
I have seen this plugin uses the plugin kolab_auth. Can I use this 
plugin and configure it to authenticate against a non kolab openldap 
server? This would be a great workaround!


Thanks in advance,
Tobias Hachmer
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

Re: [RCU] Feature Request: Independent owncloud plugin

[Benny Pedersen]

Den 2012-09-10 13:21, Torsten Grote skrev:

On Friday 07 September 2012 19:31:06 Tobias Hachmer wrote:

Just to make the owncloud plugin useable for people don't running
kolab.

There's still people not running Kolab? ;)


or complete mailserver solution on android phones ?


___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

[RCU] Feature request: reply using HTML

[Jacek Osiecki]

Hi,

As I have checked, there still is a problem with forwarding HTML
messages in roundcube. If I have option send HTML only in reply
to HTML messages - message is forwarded correctly when I click
on reply. However, if I want to forward such a message, it
doesn't work - I'm replying in plain text, and all images are
just included as attachments at the bottom of message.
In order to forward it correctly I have to either set send
all messages in HTML or press reply and replace the recipient.

I think that forward should also use HTML if we are forwarding
HTML message and have on reply to HTML message only option selected.
On the other hand, it would be nice to have dropdown option for 
compose,

reply and forward buttons named reply using HTML no matter what has
been set in config.

Greetings,
--
Jacek Osiecki
Silvercube s.c.
ul. Makuszyńskiego 4, 31-752 Kraków
tel/fax: +48 (12) 684 21 00
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

Re: [RCU] Feature request: reply using HTML

[Claudio Kuenzler]

I can confirm that behavior.
However it works when the setting Compose HTML messages is set to always.

Looks like a minor bug to me?

On Fri, Mar 9, 2012 at 1:45 PM, Jacek Osiecki josie...@silvercube.plwrote:

 Hi,

 As I have checked, there still is a problem with forwarding HTML
 messages in roundcube. If I have option send HTML only in reply
 to HTML messages - message is forwarded correctly when I click
 on reply. However, if I want to forward such a message, it
 doesn't work - I'm replying in plain text, and all images are
 just included as attachments at the bottom of message.
 In order to forward it correctly I have to either set send
 all messages in HTML or press reply and replace the recipient.

 I think that forward should also use HTML if we are forwarding
 HTML message and have on reply to HTML message only option selected.
 On the other hand, it would be nice to have dropdown option for compose,
 reply and forward buttons named reply using HTML no matter what has
 been set in config.

 Greetings,
 --
 Jacek Osiecki
 Silvercube s.c.
 ul. Makuszyńskiego 4, 31-752 Kraków
 tel/fax: +48 (12) 684 21 00
 __**_
 Roundcube Users mailing list
 users@lists.roundcube.net
 http://lists.roundcube.net/**mailman/listinfo/usershttp://lists.roundcube.net/mailman/listinfo/users
___
Roundcube Users mailing list
users@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/users

[RCU] Feature request: 'include' local config file

[Charles Marcus]

I use postfixadmin to maintain my userdb, and it offers the ability to
have all of your modified settings from the main config file
(config.inc.php) in a separate local file, which is then 'included' in
the main config file...

I have found that this makes upgrades much easier, so I'd like to
request that this be made a formal feature with RC...

So, something like an autoinclude for a main.local.php file (if it
exists), where any settings in this file override any settings in
main.inc.php...

I'd also like the ability to define *where* this local config file might
reside... ie, by default look in the current directory (where
main.inc.php is), then, if $local_config_dir (or whatever) is set, look
there (ie, /etc/roundcube)...

Thanks for your consideration...

-- 

Best regards,

Charles
-- 
List info: http://lists.roundcube.net/users/
BT/8f4f07cd

[RCU] Feature Request

[Ulli Heist]

 Hallo all and a happy new year

 Did you know CrossPoint (XP)? An old german DOS-Mailprogramm!

 This old program has a function which I'm missing for several years:

 I try to explain:

 Some of my contacts are writing private e-mails to me from their 
 work-mail-address.
 If I do not watch the reply will go to work, but it has to go to the 
 private mail-address.

 In CrossPoint there was the possibility to set an manuell 
 Reply-To-Adress which overides all Header-Reply-Settings (if exist) by 
 sending a Reply.

 This manuell Reply-To-Adress have to set manuelly in the adressbook, by 
 choosing an other existing mail-adress as Reply-To.


 Do you understand, what I try to explain?

 Best Regards from Germany

  Ulli Heist


-- 
 http://heist.hobby-site.org/witze
___
List info: http://lists.roundcube.net/users/
BT/8f4f07cd