From stefano.fiori at bac.sm Mon Jan 3 13:46:40 2022 From: stefano.fiori at bac.sm (Stefano Fiori) Date: Mon, 3 Jan 2022 14:46:40 +0100 (CET) Subject: [ZendTo] New GDPR cookie Policy References: <53968628.18094741.1641217600052.JavaMail.zimbra@bac.sm> Message-ID: Hi, new GDPR specifications concerning cookie utilizations inside a web site, will take place from 10th of January 2022. Looking to other sites there is a special grid to allow or disallow some cookie utilization. In preferences.php we find: // If you are in the EU, you really should show a consent box to // ensure the user understands that the site is (1) storing a cookie // (albeit only a session cookie), and (2) will store their email address // and name in order to talk to the sender/recipients of the drop-off. // This is for EU GDPR purposes. 'cookieGDPRConsent' => TRUE, When enabled it gives in the main page a simple information about the cookie utilizations. Empowering the cookie request is a subject that is already arised to the attention of anyone ? Thank you a lot. Bye. Stefano Fiori U.O. Organizzazione ed I.T. Banca Agricola Commerciale Istituto Bancario Sammarinese S.p.A. Email: stefano.fiori at bac.sm TEL: 0549871299 Mobile: 3391361639 >From other country TEL: +378871299 Mobile: +393391361639 -------------------------------------------------------------- Le informazioni contenute in questo messaggio sono riservate ed esclusivamente indirizzate al destinatario indicato - ovvero alla persona incaricata di recapitarlo. La riproduzione, la comunicazione, la diffusione non autorizzate non sono consentite. Nel caso in cui aveste ricevuto questo messaggio per errore, vogliate cortesemente distruggerlo, compresi gli eventuali allegati, e avvertire tempestivamente il mittente. La Societa' indicata nell'indirizzo non assume alcuna responsabilita' per eventuali danni conseguenti a eventi causati da questo messaggio in seguito a manipolazioni del contenuto o della struttura quali: intercettazioni, modifiche, danneggiamenti, usi impropri. I contenuti del messaggio non comportano alcun vincolo ne' creano obblighi per la Societa' stessa, salvo cio' non sia espressamente previsto da un accordo scritto. La Banca tratta i dati personali in linea con la Legge RSM n. 171/2018 e il Regolamento Europeo 2016/679 (GDPR). I dati personali verranno utilizzati ai sensi dell'art. 13 della Legge n. 171/2018 e dell'art. 13 del Regolamento (UE) 2016/679 (GDPR), anche tramite soggetti esterni, al fine di permettere l'espletamento degli adempimenti informativi, amministrativi e contabili connessi al rapporto contrattuale e pre-contrattuale Copia integrale dell'informativa potra' essere visionata presso le nostre sedi, scrivendo a privacy at bac.sm o consultando per informazioni la 'Privacy Policy' presente sul sito web della Banca al seguente link: https://www.bac.sm/privacy-policy/. Per ulteriori richieste e' possibile rivolgersi al Titolare del trattamento (Banca Agricola Commerciale SpA con sede legale in Via Tre Settembre, 316 - 47891 Dogana). E' possibile anche contattare il Responsabile della protezione dei dati (privacy at bac.sm). Grazie per la collaborazione. The information contained in this message is confidential and exclusively addressed to the above mentioned addressee, namely the person instructed to deliver it. Unauthorized reproduction, communication and dissemination of information are not allowed. In case you receive this message erroneously, please destroy it together with its attachments and notify immediately the sender. The company indicated in the address is not responsible for any eventual damage deriving from any form of manipulation of the content or structure of this message, such as modifications, damage, wiretaps or improper uses. The content of this message does not result in any constraint or obligation for the company itself, except for what might be explicitly provided for in further written agreements. The Bank processes personal data according to the RSM Law n. 171/2018 and the European Regulation 2016/679 (GDPR). Personal data will be used pursuant to Article 13 of RSM Law no. 171/2018 and to Article 13 of UE Regulation no. 2016/679 (GDPR), also via external parties, in order to allow the completion of the informative, administrative and accounting obligations related to the contractual and pre-contractual relationship. A full copy of the disclosure can be viewed at our sites, by sending an e-mail to privacy at bac.sm or by consulting the 'Privacy Policy' section in the Bank website, available at the following link: https://www.bac.sm/privacy-policy/. For additional inquiries, please contact the Data Controller (Banca Agricola Commerciale Spa., with registered office in Via Tre Settembre, 316 - 47891 Dogana, RSM). Finally, it is also possible to contact the Data Protection Officer (privacy at bac.sm). Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jules at zend.to Fri Jan 7 11:23:57 2022 From: jules at zend.to (jules at zend.to) Date: Fri, 7 Jan 2022 11:23:57 +0000 Subject: [ZendTo] New GDPR cookie Policy In-Reply-To: References: <53968628.18094741.1641217600052.JavaMail.zimbra@bac.sm> Message-ID: <8d5534a5-4c43-8bdd-85f5-1558fda9e448@Zend.To> The only cookies that ZendTo uses are strictly functional ones, there aren't any categories to agree to. Because they're strictly functional, I'm not sure you're duty bound to even have to tell the users much about them. If you decline the cookies, ZendTo simply won't work. But I'm sure someone who's actually read all the info about it will be able to correct me. Cheers, Jules. On 03/01/2022 13:46, Stefano Fiori via ZendTo wrote: > Hi, new GDPR specifications concerning cookie utilizations inside a > web site, will take place from 10th of January 2022. > Looking to other sites there is a special grid to allow or disallow > some cookie utilization. > > In preferences.php we find: > > ?// If you are in the EU, you really should show a consent box to > ? // ensure the user understands that the site is (1) storing a cookie > ? // (albeit only a session cookie), and (2) will store their email > address > ? // and name in order to talk to the sender/recipients of the drop-off. > ? // This is for EU GDPR purposes. > ? 'cookieGDPRConsent'? ? => TRUE, > > When enabled it gives in the main page a simple information about the > cookie utilizations. > > Empowering the cookie request is a subject that is already arised to > the attention of anyone ? > > Thank you a lot. > > Bye. > > Stefano Fiori > > U.O. Organizzazione ed I.T. > Banca Agricola Commerciale Istituto Bancario Sammarinese S.p.A. > > Email: stefano.fiori at bac.sm > TEL: ? ?0549871299 > Mobile: 3391361639 > > From other country > TEL: ? ?+378871299 > Mobile: +393391361639 > > > --------------------------------------------------------------------------------------------------------------- > Le informazioni contenute in questo messaggio sono riservate ed > esclusivamente indirizzate al destinatario indicato - ovvero alla > persona incaricata di recapitarlo.La riproduzione, la comunicazione, > la diffusione non autorizzate non sono consentite.Nel caso in cui > aveste ricevuto questo messaggio per errore, vogliate cortesemente > distruggerlo, compresi gli eventuali allegati, e avvertire > tempestivamente il mittente.La Societ? indicata nell?indirizzo non > assume alcuna responsabilit? per eventuali danni conseguenti a eventi > causati da questo messaggio in seguito a manipolazioni del contenuto o > della struttura quali: intercettazioni, modifiche, danneggiamenti, usi > impropri.I contenuti del messaggio non comportano alcun vincolo n? > creano obblighi per la Societ? stessa, salvo ci? non sia espress > amente previsto da un accordo scritto.La Banca tratta i dati personali > in linea con la Legge RSM n. 171/2018 e il Regolamento Europeo > 2016/679 (GDPR).I dati personali verranno utilizzati ai sensi > dell'art. 13 della Legge n. 171/2018 e dell'art. 13 del Regolamento > (UE) 2016/679 (GDPR), anche tramite soggetti esterni, al fine di > permettere l'espletamento degli adempimenti informativi, > amministrativi e contabili connessi al rapporto contrattuale e > pre-contrattuale.Copia integrale dell'informativa potra' essere > visionata presso le nostre sedi, scrivendo a privacy at bac.sm o > consultando per informazioni la 'Privacy Policy' presente sul sito web > della Banca al seguente link: https://www.bac.sm/privacy-policy/. Per > ulteriori richieste ? possibile rivolgersi al Titolare del trattamento > (Banca Agricola Commerciale SpA con sede legale in Via Tre Settembre, > 316 47891 Dogana).E? possibile anche contattare il Responsabile della > protezione dei dati (privacy @bac.sm) . > Grazie per la collaborazione. > > The information in this message is reserved and is exclusively > addressed to the above mentioned person.Reproduction, comunication or > sending of unauthorised information is not allowed.If you have > received this message by mistake, please delete, including any > attachments and you promptly notify the sender.The company indicated > as sender does not assume any responsability for any consequential > damage on anything that could happen on receipt of this message and > following manipulation of the contents or structure, such as: > interception, changes, damage, improper use.The contents for the > message do not create bonds nor obligations for the company, other > than those specifically expressed by written agreement.The Bank > processes personal data in line with the RSM Law n. 171/2018 and the > European Regulation 2016/679 (GDPR).Personal data will be used > pursuant to Article 13 of RSM Law no. 171/2018 and to Article 13 of UE > R egulatio n no. 2016/679 (GDPR), also via external parties, in order > to allow the completion of the informative, administrative and > accounting obligations related to the contractual and pre-contractual > relationship.A full copy of the disclosure can be viewed at our sites, > by sending an e-mail to privacy at bac.sm or by consulting the 'Privacy > Policy' section in the Bank website, available at the following link: > https://www.bac.sm/privacy-policy/.For further inquiries, please > contact the Data Controller (Banca Agricola Commerciale SpA with > registered office in Via Tre Settembre, 316 47891 Dogana).It is also > possible to contact the Data Protection Officer (privacy at bac.sm). > Thank you for your cooperation. > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'The AI does not hate you, nor does it love you, but you are made out of atoms which it can use for something else.' - Eliezer Yudkowsky www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From jules at zend.to Fri Jan 7 11:41:45 2022 From: jules at zend.to (jules at zend.to) Date: Fri, 7 Jan 2022 11:41:45 +0000 Subject: [ZendTo] Remove me from your subscription In-Reply-To: References: Message-ID: Done. On 07/12/2021 11:29, Rahul Kumar via ZendTo wrote: > -- > Thanks, > Rahul Kumar > Contact(M): 9958664330 > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'In a very real sense, we are all aliens on a strange planet. We spend most of our lives reaching out and trying to communicate. If during our whole lifetime, we could reach out and really communicate with just two people, we are indeed very fortunate.' - Gene Roddenberry www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From jules at zend.to Fri Jan 7 12:00:55 2022 From: jules at zend.to (jules at zend.to) Date: Fri, 7 Jan 2022 12:00:55 +0000 Subject: [ZendTo] Migrating current drop-offs to a new Zend.to server In-Reply-To: References: Message-ID: Glenn, Switch off the Apache daemon (systemctl stop apache2 or systemctl stop httpd) so you know nothing will be trying to change it. Then just copy the single zendto.sqlite file to wherever you want it to go. It's as simple as that. The entire database is held in that one file, that's one of the things that makes SQLite so easy to use. Cheers, Jules. On 18/11/2021 19:47, Glenn Noel via ZendTo wrote: > Hello folks, > > I'm circling back to this task and wanted to check with?you all again > to see if anyone had a fairly comprehensive set of instructions for > copying/migrating a zend.to database and drop-offs > from an older server to a new server? > > My database is the default SQLite3 (/var/zendto/zendto.sqlite) that > installs via the Zend.to installer .? I found the following historical > post: > http://mailman.ecs.soton.ac.uk/pipermail/zendto/2018-March/003159.html. > This post indicates: > > /"Export your database (full dump and upgrade schema or just data > spending?on your old version"/ > > I have tried looking up how to export SQLite databases and have tried > and failed a frustrating amount of times.? I have very little > experience with databases so it's a definitely a learning experience > for me - however I'm at the point now where I feel I'm not making any > progress.? If anyone could offer suggestions or easy-to-follow > tutorials I would be grateful. > > The next post in the thread that I listed above: > http://mailman.ecs.soton.ac.uk/pipermail/zendto/2018-March/003160.html > > "/1. Comment out the cron jobs in /etc/cron.d/zendto and then restart > crond on both your old and new servers before you give them both access > to the database. > Failure to do this will result in the overnight cleanup job *wiping all > your drop-offs and/or database records* of them. > > 2. After you've copied all the /var/zendto stuff over to your new > server, then assuming your new server is using SELinux (which it will be > by default), you need to reset the SELinux attributes on everything > under /var/zendto. > Fortunately this is very easy. On the new server, as root do > ? ? ?restorecon -FivR /var/zendto > Obviously you'll need to make sure the basic owner, group and > permissions are correct after your rsync (or however you're getting them > there), but things won't work unless you do the restorecon above as > well. "ls -Z" shows you the SELinux attributes. The "-FivR" options make > it recurse and show you any files it changes the attributes of."/ > > This sounds pretty straight-forward (Thanks Jules :) ), but I wanted > to check with the community if all of this was still accurate for > current installs? > > All assistance is always appreciated. > > Glenn > > > On Thu, Oct 21, 2021 at 1:16 PM Glenn Noel wrote: > > Hello Zendto community, > > I have an older Zend.to server running Ubuntu Server 16.04.6 LTS > running Zend Ver. 5.19-1.? I've deployed and configured a new > server running Ubuntu Server 20.04.3 LTS running Zend Ver 6.11-2. > > My new server is ready for production, but I'd like to move any > existing drop-offs from the old server to the new server. > > I have looked over the zend.to site, but have > been unable to find any documentation about how to move the > drop-offs.? I also found some older posts about others that have > done this, but I wanted to check if anyone could point?me in the > right direction for up-to-date instructions on how to do this? > > Thanks for any assistance you can provide. > > Glenn > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'Probability factor of one to one. We have normality. I repeat, we have normality. Anything you still can't cope with is therefore your own problem.' - Trillian, The Hitch Hikers Guide to the Galaxy www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From m.v.sangster at abdn.ac.uk Fri Jan 7 14:13:11 2022 From: m.v.sangster at abdn.ac.uk (Sangster, Mark) Date: Fri, 7 Jan 2022 14:13:11 +0000 Subject: [ZendTo] New GDPR cookie Policy In-Reply-To: References: <53968628.18094741.1641217600052.JavaMail.zimbra@bac.sm> <8d5534a5-4c43-8bdd-85f5-1558fda9e448@Zend.To> Message-ID: Hello, As Jules indicates, you are not required to seek consent for certain types of cookie usage. This site is from the ICO here in the UK, so it might not be valid for your own country but may help understand how it works. https://ico.org.uk/for-organisations/guide-to-pecr/guidance-on-the-use-of-cookies-and-similar-technologies/how-do-we-comply-with-the-cookie-rules/#comply16 Therefore, ZendTo doesn't require to seek consent for its cookie as it is required for it to function. ZendTo doesn't provide is a page to indicate the name, purpose, and duration of the cookies it uses. This could be a useful improvement, as it would explain the purpose of the cookie (e.g., https://www.abdn.ac.uk/about/our-website/cookies.php). Cheers Mark From: ZendTo On Behalf Of Julian Field via ZendTo Sent: 07 January 2022 11:24 To: ZendTo Users Cc: jules at zend.to; Stefano Fiori Subject: Re: [ZendTo] New GDPR cookie Policy CAUTION: External email. Ensure this message is from a trusted source before clicking links/attachments. The only cookies that ZendTo uses are strictly functional ones, there aren't any categories to agree to. Because they're strictly functional, I'm not sure you're duty bound to even have to tell the users much about them. If you decline the cookies, ZendTo simply won't work. But I'm sure someone who's actually read all the info about it will be able to correct me. Cheers, Jules. On 03/01/2022 13:46, Stefano Fiori via ZendTo wrote: Hi, new GDPR specifications concerning cookie utilizations inside a web site, will take place from 10th of January 2022. Looking to other sites there is a special grid to allow or disallow some cookie utilization. In preferences.php we find: // If you are in the EU, you really should show a consent box to // ensure the user understands that the site is (1) storing a cookie // (albeit only a session cookie), and (2) will store their email address // and name in order to talk to the sender/recipients of the drop-off. // This is for EU GDPR purposes. 'cookieGDPRConsent' => TRUE, When enabled it gives in the main page a simple information about the cookie utilizations. Empowering the cookie request is a subject that is already arised to the attention of anyone ? Thank you a lot. Bye. Stefano Fiori U.O. Organizzazione ed I.T. Banca Agricola Commerciale Istituto Bancario Sammarinese S.p.A. Email: stefano.fiori at bac.sm TEL: 0549871299 Mobile: 3391361639 >From other country TEL: +378871299 Mobile: +393391361639 --------------------------------------------------------------------------------------------------------------- Le informazioni contenute in questo messaggio sono riservate ed esclusivamente indirizzate al destinatario indicato - ovvero alla persona incaricata di recapitarlo.La riproduzione, la comunicazione, la diffusione non autorizzate non sono consentite.Nel caso in cui aveste ricevuto questo messaggio per errore, vogliate cortesemente distruggerlo, compresi gli eventuali allegati, e avvertire tempestivamente il mittente.La Societ? indicata nell'indirizzo non assume alcuna responsabilit? per eventuali danni conseguenti a eventi causati da questo messaggio in seguito a manipolazioni del contenuto o della struttura quali: intercettazioni, modifiche, danneggiamenti, usi impropri.I contenuti del messaggio non comportano alcun vincolo n? creano obblighi per la Societ? stessa, salvo ci? non sia espress amente previsto da un accordo scritto.La Banca tratta i dati personali in linea con la Legge RSM n. 171/2018 e il Regolamento Europeo 2016/679 (GDPR).I dati personali verranno utilizzati ai sensi dell'art. 13 della Legge n. 171/2018 e dell'art. 13 del Regolamento (UE) 2016/679 (GDPR), anche tramite soggetti esterni, al fine di permettere l'espletamento degli adempimenti informativi, amministrativi e contabili connessi al rapporto contrattuale e pre-contrattuale.Copia integrale dell'informativa potra' essere visionata presso le nostre sedi, scrivendo a privacy at bac.sm o consultando per informazioni la 'Privacy Policy' presente sul sito web della Banca al seguente link: https://www.bac.sm/privacy-policy/. Per ulteriori richieste ? possibile rivolgersi al Titolare del trattamento (Banca Agricola Commerciale SpA con sede legale in Via Tre Settembre, 316 47891 Dogana).E' possibile anche contattare il Responsabile della protezione dei dati (privacy @bac.sm) . Grazie per la collaborazione. The information in this message is reserved and is exclusively addressed to the above mentioned person.Reproduction, comunication or sending of unauthorised information is not allowed.If you have received this message by mistake, please delete, including any attachments and you promptly notify the sender.The company indicated as sender does not assume any responsability for any consequential damage on anything that could happen on receipt of this message and following manipulation of the contents or structure, such as: interception, changes, damage, improper use.The contents for the message do not create bonds nor obligations for the company, other than those specifically expressed by written agreement.The Bank processes personal data in line with the RSM Law n. 171/2018 and the European Regulation 2016/679 (GDPR).Personal data will be used pursuant to Article 13 of RSM Law no. 171/2018 and to Article 13 of UE R egulatio n no. 2016/679 (GDPR), also via external parties, in order to allow the completion of the informative, administrative and accounting obligations related to the contractual and pre-contractual relationship.A full copy of the disclosure can be viewed at our sites, by sending an e-mail to privacy at bac.sm or by consulting the 'Privacy Policy' section in the Bank website, available at the following link: https://www.bac.sm/privacy-policy/.For further inquiries, please contact the Data Controller (Banca Agricola Commerciale SpA with registered office in Via Tre Settembre, 316 47891 Dogana).It is also possible to contact the Data Protection Officer (privacy at bac.sm). Thank you for your cooperation. _______________________________________________ ZendTo mailing list ZendTo at zend.to http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'The AI does not hate you, nor does it love you, but you are made out of atoms which it can use for something else.' - Eliezer Yudkowsky www.Zend.To Twitter: @JulesFM The University of Aberdeen is a charity registered in Scotland, No SC013683. Tha Oilthigh Obar Dheathain na charthannas cl?raichte ann an Alba, ?ir. SC013683. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jules at zend.to Fri Jan 7 14:33:27 2022 From: jules at zend.to (jules at zend.to) Date: Fri, 7 Jan 2022 14:33:27 +0000 Subject: [ZendTo] Migrating current drop-offs to a new Zend.to server In-Reply-To: References: Message-ID: If you run ??? /opt/zendto/sbin/cleanup.php --no-purge then it should do the database schema upgrades for you, without deleting any expired drop-offs (which if you're trying this out, you won't want to do). This is normally done automatically as part of the RPM/DEB package upgrade process. It is also done as part of the routing nightly run of cleanup.php. So if you didn't do it that day, it would be done for you by the next day. Cheers, Jules. On 21/10/2021 18:24, Massimo Forni via ZendTo wrote: > Hi, > > have you tried running 6.x with a copy of the old 5.X database to > check if it will automatically upgrade what needs to be upgraded? > > ------------------------------------------------------------------------ > *From:* ZendTo on behalf of Glenn Noel via > ZendTo > *Sent:* Thursday, October 21, 2021 7:16:56 PM > *To:* ZendTo Users > *Cc:* Glenn Noel > *Subject:* [ZendTo] Migrating current drop-offs to a new Zend.to server > Hello Zendto community, > > I have an older Zend.to server running Ubuntu Server 16.04.6 LTS > running Zend Ver. 5.19-1.? I've deployed and configured a new server > running Ubuntu Server 20.04.3 LTS running Zend Ver 6.11-2. > > My new server is ready for production, but I'd like to move any > existing drop-offs from the old server to the new server. > > I have looked over the zend.to [zend.to] > > site, but have been unable to find any documentation about how to move > the drop-offs.? I also found some older posts about others that have > done this, but I wanted to check if anyone could point?me in the right > direction for up-to-date instructions on how to do this? > > Thanks for any assistance you can provide. > > Glenn > > -- > > *Massimo Forni* > ICT Manager > > Mobile: +393474110278 > > ------------------------------------------------------------------------ > > *Turboden S.p.A.* *I* via Cernaia 10 *I* 25124 Brescia *I* Italy > t. +39 030 3552001 *I* f. +39 030 3552011 > www.turboden.com > > > *Confidentiality notice*: this message, together with its attachments, > may contain strictly confidential and/or legally privileged > information and it is destined solely to the intended addressee(s), > who only may use it under his/their responsibility. Opinions, > conclusions and other information contained in this message, that do > not relate to the official business of this firm, shall be considered > as not given or endorsed by it. If you have received this > communication in error, please notify us immediately by responding to > this email and then delete it from your system. Any use, disclosure, > copying or distribution of the contents of this communication by a > not-intended recipient or in violation of the purposes of this > communication is strictly prohibited and may be unlawful. > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'The AI does not hate you, nor does it love you, but you are made out of atoms which it can use for something else.' - Eliezer Yudkowsky www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From jules at zend.to Fri Jan 7 14:35:02 2022 From: jules at zend.to (jules at zend.to) Date: Fri, 7 Jan 2022 14:35:02 +0000 Subject: [ZendTo] ClamAV error In-Reply-To: References: Message-ID: <4d5f0105-be45-5991-607d-186bd81c6fcc@Zend.To> Yes, you want to keep my modified version. There's a lacking in the clamd configuration in apparmor that needs extending to work with ZendTo, or else it won't be able to scan any files in /var/zendto/incoming. Cheers, Jules. On 18/10/2021 13:44, HILLENBRAND Marita via ZendTo wrote: > > Dear all, > > I retried the update of ourUbuntu 18.04.5 LTS and at one point there > was this message (sorry, it?s a french version)?: > > ?. > > /Fichier de configuration ??/etc/apparmor.d/usr.sbin.clamd??/ > > /==> Modifi? (par vous ou par un script) depuis l'installation./ > > /==> Le distributeur du paquet a fourni une version mise ? jour./ > > /?? Que voulez-vous faire?? Vos options sont les suivantes?:/ > > /??? Y ou I ?: installer la version du responsable du paquet/ > > /??? N ou O ?: garder votre version actuellement install?e/ > > /????? D ?: afficher les diff?rences entre les versions/ > > /????? Z ?: suspendre ce processus pour examiner la situation/ > > /L'action par d?faut garde votre version actuelle./ > > /*** usr.sbin.clamd (Y/I/N/O/D/Z) [d?faut=N] ?/ > > This time, I said ? Y?? and now clamav works fine after the update. > > The only thing that I didn?t get right, was the update of the version > of clamav?: > > /root at sv-ctm-zendto:/home/zendto# freshclam/ > > /WARNING: Ignoring deprecated option SafeBrowsing at > /etc/clamav/freshclam.conf:22/ > > /Mon Oct 18 14:33:03 2021 -> ClamAV update process started at Mon Oct > 18 14:33:03 2021/ > > /Mon Oct 18 14:33:03 2021 //-> ^Your ClamAV installation is OUTDATED!/ > > /Mon Oct 18 14:33:03 2021 -> ^Local version: 0.103.2 Recommended > version: 0.103.3/ > > /Mon Oct 18 14:33:03 2021 -> DON'T PANIC! Read > https://www.clamav.net/documents/upgrading-clamav/ > > /Mon Oct 18 14:33:03 2021 -> daily.cld database is up-to-date > (version: 26326, sigs: 1938868, f-level: 90, builder: raynman)/ > > /Mon Oct 18 14:33:03 2021 -> main.cld database is up-to-date (version: > 62, sigs: 6647427, f-level: 90, builder: sigmgr)/ > > /Mon Oct 18 14:33:03 2021 -> bytecode.cld database is up-to-date > (version: 333, sigs: 92, f-level: 63, builder: awillia2)/ > > I had a look on there website, but that didn?t help me much. I guess > I?ll wait and see. > > Best regards, > > *Marita HILLENBRAND* > Service Informatique > > *Centre Administratif et Technique* > 130, avenue Charles de Gaulle - 91230 Montgeron > T?l : 01 70 58 93 40? Port : 06 24 04 43 58 > www.montgeron.fr > > /Participez, vous aussi, ? la protection de l'environnement en > n'imprimant ce courriel que si n?cessaire.// > //Le pr?sent courriel peut contenir des renseignements confidentiels > et ne s?adresse qu?au(x) destinataire(s) indiqu?(s) ci-dessus. Si ce > courriel vous est parvenu par erreur, veuillez le supprimer et nous en > aviser aussit?t. Merci./ > > *De?:*ZendTo *De la part de* HILLENBRAND > Marita via ZendTo > *Envoy??:* lundi 18 octobre 2021 12:20 > *??:* ZendTo Users > *Cc?:* HILLENBRAND Marita > *Objet?:* Re: [ZendTo] ClamAV error > > Dear all, > > I have also the problem, I updated our Ubuntu 18.04.5 LTS (en root) > ?with the commands below and got the upload error ?The attempt to > virus-scan your drop-off failed. Please notify the system administrator.? > > apt update > > apt upgrade zendto > > # systemctl status clamav-daemon > > ?clamav-daemon.service - Clam AntiVirus userspace daemon > > ?? Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled; > vendor preset: enabled) > > ? Drop-In: /etc/systemd/system/clamav-daemon.service.d > > ??extend.conf > > ?? Active: failed (Result: exit-code) since Mon 2021-10-18 11:32:57 > CEST; 28min ago > > ???? Docs: man:clamd(8) > > man:clamd.conf(5) > > https://www.clamav.net/documents/ > > Main PID: 11391 (code=exited, status=1/FAILURE) > > oct. 18 11:32:56 sv-ctm-zendto systemd[1]: Stopped Clam AntiVirus > userspace daemon. > > oct. 18 11:32:56 sv-ctm-zendto systemd[1]: Starting Clam AntiVirus > userspace daemon... > > oct. 18 11:32:56 sv-ctm-zendto systemd[1]: Started Clam AntiVirus > userspace daemon. > > oct. 18 11:32:57 sv-ctm-zendto clamd[11391]: ERROR: lchown to user > 'clamav' failed on > > oct. 18 11:32:57 sv-ctm-zendto clamd[11391]: log file > '/var/log/clamav/clamav.log'. > > oct. 18 11:32:57 sv-ctm-zendto clamd[11391]: Error was 'Operation not > permitted' > > oct. 18 11:32:57 sv-ctm-zendto clamd[11391]: Mon Oct 18 11:32:57 2021 > -> ^lchown to user 'clamav' failed on log file > '/var/log/clamav/clamav.log'.? Erro > > oct. 18 11:32:57 sv-ctm-zendto systemd[1]: clamav-daemon.service: Main > process exited, code=exited, status=1/FAILURE > > oct. 18 11:32:57 sv-ctm-zendto systemd[1]: clamav-daemon.service: > Failed with result 'exit-code'. > > I got back to the old version for now, but I suspect, I need to update > the system to make the let?s encrypt certificate function. > > Best regards, > > *Marita HILLENBRAND* > Service Informatique > > *Centre Administratif et Technique* > 130, avenue Charles de Gaulle - 91230 Montgeron > T?l : 01 70 58 93 40? Port : 06 24 04 43 58 > www.montgeron.fr > > /Participez, vous aussi, ? la protection de l'environnement en > n'imprimant ce courriel que si n?cessaire.// > //Le pr?sent courriel peut contenir des renseignements confidentiels > et ne s?adresse qu?au(x) destinataire(s) indiqu?(s) ci-dessus. Si ce > courriel vous est parvenu par erreur, veuillez le supprimer et nous en > aviser aussit?t. Merci./ > > *De?:*ZendTo *De la part de* Dean Sherwood > via ZendTo > *Envoy??:* lundi 18 octobre 2021 09:42 > *??:* zendto at zend.to > *Cc?:* Dean Sherwood > *Objet?:* [ZendTo] ClamAV error > > Dear all > > We updated our Ubuntu 18.04.6 LTS server with below commands and now > have the upload error ?The attempt to virus-scan your drop-off failed. > Please notify the system administrator.? > > sudo apt update > > sudo apt upgrade > > --- > > Checking the clamav service we see > > systemctl status clamav-daemon.service > > ? clamav-daemon.service - Clam AntiVirus userspace daemon > > ?? Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled; > vendor preset: enabled) > > ? Drop-In: /etc/systemd/system/clamav-daemon.service.d > > ?????????? ??extend.conf > > ?? Active: failed (Result: exit-code) since Mon 2021-09-27 11:33:58 > +07; 3min 59s ago > > ???? Docs: man:clamd(8) > > ?????????? man:clamd.conf(5) > > ? Process: 1323 ExecStart=/usr/sbin/clamd --foreground=true > (code=exited, status=1/FAILURE) > > ? Process: 1317 ExecStartPre=/bin/chown clamav /run/clamav > (code=exited, status=0/SUCCESS) > > ? Process: 1097 ExecStartPre=/bin/mkdir -p /run/clamav (code=exited, > status=0/SUCCESS) > > Main PID: 1323 (code=exited, status=1/FAILURE) > > Sep 27 11:33:51 zend2 systemd[1]: Starting Clam AntiVirus userspace > daemon... > > Sep 27 11:33:53 zend2 systemd[1]: Started Clam AntiVirus userspace daemon. > > Sep 27 11:33:58 zend2 systemd[1]: clamav-daemon.service: Main process > exited, code=exited, status=1/FAILURE > > Sep 27 11:33:58 zend2 clamd[1323]: ERROR: lchown to user 'clamav' > failed on > > Sep 27 11:33:58 zend2 clamd[1323]: log file '/var/log/clamav/clamav.log'. > > Sep 27 11:33:58 zend2 clamd[1323]: Error was 'Operation not permitted' > > Sep 27 11:33:58 zend2 clamd[1323]: Mon Sep 27 11:33:58 2021 -> ^lchown > to user 'clamav' failed on log file '/var/log/clamav/clamav.log'.? > Error was 'Operation not permitted' > > Sep 27 11:33:58 zend2 systemd[1]: clamav-daemon.service: Failed with > result 'exit-code'. > > --- > > Reinstalled and skipped all parts except for ?Install and configure > virus scanner, including SELinux and AppArmor support for it.? > > Become root with "su -" if using CentOS, RedHat, Debian or SuSE, or > "sudo su -" if using Ubuntu. > > Download the installer: > curl -O zend.to path > > Unpack it and cd into it: > tar xzf install.ZendTo.tgz > cd install.ZendTo > > Run the installer: > ./install.sh > > ================================================================= > > Install and configure ClamAV > > ================================================================= > > Installing ClamAV packages > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > clamav is already the newest version (0.103.2+dfsg-0ubuntu0.18.04.2). > > clamav-daemon is already the newest version > (0.103.2+dfsg-0ubuntu0.18.04.2). > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > Making clamd notice new signatures much faster > > Stop freshclam daemon so we can update signatures > > Updating signatures > > 1. Ignore errors about not being able to notify clamd > > 2. Expect a delay after downloading main.cvd > > 3. Expect a long delay after downloading daily.cvd > > WARNING: Ignoring deprecated option SafeBrowsing at > /etc/clamav/freshclam.conf:22 > > Mon Sep 27 11:32:42 2021 -> ClamAV update process started at Mon Sep > 27 11:32:42 2021 > > Mon Sep 27 11:32:42 2021 -> ^Your ClamAV installation is OUTDATED! > > Mon Sep 27 11:32:42 2021 -> ^Local version: 0.103.2 Recommended > version: 0.103.3 > > Mon Sep 27 11:32:42 2021 -> DON'T PANIC! Read > > Mon Sep 27 11:32:42 2021 -> daily.cld database is up-to-date (version: > 26304, sigs: 1936445, f-level: 90, builder: raynman) > > Mon Sep 27 11:32:42 2021 -> main.cld database is up-to-date (version: > 62, sigs: 6647427, f-level: 90, builder: sigmgr) > > Mon Sep 27 11:32:42 2021 -> bytecode.cld database is up-to-date > (version: 333, sigs: 92, f-level: 63, builder: awillia2) > > Allowing ClamAV to read Apache files > > Allowing ClamAV through AppArmor to read ZendTo uploads > > No need, already done. > > Ubuntu 18: may need to work around a bug in the clamd AppArmor profile > > Good, they have fixed it. No change needed > > * Unloading AppArmor profiles > ????????????????????????????????????????????????????????????????????????????????????????????????????????[ > OK ] > > [ ok ] Starting apparmor (via systemctl): apparmor.service. > > [ ok ] Reloading apparmor configuration (via systemctl): apparmor.service. > > I am going to have to override the systemd definition for > > apache2 so it starts up with PrivateTmp=false. > > I am creating /etc/systemd/system/apache2.service.d/PrivateTmp_zendto.conf > > And tell systemd about the change > > Starting ClamAV and freshclam daemons > > ClamAV has been setup for you to work with ZendTo. > > --- > > However we still have the upload error ?The attempt to virus-scan your > drop-off failed. Please notify the system administrator.? > > Best regards, > > Dean > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'The AI does not hate you, nor does it love you, but you are made out of atoms which it can use for something else.' - Eliezer Yudkowsky www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 2631 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 2631 bytes Desc: not available URL: From jules at zend.to Fri Jan 7 14:47:03 2022 From: jules at zend.to (jules at zend.to) Date: Fri, 7 Jan 2022 14:47:03 +0000 Subject: [ZendTo] Using SAML in Multi Authenticator Setup In-Reply-To: References: Message-ID: <6086543e-e77c-9ebd-6d0d-e9b08071f0e1@Zend.To> You can't use the Muti-authenticator with SAML, except for the single purpose of authenticating the automation (i.e. scripted operations) user. SAML uses such a different model, that's it not really possible to offer both. However, SAML itself can be configured for multiple different authentication systems. So if you have a hybrid AD/AAD tenancy in Azure, that combination should work fine just talking SAML to AAD. Cheers, Jules. On 06/09/2021 19:41, Alex Pimperton via ZendTo wrote: > > Hi, > > Has anybody successfully used SAML as part of a multi-authenticator > setup (I?m trying to use SAML and AD)? > > Both authenticators work fine on their own but trying to use them both > together doesn?t seem to work. > > I can?t see anything in the documentation that explicitly says it > won?t work but the multi-auth examples don?t include SAML and thinking > about it, unless the username was asked for first or there was a > separate (?Click here to use SAML?) button I can?t see how this would > work. > > Can anybody shed any light please? > > Kind Regards, > > > Alex > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'Intelligence is quickness to apprehend as distinct from ability, which is capacity to act wisely on the thing apprehended.' - Alfred North Whitehead www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan.Jones at leesar.com Thu Jan 27 17:37:29 2022 From: Bryan.Jones at leesar.com (Bryan Jones) Date: Thu, 27 Jan 2022 17:37:29 +0000 Subject: [ZendTo] Translations inconsistently applied References: <63b8d6c654874680b1ed000e4dddab78@RSCEXDB01.leesar.com> Message-ID: Apologies if I'm missing something fundamental. My basic interest: Change the text of the terms and conditions presented when someone picks up files to something other than the "instructions" on how to change this text. The existing text, in ALL languages, is generic instructions on how to change the text, therefore (as I understand it) I'm recommended to change the translation of this text in EVERY language (if I don't want someone selecting a language at random to see *instructions*, but rather at least some attempt at a real disclaimer). So far, I've changed the translation in the .po files for en_US, en_UK, es_ES, and it_IT. I'll use Google translate for those that I'm confident will be reasonably close, or that I could get a friend/colleague to validate. I believe, for others that I cannot readily verify the quality of Google translate, I will simply use the English text again. However, on making these changes so far, compiling the languages, and restarting Apache, I find that my translations are not reliably presented. Sometimes the default "instructions" text is presented. In fact, I can readily reproduce a scenario in which, when viewing the Drop-Off Summary page, when switching between two languages (en_US and en_UK), I am sometimes presented the default (instructions text) and sometimes presented my "translated" disclaimer text, seemingly at random. What have I failed to do? Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived. -------------- next part -------------- An HTML attachment was scrubbed... URL: From KLE at msktd.com Thu Jan 27 18:30:49 2022 From: KLE at msktd.com (Ken Etter) Date: Thu, 27 Jan 2022 18:30:49 +0000 Subject: [ZendTo] Translations inconsistently applied In-Reply-To: References: <63b8d6c654874680b1ed000e4dddab78@RSCEXDB01.leesar.com> Message-ID: One thought?not sure if this is still applicable or not, so take backups/precautions prior to doing it. At one point, there was a cache of files that caused me similar issues (not seeing what I expected to see). Jules had me delete all php files in /var/zendto/templates_c/. These would auto-regenerate as needed. Take a backup and then remove them and see if it solves it. Ken From: ZendTo On Behalf Of Bryan Jones via ZendTo Sent: Thursday, January 27, 2022 12:37 PM To: zendto at zend.to Cc: Bryan Jones Subject: [ZendTo] Translations inconsistently applied Apologies if I?m missing something fundamental. My basic interest: Change the text of the terms and conditions presented when someone picks up files to something other than the ?instructions? on how to change this text. The existing text, in ALL languages, is generic instructions on how to change the text, therefore (as I understand it) I?m recommended to change the translation of this text in EVERY language (if I don?t want someone selecting a language at random to see *instructions*, but rather at least some attempt at a real disclaimer). So far, I?ve changed the translation in the .po files for en_US, en_UK, es_ES, and it_IT. I?ll use Google translate for those that I?m confident will be reasonably close, or that I could get a friend/colleague to validate. I believe, for others that I cannot readily verify the quality of Google translate, I will simply use the English text again. However, on making these changes so far, compiling the languages, and restarting Apache, I find that my translations are not reliably presented. Sometimes the default ?instructions? text is presented. In fact, I can readily reproduce a scenario in which, when viewing the Drop-Off Summary page, when switching between two languages (en_US and en_UK), I am sometimes presented the default (instructions text) and sometimes presented my ?translated? disclaimer text, seemingly at random. What have I failed to do? Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan.Jones at leesar.com Thu Jan 27 19:05:01 2022 From: Bryan.Jones at leesar.com (Bryan Jones) Date: Thu, 27 Jan 2022 19:05:01 +0000 Subject: [ZendTo] Translations inconsistently applied In-Reply-To: References: <63b8d6c654874680b1ed000e4dddab78@RSCEXDB01.leesar.com> <42dd0b9cdaeb4dceaa8ecea8f9463a3c@RSCEXDB01.leesar.com> Message-ID: Thank you for the suggestion, Ken. Made a backup, removed those files, restarted apache, but I still get the same behavior. -- Bryan Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived. -------------- next part -------------- An HTML attachment was scrubbed... URL: From m.v.sangster at abdn.ac.uk Fri Jan 28 09:01:19 2022 From: m.v.sangster at abdn.ac.uk (Sangster, Mark) Date: Fri, 28 Jan 2022 09:01:19 +0000 Subject: [ZendTo] Translations inconsistently applied In-Reply-To: References: <63b8d6c654874680b1ed000e4dddab78@RSCEXDB01.leesar.com> Message-ID: The locale for UK should be en_GB. Mark From: ZendTo On Behalf Of Bryan Jones via ZendTo Sent: 27 January 2022 17:37 To: zendto at zend.to Cc: Bryan Jones Subject: [ZendTo] Translations inconsistently applied CAUTION: External email. Ensure this message is from a trusted source before clicking links/attachments. Apologies if I?m missing something fundamental. My basic interest: Change the text of the terms and conditions presented when someone picks up files to something other than the ?instructions? on how to change this text. The existing text, in ALL languages, is generic instructions on how to change the text, therefore (as I understand it) I?m recommended to change the translation of this text in EVERY language (if I don?t want someone selecting a language at random to see *instructions*, but rather at least some attempt at a real disclaimer). So far, I?ve changed the translation in the .po files for en_US, en_UK, es_ES, and it_IT. I?ll use Google translate for those that I?m confident will be reasonably close, or that I could get a friend/colleague to validate. I believe, for others that I cannot readily verify the quality of Google translate, I will simply use the English text again. However, on making these changes so far, compiling the languages, and restarting Apache, I find that my translations are not reliably presented. Sometimes the default ?instructions? text is presented. In fact, I can readily reproduce a scenario in which, when viewing the Drop-Off Summary page, when switching between two languages (en_US and en_UK), I am sometimes presented the default (instructions text) and sometimes presented my ?translated? disclaimer text, seemingly at random. What have I failed to do? Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived. The University of Aberdeen is a charity registered in Scotland, No SC013683. Tha Oilthigh Obar Dheathain na charthannas cl?raichte ann an Alba, ?ir. SC013683. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Fri Jan 28 09:40:09 2022 From: Jules at Zend.To (Jules) Date: Fri, 28 Jan 2022 09:40:09 +0000 Subject: [ZendTo] Translations inconsistently applied In-Reply-To: References: <63b8d6c654874680b1ed000e4dddab78@RSCEXDB01.leesar.com> Message-ID: <2ce02c1e-8f74-ce3b-08eb-ac5823ee8744@Zend.To> Hi Bryan, Were the files you changed the zendto.po file in each of the /opt/zendto/locale//insert-language-here//LC_MESSAGES/ directories? Remember that you don't need to provide support for all the languages. There's the list of supported languages in preferences.php, you can shorten that list to remove the ones you aren't particularly interested in supporting. Did you compile the languages by running "sudo /opt/zendto/bin/makelanguages"? If you happen to be using php-fpm, ensure you restart that service too. Also, try it in a different browser or a private/incognito window or clear your browser cache, just in case you're actually just seeing web browser caching problems. Let me know what happens. Cheers, Jules. On 27/01/2022 17:37, Bryan Jones via ZendTo wrote: > > Apologies if I?m missing something fundamental. > > My basic interest: Change the text of the terms and conditions > presented when someone picks up files to something other than the > ?instructions? on how to change this text. > > The existing text, in ALL languages, is generic instructions on how to > change the text, therefore (as I understand it) I?m recommended to > change the translation of this text in EVERY language (if I don?t want > someone selecting a language at random to see **instructions**, but > rather at least some attempt at a real disclaimer). > > So far, I?ve changed the translation in the .po files for en_US, > en_UK, es_ES, and it_IT. I?ll use Google translate for those that I?m > confident will be reasonably close, or that I could get a > friend/colleague to validate. I believe, for others that I cannot > readily verify the quality of Google translate, I will simply use the > English text again. > > However, on making these changes so far, compiling the languages, and > restarting Apache, I find that my translations are not reliably > presented. Sometimes the default ?instructions? text is presented. > > In fact, I can readily reproduce a scenario in which, when viewing the > Drop-Off Summary page, when switching between two languages (en_US and > en_UK), I am sometimes presented the default (instructions text) and > sometimes presented my ?translated? disclaimer text, seemingly at random. > > What have I failed to do? > > > > *Disclaimer* > > The information contained in this communication from the sender is > confidential. It is intended solely for use by the recipient and > others authorized to receive it. If you are not the recipient, you are > hereby notified that any disclosure, copying, distribution or taking > action in relation of the contents of this information is strictly > prohibited and may be unlawful. > > This email has been scanned for viruses and malware, and may have been > automatically archived. > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'They went with songs to the battle, they were young. Straight of limb, true of eye, steady and aglow. They were staunch to the end against odds uncounted, They fell with their faces to the foe. They shall grow not old, as we that are left grow old: Age shall not weary them, nor the years condemn. At the going down of the sun and in the morning, We will remember them. They mingle not with their laughing comrades again; They sit no more at familiar tables of home; They have no lot in our labour of the day-time; They sleep beyond England's foam.' - Ode of Remembrance, Laurence Binyon www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan.Jones at leesar.com Fri Jan 28 14:40:30 2022 From: Bryan.Jones at leesar.com (Bryan Jones) Date: Fri, 28 Jan 2022 14:40:30 +0000 Subject: [ZendTo] Translations inconsistently applied In-Reply-To: References: <63b8d6c654874680b1ed000e4dddab78@RSCEXDB01.leesar.com> <2ce02c1e-8f74-ce3b-08eb-ac5823ee8744@Zend.To> <69eabcad03984369b8bfa95f016cc82f@RSCEXDB01.leesar.com> Message-ID: @Jules ? Yes, changd the zendto.po files in (so far) en_US, en_GB, it_IT, and es_ES. I didn?t think about cutting down the language support list in preferences.php ? thank you for that suggestion! Yes, compiled by executing /opt/zendto/bin/makelanguages and observed the date/time on the associated zendto.mo files update as this was done. I will try some incognito and/or cache clearing, just to be sure. @Mark ? I?m sorry, I didn?t see your previous message. You are correct, I mistyped, the language *folder* is named en_GB. However, in the UI, the language appears as ?English (UK)?, so I typed the wrong thing. -- Bryan From: Jules Sent: Friday, January 28, 2022 4:40 AM To: ZendTo Users Cc: Bryan Jones Subject: Re: [ZendTo] Translations inconsistently applied This message was not sent from a LeeSar/CSF associate email address. Do not open attachments or links from unknown senders. Hi Bryan, Were the files you changed the zendto.po file in each of the /opt/zendto/locale/insert-language-here/LC_MESSAGES/ directories? Remember that you don't need to provide support for all the languages. There's the list of supported languages in preferences.php, you can shorten that list to remove the ones you aren't particularly interested in supporting. Did you compile the languages by running "sudo /opt/zendto/bin/makelanguages"? If you happen to be using php-fpm, ensure you restart that service too. Also, try it in a different browser or a private/incognito window or clear your browser cache, just in case you're actually just seeing web browser caching problems. Let me know what happens. Cheers, Jules. On 27/01/2022 17:37, Bryan Jones via ZendTo wrote: Apologies if I?m missing something fundamental. My basic interest: Change the text of the terms and conditions presented when someone picks up files to something other than the ?instructions? on how to change this text. The existing text, in ALL languages, is generic instructions on how to change the text, therefore (as I understand it) I?m recommended to change the translation of this text in EVERY language (if I don?t want someone selecting a language at random to see *instructions*, but rather at least some attempt at a real disclaimer). So far, I?ve changed the translation in the .po files for en_US, en_UK, es_ES, and it_IT. I?ll use Google translate for those that I?m confident will be reasonably close, or that I could get a friend/colleague to validate. I believe, for others that I cannot readily verify the quality of Google translate, I will simply use the English text again. However, on making these changes so far, compiling the languages, and restarting Apache, I find that my translations are not reliably presented. Sometimes the default ?instructions? text is presented. In fact, I can readily reproduce a scenario in which, when viewing the Drop-Off Summary page, when switching between two languages (en_US and en_UK), I am sometimes presented the default (instructions text) and sometimes presented my ?translated? disclaimer text, seemingly at random. What have I failed to do? Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived. _______________________________________________ ZendTo mailing list ZendTo at zend.to http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'They went with songs to the battle, they were young. Straight of limb, true of eye, steady and aglow. They were staunch to the end against odds uncounted, They fell with their faces to the foe. They shall grow not old, as we that are left grow old: Age shall not weary them, nor the years condemn. At the going down of the sun and in the morning, We will remember them. They mingle not with their laughing comrades again; They sit no more at familiar tables of home; They have no lot in our labour of the day-time; They sleep beyond England's foam.' - Ode of Remembrance, Laurence Binyon www.Zend.To Twitter: @JulesFM Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived. -------------- next part -------------- An HTML attachment was scrubbed... URL: