Re: [Evolution] Issue when changing default location of Evolution mail folder to another device

2020-05-06 Thread Karim AFIFI via evolution-list

Hi,

Thanks for pointing to this.
After a second check  I found that I can't write in user mode (in root 
mode no problem, this confused me...).


I have some trouble, because directory still appears "read-only", even 
if Synology is setting to "R/W". I noticed :


My CIFS volume is sharing with a Windows 10 user and an Ubuntu user 
(each one has its own directory).

Is it a problem ?

My volume is sharing via CIFS, do you think that NFS should be 
better/mandatory ?


Any advice will be appreciated :-)

Regards.
Karim




Le 05/05/2020 à 08:33, Milan Crha via evolution-list a écrit :

On Tue, 2020-05-05 at 01:15 +0200, Karim.afifi wrote:

/KARIM/==EVOLUTION==/share/evolution/mail/local/.Outbox/tmp/158863326
3.2662_9.ubuntu:
Permission denied”. The message has not been sent.

...

I can acces to the NAS without any problem (read & write) via a
terminal
or via thunar, caja, etc..

Hi,
are you able to access that particular path with read/write? I'd guess
that something on that path has read only attributes. Or it's owned by
a different user. The system surely knows why it claims about
permissions.
Bye,
Milan

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

___
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] IMAP IDLE and TCP resetting

2020-05-06 Thread Nicholas Guriev via evolution-list
On Tue, 2020-05-05 at 11:17 +0200, Milan Crha wrote:
> Nicholas, it would be helpful to have filled a bug against IMAPx in
> evolution-data-server [1], to not have this lost, though I do not want
> to force that. I'll try to cook a fix and commit it to the sources in
> the following days (unless I forget).

Okay, a new issue against evolution-data-server has been opened. Thank you so
much for the help.

https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/211

___
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] Issue when changing default location of Evolution mail folder to another device

2020-05-06 Thread Karim AFIFI via evolution-list

Hello Karim

How are you mounting the CIFS volume?

Note that if you are mounting it via gvfs there are some bugs that could
result in contents appearing as if read-only. See for instance
https://gitlab.gnome.org/GNOME/gvfs/-/issues/249
Not sure if that could be the case here, it's not clear how are those
"user mode" / "root mode" you were testing in.

Best regards


Hi Angel,

I have seen this, but I did not worry because it dates from a few years. 
You've right, its not very clear, I will take a look...


I found something interesting here about uid/gid mismatching on NFS :

https://askubuntu.com/questions/677922/how-can-i-get-read-write-access-to-nfs-share-of-synology-nas 



I will try to modify  tomorrow, and I'll post the result.

Regards.
Karim


___
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] Issue when changing default location of Evolution mail folder to another device

2020-05-06 Thread Patrick O'Callaghan
On Wed, 2020-05-06 at 03:40 +0200, Karim.afifi wrote:
> It's for "transparent backup"; I am working without I need to backup 
> manually :
> - All data (I mean for all applications, including Evo) are stored on 
> the NAS.
> - Data are automatically backup on the NAS every night (multiples RAID)
> - Plus backup on external support every month.
> 
> 
> "If it's for backup, then I think the synology boxes can do SMTP & IMAP 
> - use those to manage your mail, life will be saner!"
> 
> Yes Synology supports SMTP, IMAP, etc..., but how to access to the files 
> ? I will check how it works ans if there any good Linux client.
> 

[Please use proper quoting style to make it easier to read your posts.
See most other messages on this list, including this one, for examples]

If you use Evo with IMAP, you don't need to back up your mail, just
your settings (which don't generally change very often). That's
independent of using a NAS or not. I agree with Pete: using a NAS for
your home directory is not ideal. Much better is to keep the home
directory local and have a regular (say nightly) backup to the NAS. You
can do that without NFS or CIFS by using rsnapshot, borgbackup or any
number of other options (Synology may even have an app for that). Even
if the backup solution requires NFS write access (which rsync-based
solutions do not), it's just that one program running in the small
hours, not every piece of software that touches your home directory.
You can then mount the NAS read-only with NFS for data recovery, which
avoids locking issues entirely.

poc

___
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] HTML to PDF in accessibility mode

2020-05-06 Thread U.vi via evolution-list
Le mardi 07 avril 2020 à 09:47 +0200, Milan Crha via evolution-list a
écrit :
> On Tue, 2020-04-07 at 04:19 +0200, U.vi via evolution-list wrote:
> > I've a very important HTML email conversation I have to
> > print/backup.
> 
>   Hi,
> I do not know of the use case, but I dare to ask: would the backup of
> the email, instead of some PDF, not be better? Unless you really need
> a
> data origin than the PDF file. It can be eventually harder to extract
> the information from a standalone .mbox file, without proper tooling.
> 

Well in general things begin with pdf/print, then if going further you
have to provide raw material. With visualy faked pdf you have no
chance.


> > Temporarly switching for a bright theme does nothing. It's HTML
> > coded
> > on mail source -white font when printing-.
> 
> Aha, it's very nice from the sender. Depending on how often you
> receive
> such mails, maybe you can save the message, edit the style for
> printing, then import the message and print it.
> 

Yes we can always tweak everything but definitly not a regular usage.
Lots of daily emails are prettyfied: commercials but also officials
that you can't cut trought. So nope.


> > Evolution 3.36.1 (by Flathub.org)
> 
> That version allows to disable colors in HTML mails, using theme
> colors
> like in the Plain Text mode. As you've it in Flatpak, you should run
> a
> terminal in the Evolution sandbox first:
> 
>$ flatpak run ---command=sh org.gnome.Evolution
> 
> then change the setting:
> 
>$ gsettings set org.gnome.evolution.mail preview-unset-html-colors 
> true
> 
> I do not know how much it influences print of the message, or if at
> all.
> 

It only affect inbox display. Nothing better when answer, transfer,
print/pdf.

It's pretty surprising and disappointing that such a tool like
Evolution doesn't fully handle black themes/accessibility.
I won't hit you but it really, really deserve an prioritary update and
I pray and cry for it!

Maybe there is a bug/request roadmap somewhere?

Thanks a lot.

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

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


[Evolution] Filter problems when running shell command...

2020-05-06 Thread DrOteonu via evolution-list
Hi, 

I try to define a filter that executes an external shell script.
However, the result is erratic. Sometimes the shell-script is executed
correctly, sometimes it isn't. Lets say, 25% of the time it runs, 75%
it does not. I have no clue why, it feels like throwing dice.

The script with filename "received_mail_from_john" contains the
following:

(begin script)
espeak "Why am I only read out loud sometimes, and not always?"
(end script)

I also checked the filter log. It always looks good. It states that the
script is called (except that sometimes this does not have any effect):

(begin log)
2020-05-06 13:39:21 - Applied filter "john_mail" to message from john <
j...@zoho.com> - "Re: Andijvie?"
   Info value 'john ' of header 'From' does match
'john'
   Finished test of message uid:62958 subject:'Re: Andijvie?' from 
'da...@ziggo.nl : INBOX' as MATCHED
   Filter 'john_mail' matched

Action: Executing shell command: [/bin/sh -c
/home/danny/shellscripts/communication/received_mail_from_john]
(end log)

I have tested this "in vivo" by waiting for emails, and also "in vitro"
by pressing Ctrl-Y. 

The script always works flawlessly when executing it from the command
line.

Thanks,

DrO
___
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] Filter problems when running shell command...

2020-05-06 Thread Patrick O'Callaghan
On Wed, 2020-05-06 at 13:51 +0200, DrOteonu via evolution-list wrote:
> Hi, 
> 
> I try to define a filter that executes an external shell script.
> However, the result is erratic. Sometimes the shell-script is executed
> correctly, sometimes it isn't. Lets say, 25% of the time it runs, 75%
> it does not. I have no clue why, it feels like throwing dice.
> 
> The script with filename "received_mail_from_john" contains the
> following:
> 
> (begin script)
> espeak "Why am I only read out loud sometimes, and not always?"
> (end script)
> 
> I also checked the filter log. It always looks good. It states that the
> script is called (except that sometimes this does not have any effect):
> 
> (begin log)
> 2020-05-06 13:39:21 - Applied filter "john_mail" to message from john <
> j...@zoho.com> - "Re: Andijvie?"
>Info value 'john ' of header 'From' does match
> 'john'
>Finished test of message uid:62958 subject:'Re: Andijvie?' from 
> 'da...@ziggo.nl : INBOX' as MATCHED
>Filter 'john_mail' matched
> 
> Action: Executing shell command: [/bin/sh -c
> /home/danny/shellscripts/communication/received_mail_from_john]
> (end log)
> 
> I have tested this "in vivo" by waiting for emails, and also "in vitro"
> by pressing Ctrl-Y. 
> 
> The script always works flawlessly when executing it from the command
> line.

The log shows that the script is being called, so the problem isn't
with Evolution but with the script itself. I would check that the
script always has access to the right output channel when it's run.
This could fail randomly if Evo calls it asynchronously (via the
filter) but wouldn't fail if being called synchronously (from the
command line). That's just a guess as I don't know how Evo actually
does this.

IOW I think you need to put some logging into the script itself.

poc

___
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] Issue when changing default location of Evolution mail folder to another device

2020-05-06 Thread Pete Biggs
On Wed, 2020-05-06 at 03:40 +0200, Karim.afifi wrote:
> Hi Pete, 
> 
> "Please don't top post on this list." 
> 
> OK... 
> 

Randomly putting quote marks around things is not the normal way of
quoting email content. Is there any reason why you can't just reply the
same way as everyone else??

> 
> 
> I tried to share via NFS today, but I had another issue here : 
> - user => access denied (permissions) 
> - root (just to test) => no problem 
> It seems this behavior is because the computer and the NAS have different uid 
> and gid. 
> Tomorrow, I will modify values on the NAS, I hope it will fix. 

Yes, you have to match up the UID's and GID's on the client and server,
otherwise it won't work.  That's not just for NFS, most remote storage
needs some form of user based access and you have to take care to make
sure that the control mechanisms work properly.

> 
> 
> "My general advice would be "don't do it". So, why are you wanting to
> put your Evo storage on a network filesystem? If it's purely for
> storage, then get yourself a bigger disk! " 
> 
> It's for "transparent backup"; I am working without I need to backup manually 
> : 
> - All data (I mean for all applications, including Evo) are stored on the 
> NAS. 
> - Data are automatically backup on the NAS every night (multiples RAID) 
> - Plus backup on external support every month. 

Backup doesn't need to be manual - there are lots of automated backup
solutions that are available as part of the OS repositories.

> 
> 
> "If it's for backup, then I think the synology boxes can do SMTP &
> IMAP - use those to manage your mail, life will be saner!" 
> 
> Yes Synology supports SMTP, IMAP, etc..., but how to access to the
> files ? I will check how it works ans if there any good Linux
> client. 
> 
What do you mean "how to access the files"?  If your mail is stored on
the synology box and you access it by IMAP, then you don't need to
access any of the "files". The issue you should be looking at is how to
get the mail onto the synology box in the first place.  But by far the
best solution is to use IMAP to access your mail on your mail
provider's server. You have a free.fr mail address, if that's where
your mail ends up, then they have IMAP, so use it.  Your mail will
remain on their servers, nothing of real importance will be held on
your local machine other than configuration - and since that doesn't
really change often, a daily or weekly backup of that to your synology
box will be sufficient.

P.


___
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] Issue when changing default location of Evolution mail folder to another device

2020-05-06 Thread Adam Tauno Williams
> It would be preferential to use an NFS mount. But that has issues as
> well - file locking across NFS is an issue and
> performance/reliability
> depends to a large extent on the server side.  I don't know what the
> underlying OS is on the synology NAS, but it would be worth
> investigating.

If you NFS mount your home directory - and your NFS server is sane [as
AFAIK all moderately recent servers are]

1.) You won't need to "relocate" anything.
2.) You can let the NAS or server do all the backups

That is the 'normal' way to do this.  Remote mount your entire home
directory - don't try to peace meal things.  It works just fine.  I've
had hundreds of LINUX desktops remote mounting their home directory -
it works.

Yes, your uid/gid number mapping **MUST WORK**.  That is between your
server and your client; it is not application specific.  Modern NFS has
multiple solutions for this problem.
___
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] HTML to PDF in accessibility mode

2020-05-06 Thread U.vi via evolution-list
Le mardi 07 avril 2020 à 09:47 +0200, Milan Crha via evolution-list a
écrit :
> > Evolution 3.36.1 (by Flathub.org)
> 
> That version allows to disable colors in HTML mails, using theme
> colors
> like in the Plain Text mode. As you've it in Flatpak, you should run
> a
> terminal in the Evolution sandbox first:
> 
>$ flatpak run ---command=sh org.gnome.Evolution
> 
> then change the setting:
> 
>$ gsettings set org.gnome.evolution.mail preview-unset-html-
> colors 
> true
> 
> I do not know how much it influences print of the message, or if at
> all.
> 

In addition to just above : now inbox html are only using backgroung
color theme. So we have black font on black background.

Thanks a lot.

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

___
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] Issue when changing default location of Evolution mail folder to another device

2020-05-06 Thread Patrick O'Callaghan
On Wed, 2020-05-06 at 13:04 -0400, Adam Tauno Williams wrote:
> That is the 'normal' way to do this.  Remote mount your entire home
> directory - don't try to peace meal things.  It works just fine.  I've
> had hundreds of LINUX desktops remote mounting their home directory -
> it works.

Me too, when I was running a departmental server and people could 'hot
desk'. At home I prefer not to do that as my local SSD is much faster
than a relatively slow NAS, even when it's on an Gigabit connection. In
fact my NAS blew up a few weeks ago so I'm glad I didn't. No data was
lost but the box itself stopped working (it was 10 years old and not
worth repairing).

poc

___
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] HTML to PDF in accessibility mode

2020-05-06 Thread Milan Crha via evolution-list
On Wed, 2020-05-06 at 13:33 +0200, U.vi wrote:
> It only affect inbox display. Nothing better when answer, transfer,
> print/pdf.

Hi,
right, the option is for display. I do not know what you mean with
'transfer', is it like the 'Forward' function? The 'answer' might be
'Reply', right? Nonetheless, none of the three are handled by the
option.

You should understand that the sender has some intention to present the
content in certain way. That it makes it difficult to read for the
recipients is solely their fault, from my point of view. The mail
reader software can have workarounds to "correct" it, but they'll be
just workarounds of their fault. You bet that every sender uses his/her
own special formatting, which will break the workarounds easily.

Similarly, that the black color works fine for you doesn't mean that it
works fine for others. I just received a message with the text written
in magenta color, all being in italic. It was hard to read for me, but
it seems the sender likes this (for me weird) combination. I think, for
the same reason, that it's good idea to keep the original formatting in
reply/forward, to keep as much of the original information as possible,
not to force user preferences on top of original sender's preferences.
You can always switch to the Plain Text mode in the composer, to get
the formatting lost.

You can use Edit->Preferences->Mail Preferences->HTML Messages->Plain
Text Mode->Only ever show plain and check also to show suppressed parts
as attachments, thus you can easily reach them if needed. It depends
whether the sender sends an equivalent text plain version with their
fancy HTML content (some do not, for what it worth).

> It's pretty surprising and disappointing that such a tool like
> Evolution doesn't fully handle black themes/accessibility.

I'm sorry to say this, but even it might look simple to some people,
it's obviously a complex task when one knows something about HTML and
CSS. There are too many possibilities to handle.

> ...I pray and cry for it!
> 
> Maybe there is a bug/request roadmap somewhere?

I'm not aware of other than the one I referenced earlier and that one
is considered fixed. There might be some similar, though, like to
forward/reply/print to what the user sees (you can switch between HTML
and Plain text parts in the view), but it's more about parts switching,
not about HTML modifications.

You can open a new bug, if you want to not get this forgotten.

By the way, having set black background for printing doesn't sound like
a good idea. That's an argument to *not* derive theme colors for
printing.

On Wed, 2020-05-06 at 19:08 +0200, U.vi wrote:
> In addition to just above : now inbox html are only using backgroung
> color theme. So we have black font on black background.

You see it, it's a complex task. The option worked for me when testing
on messages I had. Your massage may contain something "special". Having
a test message would help to narrow the issue down. Ideally attach one
such message to your bug report, if you'll create one. Make sure the
message will not contain any private information.

Bye,
Milan

P.S.: By the way, Reply to List (Ctrl+L) works better for me on this
mailing list.

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