#38 Question: Rainloop features

Closed
opened 3 years ago by Ghost · 9 comments
Ghost commented 3 years ago

Can the following be enabled? Is there a performance/security reason not to? Some features might have to be enabled first in ./data/.../configs/application.ini by the admin, and can be seen in action in Rainloop’s Test Webmail.

1 - Threads: By default, they should be in Settings > General > Use threads. They minimize message clutter on multiple follow-up mails and are pretty easy to navigate with the keyboard.

2 - Filters: By default, they should be in Settings > Filters. Is Sieve installed in Teknik’s mail server? I’ve been using filters to send specific messages to specific folders, sort of as a “Read Later” rule, but they could also be useful to send a mail message copy to a secondary mail address.

3 - Accounts and Identites: Since Rainloop simply accesses an IMAP server and does not actually host messages from an external account (no problem in increasing Teknik’s quota, I think), any reason why not to allow a secondary mail account to be consulted in Teknik’s webmail? Also, identities can be created but you can only send mail from but not send mail to an identity. Is this locked on purpose? Couldn’t it work with a proper SPF set up?

4 - Send message on Ctrl+Enter: As a keyboard aficionado, that’s the only keyboard shortcut missing from the current setup. Must be set in application.ini.

Can the following be enabled? Is there a performance/security reason not to? Some features might have to be enabled first in `./data/.../configs/application.ini` by the admin, and can be seen in action in [Rainloop's Test Webmail](https://mail.rainloop.net). 1 - Threads: By default, they should be in **Settings > General > Use threads**. They minimize message clutter on multiple follow-up mails and are pretty easy to navigate with the keyboard. 2 - Filters: By default, they should be in **Settings > Filters**. Is Sieve installed in Teknik's mail server? I've been using filters to send specific messages to specific folders, sort of as a "Read Later" rule, but they could also be useful to send a mail message copy to a secondary mail address. 3 - Accounts and Identites: Since Rainloop simply accesses an IMAP server and does not actually host messages from an external account (no problem in increasing Teknik's quota, I think), any reason why not to allow a secondary mail account to be consulted in Teknik's webmail? Also, identities can be created but you can only **send mail from** but not **send mail to** an identity. Is this locked on purpose? Couldn't it work with a proper SPF set up? 4 - Send message on `Ctrl+Enter`: As a keyboard *aficionado*, that's the only keyboard shortcut missing from the current setup. Must be set in [`application.ini`](https://github.com/RainLoop/rainloop-webmail/issues/1157).
Uncled1023 commented 3 years ago
Owner

Hi, thanks for the suggestions! I will try to touch on each point.

1) I do not see an option for Threads, but I enabled it in the application.ini file

2) Sadly, the mail server i’m using does not support Sieves, so I cannot leverage that feature. We have asked for a plugin to be made that will integrate with hMailServer’s Rules, but nothing so far.

3a) Each domain has to be whitelisted, so instead of allowing multiple addresses, we chose to only allow teknik emails as aliases. Also, we wanted to make it so that you had to use your teknik credentials to login into the web interface.

3b) You can send mail to an identity, just put that identity into the ‘TO’ field like a regular address. The FROM is locked to only identities, which is why you can select them. To can be anyone, which is why it’s a text box.

4) That has now been enabled.

Thanks!

Hi, thanks for the suggestions! I will try to touch on each point. 1) I do not see an option for Threads, but I enabled it in the application.ini file 2) Sadly, the mail server i'm using does not support Sieves, so I cannot leverage that feature. We have asked for a plugin to be made that will integrate with hMailServer's Rules, but nothing so far. 3a) Each domain has to be whitelisted, so instead of allowing multiple addresses, we chose to only allow teknik emails as aliases. Also, we wanted to make it so that you had to use your teknik credentials to login into the web interface. 3b) You can send mail to an identity, just put that identity into the 'TO' field like a regular address. The FROM is locked to only identities, which is why you can select them. To can be anyone, which is why it's a text box. 4) That has now been enabled. Thanks!
Ghost commented 3 years ago
Poster

Thanks for the follow-up, man.

1) Sufferin’ Succotash, I was looking on how to check if an IMAP server has threads support but found that hMailServer (which you told me on response 2) doesn’t support them. :(

2) Yeah, also found a voting request for it. :(

3a) Makes sense.

3b) I know but I tried it more than once and I aways get and “Unknown User” when sending from my local client. In Rainloop I get a “Can’t send message” error. I don’t get an error return message from the server seconds later, it just fails to send on the spot. But I can send from the identity just fine.

4) One down! Thanks. :)

Thanks for the follow-up, man. 1) Sufferin' Succotash, I was looking on how to [check if an IMAP server has threads support](http://www.afterlogic.org/docs/webmail-lite/configuring-webmail/message-threading#how-to-check-if-threading-is-supported-by-server) but found that hMailServer (which you told me on response 2) [doesn't support them](https://www.hmailserver.com/forum/viewtopic.php?t=16893&vote=viewresult). :( 2) Yeah, also found a [voting request](https://www.hmailserver.com/forum/viewtopic.php?t=17944&vote=viewresult) for it. :( 3a) Makes sense. 3b) I know but I tried it more than once and I aways get and "Unknown User" when sending from my local client. In Rainloop I get a "Can't send message" error. I don't get an error return message from the server seconds later, it just fails to send on the spot. But I can send from the identity just fine. 4) One down! Thanks. :)
Uncled1023 commented 3 years ago
Owner

Hm what address are you trying to send to? I tried sending to another identity and it worked fine. Are you sure the identity exists? If it’s returning Unknown User, then the email address isn’t a valid email address.

Hm what address are you trying to send to? I tried sending to another identity and it worked fine. Are you sure the identity exists? If it's returning Unknown User, then the email address isn't a valid email address.
Ghost commented 3 years ago
Poster

OK, never mind. I thought I could create an identity as an account alias, eg. feedback@teknik.io which would be associated to my current Teknik username. Some services allow this and can deliver the message to the right user (even if there was already an username feedback@teknik.io in Teknik’s DB) by the use of SPF records, if I’m not talking nonsense. :)

Now I realize, the identity has to be a valid secondary email address, which is also fine.

Since the first 2 suggestions are dependent on hMailServer, we can close this one. Maybe some day, they improve it.

Thanks.

OK, never mind. I thought I could create an identity as an account alias, eg. `feedback@teknik.io` which would be associated to my current Teknik username. Some services allow this and can deliver the message to the right user (even if there was already an username `feedback@teknik.io` in Teknik's DB) by the use of SPF records, if I'm not talking nonsense. :) Now I realize, the identity has to be a valid secondary email address, which is also fine. Since the first 2 suggestions are dependent on hMailServer, we can close this one. Maybe some day, they improve it. Thanks.
Ghost commented 3 years ago
Poster

Sorry to re-open. About hMailServer’s rules, the plugin could be developed with their COM API alone? What about allowing users to create rules in hMailServer’s own web admin UI, disabling all other admin options?

Possible values:
   
      0 - All users on the server should be allowed access.
      1 - Domain administrators and server administrators should be
          allowed access.
      2 - Only server administrators should be allowed access.

$hmail_config['rule_editing_level'] = 0;
Sorry to re-open. About hMailServer's rules, the plugin could be developed with their [COM API](https://www.hmailserver.com/documentation/v5.4/?page=com_objects) alone? What about [allowing users](https://www.hmailserver.com/forum/viewtopic.php?t=16605) to create rules in hMailServer's own web admin UI, disabling all other admin options? ``` Possible values: 0 - All users on the server should be allowed access. 1 - Domain administrators and server administrators should be allowed access. 2 - Only server administrators should be allowed access. $hmail_config['rule_editing_level'] = 0; ```
dmz commented 1 year ago

@Uncled1023 It seems that hMailServer will never implement Sieve filters or IMAP threads and I know hMailServer is simple, functional and easy to use out-of-the-box, so I’m not suggesting another email server which I know are usually a pain in the ass to setup and maintain.

So, IMAP threads I learned to live without but, for filters, I wonder if any of these solutions would be viable:

  • Registered user access to hMailServer panel where only the Rules tab would be enabled (also check hMailAdmin: an hMailServer PHPWebAdmin redesign project)

  • Possibility of you adding rules on demand, by emailing Teknik’s support email. Not sure if you can add rules for different users. If it can only be done globally (like whitelisting a domain from the spam filters), it wouldn’t be any use.

To help on your decision, in case this is feasible, I only have 1 rule along these lines:

If sender address contains "rss2email" OR sender address contains "newsletter" move message to folder "News"
@Uncled1023 It seems that hMailServer will never implement Sieve filters or IMAP threads and I know hMailServer is simple, functional and easy to use out-of-the-box, so I'm not suggesting another email server which I know are usually a pain in the ass to setup and maintain. So, IMAP threads I learned to live without but, for filters, I wonder if any of these solutions would be viable: - Registered user access to hMailServer panel where only the **Rules** tab would be enabled (also check [hMailAdmin: an hMailServer PHPWebAdmin redesign project](https://github.com/coax/hmailserver-webadmin)) - Possibility of you adding rules on demand, by emailing Teknik's support email. Not sure if you can add rules for different users. If it can only be done globally (like whitelisting a domain from the spam filters), it wouldn't be any use. To help on your decision, in case this is feasible, I only have 1 rule along these lines: ```txt If sender address contains "rss2email" OR sender address contains "newsletter" move message to folder "News" ```
Uncled1023 commented 1 year ago
Owner

Nice link! I may have to check that out.

In terms of adding rules, that could be something that I could create some sort of schema to make the ‘global’ rules act like individual rules, like a clause that is always added by the backend to make it specific to a user’s email.

Nice link! I may have to check that out. In terms of adding rules, that could be something that I could create some sort of schema to make the 'global' rules act like individual rules, like a clause that is always added by the backend to make it specific to a user's email.
dmz commented 1 year ago

Great that it stays open for consideration. Let us know in a blog post, in case this gets implemented.

Great that it stays open for consideration. Let us know in a blog post, in case this gets implemented.
dmz commented 1 year ago

Created a new feature request issue, just in case.

Created a new [feature request issue](https://git.teknik.io/Teknikode/Teknik/issues/88), just in case.
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Cancel
Save
There is no content yet.