From zend2ml1218-a368g at m.patpro.net Thu Feb 7 17:17:48 2019 From: zend2ml1218-a368g at m.patpro.net (patpro) Date: Thu, 7 Feb 2019 18:17:48 +0100 Subject: [ZendTo] ANNOUNCE: 5.17-1 production release In-Reply-To: References:

<7e953bb5-8d7d-aa5c-91e8-de0d56ca80a0@Zend.To>

<1b66959b-667d-b701-d0c1-6d1902e0c79b@Zend.To> <8C458141-9C14-408E-B804-8076909C33E3@m.patpro.net> <9FBBA633-6855-4DDD-8CB3-7D2F32477527@m.patpro.net> Message-ID: Hi Jules, Sorry for the very late reply. Thank you for your work about FreeBSD compatibility. Unfortunately it's very unlikely someone ever use this installer on FreeBSD. It's just not the way we install software on this platform. We also don't use /opt, unless it's a fully autonomous piece of proprietary software (Splunk for example). Everything else that is not part of the base system goes into /usr/local/{bin,sbin,share,www,...} It's very good, though, to create a quick&dirty test server, but the fact this installer will play around with pkg makes it very difficult to run on a production platform (I won't run it on my personal server for example, it could literally break everything :) ). I'm going to setup a blank FreeBSD VM for testing and see what's wrong with locales on my production server. Thanks again for the work! patpro > On 31 janv. 2019, at 17:23, Jules Field wrote: > > patpro, > > Download and try out the latest Beta Installer from > https://zend.to/files/install-beta.ZendTo.tgz > You should find that produces a working FreeBSD system on FreeBSD 11.2 and 12. > > I've also made a load of improvements to the "upgrade" utility so that it works with tarball-based ZendTo installations. > It hopes that you are using a structure like > /opt/ZendTo- > directory for each version you have, and /opt/zendto is a symlink to the current production one. > That's what the Installer will set up for you. > If you do that, then > /opt/zendto/bin/upgrade > should automatically find your last version and your newest version and do all the relevant magic. > > I strongly advise > /opt/zendto/bin/upgrade --dry-run > the first time though, so it just tells you what it would do! > > I didn't have locale or language problems at all, it all just worked. > > Cheers, > Jules. > > On 24/01/2019 19:42, patpro wrote: >> Jules, >> >>> I've setup a FreeBSD 11.2 box and am working on getting the ZendTo Installer to do it all for you. >>> It will use the .tgz of ZendTo, hopefully that will be okay. >> That's very nice! Thanks. >> >> >>> I'll have to make the "upgrade" script a bit more clever so that it notices when it's on FreeBSD as the old versions of the preferences.php and zendto.conf will be in different places. But it should still be able to do the bulk of the job for you. >> If you want to package a software that can be un-archived on top of an older version of itself, you might want to name config files with a suffix, say "preferences.php.sample" or "zendto.conf.dist". Then when you unpack the new version on top of the old one, existing config files are not erased. Users (or upgrade script) can then synch old config with new parameters from .sample/.dist files. >> >> cheers, >> patpro > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'Find a place inside where there's joy, and the joy will burn out > the pain.' - Joseph Campbell > > www.Zend.To > Twitter: @JulesFM > From zend2ml1218-a368g at m.patpro.net Thu Feb 7 19:33:15 2019 From: zend2ml1218-a368g at m.patpro.net (patpro) Date: Thu, 7 Feb 2019 20:33:15 +0100 Subject: [ZendTo] ANNOUNCE: 5.17-1 production release In-Reply-To: References:

<7e953bb5-8d7d-aa5c-91e8-de0d56ca80a0@Zend.To>

<1b66959b-667d-b701-d0c1-6d1902e0c79b@Zend.To> <8C458141-9C14-408E-B804-8076909C33E3@m.patpro.net> <9FBBA633-6855-4DDD-8CB3-7D2F32477527@m.patpro.net> <7F6CAC77-F639-4FF8-81A8-E8BC858F2212@m.patpro.net> Message-ID: I've just ran the install script on a blank FreeBSD VM, it went very smoothly. Nice work :) Just one mistake: "Is it okay for me to configure SELinux for ZendTo (y/n) [Default is y]:" <-- this one is irrelevant. On FreebSD it should be masked or default to "n". cheers, patpro On 07 f?vr. 2019, at 18:17, patpro via ZendTo wrote: > > Hi Jules, > > Sorry for the very late reply. > Thank you for your work about FreeBSD compatibility. Unfortunately it's very unlikely someone ever use this installer on FreeBSD. It's just not the way we install software on this platform. > We also don't use /opt, unless it's a fully autonomous piece of proprietary software (Splunk for example). Everything else that is not part of the base system goes into /usr/local/{bin,sbin,share,www,...} > > It's very good, though, to create a quick&dirty test server, but the fact this installer will play around with pkg makes it very difficult to run on a production platform (I won't run it on my personal server for example, it could literally break everything :) ). > > I'm going to setup a blank FreeBSD VM for testing and see what's wrong with locales on my production server. > Thanks again for the work! > > patpro > > > >> On 31 janv. 2019, at 17:23, Jules Field wrote: >> >> patpro, >> >> Download and try out the latest Beta Installer from >> https://zend.to/files/install-beta.ZendTo.tgz >> You should find that produces a working FreeBSD system on FreeBSD 11.2 and 12. >> >> I've also made a load of improvements to the "upgrade" utility so that it works with tarball-based ZendTo installations. >> It hopes that you are using a structure like >> /opt/ZendTo- >> directory for each version you have, and /opt/zendto is a symlink to the current production one. >> That's what the Installer will set up for you. >> If you do that, then >> /opt/zendto/bin/upgrade >> should automatically find your last version and your newest version and do all the relevant magic. >> >> I strongly advise >> /opt/zendto/bin/upgrade --dry-run >> the first time though, so it just tells you what it would do! >> >> I didn't have locale or language problems at all, it all just worked. >> >> Cheers, >> Jules. >> >> On 24/01/2019 19:42, patpro wrote: >>> Jules, >>> >>>> I've setup a FreeBSD 11.2 box and am working on getting the ZendTo Installer to do it all for you. >>>> It will use the .tgz of ZendTo, hopefully that will be okay. >>> That's very nice! Thanks. >>> >>> >>>> I'll have to make the "upgrade" script a bit more clever so that it notices when it's on FreeBSD as the old versions of the preferences.php and zendto.conf will be in different places. But it should still be able to do the bulk of the job for you. >>> If you want to package a software that can be un-archived on top of an older version of itself, you might want to name config files with a suffix, say "preferences.php.sample" or "zendto.conf.dist". Then when you unpack the new version on top of the old one, existing config files are not erased. Users (or upgrade script) can then synch old config with new parameters from .sample/.dist files. >>> >>> cheers, >>> patpro >> >> Jules >> >> -- >> Julian Field MEng CEng CITP MBCS MIEEE MACM >> >> 'Find a place inside where there's joy, and the joy will burn out >> the pain.' - Joseph Campbell >> >> www.Zend.To >> Twitter: @JulesFM >> > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto From zend2ml1218-a368g at m.patpro.net Thu Feb 7 19:50:19 2019 From: zend2ml1218-a368g at m.patpro.net (patpro) Date: Thu, 7 Feb 2019 20:50:19 +0100 Subject: [ZendTo] ANNOUNCE: 5.17-1 production release In-Reply-To: References:

<7e953bb5-8d7d-aa5c-91e8-de0d56ca80a0@Zend.To>

Message-ID: And full disclosure? it helped me find out what went wrong in my manual install. -> sudo -u www bash bin/makelanguages it solved my locale problem :/ My bad. > On 07 f?vr. 2019, at 20:33, patpro via ZendTo wrote: > > I've just ran the install script on a blank FreeBSD VM, it went very smoothly. Nice work :) > > Just one mistake: "Is it okay for me to configure SELinux for ZendTo (y/n) [Default is y]:" <-- this one is irrelevant. On FreebSD it should be masked or default to "n". > > cheers, > patpro > > > On 07 f?vr. 2019, at 18:17, patpro via ZendTo wrote: >> >> Hi Jules, >> >> Sorry for the very late reply. >> Thank you for your work about FreeBSD compatibility. Unfortunately it's very unlikely someone ever use this installer on FreeBSD. It's just not the way we install software on this platform. >> We also don't use /opt, unless it's a fully autonomous piece of proprietary software (Splunk for example). Everything else that is not part of the base system goes into /usr/local/{bin,sbin,share,www,...} >> >> It's very good, though, to create a quick&dirty test server, but the fact this installer will play around with pkg makes it very difficult to run on a production platform (I won't run it on my personal server for example, it could literally break everything :) ). >> >> I'm going to setup a blank FreeBSD VM for testing and see what's wrong with locales on my production server. >> Thanks again for the work! >> >> patpro >> >> >> >>> On 31 janv. 2019, at 17:23, Jules Field wrote: >>> >>> patpro, >>> >>> Download and try out the latest Beta Installer from >>> https://zend.to/files/install-beta.ZendTo.tgz >>> You should find that produces a working FreeBSD system on FreeBSD 11.2 and 12. >>> >>> I've also made a load of improvements to the "upgrade" utility so that it works with tarball-based ZendTo installations. >>> It hopes that you are using a structure like >>> /opt/ZendTo- >>> directory for each version you have, and /opt/zendto is a symlink to the current production one. >>> That's what the Installer will set up for you. >>> If you do that, then >>> /opt/zendto/bin/upgrade >>> should automatically find your last version and your newest version and do all the relevant magic. >>> >>> I strongly advise >>> /opt/zendto/bin/upgrade --dry-run >>> the first time though, so it just tells you what it would do! >>> >>> I didn't have locale or language problems at all, it all just worked. >>> >>> Cheers, >>> Jules. >>> >>> On 24/01/2019 19:42, patpro wrote: >>>> Jules, >>>> >>>>> I've setup a FreeBSD 11.2 box and am working on getting the ZendTo Installer to do it all for you. >>>>> It will use the .tgz of ZendTo, hopefully that will be okay. >>>> That's very nice! Thanks. >>>> >>>> >>>>> I'll have to make the "upgrade" script a bit more clever so that it notices when it's on FreeBSD as the old versions of the preferences.php and zendto.conf will be in different places. But it should still be able to do the bulk of the job for you. >>>> If you want to package a software that can be un-archived on top of an older version of itself, you might want to name config files with a suffix, say "preferences.php.sample" or "zendto.conf.dist". Then when you unpack the new version on top of the old one, existing config files are not erased. Users (or upgrade script) can then synch old config with new parameters from .sample/.dist files. >>>> >>>> cheers, >>>> patpro >>> >>> Jules >>> >>> -- >>> Julian Field MEng CEng CITP MBCS MIEEE MACM >>> >>> 'Find a place inside where there's joy, and the joy will burn out >>> the pain.' - Joseph Campbell >>> >>> 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 From Jules at Zend.To Fri Feb 8 09:52:42 2019 From: Jules at Zend.To (Jules Field) Date: Fri, 8 Feb 2019 09:52:42 +0000 Subject: [ZendTo] ANNOUNCE: 5.17-1 production release In-Reply-To: References:

<1b66959b-667d-b701-d0c1-6d1902e0c79b@Zend.To> <8C458141-9C14-408E-B804-8076909C33E3@m.patpro.net> <9FBBA633-6855-4DDD-8CB3-7D2F32477527@m.patpro.net> Message-ID: <27c6a981-a207-ee4e-2a0e-3a577ed655d0@Zend.To> On 07/02/2019 17:17, patpro wrote: > Hi Jules, > > Sorry for the very late reply. > Thank you for your work about FreeBSD compatibility. Unfortunately it's very unlikely someone ever use this installer on FreeBSD. It's just not the way we install software on this platform. > We also don't use /opt, unless it's a fully autonomous piece of proprietary software (Splunk for example). Everything else that is not part of the base system goes into /usr/local/{bin,sbin,share,www,...} I'm not supposed to put stuff in /opt on Linux either. :-) Most people run a VM purely for ZendTo and nothing else, as it makes system maintenance so much easier when you have multiple single-purpose VMs rather than a few horribly complicated multi-purpose VMs. > > It's very good, though, to create a quick&dirty test server, but the fact this installer will play around with pkg makes it very difficult to run on a production platform (I won't run it on my personal server for example, it could literally break everything :) ). Why not use pkg? It seems the ideal way to do it. I don't quite see why I shouldn't use the packaging system that is already there, and is used by the entire OS itself. That puts all extra stuff it adds into /usr/local and only uses the standard FreeBSD pkg services. > > I'm going to setup a blank FreeBSD VM for testing and see what's wrong with locales on my production server. > Thanks again for the work! No worries. Cheers, Jules. > > patpro > > > >> On 31 janv. 2019, at 17:23, Jules Field wrote: >> >> patpro, >> >> Download and try out the latest Beta Installer from >> https://zend.to/files/install-beta.ZendTo.tgz >> You should find that produces a working FreeBSD system on FreeBSD 11.2 and 12. >> >> I've also made a load of improvements to the "upgrade" utility so that it works with tarball-based ZendTo installations. >> It hopes that you are using a structure like >> /opt/ZendTo- >> directory for each version you have, and /opt/zendto is a symlink to the current production one. >> That's what the Installer will set up for you. >> If you do that, then >> /opt/zendto/bin/upgrade >> should automatically find your last version and your newest version and do all the relevant magic. >> >> I strongly advise >> /opt/zendto/bin/upgrade --dry-run >> the first time though, so it just tells you what it would do! >> >> I didn't have locale or language problems at all, it all just worked. >> >> Cheers, >> Jules. >> >> On 24/01/2019 19:42, patpro wrote: >>> Jules, >>> >>>> I've setup a FreeBSD 11.2 box and am working on getting the ZendTo Installer to do it all for you. >>>> It will use the .tgz of ZendTo, hopefully that will be okay. >>> That's very nice! Thanks. >>> >>> >>>> I'll have to make the "upgrade" script a bit more clever so that it notices when it's on FreeBSD as the old versions of the preferences.php and zendto.conf will be in different places. But it should still be able to do the bulk of the job for you. >>> If you want to package a software that can be un-archived on top of an older version of itself, you might want to name config files with a suffix, say "preferences.php.sample" or "zendto.conf.dist". Then when you unpack the new version on top of the old one, existing config files are not erased. Users (or upgrade script) can then synch old config with new parameters from .sample/.dist files. >>> >>> cheers, >>> patpro >> Jules >> >> -- >> Julian Field MEng CEng CITP MBCS MIEEE MACM >> >> 'Find a place inside where there's joy, and the joy will burn out >> the pain.' - Joseph Campbell >> >> www.Zend.To >> Twitter: @JulesFM >> Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'There have been nearly 3000 Gods so far but only yours actually exists. The others are silly made up nonsense. But not yours. Yours is real.' - Anon www.Zend.To Twitter: @JulesFM From Jules at Zend.To Fri Feb 8 09:54:26 2019 From: Jules at Zend.To (Jules Field) Date: Fri, 8 Feb 2019 09:54:26 +0000 Subject: [ZendTo] ANNOUNCE: 5.17-1 production release In-Reply-To: References: <9FBBA633-6855-4DDD-8CB3-7D2F32477527@m.patpro.net> <7F6CAC77-F639-4FF8-81A8-E8BC858F2212@m.patpro.net>

Message-ID: I always just run stuff like that as root. Presumably you were ending up with the wrong permissions on the zendto.mo files? They should just be world readable. You do need to remember to "su -" and not just "su" though. Unix101. :-) Glad you found and fixed the problem though! Cheers, Jules. On 07/02/2019 19:50, patpro via ZendTo wrote: > And full disclosure? it helped me find out what went wrong in my manual install. > > -> sudo -u www bash bin/makelanguages > > it solved my locale problem :/ > My bad. > > >> On 07 f?vr. 2019, at 20:33, patpro via ZendTo wrote: >> >> I've just ran the install script on a blank FreeBSD VM, it went very smoothly. Nice work :) >> >> Just one mistake: "Is it okay for me to configure SELinux for ZendTo (y/n) [Default is y]:" <-- this one is irrelevant. On FreebSD it should be masked or default to "n". >> >> cheers, >> patpro >> >> >> On 07 f?vr. 2019, at 18:17, patpro via ZendTo wrote: >>> Hi Jules, >>> >>> Sorry for the very late reply. >>> Thank you for your work about FreeBSD compatibility. Unfortunately it's very unlikely someone ever use this installer on FreeBSD. It's just not the way we install software on this platform. >>> We also don't use /opt, unless it's a fully autonomous piece of proprietary software (Splunk for example). Everything else that is not part of the base system goes into /usr/local/{bin,sbin,share,www,...} >>> >>> It's very good, though, to create a quick&dirty test server, but the fact this installer will play around with pkg makes it very difficult to run on a production platform (I won't run it on my personal server for example, it could literally break everything :) ). >>> >>> I'm going to setup a blank FreeBSD VM for testing and see what's wrong with locales on my production server. >>> Thanks again for the work! >>> >>> patpro >>> >>> >>> >>>> On 31 janv. 2019, at 17:23, Jules Field wrote: >>>> >>>> patpro, >>>> >>>> Download and try out the latest Beta Installer from >>>> https://zend.to/files/install-beta.ZendTo.tgz >>>> You should find that produces a working FreeBSD system on FreeBSD 11.2 and 12. >>>> >>>> I've also made a load of improvements to the "upgrade" utility so that it works with tarball-based ZendTo installations. >>>> It hopes that you are using a structure like >>>> /opt/ZendTo- >>>> directory for each version you have, and /opt/zendto is a symlink to the current production one. >>>> That's what the Installer will set up for you. >>>> If you do that, then >>>> /opt/zendto/bin/upgrade >>>> should automatically find your last version and your newest version and do all the relevant magic. >>>> >>>> I strongly advise >>>> /opt/zendto/bin/upgrade --dry-run >>>> the first time though, so it just tells you what it would do! >>>> >>>> I didn't have locale or language problems at all, it all just worked. >>>> >>>> Cheers, >>>> Jules. >>>> >>>> On 24/01/2019 19:42, patpro wrote: >>>>> Jules, >>>>> >>>>>> I've setup a FreeBSD 11.2 box and am working on getting the ZendTo Installer to do it all for you. >>>>>> It will use the .tgz of ZendTo, hopefully that will be okay. >>>>> That's very nice! Thanks. >>>>> >>>>> >>>>>> I'll have to make the "upgrade" script a bit more clever so that it notices when it's on FreeBSD as the old versions of the preferences.php and zendto.conf will be in different places. But it should still be able to do the bulk of the job for you. >>>>> If you want to package a software that can be un-archived on top of an older version of itself, you might want to name config files with a suffix, say "preferences.php.sample" or "zendto.conf.dist". Then when you unpack the new version on top of the old one, existing config files are not erased. Users (or upgrade script) can then synch old config with new parameters from .sample/.dist files. >>>>> >>>>> cheers, >>>>> patpro >>>> Jules >>>> >>>> -- >>>> Julian Field MEng CEng CITP MBCS MIEEE MACM >>>> >>>> 'Find a place inside where there's joy, and the joy will burn out >>>> the pain.' - Joseph Campbell >>>> >>>> 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 > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'A committee is a group of the unwilling, chosen from the unfit, to do the unnecessary.' - Anon www.Zend.To Twitter: @JulesFM From zend.to at neilzone.co.uk Tue Feb 12 09:07:30 2019 From: zend.to at neilzone.co.uk (zend.to at neilzone.co.uk) Date: Tue, 12 Feb 2019 09:07:30 +0000 Subject: [ZendTo] Purging the list of previous recipients References: Message-ID: Sorry if I am overlooking something obvious. Is there a way of purging the list of previous recipients of zend.to transfers? Or perhaps even disabling retaining recipient information completely? Best wishes Neil -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Tue Feb 12 12:09:24 2019 From: Jules at Zend.To (Jules Field) Date: Tue, 12 Feb 2019 12:09:24 +0000 Subject: [ZendTo] Purging the list of previous recipients In-Reply-To: References: Message-ID: <36d04c6f-c19f-3bfe-2d20-cefeeb2c5a10@Zend.To> Neil, Are you talking about the automatic "address book" feature in the "New Dropoff" form? Or any other records as well / instead? Cheers, Jules. On 12/02/2019 09:07, Neil via ZendTo wrote: > Sorry if I am overlooking something obvious. Is there a way of purging > the list of previous recipients of zend.to transfers? > > Or perhaps even disabling retaining recipient information completely? > > Best wishes > > Neil > > > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'When a man points a finger at someone else, he should remember that four of his fingers are pointing at himself.' - Louis Nizer www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From R.A.Gardener at shu.ac.uk Thu Feb 21 09:26:09 2019 From: R.A.Gardener at shu.ac.uk (Gardener, Ray A) Date: Thu, 21 Feb 2019 09:26:09 +0000 Subject: [ZendTo] support for x-forwarded-for headers References: Message-ID: Hi, Access to our zendto installation is behind an F5 load-balancing proxy. The affect of this is that the IP addresses of client access all look to come from the IP address associated with the proxy rather than the actual IP address of the client machines. The proxy address is what is captured in the zendto database and is included in the reports which zendto sends out. For security it would be useful to see the client IP addresses. The Apache server can be configured to log this as an x-forwarded-for address https://en.wikipedia.org/wiki/X-Forwarded-For is there any way that zendto con be configured to use either x-forwarded-for or a similar mechanism to log and report the real IP address of the client? Ray Gardener Infrastructure Analyst Digital Technology Services Sheffield Hallam University 0114 225 4926 -------------- next part -------------- An HTML attachment was scrubbed... URL: From damjan at povej.net Thu Feb 21 09:31:35 2019 From: damjan at povej.net (Damjan Hajsek) Date: Thu, 21 Feb 2019 10:31:35 +0100 Subject: [ZendTo] no login References: <00d101d4c9c8$3d6d4340$b847c9c0$@povej.net> Message-ID: Hi Is it possible to have zendto for users which have no username and password?? So anyone can send files? But It can be limited to 5Gb for example. Bets regards Damian -------------- next part -------------- An HTML attachment was scrubbed... URL: From armando.mart1s at gmail.com Thu Feb 21 09:39:33 2019 From: armando.mart1s at gmail.com (Armando Martins) Date: Thu, 21 Feb 2019 10:39:33 +0100 Subject: [ZendTo] support for x-forwarded-for headers In-Reply-To: References:

Message-ID: Hi, you can use the rpaf apache module. I use this behind haproxy and it works fine. Le jeu. 21 f?vr. 2019 ? 10:27, Gardener, Ray A via ZendTo a ?crit : > Hi, > > > > Access to our zendto installation is behind an F5 load-balancing proxy. > The affect of this is that the IP addresses of client access all look to > come from the IP address associated with the proxy rather than the actual > IP address of the client machines. The proxy address is what is > captured in the zendto database and is included in the reports which > zendto sends out. For security it would be useful to see the client IP > addresses. The Apache server can be configured to log this as an > x-forwarded-for address > > > > https://en.wikipedia.org/wiki/X-Forwarded-For > > > > is there any way that zendto con be configured to use either > x-forwarded-for or a similar mechanism to log and report the real IP > address of the client? > > > > > > > > Ray Gardener > > Infrastructure Analyst > > Digital Technology Services > > Sheffield Hallam University > > 0114 225 4926 > > > > > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto > -- Armando Martins -------------- next part -------------- An HTML attachment was scrubbed... URL: From R.A.Gardener at shu.ac.uk Thu Feb 21 10:26:13 2019 From: R.A.Gardener at shu.ac.uk (Gardener, Ray A) Date: Thu, 21 Feb 2019 10:26:13 +0000 Subject: [ZendTo] support for x-forwarded-for headers In-Reply-To: References:

Message-ID: Hi Armando, Thanks for this. Would I just need to configure the rpaf module on Apache? Is there anything else that needs doing in the zendto configuration? Ray Gardener Infrastructure Analyst Digital technology Services Sheffield Hallam University 0114 225 4926 From: ZendTo On Behalf Of Armando Martins via ZendTo Sent: 21 February 2019 09:40 To: ZendTo Users Cc: Armando Martins Subject: Re: [ZendTo] support for x-forwarded-for headers Hi, you can use the rpaf apache module. I use this behind haproxy and it works fine. Le jeu. 21 f?vr. 2019 ? 10:27, Gardener, Ray A via ZendTo > a ?crit : Hi, Access to our zendto installation is behind an F5 load-balancing proxy. The affect of this is that the IP addresses of client access all look to come from the IP address associated with the proxy rather than the actual IP address of the client machines. The proxy address is what is captured in the zendto database and is included in the reports which zendto sends out. For security it would be useful to see the client IP addresses. The Apache server can be configured to log this as an x-forwarded-for address https://en.wikipedia.org/wiki/X-Forwarded-For is there any way that zendto con be configured to use either x-forwarded-for or a similar mechanism to log and report the real IP address of the client? Ray Gardener Infrastructure Analyst Digital Technology Services Sheffield Hallam University 0114 225 4926 _______________________________________________ ZendTo mailing list ZendTo at zend.to http://jul.es/mailman/listinfo/zendto -- Armando Martins -------------- next part -------------- An HTML attachment was scrubbed... URL: From armando.mart1s at gmail.com Thu Feb 21 10:31:41 2019 From: armando.mart1s at gmail.com (Armando Martins) Date: Thu, 21 Feb 2019 11:31:41 +0100 Subject: [ZendTo] support for x-forwarded-for headers In-Reply-To: References:

Message-ID: You're welcome ;) You just need to configure the rpaf module and stop using x-forwarded-for for you apache logs. Rpaf do all the job. Explanation from the author: ?Rpaf changes the remote address of the client visible to other Apache modules when two conditions are satisfied. First condition is that the remote client is actually a proxy that is defined in module configuration. Secondly if there is an incoming X-Forwarded-For header and the proxy is in it's list of known proxies it takes the last IP from the incoming X-Forwarded-For header and changes the remote address of the client in the request structure.? Le jeu. 21 f?vr. 2019 ? 11:26, Gardener, Ray A a ?crit : > Hi Armando, > > > > > > Thanks for this. Would I just need to configure the rpaf module on > Apache? Is there anything else that needs doing in the zendto > configuration? > > > > > > Ray Gardener > > Infrastructure Analyst > > Digital technology Services > > Sheffield Hallam University > > 0114 225 4926 > > > > > > > > *From:* ZendTo *On Behalf Of *Armando Martins > via ZendTo > *Sent:* 21 February 2019 09:40 > *To:* ZendTo Users > *Cc:* Armando Martins > *Subject:* Re: [ZendTo] support for x-forwarded-for headers > > > > Hi, > > > > you can use the rpaf apache module. I use this behind haproxy and it works > fine. > > > > Le jeu. 21 f?vr. 2019 ? 10:27, Gardener, Ray A via ZendTo > a ?crit : > > Hi, > > > > Access to our zendto installation is behind an F5 load-balancing proxy. > The affect of this is that the IP addresses of client access all look to > come from the IP address associated with the proxy rather than the actual > IP address of the client machines. The proxy address is what is > captured in the zendto database and is included in the reports which > zendto sends out. For security it would be useful to see the client IP > addresses. The Apache server can be configured to log this as an > x-forwarded-for address > > > > https://en.wikipedia.org/wiki/X-Forwarded-For > > > > is there any way that zendto con be configured to use either > x-forwarded-for or a similar mechanism to log and report the real IP > address of the client? > > > > > > > > Ray Gardener > > Infrastructure Analyst > > Digital Technology Services > > Sheffield Hallam University > > 0114 225 4926 > > > > > > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto > > > > > -- > > Armando Martins > -- Armando Martins -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailinglists at pcfreak.de Thu Feb 21 14:21:18 2019 From: mailinglists at pcfreak.de (Der PCFreak) Date: Thu, 21 Feb 2019 15:21:18 +0100 Subject: [ZendTo] [Feature Request custom string in subject per DropOff] References: Message-ID: Hi Jules, hi all. I have a strange request from our ZendTo users. They asked if it would be possible to add a custom field when sending a DropOff that results in a custom text in all ZendTo email concerning this specific DropOff. Example current: [ZENDTO] One of the recipients has picked up your drop-off! Example requested: [ZENDTO] CUSTOM_STRING One of the recipients has picked up your drop-off! I asked a little bit about the purpose of their request and they told me that project teams sort their email by subject and consequently keep the project name (CUSTOM_STRING) in every subject of their emails concerning that specific project. So later they could sort by project name (CUSTOM_STRING) within Outlook to be able to verify when they sent a specific DropOff. Question: Is it possible to implement such a feature? I know that I could handcraft it but I don't want to make big changes to the source and always have to keep track of them when upgrading. I am currently not on the latest version of ZendTo, so if such a feature is maybe already present in the latest version, feel free to tell me. Thanks in advance. Peter From john.thurston at alaska.gov Thu Feb 21 17:03:10 2019 From: john.thurston at alaska.gov (John Thurston) Date: Thu, 21 Feb 2019 08:03:10 -0900 Subject: [ZendTo] support for x-forwarded-for headers In-Reply-To: References:

Message-ID: I do the same. My notes indicate I have edited rpaf.conf to replace RPAFproxy_ips 127.0.0.1 ::1 with RPAFproxy_ips 10.11.12.13\nRPAFheader X-Forwarded-For where 10.11.12.13 is address of my proxy. -- 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 2/21/2019 12:39 AM, Armando Martins via ZendTo wrote: > you can use the rpaf apache module. I use this behind haproxy and it > works fine. From kbe2 at lehigh.edu Thu Feb 21 17:21:05 2019 From: kbe2 at lehigh.edu (Keith Erekson) Date: Thu, 21 Feb 2019 12:21:05 -0500 Subject: [ZendTo] support for x-forwarded-for headers In-Reply-To: References:

Message-ID: We use mod_remoteip for this https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html Conf is very simple, and this module is built into the Debian/Ubuntu package: ??????? RemoteIPHeader X-Forwarded-For ??????? RemoteIPTrustedProxy x.x.x.x y.y.y.y On 2/21/19 5:31 AM, Armando Martins via ZendTo wrote: > You're welcome ;)? > You just need to configure the rpaf module and stop using > x-forwarded-for for you apache logs. Rpaf do all the job. > > Explanation from the author: > > ?Rpaf changes the remote address of the client visible to other Apache > modules when two conditions are satisfied. First condition is that the > remote client is actually a proxy that is defined in module > configuration. Secondly if there is an incoming X-Forwarded-For header > and the proxy is in it's list of known proxies it takes the last IP > from the incoming X-Forwarded-For header and changes the remote > address of the client in the request structure.? > > Le?jeu. 21 f?vr. 2019 ??11:26, Gardener, Ray A > a ?crit?: > > Hi Armando, > > ? > > ? > > Thanks for? this. Would I just need to configure the rpaf module? > on Apache?? Is? there anything else ?that needs doing in the > zendto configuration? > > ? > > ? > > Ray Gardener > > Infrastructure Analyst > > Digital technology Services > > Sheffield Hallam University > > 0114 225 4926 > > ? > > ? > > ? > > *From:*ZendTo

Message-ID: Ray, ZendTo already supports the X-Forwarded-For header. Our setup at the University of Southampton is also behind an F5, and it all works fine. I haven't installed any extra Apache modules to make it work. The only problem we had was when our enterprise IT folks hadn't enabled the X-Forwarded-For header on the F5 config that was for the ZendTo service (dropoff.soton.ac.uk). Are you using the latest version of ZendTo? Cheers, Jules. On 21/02/2019 10:31 am, Armando Martins via ZendTo wrote: > You're welcome ;) > You just need to configure the rpaf module and stop using > x-forwarded-for for you apache logs. Rpaf do all the job. > > Explanation from the author: > > ?Rpaf changes the remote address of the client visible to other Apache > modules when two conditions are satisfied. First condition is that the > remote client is actually a proxy that is defined in module > configuration. Secondly if there is an incoming X-Forwarded-For header > and the proxy is in it's list of known proxies it takes the last IP > from the incoming X-Forwarded-For header and changes the remote > address of the client in the request structure.? > > Le?jeu. 21 f?vr. 2019 ??11:26, Gardener, Ray A > a ?crit?: > > Hi Armando, > > Thanks for? this. Would I just need to configure the rpaf module? > on Apache?? Is there anything else ?that needs doing in the zendto > configuration? > > Ray Gardener > > Infrastructure Analyst > > Digital technology Services > > Sheffield Hallam University > > 0114 225 4926 > > *From:*ZendTo

> *On Behalf Of *Armando Martins > via ZendTo > *Sent:* 21 February 2019 09:40 > *To:* ZendTo Users > > *Cc:* Armando Martins > > *Subject:* Re: [ZendTo] support for x-forwarded-for headers > > Hi, > > you can use the rpaf apache module. I use this behind haproxy and > it works fine. > > Le?jeu. 21 f?vr. 2019 ??10:27, Gardener, Ray A via ZendTo > > a ?crit?: > > Hi, > > Access to our zendto installation is behind an F5 > load-balancing proxy.? The affect of this is that the IP > addresses of client access all look to come from? the IP > address associated with the proxy rather than the actual ?IP > address of the client machines. ???The proxy address is what > ?is captured in the zendto database and is included in? the > reports which zendto sends out. ??For security it would be > useful to see the? client IP addresses.?? The Apache server > can be configured to log this? as? an? x-forwarded-for address > > https://en.wikipedia.org/wiki/X-Forwarded-For > > is there any way that zendto con be configured to use either > x-forwarded-for or a similar mechanism? to log and report the > real IP address of the client? > > Ray Gardener > > Infrastructure Analyst > > Digital Technology Services > > Sheffield Hallam University > > 0114 225 4926 > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto > > > -- > > Armando Martins > > > > -- > Armando Martins > > _______________________________________________ > 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: Fisher: Variable 3 or 4, becoming west 4 or 5 later. Slight or moderate. Fog banks. Moderate or good, occasionally very poor. www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Sun Feb 24 13:59:14 2019 From: Jules at Zend.To (Jules) Date: Sun, 24 Feb 2019 13:59:14 +0000 Subject: [ZendTo] no login In-Reply-To: References: <00d101d4c9c8$3d6d4340$b847c9c0$@povej.net> Message-ID: <523b0146-897e-b27f-8679-43aa4d56f5d2@Zend.To> Damjan, Users who can't login (i.e "external users") can send files to "internal users" who can login. The "internaldomains.conf" file lists the email domains that are considered to be "internal". So someone who cannot login can send files to anyone who has an email address in one of the domains listed in "internaldomains.conf". ZendTo specifically prohibits external users sending files to other external users. If you allowed that, you would be the world centre for distributing pr0n and dodgy software within 24 hours! You really don't want that. I hope that answers your question. Cheers, Jules. On 21/02/2019 9:31 am, Damjan Hajsek via ZendTo wrote: > > Hi > > Is it possible to have zendto for users which have no username and > password?? > > So anyone can send files? But It can be limited to 5Gb for example. > > Bets regards > > Damian > > > _______________________________________________ > 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: Fisher: Variable 3 or 4, becoming west 4 or 5 later. Slight or moderate. Fog banks. Moderate or good, occasionally very poor. www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Sun Feb 24 14:04:04 2019 From: Jules at Zend.To (Jules) Date: Sun, 24 Feb 2019 14:04:04 +0000 Subject: [ZendTo] Content Security Policy In-Reply-To: References: <218d111d-7b48-19aa-8d12-d783243db4a8@stony.com> Message-ID: Viktor, Agreed, I should move the JS out of the template files. I've just never had a good reason to do so before, so never bothered. :-) I'll add it to the list of jobs to do. Cheers, Jules. On 22/02/2019 7:40 am, Viktor Steinmann via ZendTo wrote: > Good morning all > > I have been playing around with Content Security Headers for ZendTo, > but didn't manage to get them completely right. Does someone have a > working set of of CSP headers available to share? > > While we're at it: Inline JavaScript kills part of any CSP, as it > required an "unsafe-inline" part in the policy. If all JavaScript > could be extracted from the HTML and put into separate .js files, the > CSP could be tightened even more. Increasing security would be cool, > right? ;-) > > Kind regards, > > Viktor > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'Find a place inside where there's joy, and the joy will burn out the pain.' - Joseph Campbell www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From stony at stony.com Sun Feb 24 16:20:11 2019 From: stony at stony.com (Viktor Steinmann) Date: Sun, 24 Feb 2019 17:20:11 +0100 Subject: [ZendTo] Content Security Policy In-Reply-To: References: <218d111d-7b48-19aa-8d12-d783243db4a8@stony.com>

<2ec2cbb8-9be8-c022-7fcb-0f8a4a4b2a84@stony.com> Message-ID: Jules, I just figured, the same is true for inline CSS. Would be great, if this could be implemented some day. Kind regards, Viktor Am 24.02.2019 um 15:04 schrieb Jules: > Viktor, > > Agreed, I should move the JS out of the template files. I've just > never had a good reason to do so before, so never bothered. :-) > > I'll add it to the list of jobs to do. > > Cheers, > Jules. > > On 22/02/2019 7:40 am, Viktor Steinmann via ZendTo wrote: >> Good morning all >> >> I have been playing around with Content Security Headers for ZendTo, >> but didn't manage to get them completely right. Does someone have a >> working set of of CSP headers available to share? >> >> While we're at it: Inline JavaScript kills part of any CSP, as it >> required an "unsafe-inline" part in the policy. If all JavaScript >> could be extracted from the HTML and put into separate .js files, the >> CSP could be tightened even more. Increasing security would be cool, >> right? ;-) >> >> Kind regards, >> >> Viktor >> >> >> _______________________________________________ >> ZendTo mailing list >> ZendTo at zend.to >> http://jul.es/mailman/listinfo/zendto > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'Find a place inside where there's joy, and the joy will burn out > the pain.' - Joseph Campbell > > www.Zend.To > Twitter: @JulesFM From R.A.Gardener at shu.ac.uk Sun Feb 24 23:05:52 2019 From: R.A.Gardener at shu.ac.uk (Gardener, Ray A) Date: Sun, 24 Feb 2019 23:05:52 +0000 Subject: [ZendTo] support for x-forwarded-for headers In-Reply-To: References:

Message-ID: Jules, Thanks for the reply, The current version is 4.11. However I am updating to the latest version of 5 on a new server in the next two weeks. I have already installed rpaf on both the old and new install but will disable it on the new install and test prior to deployment. Ray Gardener From: Jules Sent: 24 February 2019 13:55 To: ZendTo Users ; Gardener, Ray A Cc: Armando Martins Subject: Re: [ZendTo] support for x-forwarded-for headers Ray, ZendTo already supports the X-Forwarded-For header. Our setup at the University of Southampton is also behind an F5, and it all works fine. I haven't installed any extra Apache modules to make it work. The only problem we had was when our enterprise IT folks hadn't enabled the X-Forwarded-For header on the F5 config that was for the ZendTo service (dropoff.soton.ac.uk). Are you using the latest version of ZendTo? Cheers, Jules. On 21/02/2019 10:31 am, Armando Martins via ZendTo wrote: You're welcome ;) You just need to configure the rpaf module and stop using x-forwarded-for for you apache logs. Rpaf do all the job. Explanation from the author: ?Rpaf changes the remote address of the client visible to other Apache modules when two conditions are satisfied. First condition is that the remote client is actually a proxy that is defined in module configuration. Secondly if there is an incoming X-Forwarded-For header and the proxy is in it's list of known proxies it takes the last IP from the incoming X-Forwarded-For header and changes the remote address of the client in the request structure.? Le jeu. 21 f?vr. 2019 ? 11:26, Gardener, Ray A > a ?crit : Hi Armando, Thanks for this. Would I just need to configure the rpaf module on Apache? Is there anything else that needs doing in the zendto configuration? Ray Gardener Infrastructure Analyst Digital technology Services Sheffield Hallam University 0114 225 4926 From: ZendTo > On Behalf Of Armando Martins via ZendTo Sent: 21 February 2019 09:40 To: ZendTo Users > Cc: Armando Martins > Subject: Re: [ZendTo] support for x-forwarded-for headers Hi, you can use the rpaf apache module. I use this behind haproxy and it works fine. Le jeu. 21 f?vr. 2019 ? 10:27, Gardener, Ray A via ZendTo > a ?crit : Hi, Access to our zendto installation is behind an F5 load-balancing proxy. The affect of this is that the IP addresses of client access all look to come from the IP address associated with the proxy rather than the actual IP address of the client machines. The proxy address is what is captured in the zendto database and is included in the reports which zendto sends out. For security it would be useful to see the client IP addresses. The Apache server can be configured to log this as an x-forwarded-for address https://en.wikipedia.org/wiki/X-Forwarded-For is there any way that zendto con be configured to use either x-forwarded-for or a similar mechanism to log and report the real IP address of the client? Ray Gardener Infrastructure Analyst Digital Technology Services Sheffield Hallam University 0114 225 4926 _______________________________________________ ZendTo mailing list ZendTo at zend.to http://jul.es/mailman/listinfo/zendto -- Armando Martins -- Armando Martins _______________________________________________ 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: Fisher: Variable 3 or 4, becoming west 4 or 5 later. Slight or moderate. Fog banks. Moderate or good, occasionally very poor. www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Tue Feb 26 10:19:26 2019 From: Jules at Zend.To (Jules Field) Date: Tue, 26 Feb 2019 10:19:26 +0000 Subject: [ZendTo] support for x-forwarded-for headers In-Reply-To: References:

Message-ID: <6915abb6-9a68-34b7-9f79-12e8ce55e603@Zend.To> Ray, That sounds good. 4.11 certainly won't understand things like X-Forwarded-For. Cheers, Jules. On 24/02/2019 23:05, Gardener, Ray A wrote: > > Jules, > > Thanks for the reply, > > The current version is 4.11. However I am updating to? the latest > version of 5 on a new server in the next two weeks. I have already > installed rpaf on both the old and new install? but will disable it on > the new install and test prior to deployment. > > Ray Gardener > > *From:*Jules > *Sent:* 24 February 2019 13:55 > *To:* ZendTo Users ; Gardener, Ray A > > *Cc:* Armando Martins > *Subject:* Re: [ZendTo] support for x-forwarded-for headers > > Ray, > > ZendTo already supports the X-Forwarded-For header. > > Our setup at the University of Southampton is also behind an F5, and > it all works fine. > I haven't installed any extra Apache modules to make it work. > > The only problem we had was when our enterprise IT folks hadn't > enabled the X-Forwarded-For header on the F5 config that was for the > ZendTo service (dropoff.soton.ac.uk). > > Are you using the latest version of ZendTo? > > Cheers, > Jules. > > On 21/02/2019 10:31 am, Armando Martins via ZendTo wrote: > > You're welcome ;) > > You just need to configure the rpaf module and stop using > x-forwarded-for for you apache logs. Rpaf do all the job. > > Explanation from the author: > > ?Rpaf changes the remote address of the client visible to other > Apache modules when two conditions are satisfied. First condition > is that the remote client is actually a proxy that is defined in > module configuration. Secondly if there is an incoming > X-Forwarded-For header and the proxy is in it's list of known > proxies it takes the last IP from the incoming X-Forwarded-For > header and changes the remote address of the client in the request > structure.? > > Le?jeu. 21 f?vr. 2019 ??11:26, Gardener, Ray A > > a ?crit?: > > Hi Armando, > > Thanks for? this. Would I just need to configure the rpaf > module? on Apache?? Is? there anything else ?that needs doing > in the zendto configuration? > > Ray Gardener > > Infrastructure Analyst > > Digital technology Services > > Sheffield Hallam University > > 0114 225 4926 > > *From:*ZendTo

> *On Behalf Of *Armando > Martins via ZendTo > *Sent:* 21 February 2019 09:40 > *To:* ZendTo Users > > *Cc:* Armando Martins > > *Subject:* Re: [ZendTo] support for x-forwarded-for headers > > Hi, > > you can use the rpaf apache module. I use this behind haproxy > and it works fine. > > Le?jeu. 21 f?vr. 2019 ??10:27, Gardener, Ray A via ZendTo > > a ?crit?: > > Hi, > > Access to our zendto installation is behind an F5 > load-balancing proxy.? The affect of this is that the IP > addresses of client access all look to come from? the IP > address associated with the proxy rather than the actual > ?IP address of the client machines. ???The proxy address > is what ?is captured in the zendto database and is > included in? the reports which zendto sends out. ??For > security it would be useful to see the? client IP > addresses.?? The Apache server can be configured to log > this? as? an x-forwarded-for address > > https://en.wikipedia.org/wiki/X-Forwarded-For > > is there any way that zendto? con be configured to use > either x-forwarded-for or a similar mechanism? to log and > report the real IP address of the client? > > Ray Gardener > > Infrastructure Analyst > > Digital Technology Services > > Sheffield Hallam University > > 0114 225 4926 > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto > > > -- > > Armando Martins > > > -- > > Armando Martins > > > > _______________________________________________ > > 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: > Fisher: Variable 3 or 4, becoming west 4 or 5 later. Slight or moderate. Fog > banks. Moderate or good, occasionally very poor. > www.Zend.To > Twitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'I have lost friends, some by death ... others through sheer inability to cross the street.' - Virginia Woolf www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.martel at vsc.edu Tue Feb 26 15:04:53 2019 From: michael.martel at vsc.edu (Martel, Michael H.) Date: Tue, 26 Feb 2019 15:04:53 +0000 Subject: [ZendTo] Finding unclaimed drop off's. References: Message-ID: Greetings! We are in the midst of setting up a new ZendTo server to replace our old one, and were wondering if we can see if there are any unclaimed drop off's before we replace the old server ? I assume, I will need to get into the database and write a query of some sort, but was hoping someone had already done it. Thanks! Michael -- --------------------------------o--------------------------------- Michael H. Martel | Director of Data Center Administration michael.martel at vsc.edu | Systems and Security Administrator Vermont State Colleges | PH:802-224-3010 FX:802-224-3035 From michael.martel at vsc.edu Tue Feb 26 18:04:02 2019 From: michael.martel at vsc.edu (Martel, Michael H.) Date: Tue, 26 Feb 2019 18:04:02 +0000 Subject: [ZendTo] Finding unclaimed drop off's. In-Reply-To: References: Message-ID: As is usual, I suspect if I just didn't drink as much coffee I might find the answer before I post. It appears that I can do this : select rowID,created from dropoff left join pickup on dId = rowID where dID is null; And that appears to produce what I am looking for. DOH. Sorry to waste your time! Michael -- --------------------------------o--------------------------------- Michael H. Martel | Director of Data Center Administration michael.martel at vsc.edu | Systems and Security Administrator Vermont State Colleges | PH:802-224-3010 FX:802-224-3035 -----Original Message----- From: ZendTo On Behalf Of Martel, Michael H. via ZendTo Sent: Tuesday, February 26, 2019 10:05 AM To: zendto at zend.to Cc: Martel, Michael H. Subject: [ZendTo] Finding unclaimed drop off's. This message is from an external sender. Please be careful when clicking on links and attachments. Greetings! We are in the midst of setting up a new ZendTo server to replace our old one, and were wondering if we can see if there are any unclaimed drop off's before we replace the old server ? I assume, I will need to get into the database and write a query of some sort, but was hoping someone had already done it. Thanks! Michael -- --------------------------------o--------------------------------- Michael H. Martel | Director of Data Center Administration michael.martel at vsc.edu | Systems and Security Administrator Vermont State Colleges | PH:802-224-3010 FX:802-224-3035 _______________________________________________ ZendTo mailing list ZendTo at zend.to https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=02%7C01%7Cmichael.martel%40vsc.edu%7C64182a6ab1ca4ab71c4808d69c05d94a%7Cb17e9703dbdd49fa909c03dfd13086af%7C1%7C0%7C636867946282926303&sdata=Cnw9AugL2qyKAkcCIQ%2BxMYFbwS%2BYY3h0%2FC8JX2Tyb9g%3D&reserved=0