From miguel at uhtasi.org  Thu Mar  7 00:57:48 2019
From: miguel at uhtasi.org (Miguel Brostrom)
Date: Wed, 6 Mar 2019 14:57:48 -1000 (HST)
Subject: [ZendTo] Installer issue using RHEL7 - wrong PHP version
References: <037601d4d480$f251b350$d6f519f0$@uhtasi.org>
Message-ID: <WM!2cbf4c930ab04427b29f30172236847f1ee6403b2f792c20352dffd535bb4fa68edeb9228364b16dc511cbedc71a195c!@mx.jul.es>

Hi all,

 

Being a relatively new hire I've been tasked with updated our older RHEL 6
systems to RHEL 7. I've recently come to our ZendTo server and realized it
was time for a fresh install and noticed there was installer over on the
ZendTo website. The installer said 
Good, you are on CentOS or RedHat 6 or later, so PHP 7 is available
ready-built. 
Adding the IUS repo.

 

The repo begins to install but never get's installed and gives the error:
Public key for ius-release.rpm is not installed

error: /etc/pki/rpm-gpg/IUS-COMMUNITY-GPG-KEY: import read failed(2).

 

The installer then proceeds "I am going to install the latest PHP I can
find, which is php."

 

It then installs php.x86_64 0:5.4.16-46.el7, which is not PHP 7 or higher
and does not contain the sodium module that is required.

 

The installer keeps going through the end. After the reboot I'm asked to
go the website's homepage, which turns out to be the Apache test page.

 

Any ideas on where to go from here? I was asked to keep the OS RHEL7.

 

Thanks in advance for any help,

 

Miguel  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190306/cbb3c8c9/attachment.html>

From djones at ena.com  Thu Mar  7 01:14:49 2019
From: djones at ena.com (David Jones)
Date: Thu, 7 Mar 2019 01:14:49 +0000
Subject: [ZendTo] Installer issue using RHEL7 - wrong PHP version
In-Reply-To: <WM!b2310105620e0dd7c5fcd2d236f53907203ccc89eba50770c1049d7078fd32c04eb4e5e6f1e2ef6d6e4d595d37dbb8b632e4aadd13e78aa3fd690a978faaae54!@mx.jul.es>
References: <037601d4d480$f251b350$d6f519f0$@uhtasi.org>
 <WM!2cbf4c930ab04427b29f30172236847f1ee6403b2f792c20352dffd535bb4fa68edeb9228364b16dc511cbedc71a195c!@mx.jul.es>,
 <WM!b2310105620e0dd7c5fcd2d236f53907203ccc89eba50770c1049d7078fd32c04eb4e5e6f1e2ef6d6e4d595d37dbb8b632e4aadd13e78aa3fd690a978faaae54!@mx.jul.es>
 <DM5PR19MB1050CE6ABF9CBA71188A87CBC64C0@DM5PR19MB1050.namprd19.prod.outlook.com>
Message-ID: <WM!a7523bd2260766d935c61f22c3007c08188affdbb303b17913fb76d7d94cfd2490d8c3539959db64066926554319655f!@mx.jul.es>

Are you running real RHEL7?  If you are running a RHEL variant like CentOS 7 then it's a bit easier.  Real RHEL7 has a few extra steps like installing the EPEL repo first:  https://ius.io/GettingStarted/

Get the IUS repo installed manually and run "yum list" to see if there are any errors then Google from there.

When I run "yum list | grep php7" on CentOS 7, I get a long list of packages.  I bet if you can get this sorted then the installer would work fine.

Dave

________________________________
From: ZendTo <zendto-bounces at zend.to> on behalf of Miguel Brostrom via ZendTo <zendto at zend.to>
Sent: Wednesday, March 6, 2019 6:57 PM
To: zendto at zend.to
Cc: Miguel Brostrom
Subject: [ZendTo] Installer issue using RHEL7 - wrong PHP version


Hi all,



Being a relatively new hire I?ve been tasked with updated our older RHEL 6 systems to RHEL 7. I?ve recently come to our ZendTo server and realized it was time for a fresh install and noticed there was installer over on the ZendTo website. The installer said
Good, you are on CentOS or RedHat 6 or later, so PHP 7 is available ready-built.
Adding the IUS repo.



The repo begins to install but never get?s installed and gives the error: Public key for ius-release.rpm is not installed

error: /etc/pki/rpm-gpg/IUS-COMMUNITY-GPG-KEY: import read failed(2).



The installer then proceeds ?I am going to install the latest PHP I can find, which is php.?



It then installs php.x86_64 0:5.4.16-46.el7, which is not PHP 7 or higher and does not contain the sodium module that is required.



The installer keeps going through the end. After the reboot I?m asked to go the website?s homepage, which turns out to be the Apache test page.



Any ideas on where to go from here? I was asked to keep the OS RHEL7.



Thanks in advance for any help,



Miguel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190307/be7ff5d9/attachment-0001.html>

From Jules at Zend.To  Thu Mar  7 12:43:17 2019
From: Jules at Zend.To (Jules Field)
Date: Thu, 7 Mar 2019 12:43:17 +0000
Subject: [ZendTo] Installer issue using RHEL7 - wrong PHP version
In-Reply-To: <WM!2cbf4c930ab04427b29f30172236847f1ee6403b2f792c20352dffd535bb4fa68edeb9228364b16dc511cbedc71a195c!@mx.jul.es>
References: <037601d4d480$f251b350$d6f519f0$@uhtasi.org>
 <WM!2cbf4c930ab04427b29f30172236847f1ee6403b2f792c20352dffd535bb4fa68edeb9228364b16dc511cbedc71a195c!@mx.jul.es>
Message-ID: <f367f007-d312-c04c-04e0-06c979373f71@Zend.To>

Miguel,

On 07/03/2019 00:57, Miguel Brostrom via ZendTo wrote:
>
> Hi all,
>
> Being a relatively new hire I?ve been tasked with updated our older 
> RHEL 6 systems to RHEL 7. I?ve recently come to our ZendTo server and 
> realized it was time for a fresh install and noticed there was 
> installer over on the ZendTo website. The installer said
> Good, you are on CentOS or RedHat 6 or later, so PHP 7 is available 
> ready-built.
> Adding the IUS repo.
>
> The repo begins to install but never get?s installed and gives the 
> error: Public key for ius-release.rpm is not installed
>
> error: /etc/pki/rpm-gpg/IUS-COMMUNITY-GPG-KEY: import read failed(2).
>
Something went wrong with the signing key for the IUS repo.

The Installer knows about the differences between RHEL7 and CentOS 7 and 
will cope with both. We use RHEL at my day-job at the University of 
Southampton, which gives me access to all of the genuine RHEL resources.

If you can manually enable the IUS repo (Google it) and then re-run the 
Installer, it should sort it all out for you. It will spot the old 
version of PHP you've now got installed, uninstall it, then install the 
right one.

Cheers,
Jules.
>
> The installer then proceeds ?I am going to install the latest PHP I 
> can find, which is php.?
>
> It then installs php.x86_64 0:5.4.16-46.el7, which is not PHP 7 or 
> higher and does not contain the sodium module that is required.
>
> The installer keeps going through the end. After the reboot I?m asked 
> to go the website?s homepage, which turns out to be the Apache test page.
>
> Any ideas on where to go from here? I was asked to keep the OS RHEL7.
>
> Thanks in advance for any help,
>
> Miguel
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Split apart, reunited, or adjusting for new conditions on the
  ground, a family is a double-edged sword. They're the best of times,
  the worst of times, your keys to the kingdom and the skeletons in
  your closet. If only we didn't have to eat dinner with them.'
  -- Mary, "In Plain Sight"

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190307/f213663b/attachment.html>

From mrm at medicine.wisc.edu  Fri Mar  8 21:11:27 2019
From: mrm at medicine.wisc.edu (MICHAEL R MASSE)
Date: Fri, 8 Mar 2019 21:11:27 +0000
Subject: [ZendTo] authLDAPEmailAttr instead of internaldomains.conf
References: <0b535a6c-40c3-1fc1-d024-ac7f52ba29ae@medicine.wisc.edu>
Message-ID: <WM!eedb26cd0a9a1a17807ab6ecd43e765d67784fc33b79f13815847a3e58465940567382cd1689a16a96e3f6f83139835a!@mx.jul.es>

I currently have a working system which utilizes internaldomains.conf to 
restrict outside users from sending to any domain except ones our users 
use.??? The problem is that some of those email domains listed have 
users we do not manage, and therefore those users should not be capable 
of receiving an email from Zendto from an outside user.??? My 
understanding is that if a domain is included in internaldomains.conf, 
then any email address which matches is capable of receiving said 
email.??? I also utilize ldap for user authentication.??? Each user in 
my ldap directory has their correct email address which could be made up 
of a number of different domains.??? Is it possible for Zendto to check 
for specific valid recipient email addresses by utilizing 
authLDAPEmailAttr instead of the very broad and general 
internaldomains.conf?




From Jules at Zend.To  Mon Mar 11 09:07:41 2019
From: Jules at Zend.To (Jules Field)
Date: Mon, 11 Mar 2019 09:07:41 +0000
Subject: [ZendTo] authLDAPEmailAttr instead of internaldomains.conf
In-Reply-To: <WM!eedb26cd0a9a1a17807ab6ecd43e765d67784fc33b79f13815847a3e58465940567382cd1689a16a96e3f6f83139835a!@mx.jul.es>
References: <0b535a6c-40c3-1fc1-d024-ac7f52ba29ae@medicine.wisc.edu>
 <WM!eedb26cd0a9a1a17807ab6ecd43e765d67784fc33b79f13815847a3e58465940567382cd1689a16a96e3f6f83139835a!@mx.jul.es>
Message-ID: <246d9a19-0310-3000-a4a2-eb49da535e72@Zend.To>

Michael,

Do your users have several different email addresses? Here we have 
multiple ones that work, e.g. among others I have
jkf at soton.....
jkf at southampton...
jkf at ecs.soton.....
J.K.Field at soton.....
J.K.Field at southampton.....

and so on.

What appears in your authLDAPEmailAttr attribute?
It's all very well sending an email to the contents of that attribute, 
but is there enough information there to be able to prove the user 
should be allowed / denied sending a drop-off to some other address?

If all I have is *an* email address of an internal recipient, can I 
guarantee being able to find that in the authLDAPEmailAttr attribute of 
your LDAP?

Cheers,
Jules.

On 08/03/2019 21:11, MICHAEL R MASSE via ZendTo wrote:
> I currently have a working system which utilizes internaldomains.conf to
> restrict outside users from sending to any domain except ones our users
> use.??? The problem is that some of those email domains listed have
> users we do not manage, and therefore those users should not be capable
> of receiving an email from Zendto from an outside user.??? My
> understanding is that if a domain is included in internaldomains.conf,
> then any email address which matches is capable of receiving said
> email.??? I also utilize ldap for user authentication.??? Each user in
> my ldap directory has their correct email address which could be made up
> of a number of different domains.??? Is it possible for Zendto to check
> for specific valid recipient email addresses by utilizing
> authLDAPEmailAttr instead of the very broad and general
> internaldomains.conf?
>
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

The current UK shipping forecast:
Viking, North Utsire, South Utsire, Northeast Forties: Cyclonic, mainly
westerly, 5 to 7, backing southerly 7 to severe gale 9 later. Moderate or
rough, occasionally very rough later. Showers, rain later. Good, occasionally
poor.

www.Zend.To
Twitter: @JulesFM



From mrm at medicine.wisc.edu  Mon Mar 11 16:20:27 2019
From: mrm at medicine.wisc.edu (MICHAEL R MASSE)
Date: Mon, 11 Mar 2019 16:20:27 +0000
Subject: [ZendTo] authLDAPEmailAttr instead of internaldomains.conf
In-Reply-To: <WM!83bf94c94c0a6a0bbfea6fbb19e8cfcff86f5336892215ca6d7639de8ec91949b0d288fe07be7458edf4cddcfcee66399cf549017e1c81f4f526eb206b0e7500!@mx.jul.es>
References: <0b535a6c-40c3-1fc1-d024-ac7f52ba29ae@medicine.wisc.edu>
 <WM!eedb26cd0a9a1a17807ab6ecd43e765d67784fc33b79f13815847a3e58465940567382cd1689a16a96e3f6f83139835a!@mx.jul.es>
 <246d9a19-0310-3000-a4a2-eb49da535e72@Zend.To>
 <WM!83bf94c94c0a6a0bbfea6fbb19e8cfcff86f5336892215ca6d7639de8ec91949b0d288fe07be7458edf4cddcfcee66399cf549017e1c81f4f526eb206b0e7500!@mx.jul.es>
 <MWHPR06MB3455CBB6A4AE2F24298F158EF6480@MWHPR06MB3455.namprd06.prod.outlook.com>
Message-ID: <WM!ca108779ae496288621ea96e7d845b1d203efffe97e17c847b87270e79d443a258158e51d66b6b476f4a95371b9aa955!@mx.jul.es>

We have users that use our own internal email domains and using the internaldomains.conf file works well for those cases, but I also have users that do not use our email domains and use something like gmail.com and I would really rather not add gmail.com to our internaldomains.conf file.     We consider our authLDAPEmailAttr as definitive, so it contains the user's correct email address regardless of whether it is an internal or external email domain.    So essentially, if a lookup of authLDAPEmailAttr finds a match, then they are an internal user.    I'm not so worried about sending, because legitimate users can always just log in to Zendto, but if I have a gmail email user, they cannot receive from an outside user unless I add gmail.com to internaldomains.conf.     That does bring up a question though.   Does internaldomains.conf allow you to specify individual email addresses?   Could I specify userabc at gmail.com in internaldomains.conf without having to allow every other gmail.com automatically?

Mike



-----Original Message-----
From: Jules Field <Jules at Zend.To> 
Sent: Monday, March 11, 2019 4:08 AM
To: ZendTo Users <zendto at zend.to>
Cc: MICHAEL R MASSE <mrm at medicine.wisc.edu>
Subject: Re: [ZendTo] authLDAPEmailAttr instead of internaldomains.conf

Michael,

Do your users have several different email addresses? Here we have multiple ones that work, e.g. among others I have jkf at soton.....
jkf at southampton...
jkf at ecs.soton.....
J.K.Field at soton.....
J.K.Field at southampton.....

and so on.




What appears in your authLDAPEmailAttr attribute?
It's all very well sending an email to the contents of that attribute, but is there enough information there to be able to prove the user should be allowed / denied sending a drop-off to some other address?

If all I have is *an* email address of an internal recipient, can I guarantee being able to find that in the authLDAPEmailAttr attribute of your LDAP?

Cheers,
Jules.

On 08/03/2019 21:11, MICHAEL R MASSE via ZendTo wrote:
> I currently have a working system which utilizes internaldomains.conf 
> to restrict outside users from sending to any domain except ones our 
> users use.??? The problem is that some of those email domains listed 
> have users we do not manage, and therefore those users should not be 
> capable of receiving an email from Zendto from an outside user.??? My 
> understanding is that if a domain is included in internaldomains.conf, 
> then any email address which matches is capable of receiving said 
> email.??? I also utilize ldap for user authentication.??? Each user in 
> my ldap directory has their correct email address which could be made 
> up of a number of different domains.??? Is it possible for Zendto to 
> check for specific valid recipient email addresses by utilizing 
> authLDAPEmailAttr instead of the very broad and general 
> internaldomains.conf?
>
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

--
Julian Field MEng CEng CITP MBCS MIEEE MACM

The current UK shipping forecast:
Viking, North Utsire, South Utsire, Northeast Forties: Cyclonic, mainly westerly, 5 to 7, backing southerly 7 to severe gale 9 later. Moderate or rough, occasionally very rough later. Showers, rain later. Good, occasionally poor.

www.Zend.To
Twitter: @JulesFM


From Jules at Zend.To  Mon Mar 11 17:12:43 2019
From: Jules at Zend.To (Jules Field)
Date: Mon, 11 Mar 2019 17:12:43 +0000
Subject: [ZendTo] authLDAPEmailAttr instead of internaldomains.conf
In-Reply-To: <WM!ca108779ae496288621ea96e7d845b1d203efffe97e17c847b87270e79d443a258158e51d66b6b476f4a95371b9aa955!@mx.jul.es>
References: <0b535a6c-40c3-1fc1-d024-ac7f52ba29ae@medicine.wisc.edu>
 <WM!eedb26cd0a9a1a17807ab6ecd43e765d67784fc33b79f13815847a3e58465940567382cd1689a16a96e3f6f83139835a!@mx.jul.es>
 <246d9a19-0310-3000-a4a2-eb49da535e72@Zend.To>
 <WM!83bf94c94c0a6a0bbfea6fbb19e8cfcff86f5336892215ca6d7639de8ec91949b0d288fe07be7458edf4cddcfcee66399cf549017e1c81f4f526eb206b0e7500!@mx.jul.es>
 <MWHPR06MB3455CBB6A4AE2F24298F158EF6480@MWHPR06MB3455.namprd06.prod.outlook.com>
 <WM!ca108779ae496288621ea96e7d845b1d203efffe97e17c847b87270e79d443a258158e51d66b6b476f4a95371b9aa955!@mx.jul.es>
Message-ID: <93168948-9161-f348-a4bb-6b0e38da252d@Zend.To>

Michael,

Currently you can't put userabc at gmail.com in internaldomains.conf, but 
it would be a pretty easy change to allow that.
How many of this type of user do you have?
Are you really happy to have to maintain that list in 
internaldomains.conf by hand?
(Or by a little script that you write yourself?)

Otherwise I'll need to extend the authenticator so it can look for an 
email address and return true/false on whether it finds it via the 
authentication system. It would call that if the check in 
internaldomains.conf failed to find a matching domain.

Cheers,
Jules.

On 11/03/2019 16:20, MICHAEL R MASSE via ZendTo wrote:
> We have users that use our own internal email domains and using the internaldomains.conf file works well for those cases, but I also have users that do not use our email domains and use something like gmail.com and I would really rather not add gmail.com to our internaldomains.conf file.     We consider our authLDAPEmailAttr as definitive, so it contains the user's correct email address regardless of whether it is an internal or external email domain.    So essentially, if a lookup of authLDAPEmailAttr finds a match, then they are an internal user.    I'm not so worried about sending, because legitimate users can always just log in to Zendto, but if I have a gmail email user, they cannot receive from an outside user unless I add gmail.com to internaldomains.conf.     That does bring up a question though.   Does internaldomains.conf allow you to specify individual email addresses?   Could I specify userabc at gmail.com in internaldomains.conf without having to allow every other gmail.com automatically?
>
> Mike
>
>
>
> -----Original Message-----
> From: Jules Field <Jules at Zend.To>
> Sent: Monday, March 11, 2019 4:08 AM
> To: ZendTo Users <zendto at zend.to>
> Cc: MICHAEL R MASSE <mrm at medicine.wisc.edu>
> Subject: Re: [ZendTo] authLDAPEmailAttr instead of internaldomains.conf
>
> Michael,
>
> Do your users have several different email addresses? Here we have multiple ones that work, e.g. among others I have jkf at soton.....
> jkf at southampton...
> jkf at ecs.soton.....
> J.K.Field at soton.....
> J.K.Field at southampton.....
>
> and so on.
>
>
>
>
> What appears in your authLDAPEmailAttr attribute?
> It's all very well sending an email to the contents of that attribute, but is there enough information there to be able to prove the user should be allowed / denied sending a drop-off to some other address?
>
> If all I have is *an* email address of an internal recipient, can I guarantee being able to find that in the authLDAPEmailAttr attribute of your LDAP?
>
> Cheers,
> Jules.
>
> On 08/03/2019 21:11, MICHAEL R MASSE via ZendTo wrote:
>> I currently have a working system which utilizes internaldomains.conf
>> to restrict outside users from sending to any domain except ones our
>> users use.??? The problem is that some of those email domains listed
>> have users we do not manage, and therefore those users should not be
>> capable of receiving an email from Zendto from an outside user.??? My
>> understanding is that if a domain is included in internaldomains.conf,
>> then any email address which matches is capable of receiving said
>> email.??? I also utilize ldap for user authentication.??? Each user in
>> my ldap directory has their correct email address which could be made
>> up of a number of different domains.??? Is it possible for Zendto to
>> check for specific valid recipient email addresses by utilizing
>> authLDAPEmailAttr instead of the very broad and general
>> internaldomains.conf?
>>
>>
>>
>> _______________________________________________
>> ZendTo mailing list
>> ZendTo at zend.to
>> http://jul.es/mailman/listinfo/zendto
> Jules
>
> --
> Julian Field MEng CEng CITP MBCS MIEEE MACM
>
> The current UK shipping forecast:
> Viking, North Utsire, South Utsire, Northeast Forties: Cyclonic, mainly westerly, 5 to 7, backing southerly 7 to severe gale 9 later. Moderate or rough, occasionally very rough later. Showers, rain later. Good, occasionally poor.
>
> www.Zend.To
> Twitter: @JulesFM
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

The current UK shipping forecast:
Sole, Lundy, Fastnet: Southwest veering west 7 to severe gale 9. Very rough,
occasionally high. Rain then showers. Good occasionally poor.

www.Zend.To
Twitter: @JulesFM




From mrm at medicine.wisc.edu  Mon Mar 11 18:54:59 2019
From: mrm at medicine.wisc.edu (MICHAEL R MASSE)
Date: Mon, 11 Mar 2019 18:54:59 +0000
Subject: [ZendTo] authLDAPEmailAttr instead of internaldomains.conf
In-Reply-To: <WM!86e45809fffb9f1ee6175b40d416ef72dafb7990fd7a55f0c1340d6c45c6d806e87b4caabe22d3d473dd00578a9bb3cb95d0301d90843c98a88e055fb21b5c87!@mx.jul.es>
References: <0b535a6c-40c3-1fc1-d024-ac7f52ba29ae@medicine.wisc.edu>
 <WM!eedb26cd0a9a1a17807ab6ecd43e765d67784fc33b79f13815847a3e58465940567382cd1689a16a96e3f6f83139835a!@mx.jul.es>
 <246d9a19-0310-3000-a4a2-eb49da535e72@Zend.To>
 <WM!83bf94c94c0a6a0bbfea6fbb19e8cfcff86f5336892215ca6d7639de8ec91949b0d288fe07be7458edf4cddcfcee66399cf549017e1c81f4f526eb206b0e7500!@mx.jul.es>
 <MWHPR06MB3455CBB6A4AE2F24298F158EF6480@MWHPR06MB3455.namprd06.prod.outlook.com>
 <WM!ca108779ae496288621ea96e7d845b1d203efffe97e17c847b87270e79d443a258158e51d66b6b476f4a95371b9aa955!@mx.jul.es>
 <93168948-9161-f348-a4bb-6b0e38da252d@Zend.To>
 <WM!86e45809fffb9f1ee6175b40d416ef72dafb7990fd7a55f0c1340d6c45c6d806e87b4caabe22d3d473dd00578a9bb3cb95d0301d90843c98a88e055fb21b5c87!@mx.jul.es>
 <173b45c8-0a1d-7df2-91b0-2421c63038d9@medicine.wisc.edu>
Message-ID: <WM!2c893238179d55f8538f7904fa231b8e8330ec6a0fcf07393b47d634a82aa3a314012ad77dcbada00e360f010e237c77!@mx.jul.es>

Thanks Jules,

My preference would be to utilize the LDAP authenticator since that 
already has the email addresses in it.?? Maintaining 
internaldomains.conf on an individual email address basis would be a lot 
of work.?? I only mentioned it as a possible way around the issue if you 
weren't willing to incorporate code to utilize LDAP.

-Mike


On 3/11/2019 12:12 PM, Jules Field wrote:
> Michael,
>
> Currently you can't put userabc at gmail.com in internaldomains.conf, but 
> it would be a pretty easy change to allow that.
> How many of this type of user do you have?
> Are you really happy to have to maintain that list in 
> internaldomains.conf by hand?
> (Or by a little script that you write yourself?)
>
> Otherwise I'll need to extend the authenticator so it can look for an 
> email address and return true/false on whether it finds it via the 
> authentication system. It would call that if the check in 
> internaldomains.conf failed to find a matching domain.
>
> Cheers,
> Jules.
>
> On 11/03/2019 16:20, MICHAEL R MASSE via ZendTo wrote:
>> We have users that use our own internal email domains and using the 
>> internaldomains.conf file works well for those cases, but I also have 
>> users that do not use our email domains and use something like 
>> gmail.com and I would really rather not add gmail.com to our 
>> internaldomains.conf file. We consider our authLDAPEmailAttr as 
>> definitive, so it contains the user's correct email address 
>> regardless of whether it is an internal or external email domain.??? 
>> So essentially, if a lookup of authLDAPEmailAttr finds a match, then 
>> they are an internal user.??? I'm not so worried about sending, 
>> because legitimate users can always just log in to Zendto, but if I 
>> have a gmail email user, they cannot receive from an outside user 
>> unless I add gmail.com to internaldomains.conf.???? That does bring 
>> up a question though.?? Does internaldomains.conf allow you to 
>> specify individual email addresses??? Could I specify 
>> userabc at gmail.com in internaldomains.conf without having to allow 
>> every other gmail.com automatically?
>>
>> Mike
>>
>>
>>
>> -----Original Message-----
>> From: Jules Field <Jules at Zend.To>
>> Sent: Monday, March 11, 2019 4:08 AM
>> To: ZendTo Users <zendto at zend.to>
>> Cc: MICHAEL R MASSE <mrm at medicine.wisc.edu>
>> Subject: Re: [ZendTo] authLDAPEmailAttr instead of internaldomains.conf
>>
>> Michael,
>>
>> Do your users have several different email addresses? Here we have 
>> multiple ones that work, e.g. among others I have jkf at soton.....
>> jkf at southampton...
>> jkf at ecs.soton.....
>> J.K.Field at soton.....
>> J.K.Field at southampton.....
>>
>> and so on.
>>
>>
>>
>>
>> What appears in your authLDAPEmailAttr attribute?
>> It's all very well sending an email to the contents of that 
>> attribute, but is there enough information there to be able to prove 
>> the user should be allowed / denied sending a drop-off to some other 
>> address?
>>
>> If all I have is *an* email address of an internal recipient, can I 
>> guarantee being able to find that in the authLDAPEmailAttr attribute 
>> of your LDAP?
>>
>> Cheers,
>> Jules.
>>
>> On 08/03/2019 21:11, MICHAEL R MASSE via ZendTo wrote:
>>> I currently have a working system which utilizes internaldomains.conf
>>> to restrict outside users from sending to any domain except ones our
>>> users use.??? The problem is that some of those email domains listed
>>> have users we do not manage, and therefore those users should not be
>>> capable of receiving an email from Zendto from an outside user.??? My
>>> understanding is that if a domain is included in internaldomains.conf,
>>> then any email address which matches is capable of receiving said
>>> email.??? I also utilize ldap for user authentication.??? Each user in
>>> my ldap directory has their correct email address which could be made
>>> up of a number of different domains.??? Is it possible for Zendto to
>>> check for specific valid recipient email addresses by utilizing
>>> authLDAPEmailAttr instead of the very broad and general
>>> internaldomains.conf?
>>>
>>>
>>>
>>> _______________________________________________
>>> ZendTo mailing list
>>> ZendTo at zend.to
>>> http://jul.es/mailman/listinfo/zendto
>> Jules
>>
>> -- 
>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>
>> The current UK shipping forecast:
>> Viking, North Utsire, South Utsire, Northeast Forties: Cyclonic, 
>> mainly westerly, 5 to 7, backing southerly 7 to severe gale 9 later. 
>> Moderate or rough, occasionally very rough later. Showers, rain 
>> later. Good, occasionally poor.
>>
>> www.Zend.To
>> Twitter: @JulesFM
>>
>> _______________________________________________
>> ZendTo mailing list
>> ZendTo at zend.to
>> http://jul.es/mailman/listinfo/zendto
>
> Jules
>


From tobias.tafart at nextlayer.at  Tue Mar 12 11:11:13 2019
From: tobias.tafart at nextlayer.at (Tobias Tafart)
Date: Tue, 12 Mar 2019 11:11:13 +0000
Subject: [ZendTo] Amount of allowed characters not shown correctly in
 "Request a Dropoff" subject
References: <844440EC3564CA47950E69FB8C968CA47F9CD2@EXCHANGE.intern.nextlayer.at>
Message-ID: <WM!5fe8e2f8b85cf52f73e2b613e60ec056377d2e3a226d2f064d48cc523dac9448c1c5e427b797821ac102d56ef4e183d4!@mx.jul.es>

Hi,

 

We?re running Zendto 5.17-4.

When a user tries to request a dropoff with a subject line longer than the
amount of allowed characters, they get a request error as expected. But the
error does not show the number of allowed characters. Here?s  the output to
the user:

 

> Your subject line to the recipients is characters long. It must be less
than Use the Back button in your browser to go back and fix this error
before trying again.

 

As this happened just the same on a fresh install without customized
configuration on a separate server with a different PHP version, I assume
this is a bug and not a configuration error, but I just want to confirm
here.

 

In the webserver logs there also is a PHP error:

[Tue Mar 12 11:46:35.331412 2019] [php7:notice] [pid 4833] [client
::1:58278] PHP Notice:  Undefined variable: d in /opt/zendto/lib/Req.php on
line 180

 

The problem seems to be that " are used instead of ' for the string, so
sprintf can?t replace the arguments with their contents; if I replace the
apostrophes, it works just fine but I?m not a PHP dev so I don?t know if
that is the best fix...

 

Anyone else facing that problem? Is there a place where I can file a bug
report?

 

Regards,

 

Tobias Tafart
System Engineer 

 <https://www.nextlayer.at/> 

next layer Tele?kommunikations?dienst?leistungs- und Beratungs GmbH
1150 Wien | Mariahilfer G?rtel 37/7
fon: +43 5 1764-894 | fax: +43 5 1764-900 | m: +43 664 2 1764 94
web:  <https://www.nextlayer.at/> www.nextlayer.at


 <https://www.nextlayer.at/twitter> 

 <https://www.nextlayer.at/xing> 

 <https://www.nextlayer.at/linkedin> 

 <https://www.nextlayer.at/facebook> 

FN 257486g | HG Wien

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190312/d9903fba/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3755 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20190312/d9903fba/attachment-0001.p7s>

From Jules at Zend.To  Tue Mar 12 11:37:31 2019
From: Jules at Zend.To (Jules Field)
Date: Tue, 12 Mar 2019 11:37:31 +0000
Subject: [ZendTo] Amount of allowed characters not shown correctly in
 "Request a Dropoff" subject
In-Reply-To: <WM!5fe8e2f8b85cf52f73e2b613e60ec056377d2e3a226d2f064d48cc523dac9448c1c5e427b797821ac102d56ef4e183d4!@mx.jul.es>
References: <844440EC3564CA47950E69FB8C968CA47F9CD2@EXCHANGE.intern.nextlayer.at>
 <WM!5fe8e2f8b85cf52f73e2b613e60ec056377d2e3a226d2f064d48cc523dac9448c1c5e427b797821ac102d56ef4e183d4!@mx.jul.es>
Message-ID: <e6ddc3bb-d1ed-f63d-c8ff-99735daa4bdf@Zend.To>

Tobias,

On 12/03/2019 11:11, Tobias Tafart via ZendTo wrote:
>
> We?re running Zendto 5.17-4.
>
> When a user tries to request a dropoff with a subject line longer than 
> the amount of allowed characters, they get a request error as 
> expected. But the error does not show the number of allowed 
> characters. Here?s ?the output to the user:
>
> > Your subject line to the recipients is characters long. It must be 
> less than Use the Back button in your browser to go back and fix this 
> error before trying again.
>
> As this happened just the same on a fresh install without customized 
> configuration on a separate server with a different PHP version, I 
> assume this is a bug and not a configuration error, but I just want to 
> confirm here.
>
> In the webserver logs there also is a PHP error:
>
> [Tue Mar 12 11:46:35.331412 2019] [php7:notice] [pid 4833] [client 
> ::1:58278] PHP Notice: Undefined variable: d in 
> /opt/zendto/lib/Req.php on line 180
>
> The problem seems to be that " are used instead of ' for the string, 
> so sprintf can?t replace the arguments with their contents; if I 
> replace the apostrophes, it works just fine but I?m not a PHP dev so I 
> don?t know if that is the best fix...
>
Yes, well spotted. Should of course have been single quotes.
>
> Is there a place where I can file a bug report?
>
You just did. :-)
As you have confirmed that the change fixes the problem for you, it will 
be in the next release.

Many thanks for letting me know!

Cheers,

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'I've heard that it's possible to grow up. I've just never met
  anyone who's actually done it.' - Meredith Grey, Grey's Anatomy

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190312/8f15cc17/attachment.html>

From Jules at Zend.To  Wed Mar 13 09:08:17 2019
From: Jules at Zend.To (Jules Field)
Date: Wed, 13 Mar 2019 09:08:17 +0000
Subject: [ZendTo] Ideas wanted: "Forget me" button
Message-ID: <2137f239-68f5-7b4d-f54e-6737a8149d12@Zend.To>

Folks,

I want to add a button somewhere in ZendTo that will clear a user's 
address list, the list of addresses you have sent drop-offs to before. 
The list is used in the "New Drop-off" form to provide the auto-complete 
list when adding a recipient.

It's also a GDPR requirement, as it happens.

So I want some sort of "Delete recipients list" or "Delete address list" 
button.

Which gives me 2 questions I don't know the answer to:

1. Where should the button go in the user interface?
2. What should it say? (I'm assuming some sort of explanatory text by 
it. It's the actual text in the button I'm most interested in)

The obvious answer to (1) is "at the end of the main menu". But is that 
really the best place?
The answer to (2) needs to be very short.

BTW this only affects internal users, i.e. those who can log in.

All ideas most welcome please!

Thanks,

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'I've heard that it's possible to grow up. I've just never met
  anyone who's actually done it.' - Meredith Grey, Grey's Anatomy

www.Zend.To
Twitter: @JulesFM



From zend.to at neilzone.co.uk  Wed Mar 13 09:22:17 2019
From: zend.to at neilzone.co.uk (zend.to at neilzone.co.uk)
Date: Wed, 13 Mar 2019 09:22:17 +0000
Subject: [ZendTo] Ideas wanted: "Forget me" button
In-Reply-To: <WM!99196cbb2c8580778bff45dc54e653ff084124a42b77a896cc820cdb1c675e3d21c377fcdc19063faa45edf1a6aa548f39fba3dce10b8569623d7d61ac0cafb9!@mx.jul.es>
References: <2137f239-68f5-7b4d-f54e-6737a8149d12@Zend.To>
 <WM!99196cbb2c8580778bff45dc54e653ff084124a42b77a896cc820cdb1c675e3d21c377fcdc19063faa45edf1a6aa548f39fba3dce10b8569623d7d61ac0cafb9!@mx.jul.es>
 <E413467B-1B9F-4361-9810-0D19F57AE3B6@neilzone.co.uk>
Message-ID: <WM!84bfd86e3fc1d7802912a101a104ecbaa1c02f3888f00a65dc016c82bb8257e0dbe7bf945d37b15afd5a1eb749de3cb7!@mx.jul.es>



> On 13 Mar 2019, at 09:08, Jules Field via ZendTo <zendto at zend.to> wrote:
> 
> 2. What should it say?


"Forget previous recipients?, perhaps?

Neil



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190313/82776705/attachment.html>

From tobias.tafart at nextlayer.at  Wed Mar 13 10:19:46 2019
From: tobias.tafart at nextlayer.at (Tobias Tafart)
Date: Wed, 13 Mar 2019 10:19:46 +0000
Subject: [ZendTo] Ideas wanted: "Forget me" button
In-Reply-To: <WM!99196cbb2c8580778bff45dc54e653ff084124a42b77a896cc820cdb1c675e3d21c377fcdc19063faa45edf1a6aa548f39fba3dce10b8569623d7d61ac0cafb9!@mx.jul.es>
References: <2137f239-68f5-7b4d-f54e-6737a8149d12@Zend.To>
 <WM!99196cbb2c8580778bff45dc54e653ff084124a42b77a896cc820cdb1c675e3d21c377fcdc19063faa45edf1a6aa548f39fba3dce10b8569623d7d61ac0cafb9!@mx.jul.es>
 <844440EC3564CA47950E69FB8C968CA47F9EB5@EXCHANGE.intern.nextlayer.at>
Message-ID: <WM!2006ed69e41ba2102022f13b06500a9482285d99ebdce167b937e28f05afa736e6df08d13fc5412267e10f9991c67b52!@mx.jul.es>

Hi,

Different Idea: Why not make a separate little "address management" menu,
and additionally to the usual "add contact", "remove contact" and so on -
have a "delete all" button there. 
I've been asked by our users before if there is an option to manage
recipients from the suggestions, so there is a bit of a need for such
functionality. Wasn't hugely important to us though.

Just an idea.

Regards

-----Original Message-----
From: ZendTo <zendto-bounces at zend.to> On Behalf Of Jules Field via ZendTo
Sent: 13 March, 2019 10:08
To: ZendTo Users <zendto at zend.to>
Cc: Jules Field <Jules at zend.to>
Subject: [ZendTo] Ideas wanted: "Forget me" button

Folks,

I want to add a button somewhere in ZendTo that will clear a user's address
list, the list of addresses you have sent drop-offs to before. 
The list is used in the "New Drop-off" form to provide the auto-complete
list when adding a recipient.

It's also a GDPR requirement, as it happens.

So I want some sort of "Delete recipients list" or "Delete address list" 
button.

Which gives me 2 questions I don't know the answer to:

1. Where should the button go in the user interface?
2. What should it say? (I'm assuming some sort of explanatory text by it.
It's the actual text in the button I'm most interested in)

The obvious answer to (1) is "at the end of the main menu". But is that
really the best place?
The answer to (2) needs to be very short.

BTW this only affects internal users, i.e. those who can log in.

All ideas most welcome please!

Thanks,

Jules

--
Julian Field MEng CEng CITP MBCS MIEEE MACM

'I've heard that it's possible to grow up. I've just never met
  anyone who's actually done it.' - Meredith Grey, Grey's Anatomy

www.Zend.To
Twitter: @JulesFM


_______________________________________________
ZendTo mailing list
ZendTo at zend.to
http://jul.es/mailman/listinfo/zendto
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3755 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20190313/0d6b4a15/attachment-0001.p7s>

From mailinglists at pcfreak.de  Wed Mar 13 10:34:53 2019
From: mailinglists at pcfreak.de (Der PCFreak)
Date: Wed, 13 Mar 2019 11:34:53 +0100
Subject: [ZendTo] Ideas wanted: "Forget me" button
In-Reply-To: <WM!97e133e9ddd8d0f4354439d7770be5d6bd12a4f959f5075ff668bca4d7b225050c56204f66257bf0fdb23da074da96be4070b68cf2d1a1172ef80275d05e8f5b!@mx.jul.es>
References: <2137f239-68f5-7b4d-f54e-6737a8149d12@Zend.To>
 <WM!99196cbb2c8580778bff45dc54e653ff084124a42b77a896cc820cdb1c675e3d21c377fcdc19063faa45edf1a6aa548f39fba3dce10b8569623d7d61ac0cafb9!@mx.jul.es>
 <E413467B-1B9F-4361-9810-0D19F57AE3B6@neilzone.co.uk>
 <WM!84bfd86e3fc1d7802912a101a104ecbaa1c02f3888f00a65dc016c82bb8257e0dbe7bf945d37b15afd5a1eb749de3cb7!@mx.jul.es>
 <WM!97e133e9ddd8d0f4354439d7770be5d6bd12a4f959f5075ff668bca4d7b225050c56204f66257bf0fdb23da074da96be4070b68cf2d1a1172ef80275d05e8f5b!@mx.jul.es>
 <2b15951e-e227-0867-7279-fc27949c05fb@pcfreak.de>
Message-ID: <WM!7be4214b99bb8a4e03219173f0e6bed5d588c8390cc0b7b3137cd3493ef2ad3d92b363d3d3b37ffa813d1a466fab0428!@mx.jul.es>

I would say "Clear recipients history" and in german "Empf?ngerhistorie 
l?schen" maybe with a warning in between that says that this is not 
recoverable and will clear ALL previously stored recipients.

On 13.03.2019 10:22, Neil via ZendTo wrote:
>
>
>> On 13 Mar 2019, at 09:08, Jules Field via ZendTo <zendto at zend.to 
>> <mailto:zendto at zend.to>> wrote:
>>
>> 2. What should it say?
>
> "Forget previous recipients?, perhaps?
>
> Neil
>
>
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190313/d6bdfb04/attachment.html>

From Jules at Zend.To  Wed Mar 13 15:12:57 2019
From: Jules at Zend.To (Jules Field)
Date: Wed, 13 Mar 2019 15:12:57 +0000
Subject: [ZendTo] Ideas wanted: "Forget me" button
In-Reply-To: <WM!2006ed69e41ba2102022f13b06500a9482285d99ebdce167b937e28f05afa736e6df08d13fc5412267e10f9991c67b52!@mx.jul.es>
References: <2137f239-68f5-7b4d-f54e-6737a8149d12@Zend.To>
 <WM!99196cbb2c8580778bff45dc54e653ff084124a42b77a896cc820cdb1c675e3d21c377fcdc19063faa45edf1a6aa548f39fba3dce10b8569623d7d61ac0cafb9!@mx.jul.es>
 <844440EC3564CA47950E69FB8C968CA47F9EB5@EXCHANGE.intern.nextlayer.at>
 <WM!2006ed69e41ba2102022f13b06500a9482285d99ebdce167b937e28f05afa736e6df08d13fc5412267e10f9991c67b52!@mx.jul.es>
Message-ID: <46136372-ab52-d093-f328-9e7d127bd464@Zend.To>

Tobias,

I really don't want to write an entire address book editor. It's just 
not worth it.

When a user starts typing a name into the recipients box, the matching 
entries are returned in the order of most-recently-used at the top. So 
entries that they don't want to use again will just sink to the bottom 
as their date of last use gets older and older. Hence no need to remove 
individual entries from it, as you will have to go out of your way to 
use them anyway.

The only functionality I want to add is the ability to clear your entire 
address book, so that people can exercise their "right to be forgotten".

Cheers,
Jules.

On 13/03/2019 10:19, Tobias Tafart via ZendTo wrote:
> Hi,
>
> Different Idea: Why not make a separate little "address management" menu,
> and additionally to the usual "add contact", "remove contact" and so on -
> have a "delete all" button there.
> I've been asked by our users before if there is an option to manage
> recipients from the suggestions, so there is a bit of a need for such
> functionality. Wasn't hugely important to us though.
>
> Just an idea.
>
> Regards
>
> -----Original Message-----
> From: ZendTo <zendto-bounces at zend.to> On Behalf Of Jules Field via ZendTo
> Sent: 13 March, 2019 10:08
> To: ZendTo Users <zendto at zend.to>
> Cc: Jules Field <Jules at zend.to>
> Subject: [ZendTo] Ideas wanted: "Forget me" button
>
> Folks,
>
> I want to add a button somewhere in ZendTo that will clear a user's address
> list, the list of addresses you have sent drop-offs to before.
> The list is used in the "New Drop-off" form to provide the auto-complete
> list when adding a recipient.
>
> It's also a GDPR requirement, as it happens.
>
> So I want some sort of "Delete recipients list" or "Delete address list"
> button.
>
> Which gives me 2 questions I don't know the answer to:
>
> 1. Where should the button go in the user interface?
> 2. What should it say? (I'm assuming some sort of explanatory text by it.
> It's the actual text in the button I'm most interested in)
>
> The obvious answer to (1) is "at the end of the main menu". But is that
> really the best place?
> The answer to (2) needs to be very short.
>
> BTW this only affects internal users, i.e. those who can log in.
>
> All ideas most welcome please!
>
> Thanks,
>
> Jules
>
> --
> Julian Field MEng CEng CITP MBCS MIEEE MACM
>
> 'I've heard that it's possible to grow up. I've just never met
>    anyone who's actually done it.' - Meredith Grey, Grey's Anatomy
>
> www.Zend.To
> Twitter: @JulesFM
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'There is always one moment in childhood when the door opens and
  lets the future in.' - Graham Greene

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190313/0f9e098f/attachment.html>

From ricardo.araujo at modal.com.br  Wed Mar 13 15:18:05 2019
From: ricardo.araujo at modal.com.br (=?iso-8859-1?Q?RICARDO_ARA=DAJO_POPOIRE_WANDERLEY?=)
Date: Wed, 13 Mar 2019 15:18:05 +0000
Subject: [ZendTo] Deny upload files
References: <3937565F9BCD054E940A4DD090B79BBC67000202@MBX01-RJ01.modal.net.br>
Message-ID: <WM!0255a61dd8fd2d5377c79106ab2bd328d7c33bb19dd176185d0d5c3edeebd544fac0c4b6d7f7721f6c28c6df34fd2f3c!@mx.jul.es>

Hi Guys
Is there a way to create an user only with download and request drop-off permissions?
Thanks

[http://www.modal.com.br/emailmkt/marca-assinatura.jpg]<https://modal.com.br/html/index.php>



RICARDO ARAUJO POPOIRE WANDERLEY







Tels. 55 21 3223 7944 | 7700
Cel.  55 21 99477 6779
Fax   55 21 3223 7738










A impress?o consciente gera economia e responsabilidade com o meio ambiente.

Aten??o: Esta comunica??o deve ser lida apenas pelo seu destinat?rio e n?o pode ser retransmitida sem autoriza??o formal. Se esta mensagem tiver sido recebida indevidamente, por favor destrua-a e retire-a de seu computador.
Qualquer reprodu??o, dissemina??o, altera??o, distribui??o e/ou publica??o deste e-mail ? estritamente proibida.  
  
Notice of Confidentiality: This document should only be read by those persons to whom it is addressed and is not intended to be relied upon by any person without subsequent written confirmation of its contents. If you have received this e-mail message in error, please destroy it and delete it from your computer.
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message is strictly prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190313/25b137b9/attachment-0001.html>

From Jules at Zend.To  Wed Mar 13 15:30:48 2019
From: Jules at Zend.To (Jules Field)
Date: Wed, 13 Mar 2019 15:30:48 +0000
Subject: [ZendTo] Deny upload files
In-Reply-To: <WM!0255a61dd8fd2d5377c79106ab2bd328d7c33bb19dd176185d0d5c3edeebd544fac0c4b6d7f7721f6c28c6df34fd2f3c!@mx.jul.es>
References: <3937565F9BCD054E940A4DD090B79BBC67000202@MBX01-RJ01.modal.net.br>
 <WM!0255a61dd8fd2d5377c79106ab2bd328d7c33bb19dd176185d0d5c3edeebd544fac0c4b6d7f7721f6c28c6df34fd2f3c!@mx.jul.es>
Message-ID: <6bd01a68-ef2f-e27c-1875-c3a7f8207011@Zend.To>

No. Internal users can send files too. You can easily stop external 
users from being able to send files completely, but you can't restrict 
an internal user so they can't send a drop-off to someone.

Sorry.

Jules

On 13/03/2019 15:18, RICARDO ARA?JO POPOIRE WANDERLEY via ZendTo wrote:
>
> Hi Guys
>
> Is there a way to create an user only with download and request 
> drop-off permissions?
>
> Thanks
>
> http://www.modal.com.br/emailmkt/marca-assinatura.jpg 
> <https://modal.com.br/html/index.php>
>
> 	
>
> 	
>
> *RICARDO ARAUJO POPOIRE WANDERLEY*
>
>
> 	
>
> 	
>
> 	
>
> Tels.?55?21 3223 7944?|?7700
> Cel.??55?21 99477 6779
> Fax???55?21 3223 7738
>
> 	
>
> 	
>
> 	A impress?o consciente gera economia e responsabilidade com o meio 
> ambiente
>
> Aten??o:Esta comunica??o deve ser lida apenas pelo seu destinat?rio e 
> n?o pode ser retransmitida sem autoriza??o formal. Se esta mensagem 
> tiver sido recebida indevidamente, por favor destrua-a e retire-a de 
> seu computador.
> Qualquer reprodu??o, dissemina??o, altera??o, distribui??o e/ou 
> publica??o deste e-mail ? estritamente proibida.
> Notice of Confidentiality:This document should only be read by those 
> persons to whom it is addressed and is not intended to be relied upon 
> by any person without subsequent written confirmation of its contents. 
> If you have received this e-mail message in error, please destroy it 
> and delete it from your computer.
> Any form of reproduction, dissemination, copying, disclosure, 
> modification, distribution and/or publication of this e-mail message 
> is strictly prohibited.
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'I never saw a wild thing
  Sorry for itself.' - D.H. Lawrence

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190313/66fb68b9/attachment.html>

From Guy.Bertrand at banctec.ca  Wed Mar 13 16:38:40 2019
From: Guy.Bertrand at banctec.ca (Bertrand, Guy)
Date: Wed, 13 Mar 2019 16:38:40 +0000
Subject: [ZendTo] Ideas wanted: "Forget me" button
References: <9E8FF5130DE9CD4D895AF10041C1085B040B000AAC@BTIEXCH04.BTec.ad.banctec.com>
Message-ID: <WM!1c04c3a622dbe66df5148aa28e069a1af6f15239251ac98e291ef4cdae6b14958a8db5f59069c39e04774e13980ea45d!@mx.jul.es>

Hi Jules,

Are you looking to delete all "remembered users" with one button??  Or just to delete one user?  If it deletes all names, it would be an inconvenience to have to re-type all names when needed.

Since you do not want to write an entire address book editor in the s/w, how about just adding an X beside a remembered name?

Example:
When a user starts typing a name into the recipients box, the matching entries are returned in the order of most-recently-used at the top.  As they are displayed, add an field to the right of each name with an X.  To delete just that entry, press the X at the right of the name.  That way, you maintain your existing list, and have deleted just that name, without a full address book editor.

However, I think I need to discuss a caveat.  I'm no expert of the GDPR, but if a user/person requests that their name "be forgotten", doesn't also imply that it is from the whole system, not just one user's cache of names??  Example, if we are 2 users who have sent files to the same external user, and I delete the name from my list, it will still remain in the second user's list.

I need another coffee.

Cheers and keep up the good work!!

Regards,

Guy 

Guy Bertrand, M.Ing
Directeur informatique / IT Manager
EXELA TECHNOLOGIES 
b: +1.514.392.4999 | m: +1.514.265.9754
1155, boulevard Robert-Bourassa, suite 500 | Montr?al (Qu?bec) CANADA H3B 3A7
www.ExelaTech.com | EXELA LinkedIn



From ssilva at sgvwater.com  Wed Mar 13 16:49:02 2019
From: ssilva at sgvwater.com (Scott Silva)
Date: Wed, 13 Mar 2019 16:49:02 +0000
Subject: [ZendTo] Ideas wanted: "Forget me" button
In-Reply-To: <WM!348e35d2401883501b05e992b7b06607c184e6291213190b2cfc5a2c95d3a72a148761a7edcdfff0043a80e8d125dcac4463c52687eca0d5dfab71c27cc573a5!@mx.jul.es>
References: <2137f239-68f5-7b4d-f54e-6737a8149d12@Zend.To>
 <WM!348e35d2401883501b05e992b7b06607c184e6291213190b2cfc5a2c95d3a72a148761a7edcdfff0043a80e8d125dcac4463c52687eca0d5dfab71c27cc573a5!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F42047FD72@FONEXCH01.sgvwc.local>
Message-ID: <WM!a1a53f015ef6b15b6a5b69f3fb3f9fb4e6ac99b0e8092bd330e7f1acd0d842d280106fd1d63231df0c99283089155efb!@mx.jul.es>

Maybe it would be better to add a "GDPR" required config entry, and just not save them to begin with on a system required to comply with GDPR. It could reside in zendto.conf next to the "where to send users that reject the GDPR"  area


-----Original Message-----
From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Jules Field via ZendTo
Sent: Wednesday, March 13, 2019 2:09 AM
To: ZendTo Users <zendto at zend.to>
Cc: Jules Field <Jules at Zend.To>
Subject: [ZendTo] Ideas wanted: "Forget me" button

Folks,

I want to add a button somewhere in ZendTo that will clear a user's address list, the list of addresses you have sent drop-offs to before. 
The list is used in the "New Drop-off" form to provide the auto-complete list when adding a recipient.

It's also a GDPR requirement, as it happens.

So I want some sort of "Delete recipients list" or "Delete address list" 
button.

Which gives me 2 questions I don't know the answer to:

1. Where should the button go in the user interface?
2. What should it say? (I'm assuming some sort of explanatory text by it. It's the actual text in the button I'm most interested in)

The obvious answer to (1) is "at the end of the main menu". But is that really the best place?
The answer to (2) needs to be very short.

BTW this only affects internal users, i.e. those who can log in.

All ideas most welcome please!

Thanks,

Jules

--
Julian Field MEng CEng CITP MBCS MIEEE MACM

'I've heard that it's possible to grow up. I've just never met
  anyone who's actually done it.' - Meredith Grey, Grey's Anatomy

www.Zend.To
Twitter: @JulesFM


_______________________________________________
ZendTo mailing list
ZendTo at zend.to
http://jul.es/mailman/listinfo/zendto


From deq at pattishall.com  Wed Mar 13 16:52:56 2019
From: deq at pattishall.com (Dale E. Qualls)
Date: Wed, 13 Mar 2019 16:52:56 +0000
Subject: [ZendTo] Ideas wanted: "Forget me" button
References: <E81C383E98FE7E44B1BD819DC8E687CA4FDAF0AC@PM-EXC.ad.pattishall.com>
Message-ID: <WM!be996986fbf9772ee7c09c926b4389aae10a8a0d625d78104381eb272ad59a0548ec6352f37bb14903ab8e0975b8e3b1!@mx.jul.es>

I wouldn't restrict it to GDPR.  California in the U.S. has a similar requirement going into effect in January of 2020 and I bet many other places will follow suit.

From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Scott Silva via ZendTo
Sent: Wednesday, March 13, 2019 11:49 AM
To: 'ZendTo Users'
Cc: Scott Silva
Subject: Re: [ZendTo] Ideas wanted: "Forget me" button


External email, exercise caution.



Maybe it would be better to add a "GDPR" required config entry, and just not save them to begin with on a system required to comply with GDPR. It could reside in zendto.conf next to the "where to send users that reject the GDPR" area


-----Original Message-----
From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Jules Field via ZendTo
Sent: Wednesday, March 13, 2019 2:09 AM
To: ZendTo Users <zendto at zend.to>
Cc: Jules Field <Jules at Zend.To>
Subject: [ZendTo] Ideas wanted: "Forget me" button

Folks,

I want to add a button somewhere in ZendTo that will clear a user's address list, the list of addresses you have sent drop-offs to before.
The list is used in the "New Drop-off" form to provide the auto-complete list when adding a recipient.

It's also a GDPR requirement, as it happens.

So I want some sort of "Delete recipients list" or "Delete address list"
button.

Which gives me 2 questions I don't know the answer to:

1. Where should the button go in the user interface?
2. What should it say? (I'm assuming some sort of explanatory text by it. It's the actual text in the button I'm most interested in)

The obvious answer to (1) is "at the end of the main menu". But is that really the best place?
The answer to (2) needs to be very short.

BTW this only affects internal users, i.e. those who can log in.

All ideas most welcome please!

Thanks,

Jules

--
Julian Field MEng CEng CITP MBCS MIEEE MACM

'I've heard that it's possible to grow up. I've just never met
anyone who's actually done it.' - Meredith Grey, Grey's Anatomy

www.Zend.To<http://www.Zend.To>
Twitter: @JulesFM


_______________________________________________
ZendTo mailing list
ZendTo at zend.to
http://jul.es/mailman/listinfo/zendto<http://jul.es/mailman/listinfo/zendto>

_______________________________________________
ZendTo mailing list
ZendTo at zend.to
http://jul.es/mailman/listinfo/zendto<http://jul.es/mailman/listinfo/zendto>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190313/946020e1/attachment.html>

From pedrosi at millercanfield.com  Thu Mar 21 19:32:28 2019
From: pedrosi at millercanfield.com (Pedrosi, Derek G.)
Date: Thu, 21 Mar 2019 19:32:28 +0000
Subject: [ZendTo] Uncaught SyntaxError: Unexpected identifier
References: <BL0PR0102MB3601EE655B71AD37DF86DAD6DE420@BL0PR0102MB3601.prod.exchangelabs.com>
Message-ID: <WM!ca6298195cda834bb41c0f5e16fa3d8afe2bd11406b3b02e6fa8d20dad84b4597538163ad31f27705157637364d4794a!@mx.jul.es>

I'm running v 5.03 of ZendTo on Ubuntu.

For at least one certain user, when a drop-off is requested and the link is clicked or the claim number is entered, the "To:" field of the drop-off is left blank, and no drop-off is allowed (clicking the link to drop does nothing).  When I open a console in Chrome, I see an error:
req.php?req=484624041:77 Uncaught SyntaxError: Unexpected identifier

When I do this with any other use I try, this error does not occur and the "To:" field is populated, the drop-off works as advertised.
I have no idea what makes this user different (nothing).

Also, when I look at eh SQLite db I see that all of the data is correctly populated in the "reqtable" table.




Thanks in advance,
derek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190321/7ce78a25/attachment.html>

From Jules at Zend.To  Fri Mar 22 11:00:02 2019
From: Jules at Zend.To (Jules Field)
Date: Fri, 22 Mar 2019 11:00:02 +0000
Subject: [ZendTo] Uncaught SyntaxError: Unexpected identifier
In-Reply-To: <WM!ca6298195cda834bb41c0f5e16fa3d8afe2bd11406b3b02e6fa8d20dad84b4597538163ad31f27705157637364d4794a!@mx.jul.es>
References: <BL0PR0102MB3601EE655B71AD37DF86DAD6DE420@BL0PR0102MB3601.prod.exchangelabs.com>
 <WM!ca6298195cda834bb41c0f5e16fa3d8afe2bd11406b3b02e6fa8d20dad84b4597538163ad31f27705157637364d4794a!@mx.jul.es>
Message-ID: <201747d1-9e90-a903-9431-82ac309e78d5@Zend.To>

Derek,

Any chance you could build a test VM using the very latest version of 
ZendTo, and see if this problem persists for this 1 user?

Unfortunately the error message you're getting probably refers to the 
php output of one of the template files. So the line number doesn't help 
at all, sadly.

Can you also check your Apache logs for this same "Unexpected 
identifier" error message? That might give more clue, possible.

Thanks!
Jules.

On 21/03/2019 19:32, Pedrosi, Derek G. via ZendTo wrote:
>
> I?m running v 5.03 of ZendTo on Ubuntu.
>
> For at least one certain user, when a drop-off is requested and the 
> link is clicked or the claim number is entered, the ?To:? field of the 
> drop-off is left blank, and no drop-off is allowed (clicking the link 
> to drop does nothing).? When I open a console in Chrome, I see an error:
>
> req.php?req=484624041:77 Uncaught SyntaxError: Unexpected identifier
>
> When I do this with any other use I try, this error does not occur and 
> the ?To:? field is populated, the drop-off works as advertised.
>
> I have no idea what makes this user different (nothing).
>
> Also, when I look at eh SQLite db I see that all of the data is 
> correctly populated in the ?reqtable? table.
>
> Thanks in advance,
>
> derek
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'The past is supposed to be a place of reference, not a place of
residence! There is a reason why your car has a big windshield and
a small rearview mirror. You are supposed to keep your eyes on where
you are going, and just occasionally check out where you have been.'
   - Willie Jolley

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190322/e1dbe134/attachment-0001.html>

From john.thurston at alaska.gov  Wed Mar 27 22:52:26 2019
From: john.thurston at alaska.gov (John Thurston)
Date: Wed, 27 Mar 2019 14:52:26 -0800
Subject: [ZendTo] Authenticator after update
In-Reply-To: <WM!f39caff7360cca6f88d86ef9aa468a0a84294bf471539dcaced7819d5f013eebd633fa29f2c32a3b767cf337f4dd3d38988a671c45b3e512d3af00fd4f3eb301!@mx.jul.es>
References: <e232dd06-f1d1-da6f-6084-8808659b08db@alaska.gov>
 <WM!5ce3af886688c19a43bef347ff58b76de48332846cd04370cc1bc374407f667f870e766dacb527d05e8a20b78d8ebc47!@mx.jul.es>
 <3ec5343f-7cd8-136c-8f7b-aaedb15ccb04@Zend.To>
 <WM!262db9ec14a18db60ee95d730dbb0863da618e51ea6d6c45b54a15f24f287054c2579433479068b69f287c62343409f443d13519b189ad2d46a3a1a662650249!@mx.jul.es>
 <cc48bffa-7ebd-2f69-d847-083211618e31@alaska.gov>
 <WM!905c727770ad2e2c47048eb513c1c2dea31709ca8fd0a2284a3d1aa1eb05fbd2d9ccc40e2913d470ebeed57636d8084f!@mx.jul.es>
 <WM!f39caff7360cca6f88d86ef9aa468a0a84294bf471539dcaced7819d5f013eebd633fa29f2c32a3b767cf337f4dd3d38988a671c45b3e512d3af00fd4f3eb301!@mx.jul.es>
 <6ea9532e-2e68-e698-be03-7aabc0d3234c@alaska.gov>
Message-ID: <WM!67d09d33e3b38212979d9b13bf9551de4793570f3bcc6c1d5c37977d50556420a4a0dbc5d0756ab00f78419b9ec33653!@mx.jul.es>

I've just been playing with an update from 5.10 to 5.17, and this 
behavior is still here. Thankfully, when authentication failed I 
thought, "This seems familiar".

Digging through the archives, I found my notes from last year.

Am I the only user doing ldap authentication?

Synopsis:
upgrade_preferences_php doesn't handle authLDAP settings nicely.

--
    Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska

On 7/5/2018 9:53 AM, John Thurston via ZendTo wrote:
> I did a few tests.
> 
> I don't have to uncomment the enabling line:
>  ? 'authenticator'???????? => 'LDAP'
> But I must uncomment only those ldap lines I have enabled in my 'old' 
> config for upgrade_pref to do its job for me. If I uncomment all the 
> ldap lines in the rpmnew config, the upgrade_pref adds values for any I 
> did not have enabled in my 'old' config.
> 
> If I switch the 'old' config to imap, the upgrade_pref does its job with 
> the stock rpmnew file.
> 
> 
> -- 
> 
>  ?? Do things because you should, not just because you can.
> 
> John Thurston??? 907-465-8591
> John.Thurston at alaska.gov
> Department of Administration
> State of Alaska
> 
> 
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
> 


From john.thurston at alaska.gov  Wed Mar 27 23:16:20 2019
From: john.thurston at alaska.gov (John Thurston)
Date: Wed, 27 Mar 2019 15:16:20 -0800
Subject: [ZendTo] Possible CSS problem with logo in 5.17
References: <72021174-b85a-f62a-78e5-92fa9cb9e4a1@alaska.gov>
Message-ID: <WM!601aa15929bdeea29ad985192f134949b64c158e8f19715b26ede15fb5acf855d89ce87182681bd05fd1efc2eb20ff31!@mx.jul.es>

I'm working on an update from 5.10 to 5.17, and I'm not a CSS pro, so 
I'm looking for for help or confirmation of problem.

After the update, the logo text in the upper right corer "ZendTo" gets a 
vertical scroll bar and thumb. There is a very tiny amount of movement 
in it. When I use Firefox element inspector, and un-tick the 'logoxclip 
overflow-x:hidden' from swish2.css, the scroll bar goes away.

I know little of css, so I went to w3schools to see what I can learn.
https://www.w3schools.com/cssref/css3_pr_overflow-x.asp

I can make it display correctly by replacing 'overflow-x' with 
'overflow', or by also defining a similar value for 'overflow-y'. Does 
anyone else see this problem? Have I messed up something else which is 
making my logo text render a tiny bit larger than everyone elses?
-- 
    Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska


From Mark-Andrew.Allen at icr.ac.uk  Thu Mar 28 10:09:11 2019
From: Mark-Andrew.Allen at icr.ac.uk (Mark Allen)
Date: Thu, 28 Mar 2019 10:09:11 +0000
Subject: [ZendTo] Authenticator after update
In-Reply-To: <WM!8632503b4d59c15c449b53490055c9c65422755b32e926b83a970ad16e66ca5c2afffd167d350dd2cd27c6111f0ef8c65538dee77987835757ed52262b0d99b8!@mx.jul.es>
References: <e232dd06-f1d1-da6f-6084-8808659b08db@alaska.gov>
 <WM!5ce3af886688c19a43bef347ff58b76de48332846cd04370cc1bc374407f667f870e766dacb527d05e8a20b78d8ebc47!@mx.jul.es>
 <3ec5343f-7cd8-136c-8f7b-aaedb15ccb04@Zend.To>
 <WM!262db9ec14a18db60ee95d730dbb0863da618e51ea6d6c45b54a15f24f287054c2579433479068b69f287c62343409f443d13519b189ad2d46a3a1a662650249!@mx.jul.es>
 <cc48bffa-7ebd-2f69-d847-083211618e31@alaska.gov>
 <WM!905c727770ad2e2c47048eb513c1c2dea31709ca8fd0a2284a3d1aa1eb05fbd2d9ccc40e2913d470ebeed57636d8084f!@mx.jul.es>
 <WM!f39caff7360cca6f88d86ef9aa468a0a84294bf471539dcaced7819d5f013eebd633fa29f2c32a3b767cf337f4dd3d38988a671c45b3e512d3af00fd4f3eb301!@mx.jul.es>
 <6ea9532e-2e68-e698-be03-7aabc0d3234c@alaska.gov>
 <WM!67d09d33e3b38212979d9b13bf9551de4793570f3bcc6c1d5c37977d50556420a4a0dbc5d0756ab00f78419b9ec33653!@mx.jul.es>
 <WM!8632503b4d59c15c449b53490055c9c65422755b32e926b83a970ad16e66ca5c2afffd167d350dd2cd27c6111f0ef8c65538dee77987835757ed52262b0d99b8!@mx.jul.es>
 <1B7C5C09-2D9F-440A-BE09-7213B6A38405@icr.ac.uk>
Message-ID: <WM!9666e0f98f2f018e017e9e1aefd751985b3d8630f0c23087823f76febf7e23f03c248b6dd1c8382b0894e5cbbd868405!@mx.jul.es>

John,
      I had the same issue recently, we had to change the background to conform to the Corporate colours and to get the logo to fit correctly. here?s what we did:

**MAKE SURE YOU MAKE COPIES OF THE FILE FIRST.**

Amend the file /opt/zendto/www/css/swish2.css
 
comment out *background image line13:
/*background-image: url(../images/swish/background.png);*/
 
On line14 change background colour to #eee:
background-color: #eee;
This creates a lighter background which the ICRComms team
recommend for all ICR webpages and docs.
 
topMenu Dropdown menu - change white to black display
 
On line 79 change colour white to black
color: black;

**THIS IS THE BIT YOU NEED TO CHANGE THE LOGO SIZE**
To ensure the ICR logo fits on
the page:
Change logo line 683 to max width
290: max-width: 290px;






On 27/03/2019, 22:52, "ZendTo on behalf of John Thurston via ZendTo" <zendto-bounces at zend.to on behalf of zendto at zend.to> wrote:

>I've just been playing with an update from 5.10 to 5.17, and this 
>behavior is still here. Thankfully, when authentication failed I 
>thought, "This seems familiar".
>
>Digging through the archives, I found my notes from last year.
>
>Am I the only user doing ldap authentication?
>
>Synopsis:
>upgrade_preferences_php doesn't handle authLDAP settings nicely.
>
>--
>    Do things because you should, not just because you can.
>
>John Thurston    907-465-8591
>John.Thurston at alaska.gov
>Department of Administration
>State of Alaska
>
>On 7/5/2018 9:53 AM, John Thurston via ZendTo wrote:
>> I did a few tests.
>> 
>> I don't have to uncomment the enabling line:
>>    'authenticator'         => 'LDAP'
>> But I must uncomment only those ldap lines I have enabled in my 'old' 
>> config for upgrade_pref to do its job for me. If I uncomment all the 
>> ldap lines in the rpmnew config, the upgrade_pref adds values for any I 
>> did not have enabled in my 'old' config.
>> 
>> If I switch the 'old' config to imap, the upgrade_pref does its job with 
>> the stock rpmnew file.
>> 
>> 
>> -- 
>> 
>>     Do things because you should, not just because you can.
>> 
>> John Thurston    907-465-8591
>> John.Thurston at alaska.gov
>> Department of Administration
>> State of Alaska
>> 
>> 
>> _______________________________________________
>> ZendTo mailing list
>> ZendTo at zend.to
>> http://jul.es/mailman/listinfo/zendto
>> 
>
>_______________________________________________
>ZendTo mailing list
>ZendTo at zend.to
>http://jul.es/mailman/listinfo/zendto

The Institute of Cancer Research: Royal Cancer Hospital, a charitable Company Limited by Guarantee, Registered in England under Company No. 534147 with its Registered Office at 123 Old Brompton Road, London SW7 3RP.

This e-mail message is confidential and for use by the addressee only.  If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer and network.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: default.vnd.ms-officetheme
Type: application/octet-stream
Size: 3131 bytes
Desc: default.vnd.ms-officetheme
URL: <http://jul.es/pipermail/zendto/attachments/20190328/f79f40a2/attachment.obj>

From KLE at msktd.com  Thu Mar 28 12:22:27 2019
From: KLE at msktd.com (Ken Etter)
Date: Thu, 28 Mar 2019 08:22:27 -0400
Subject: [ZendTo] Authenticator after update
In-Reply-To: <WM!16d95f4a4e68b5a3c9b18eca328410920b3a965833dd40daeb468f9a82d57a78b6a66a497efeb762ecbd9380511f7155a0880585e292a4d52ccdfa7bfc0ad153!@mx.jul.es>
References: <e232dd06-f1d1-da6f-6084-8808659b08db@alaska.gov>
 <WM!5ce3af886688c19a43bef347ff58b76de48332846cd04370cc1bc374407f667f870e766dacb527d05e8a20b78d8ebc47!@mx.jul.es>
 <3ec5343f-7cd8-136c-8f7b-aaedb15ccb04@Zend.To>
 <WM!262db9ec14a18db60ee95d730dbb0863da618e51ea6d6c45b54a15f24f287054c2579433479068b69f287c62343409f443d13519b189ad2d46a3a1a662650249!@mx.jul.es>
 <cc48bffa-7ebd-2f69-d847-083211618e31@alaska.gov>
 <WM!905c727770ad2e2c47048eb513c1c2dea31709ca8fd0a2284a3d1aa1eb05fbd2d9ccc40e2913d470ebeed57636d8084f!@mx.jul.es>
 <WM!f39caff7360cca6f88d86ef9aa468a0a84294bf471539dcaced7819d5f013eebd633fa29f2c32a3b767cf337f4dd3d38988a671c45b3e512d3af00fd4f3eb301!@mx.jul.es>
 <6ea9532e-2e68-e698-be03-7aabc0d3234c@alaska.gov>
 <WM!67d09d33e3b38212979d9b13bf9551de4793570f3bcc6c1d5c37977d50556420a4a0dbc5d0756ab00f78419b9ec33653!@mx.jul.es>
 <WM!16d95f4a4e68b5a3c9b18eca328410920b3a965833dd40daeb468f9a82d57a78b6a66a497efeb762ecbd9380511f7155a0880585e292a4d52ccdfa7bfc0ad153!@mx.jul.es>
 <5C9CBC8302000013001335A0@mail.msktd.com>
Message-ID: <WM!25ebe10779e4b2f8cbbdf814c4010d34a2559cd2960398e2357a75510782e7267c76f37714479db8d29f9363bf591bdb!@mx.jul.es>

I'm using LDAP authentication.  But last time I upgraded I needed to change OS, so I built a new VM.  It has been quite a while since I had to do a ZendTo update.  Thanks for sharing the info, I'll keep it in mind.

Ken Etter, System Administrator
Architectural Group
260.432.9337 | msktd.com




>>> John Thurston via ZendTo <zendto at zend.to> 3/27/2019 6:52 PM >>>
I've just been playing with an update from 5.10 to 5.17, and this 
behavior is still here. Thankfully, when authentication failed I 
thought, "This seems familiar".

Digging through the archives, I found my notes from last year.

Am I the only user doing ldap authentication?

Synopsis:
upgrade_preferences_php doesn't handle authLDAP settings nicely.

--
    Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska

On 7/5/2018 9:53 AM, John Thurston via ZendTo wrote:
> I did a few tests.
> 
> I don't have to uncomment the enabling line:
>    'authenticator' 	    => 'LDAP'
> But I must uncomment only those ldap lines I have enabled in my 'old' 
> config for upgrade_pref to do its job for me. If I uncomment all the 
> ldap lines in the rpmnew config, the upgrade_pref adds values for any I 
> did not have enabled in my 'old' config.
> 
> If I switch the 'old' config to imap, the upgrade_pref does its job with 
> the stock rpmnew file.
> 
> 
> -- 
> 
>	 Do things because you should, not just because you can.
> 
> John Thurston    907-465-8591
> John.Thurston at alaska.gov
> Department of Administration
> State of Alaska
> 
> 
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

> 

_______________________________________________
ZendTo mailing list
ZendTo at zend.to
http://jul.es/mailman/listinfo/zendto

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190328/432d3432/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE.png
Type: image/png
Size: 18080 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20190328/432d3432/attachment-0001.png>

From ssilva at sgvwater.com  Thu Mar 28 15:02:17 2019
From: ssilva at sgvwater.com (Scott Silva)
Date: Thu, 28 Mar 2019 15:02:17 +0000
Subject: [ZendTo] Authenticator after update
In-Reply-To: <WM!ab33ddb78db808d51ad4b1cfe23cb5bab8d67e21e10ce84626246605edef8532130eb880da67e4697519a194210d3dd1ea33d2a2d00147c7d9712b2080410a21!@mx.jul.es>
References: <e232dd06-f1d1-da6f-6084-8808659b08db@alaska.gov>
 <WM!5ce3af886688c19a43bef347ff58b76de48332846cd04370cc1bc374407f667f870e766dacb527d05e8a20b78d8ebc47!@mx.jul.es>
 <3ec5343f-7cd8-136c-8f7b-aaedb15ccb04@Zend.To>
 <WM!262db9ec14a18db60ee95d730dbb0863da618e51ea6d6c45b54a15f24f287054c2579433479068b69f287c62343409f443d13519b189ad2d46a3a1a662650249!@mx.jul.es>
 <cc48bffa-7ebd-2f69-d847-083211618e31@alaska.gov>
 <WM!905c727770ad2e2c47048eb513c1c2dea31709ca8fd0a2284a3d1aa1eb05fbd2d9ccc40e2913d470ebeed57636d8084f!@mx.jul.es>
 <WM!f39caff7360cca6f88d86ef9aa468a0a84294bf471539dcaced7819d5f013eebd633fa29f2c32a3b767cf337f4dd3d38988a671c45b3e512d3af00fd4f3eb301!@mx.jul.es>
 <6ea9532e-2e68-e698-be03-7aabc0d3234c@alaska.gov>
 <WM!67d09d33e3b38212979d9b13bf9551de4793570f3bcc6c1d5c37977d50556420a4a0dbc5d0756ab00f78419b9ec33653!@mx.jul.es>
 <WM!16d95f4a4e68b5a3c9b18eca328410920b3a965833dd40daeb468f9a82d57a78b6a66a497efeb762ecbd9380511f7155a0880585e292a4d52ccdfa7bfc0ad153!@mx.jul.es>
 <5C9CBC8302000013001335A0@mail.msktd.com>
 <WM!25ebe10779e4b2f8cbbdf814c4010d34a2559cd2960398e2357a75510782e7267c76f37714479db8d29f9363bf591bdb!@mx.jul.es>
 <WM!ab33ddb78db808d51ad4b1cfe23cb5bab8d67e21e10ce84626246605edef8532130eb880da67e4697519a194210d3dd1ea33d2a2d00147c7d9712b2080410a21!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F4204A073F@FONEXCH01.sgvwc.local>
Message-ID: <WM!61d5e9188fb917f2f52e3cad113e4373e21081615ec558dc95dea5c797fb8b16938ffa836eea654856f1cf635ca0b8f6!@mx.jul.es>

I just ran the new upgrade script on an update from 5.15 to 5.17 and everything seems to be going smoothly in my testing. And I am using LDAP auth against an AD system.

From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Ken Etter via ZendTo
Sent: Thursday, March 28, 2019 5:23 AM
To: ZendTo List <zendto at zend.to>
Cc: Ken Etter <KLE at msktd.com>
Subject: Re: [ZendTo] Authenticator after update

I'm using LDAP authentication.  But last time I upgraded I needed to change OS, so I built a new VM.  It has been quite a while since I had to do a ZendTo update.  Thanks for sharing the info, I'll keep it in mind.


Ken Etter, System Administrator
Architectural Group
260.432.9337 | msktd.com<http://msktd.com/>

[cid:image001.png at 01D4E53C.3F12C460]<http://msktd.com/>


>>> John Thurston via ZendTo <zendto at zend.to<mailto:zendto at zend.to>> 3/27/2019 6:52 PM >>>
I've just been playing with an update from 5.10 to 5.17, and this
behavior is still here. Thankfully, when authentication failed I
thought, "This seems familiar".

Digging through the archives, I found my notes from last year.

Am I the only user doing ldap authentication?

Synopsis:
upgrade_preferences_php doesn't handle authLDAP settings nicely.

--
    Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov<mailto:John.Thurston at alaska.gov>
Department of Administration
State of Alaska

On 7/5/2018 9:53 AM, John Thurston via ZendTo wrote:
> I did a few tests.
>
> I don't have to uncomment the enabling line:
>    'authenticator'         => 'LDAP'
> But I must uncomment only those ldap lines I have enabled in my 'old'
> config for upgrade_pref to do its job for me. If I uncomment all the
> ldap lines in the rpmnew config, the upgrade_pref adds values for any I
> did not have enabled in my 'old' config.
>
> If I switch the 'old' config to imap, the upgrade_pref does its job with
> the stock rpmnew file.
>
>
> --
>
>     Do things because you should, not just because you can.
>
> John Thurston    907-465-8591
> John.Thurston at alaska.gov<mailto:John.Thurston at alaska.gov>
> Department of Administration
> State of Alaska
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to<mailto:ZendTo at zend.to>
> http://jul.es/mailman/listinfo/zendto

>

_______________________________________________
ZendTo mailing list
ZendTo at zend.to<mailto:ZendTo at zend.to>
http://jul.es/mailman/listinfo/zendto

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190328/2020aab6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 18080 bytes
Desc: image001.png
URL: <http://jul.es/pipermail/zendto/attachments/20190328/2020aab6/attachment-0001.png>

From john.thurston at alaska.gov  Thu Mar 28 16:26:10 2019
From: john.thurston at alaska.gov (John Thurston)
Date: Thu, 28 Mar 2019 08:26:10 -0800
Subject: [ZendTo] Authenticator after update
In-Reply-To: <WM!ceeb6dc5e97371edb35ebbe6d31c4c4d8d2d136b823c1329914e331ad99d926b8fb47999e8830908a99efc1599b3302b898167b9668fa7ad370e3f696de48067!@mx.jul.es>
References: <e232dd06-f1d1-da6f-6084-8808659b08db@alaska.gov>
 <6ea9532e-2e68-e698-be03-7aabc0d3234c@alaska.gov>
 <WM!67d09d33e3b38212979d9b13bf9551de4793570f3bcc6c1d5c37977d50556420a4a0dbc5d0756ab00f78419b9ec33653!@mx.jul.es>
 <WM!16d95f4a4e68b5a3c9b18eca328410920b3a965833dd40daeb468f9a82d57a78b6a66a497efeb762ecbd9380511f7155a0880585e292a4d52ccdfa7bfc0ad153!@mx.jul.es>
 <5C9CBC8302000013001335A0@mail.msktd.com>
 <WM!25ebe10779e4b2f8cbbdf814c4010d34a2559cd2960398e2357a75510782e7267c76f37714479db8d29f9363bf591bdb!@mx.jul.es>
 <WM!ab33ddb78db808d51ad4b1cfe23cb5bab8d67e21e10ce84626246605edef8532130eb880da67e4697519a194210d3dd1ea33d2a2d00147c7d9712b2080410a21!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F4204A073F@FONEXCH01.sgvwc.local>
 <WM!61d5e9188fb917f2f52e3cad113e4373e21081615ec558dc95dea5c797fb8b16938ffa836eea654856f1cf635ca0b8f6!@mx.jul.es>
 <WM!ceeb6dc5e97371edb35ebbe6d31c4c4d8d2d136b823c1329914e331ad99d926b8fb47999e8830908a99efc1599b3302b898167b9668fa7ad370e3f696de48067!@mx.jul.es>
 <1d7de9d0-991f-62f3-7406-d11939f561dc@alaska.gov>
Message-ID: <WM!999efad5bf8cb0c5e95a2ee98c9d3844b82302ce3480728f644c309b61d24a9d7977014dd74124289da4bba1927a20a1!@mx.jul.es>

Are you using all of the available "authLDAP" config values?

In my case, the updater re-enables configuration values I have 
explicitly commented out. Things like:
'authLDAPBindDn'
'authLDAPBindPass'
'authLDAPOrganization'
'authLDAPUsernameAttr'
'authLDAPEmailAttr'
'authLDAPMemberKey'
'authLDAPMemberRole'

When they get re-enabled, authentication fails because none of the 
values are applicable or correct.

--
    Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska

On 3/28/2019 7:02 AM, Scott Silva via ZendTo wrote:
> I just ran the new upgrade script on an update from 5.15 to 5.17 and 
> everything seems to be going smoothly in my testing. And I am using LDAP 
> auth against an AD system.
> 


From ssilva at sgvwater.com  Thu Mar 28 17:06:59 2019
From: ssilva at sgvwater.com (Scott Silva)
Date: Thu, 28 Mar 2019 17:06:59 +0000
Subject: [ZendTo] Authenticator after update
In-Reply-To: <WM!84fc0c96015a49287fef827b60a4cdc0e88853e7426e2f8edc7012c05e08942d2ae88339c3a92f3a41ca27b45844f06c0952fab958aab1e1e74c5ad856366762!@mx.jul.es>
References: <e232dd06-f1d1-da6f-6084-8808659b08db@alaska.gov>
 <6ea9532e-2e68-e698-be03-7aabc0d3234c@alaska.gov>
 <WM!67d09d33e3b38212979d9b13bf9551de4793570f3bcc6c1d5c37977d50556420a4a0dbc5d0756ab00f78419b9ec33653!@mx.jul.es>
 <WM!16d95f4a4e68b5a3c9b18eca328410920b3a965833dd40daeb468f9a82d57a78b6a66a497efeb762ecbd9380511f7155a0880585e292a4d52ccdfa7bfc0ad153!@mx.jul.es>
 <5C9CBC8302000013001335A0@mail.msktd.com>
 <WM!25ebe10779e4b2f8cbbdf814c4010d34a2559cd2960398e2357a75510782e7267c76f37714479db8d29f9363bf591bdb!@mx.jul.es>
 <WM!ab33ddb78db808d51ad4b1cfe23cb5bab8d67e21e10ce84626246605edef8532130eb880da67e4697519a194210d3dd1ea33d2a2d00147c7d9712b2080410a21!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F4204A073F@FONEXCH01.sgvwc.local>
 <WM!61d5e9188fb917f2f52e3cad113e4373e21081615ec558dc95dea5c797fb8b16938ffa836eea654856f1cf635ca0b8f6!@mx.jul.es>
 <WM!ceeb6dc5e97371edb35ebbe6d31c4c4d8d2d136b823c1329914e331ad99d926b8fb47999e8830908a99efc1599b3302b898167b9668fa7ad370e3f696de48067!@mx.jul.es>
 <1d7de9d0-991f-62f3-7406-d11939f561dc@alaska.gov>
 <WM!999efad5bf8cb0c5e95a2ee98c9d3844b82302ce3480728f644c309b61d24a9d7977014dd74124289da4bba1927a20a1!@mx.jul.es>
 <WM!84fc0c96015a49287fef827b60a4cdc0e88853e7426e2f8edc7012c05e08942d2ae88339c3a92f3a41ca27b45844f06c0952fab958aab1e1e74c5ad856366762!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F4204A1931@FONEXCH01.sgvwc.local>
Message-ID: <WM!9ca4b1b4fdaa14ffdbba104b2bf6270e8c772b2e89ba90d4afbeba44e07ae3d3495c3a47f4f7b7e3516543d4f7c4acc4!@mx.jul.es>

I had some old defaults in my config that I was just ignoring. Need to do some cleanup... 
I guess once I got it working, I didn't mess with it anymore.


-----Original Message-----
From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of John Thurston via ZendTo
Sent: Thursday, March 28, 2019 9:27 AM
To: zendto at zend.to
Cc: John Thurston <john.thurston at alaska.gov>
Subject: Re: [ZendTo] Authenticator after update

Are you using all of the available "authLDAP" config values?

In my case, the updater re-enables configuration values I have explicitly commented out. Things like:
'authLDAPBindDn'
'authLDAPBindPass'
'authLDAPOrganization'
'authLDAPUsernameAttr'
'authLDAPEmailAttr'
'authLDAPMemberKey'
'authLDAPMemberRole'

When they get re-enabled, authentication fails because none of the values are applicable or correct.

--
    Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska

On 3/28/2019 7:02 AM, Scott Silva via ZendTo wrote:
> I just ran the new upgrade script on an update from 5.15 to 5.17 and 
> everything seems to be going smoothly in my testing. And I am using 
> LDAP auth against an AD system.
> 

_______________________________________________
ZendTo mailing list
ZendTo at zend.to
http://jul.es/mailman/listinfo/zendto


From john.thurston at alaska.gov  Thu Mar 28 17:33:11 2019
From: john.thurston at alaska.gov (John Thurston)
Date: Thu, 28 Mar 2019 09:33:11 -0800
Subject: [ZendTo] Feature requests - Global Drop-off List
References: <eb696566-d2e7-d0a4-aab8-8b8fc9026312@alaska.gov>
Message-ID: <WM!28188fe001a22bb6ccf2a7b74b506b22ae4d8458cd11e247643900e3c5d5dc8051d275b36fc56594e7857e57ff79ecff!@mx.jul.es>

The part of ZendTo with which I interact most often is the 'Global 
Drop-off List". It would be wonderful to have some more information 
there. I'm thinking specifically of
   Indicators for "encrypted" and "picked-up"

It would also be helpful if there were a way to 'open in new tab' from 
that screen. If I sort by size and want to examine the 8 largest 
dropoffs, I have to open the list, sort the list, identify the claimID I 
want, open it, examine it, ... then I must repeat all the steps from the 
beginning. If I could ctrl-click on a claimID and open it in a new tab, 
I would save a whole bunch of clicks.

Alternatively, a select-box so a bulk action could be taken on multiple 
items. Then I could open the list, sort it, select several, and open 
then all in new tabs.


-- 
    Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska


From john.thurston at alaska.gov  Thu Mar 28 20:49:13 2019
From: john.thurston at alaska.gov (John Thurston)
Date: Thu, 28 Mar 2019 12:49:13 -0800
Subject: [ZendTo] Possible CSS problem with logo in 5.17
In-Reply-To: <WM!69ddbd46c492c10ace9d9b472ee360d5b5aae89f8636aba653a1794ed8e2e9269242eee7e7675294c86615d9145898cdcbd25d3cd93fbe170b83bb8cc6bac7ef!@mx.jul.es>
References: <72021174-b85a-f62a-78e5-92fa9cb9e4a1@alaska.gov>
 <WM!601aa15929bdeea29ad985192f134949b64c158e8f19715b26ede15fb5acf855d89ce87182681bd05fd1efc2eb20ff31!@mx.jul.es>
 <WM!69ddbd46c492c10ace9d9b472ee360d5b5aae89f8636aba653a1794ed8e2e9269242eee7e7675294c86615d9145898cdcbd25d3cd93fbe170b83bb8cc6bac7ef!@mx.jul.es>
 <20752f01-40b2-b4ba-eb8a-0ab75c6e6abe@alaska.gov>
Message-ID: <WM!1a4a7cb50ac70b60ac73fe0bdcc7fcae032b0af70be5fdb99cd3579b3c299c0212d77733ac56f63ae4d6f0a2dbf19f5f!@mx.jul.es>

On 3/28/2019 2:09 AM, Mark Allen wrote:
> John,
>       I had the same issue recently, we had to change the background to conform to the Corporate colours and to get the logo to fit correctly. here?s what we did:
...

> **THIS IS THE BIT YOU NEED TO CHANGE THE LOGO SIZE**
> To ensure the ICR logo fits on
> the page:
> Change logo line 683 to max width
> 290: max-width: 290px;

I don't think this is for the problem I'm seeing. I'm not trying to 
change the logo, and there is no horizontal clipping or scrolling 
happening, so the width is ok. I think the problem is the 'font-size' is 
set larger than 3.46em in #logo. If I set that to 3.4em the vertical 
scroll goes away. Maybe there is something wrong with font scaling or 
substitution on my browser.

But with some more digging, I think this may go back to the #logo style 
definitions.

#logo defines "overflow-y: visible;"

and then

#logoxclip defines  "overflow-x: hidden;"

There is no #logoyclip style.

So it sure looks like that silly vertical scroll bar is by design. Why 
is there an 'xclip' style? Why doesn't #logo just contain "overflow: 
hidden;" and have done with it?

I think the simplest way to solve my problem (so all the edits are to a 
single file) will be to modify swish2.css to
   Change "overflow-y: hidden;" in #logo
and to
   Add "overflow-y: inherit;" to #logoxclip

I've just managed to look at my test site with google chrome browser. It 
has the same problem, so I don't think this is just a case of my firefox 
not being able to scale a font.

I don't think this is a problem at the reference installation at 
Southampton (https://dropoff.soton.ac.uk/) because they're using an 
image for their logo rather than text.

--
    Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska

On 3/27/2019 3:16 PM, John Thurston via ZendTo wrote:
> I'm working on an update from 5.10 to 5.17, and I'm not a CSS pro, so 
> I'm looking for for help or confirmation of problem.
> 
> After the update, the logo text in the upper right corer "ZendTo" gets a 
> vertical scroll bar and thumb. There is a very tiny amount of movement 
> in it. When I use Firefox element inspector, and un-tick the 'logoxclip 
> overflow-x:hidden' from swish2.css, the scroll bar goes away.
> 
> I know little of css, so I went to w3schools to see what I can learn.
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3schools.com_cssref_css3-5Fpr-5Foverflow-2Dx.asp&d=DwICAg&c=teXCf5DW4bHgLDM-H5_GmQ&r=LXZcjhZDA2Cbv2Jma4IUFbBvxdnXAg5iEX34eEaPIoo&m=vXs9BxoD0Qm9e7vzPU5Dc2g3-YfjGIOgAAyqGBTe2zk&s=71dNdTQFQ1LmxueZ1flK7bUI7mu2aD8eKYAyZ_hCOjs&e= 
> 
> 
> I can make it display correctly by replacing 'overflow-x' with 
> 'overflow', or by also defining a similar value for 'overflow-y'. Does 
> anyone else see this problem? Have I messed up something else which is 
> making my logo text render a tiny bit larger than everyone elses?


From john.thurston at alaska.gov  Thu Mar 28 21:07:29 2019
From: john.thurston at alaska.gov (John Thurston)
Date: Thu, 28 Mar 2019 13:07:29 -0800
Subject: [ZendTo] Possible CSS problem with logo in 5.17
In-Reply-To: <WM!f99ff47a45eb5205efd595fae1c433bc6e5df00c8a77130545b194d67fe5890570d8c0516f7a4ef5a913cf476457abf9f1ad0eb28621a9eff5210264b064ffa9!@mx.jul.es>
References: <72021174-b85a-f62a-78e5-92fa9cb9e4a1@alaska.gov>
 <WM!601aa15929bdeea29ad985192f134949b64c158e8f19715b26ede15fb5acf855d89ce87182681bd05fd1efc2eb20ff31!@mx.jul.es>
 <WM!69ddbd46c492c10ace9d9b472ee360d5b5aae89f8636aba653a1794ed8e2e9269242eee7e7675294c86615d9145898cdcbd25d3cd93fbe170b83bb8cc6bac7ef!@mx.jul.es>
 <20752f01-40b2-b4ba-eb8a-0ab75c6e6abe@alaska.gov>
 <WM!1a4a7cb50ac70b60ac73fe0bdcc7fcae032b0af70be5fdb99cd3579b3c299c0212d77733ac56f63ae4d6f0a2dbf19f5f!@mx.jul.es>
 <WM!f99ff47a45eb5205efd595fae1c433bc6e5df00c8a77130545b194d67fe5890570d8c0516f7a4ef5a913cf476457abf9f1ad0eb28621a9eff5210264b064ffa9!@mx.jul.es>
 <9e9b4afe-1e65-2aa5-7f68-472712223a5b@alaska.gov>
Message-ID: <WM!9c07e8a091440e5297d7fe60533efe71aa7f306efd444d5aa916c07347430c2fdf3d1e57bdf0b391c11095ddd5fb22a7!@mx.jul.es>


On 3/28/2019 12:49 PM, John Thurston via ZendTo wrote:
> I think the simplest way to solve my problem (so all the edits are to a 
> single file) will be to modify swish2.css to
>  ? Change "overflow-y: hidden;" in #logo
> and to
>  ? Add "overflow-y: inherit;" to #logoxclip

K. I looked in swish2.css and found the admonition to leave it alone, so 
I've made the following additions to /opt/zendto/www/css/local.css


#logo {
         overflow-y: hidden;
}

#logoxclip {
         overflow-y: inherit;
}



And that crazy little scroll bar is gone.

--
    Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska