Re: [Evolution] Would this have side effects ?

2021-02-23 Thread Ángel
On 2021-02-05 at 17:10 -0600, Anonymous Japhering wrote:
> Mgmt is mandating that I interface with the corporate CRM software,
> which if you are not using a browser  for
> email is a BCC to a specific email address.
> 
> That means you either have to  remember to add the BCC ( and remember
> how you saved it) , or set it in the 
> composer options for every email.   Neither option by itself is very
> appealing as it means you either miss a 
> bunch  of outbound emails or you cram a lot of CRAP into the CRM.


I suspect their system is broken, but the management that came up with
that solution is probably earning many times my salary.

As I understand it, your CRM shall contain a copy of all messages sent
*to* the clients, and so you are being asked to BCC an internal CRM
address (e.g. c...@example.com).

If you use a separate account to with the clients (e.g. 
sa...@example.com), then it's trivial to configure it to BCC a certain
mailbox (option 'Always blind carbon-copy to'). This is the classic
solution, where many people work from a common mailbox.

However, in the system on your company, you are apparently using your
'normal' account both for interacting with clients and for other
interactions that shouldn't go through the CRM (e.g. sharing kitten
videos as attachments with your coworkers)

This has the obvious drawback that your CRM will get the messages you
send but not the ones you receive.

You could use the same approach for this, by configuring two email
accounts (only the sending part matters, you don't need to -and
probably shouldn't- configure the inbox twice), one with the bcc mail
and one without.

However, this still requires you to choose the right sending account on
the From field (and it will probably pick automatically the wrong
account on 50% of replies, since both would have the same address
configured).
A similar approach would be to configure it to always bcc and manually
remove it when unneeded (less typing, but needed on 80% of your
emails).

In order to automatically bcc c...@example.com on certain messages only
(e.g. only those not to @example.com), the approach I would follow is
to configure the account to send with sendmail, but with the option
'Use custom binary, instead of sendmail'.
Then you point it to a script which evaluates the recipients (which is
quite easy, as they are all individual parameters) and, depending
whether all recipients match your whitelist or not, exec
 sendmail "$@"
or
 sendmail "$@" c...@example.com


Best regards



___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Safe to delete .debris folder? Y/N?

2021-02-23 Thread Kiwi Rider via evolution-list

On 22/02/21 11:04 pm, Andy Proctor via evolution-list wrote:



[..]
Do you by any chance have Mega installed and linked to your Evolution 
folder?

[..]
No worries, thanks it really helps, yes I do have mega installed and linked to 
my evolution folder. It would point to it being sync errors across machines, or 
items deleted on one then moved to the other.
Useful to know, thoughts on "safe to delete"? I might just move/rename and see 
and report back.
Rename or move would be best (and I do that often myself if I have any 
doubts), however there is a 'clear' button if you go to Mega -> Settings 
-> Advanced.


There's also a schedule option, on mine it is set to clear .debris after 
30 days which I suspect is the default. I only have 2 files there, a 
script runs on my media PC every few hours to check the IP address and 
overwrites one file when it changes (every few months), with that file 
synced over mega (in case I ever need to access a machine while away 
from home)


I believe (and I could be wrong on this) that the  .debris folder is 
used where files change often and there's some uncertainty as to which 
is the correct version, or in cases where files change on 2 clients 
causing conflicting versions. I only have a couple that may change and 
there's copies of them in my debris folder, but in your case you'd 
probably have quite a few and changes, and if more than one machine uses 
that sync and can update emails (via the email server), and wind up 
polling simultaneously, that could lead to apparent conflicts.


I'm replying to the list in case it helps others with similar questions. 
Very little search results on this folder on duckduckgo etc :)


Take care,
KR
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Safe to delete .debris folder? Y/N?

2021-02-23 Thread Andy Proctor via evolution-list





-Original Message-
From: Kiwi Rider via evolution-list 
Reply-To: kiwirider...@gmail.com
To: evolution-list@gnome.org
Subject: Re: [Evolution] Safe to delete .debris folder? Y/N?
Date: Mon, 22 Feb 2021 21:15:30 +1300



  

  
  
Hi there, 



I've only seen ".debris" folders from the sync/cloud backup tool
"Mega" (aka 'mega.nz'). I haven't come across it anywhere else on
my
system or any other's I've administered (and a check on the
machines
here that have Mega shows it somewhere with that, those that don't
have Mega don't have such a folder).



Searching on the web also only finds references to Mega.



Do you by any chance have Mega installed and linked to your
Evolution folder?



HTH,HAND,

KR



[Sorry for the repeated message Andy, I often forget to hit
"reply-list" and didn't manage to catch it this time :)]


No worries, thanks it really helps, yes I do have mega installed and
linked to my evolution folder. It would point to it being sync errors
across machines, or items deleted on one then moved to the other. 
Useful to know, thoughts on "safe to delete"? I might just move/rename
and see and report back. 
Thanks
Andy

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list