Re: [Evolution] Sending photos from digKam: "Skipping suspicious attachment"

g > in Bugzilla and mark it as an enhancement or feature request I'll do that if the .kde directory doesn't make it onto the official whitelist. If .kde does make the list, then it's probably better to wait and see if the need ever arises again. Jacob Nielsen ___

Re: [Evolution] Sending photos from digKam: "Skipping suspicious attachment"

gt; if I read the code properly, then there is submitted an alert about > suspicious attachment, but the file is attached anyway, in 3.4.x+, thus > this works way differently in current stable than in 3.2.3. The 3.4.x behaviour is very reasonable, but i

Re: [Evolution] Sending photos from digKam: "Skipping suspicious attachment"

DA8UIj/667ZFW/IMG_2488.jpeg" Maybe because of the second hidden directory in the path? Jacob Nielsen ___ 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] Sending photos from digKam: "Skipping suspicious attachment"

select KDE apps. But if they don't, they should. Will Evolution accept any path in $XDG_CACHE_HOME? Jacob Nielsen ___ 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] Sending photos from digKam: "Skipping suspicious attachment"

t it in the composer window." Fair enough. But I get no indication at all in the GUI that the attachments were skipped. And is it possible to convince Evolution that stuff in .kde is not suspicious? Thanks in advance, Jacob Nielsen Ubuntu 12.04 Evolution version 3.2.3-0ubunt