From TDavis at bleylengineering.com Tue Oct 2 17:19:40 2018 From: TDavis at bleylengineering.com (Tim Davis) Date: Tue, 2 Oct 2018 16:19:40 +0000 Subject: [ZendTo] Database Errors References: Message-ID: I have setup a brand new ZendTo server using Ubuntu 18.04, everything works except the main portion, drop-offs. This is the error I receive when trying to dropoff a file: Upload Error Unable to add a drop-off record to the database. Please notify the system administrator. I'm sure that it's something I have overlooked or missed in the documentation. Any assistance would be greatly appreciated. Regards, Tim Davis [New Bleyl logo 2016] Bleyl Engineering 100 Nugent Street Conroe, Texas 77301 Phone: 936.441.7833 Direct: 936.521.1377 Cell: 281.660.4677 Fax: 936.760.3833 tdavis at bleylengineering.com www.bleylengineering.com CONROE ? BRYAN ? HOUSTON ? AUSTIN <>< This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6818 bytes Desc: image001.jpg URL: From Jules at Zend.To Wed Oct 3 09:04:33 2018 From: Jules at Zend.To (Jules Field) Date: Wed, 3 Oct 2018 09:04:33 +0100 Subject: [ZendTo] Database Errors In-Reply-To: References: Message-ID: Tim, You probably created a new ZendTo user using adduser.php *before* browsing to your ZendTo's site home page. Delete /var/zendto/zendto.sqlite, *then* browse to your ZendTo site's home page. That triggers creation of the database with the correct ownership and permissions. Only *then* should you use adduser.php to create a new local user. Cheers, Jules. On 02/10/2018 17:19, Tim Davis via ZendTo wrote: > > I have setup a brand new ZendTo server using Ubuntu 18.04, everything > works except the main portion, drop-offs.? This is the error I receive > when trying to dropoff a file: > > Upload Error > > > > > Unable to add a drop-off record to the database. Please notify the > system administrator. > > I?m sure that it?s something I have overlooked or missed in the > documentation. > > Any assistance would be greatly appreciated. > > Regards, > > *Tim Davis* > > New Bleyl logo 2016 > > Bleyl Engineering > > 100 Nugent Street > > Conroe, Texas 77301 > > Phone: 936.441.7833 > > Direct: 936.521.1377 > > Cell: 281.660.4677 > > Fax: 936.760.3833 > > tdavis at bleylengineering.com > > www.bleylengineering.com > > CONROE???? ????? BRYAN???? ? HOUSTON????? ????? AUSTIN > > <>< > > This message contains confidential information and is intended only > for the individual named. If you are not the named addressee you > should not disseminate, distribute or copy this e-mail. Please notify > the sender immediately by e-mail if you have received this e-mail by > mistake and delete this e-mail from your system. E-mail transmission > cannot be guaranteed to be secure or error-free as information could > be intercepted, corrupted, lost, destroyed, arrive late or incomplete, > or contain viruses. The sender therefore does not accept liability for > any errors or omissions in the contents of this message, which arise > as a result of e-mail transmission. If verification is required please > request a hard-copy version. > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6818 bytes Desc: not available URL: From Jules at Zend.To Wed Oct 3 09:36:26 2018 From: Jules at Zend.To (Jules Field) Date: Wed, 3 Oct 2018 09:36:26 +0100 Subject: [ZendTo] Calling all translators (quick easy one this time!) Message-ID: <464e4195-3b1c-3fd8-bb00-945631da1c3d@Zend.To> Folks, 5.14 is nearly ready for release. The only change in text this time is for the "Add Recipient" (single and multiple) dialog box that appears as part of the New Drop-off form. - In the add single recipient box, I have replaced the "Add Recipient" button with 2 buttons: "Add" and "Add & Close". Hopefully this will be easier for novice users who don't know to click on the X icon or press Esc to close the dialog. - In the add multiple recipients box, I have improved the example entry shown. So the new strings I would like you to translate for me are: 1. "Add" 2. "Add & Close" 3. "Recipient's Name email at example.com" Please try to word the first 2 as short as possible, as they go into buttons. Many thanks all, your help is hugely appreciated! Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'The owls are not what they appear.' - David Lynch (indirectly) www.Zend.To Twitter: @JulesFM From TDavis at bleylengineering.com Wed Oct 3 14:52:51 2018 From: TDavis at bleylengineering.com (Tim Davis) Date: Wed, 3 Oct 2018 13:52:51 +0000 Subject: [ZendTo] Database Errors In-Reply-To: References: Message-ID: Thanks Jules that resolved my problem! Regards, Tim Davis Bleyl Engineering From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Jules Field via ZendTo Sent: Wednesday, October 03, 2018 3:05 AM To: Tim Davis via ZendTo Cc: Jules Field Subject: Re: [ZendTo] Database Errors Tim, You probably created a new ZendTo user using adduser.php *before* browsing to your ZendTo's site home page. Delete /var/zendto/zendto.sqlite, *then* browse to your ZendTo site's home page. That triggers creation of the database with the correct ownership and permissions. Only *then* should you use adduser.php to create a new local user. Cheers, Jules. On 02/10/2018 17:19, Tim Davis via ZendTo wrote: I have setup a brand new ZendTo server using Ubuntu 18.04, everything works except the main portion, drop-offs. This is the error I receive when trying to dropoff a file: Upload Error Unable to add a drop-off record to the database. Please notify the system administrator. I?m sure that it?s something I have overlooked or missed in the documentation. Any assistance would be greatly appreciated. Regards, Tim Davis [New Bleyl logo 2016] Bleyl Engineering 100 Nugent Street Conroe, Texas 77301 Phone: 936.441.7833 Direct: 936.521.1377 Cell: 281.660.4677 Fax: 936.760.3833 tdavis at bleylengineering.com www.bleylengineering.com CONROE ? BRYAN ? HOUSTON ? AUSTIN <>< This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. _______________________________________________ ZendTo mailing list ZendTo at zend.to http://jul.es/mailman/listinfo/zendto 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 This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6818 bytes Desc: image001.jpg URL: From gm.pawanthakur at gmail.com Wed Oct 10 15:58:11 2018 From: gm.pawanthakur at gmail.com (Pawan Thakur) Date: Wed, 10 Oct 2018 20:28:11 +0530 Subject: [ZendTo] New Installation - Admin Login - SMTP Configuration issues on AWS References: Message-ID: Hello All, I stumbled upon ZendTo and it fits all my needs as a file sharing Platform> I have setup this on Ubuntu 16 AWS machine. I have read the documentation carefully but either I am missing something or made a mistake but I am facing the following issues. 1. I see in preferences file admin Users admin1, admin2 and so on. How to access the system as an admin ? is there a default Password ? If not, How can I create one ? 2. I am trying to setup the email using basic SMTP, it is throwing an error. I created a one page php script to send mail with same settings and that works. Can some one please share a Snippet or screen shot of how can I setup SMTP I am sorry if there are silly questions, I tried spending time and researching and testing configs but the mail is not configured and hence I cannot even create user and test the system. I am running against a tight deadline and hence asking for help. Thanks in advance, Really appreciate any help. Pawan From klou at themusiclink.net Wed Oct 10 18:19:18 2018 From: klou at themusiclink.net (Kris Lou) Date: Wed, 10 Oct 2018 10:19:18 -0700 Subject: [ZendTo] New Installation - Admin Login - SMTP Configuration issues on AWS In-Reply-To: References: Message-ID: > 1. I see in preferences file admin Users admin1, admin2 and so on. How to > access the system as an admin ? is there a default Password ? If not, How > can I create one ? > This depends upon your authentication backend (https://zend.to/authenticatio n.php). There's a(n) /opt/zendto/bin/README.txt which should document the commands/scripts needed to create local users (admin1, admin2, etc.), but "adduser.php" is probably the one you're looking for. Execute that from CLI to add your first user and specify it as an Admin User in preferences.php. > 2. I am trying to setup the email using basic SMTP, it is throwing an > error. I created a one page php script to send mail with same settings and > that works. Can some one please share a Snippet or screen shot of how can I > setup SMTP I push emails to an external SMTP server, with only 'defaultEmailDomain', 'SMTPserver', 'SMTPport', 'SMTPsecure', and 'SMTPcharset' specified. No local configuration required. For the previous 3-4 months, ALL of those settings except 'defaultEmailDomain' and 'SMTPcharset' were commented out, so it used the default PHPMail but still worked. I would think that you still need Postfix or Sendmail on your local Zendto server, but still no local configuration required. Side note: By default, PHPMail sends out as "apache@.", so this may result in NEUTRAL grades if you have SPF set for < yourdomain.com>. I believe the outbound email address is set via PHP settings. However, using an external SMTP server bypasses this with a return address of "zendto@" or whatever you may have configured. Also, enabling 'SMTPdebug' might help you figure things out. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gm.pawanthakur at gmail.com Thu Oct 11 16:47:21 2018 From: gm.pawanthakur at gmail.com (Pawan Thakur) Date: Thu, 11 Oct 2018 21:17:21 +0530 Subject: [ZendTo] New Installation - Admin Login - SMTP Configuration issues on AWS In-Reply-To: References: <1fab1671-a584-192d-05d7-513472516fa7@gmail.com> Message-ID: Hello Kris, Thanks a lot for your swift reply. It helped me. While emails are still an issue, I created users and I can access the system and that's progress. 2 Issues with uploads 1. While uploading to the server, It gets stuck here. Screen I later checked my outbox, there was an entry and I could see the generated file link as well. 2. I could see the file and the link here. But clicking on the file / download all button goes into a loop and nothing happens. It's hardly a 4 KB file. === I started looking into this issue. Logs show messages about failed emails ( which I know is to be fixed ) but though it says Download is completed but nothing happened. *Note: *https://zend.to/clamavpermissions.php The memory issue**was there from CLAMAV and I configured SWAP and did an external setup for it. I am not using SELinux*. * *I am just going to debug the Emails but any help related to these files not working would be appreciated* Thanks, Pawan* * On 10/10/2018 10:49 PM, Kris Lou via ZendTo wrote: > > 1. I see in preferences file admin Users admin1, admin2 and so on. > How to access the system as an admin ? is there a default Password > ? If not, How can I create one ? > > > This depends upon your authentication backend > (https://zend.to/authentication.php > ). There's a(n) > /opt/zendto/bin/README.txt? which should document the commands/scripts > needed to create local users (admin1, admin2, etc.), but "adduser.php" > is probably the one you're looking for.? Execute that from CLI to add > your first user and specify it as an Admin User in preferences.php. > > 2. I am trying to setup the email using basic SMTP, it is throwing > an error. I created a one page php script to send mail with same > settings and that works. Can some one please share a Snippet or > screen shot of how can I setup SMTP > > > I push emails to an external SMTP server, with only > 'defaultEmailDomain', 'SMTPserver', 'SMTPport', 'SMTPsecure', and > 'SMTPcharset' specified.? No local configuration required. > > For the previous 3-4 months, ALL of those settings except > 'defaultEmailDomain' and 'SMTPcharset' were commented out, so it used > the default PHPMail but still worked.? I would think that you still > need Postfix or Sendmail on your local Zendto server, but still no > local configuration required. > > Side note:? By default, PHPMail sends out as > "apache@.>", so > this may result in NEUTRAL grades if you have SPF set for > >.? I believe the outbound > email address is set via PHP settings.? However, using an external > SMTP server bypasses this with a return address of > "zendto@>" or whatever you may > have configured. > > Also, enabling 'SMTPdebug' might help you figure things out. > > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: screen.png Type: image/png Size: 205935 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: epinddpimojjkpbl.png Type: image/png Size: 132770 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bjpjlnkpgjhkkimh.png Type: image/png Size: 99317 bytes Desc: not available URL: From klou at themusiclink.net Thu Oct 11 17:57:12 2018 From: klou at themusiclink.net (Kris Lou) Date: Thu, 11 Oct 2018 09:57:12 -0700 Subject: [ZendTo] New Installation - Admin Login - SMTP Configuration issues on AWS In-Reply-To: References: <1fab1671-a584-192d-05d7-513472516fa7@gmail.com> Message-ID: Verify that the uploaded file exists? If I recall, ClamAV and apache need write access to the uploads directory. The installer should already deal with this, but doesn't hurt to check. Kris Lou klou at themusiclink.net On Thu, Oct 11, 2018 at 8:47 AM, Pawan Thakur via ZendTo wrote: > Hello Kris, > > Thanks a lot for your swift reply. It helped me. > > While emails are still an issue, I created users and I can access the > system and that's progress. > > 2 Issues with uploads > > 1. While uploading to the server, It gets stuck here. > > [image: Screen] > > I later checked my outbox, there was an entry and I could see the > generated file link as well. > > 2. I could see the file and the link here. But clicking on the file / > download all button goes into a loop and nothing happens. It's hardly a 4 > KB file. > > > > === > > I started looking into this issue. Logs show messages about failed emails > ( which I know is to be fixed ) but though it says Download is completed > but nothing happened. > > > *Note: *https://zend.to/clamavpermissions.php > The memory issue was there from CLAMAV and I configured SWAP and did an > external setup for it. I am not using SELinux*. * > > *I am just going to debug the Emails but any help related to these files > not working would be appreciated* > > Thanks, > Pawan > On 10/10/2018 10:49 PM, Kris Lou via ZendTo wrote: > > > 1. I see in preferences file admin Users admin1, admin2 and so on. How to >> access the system as an admin ? is there a default Password ? If not, How >> can I create one ? >> > > This depends upon your authentication backend ( > https://zend.to/authentication.php). There's a(n) > /opt/zendto/bin/README.txt which should document the commands/scripts > needed to create local users (admin1, admin2, etc.), but "adduser.php" is > probably the one you're looking for. Execute that from CLI to add your > first user and specify it as an Admin User in preferences.php. > > >> 2. I am trying to setup the email using basic SMTP, it is throwing an >> error. I created a one page php script to send mail with same settings and >> that works. Can some one please share a Snippet or screen shot of how can I >> setup SMTP > > > I push emails to an external SMTP server, with only 'defaultEmailDomain', > 'SMTPserver', 'SMTPport', 'SMTPsecure', and 'SMTPcharset' specified. No > local configuration required. > > For the previous 3-4 months, ALL of those settings except > 'defaultEmailDomain' and 'SMTPcharset' were commented out, so it used the > default PHPMail but still worked. I would think that you still need > Postfix or Sendmail on your local Zendto server, but still no local > configuration required. > > Side note: By default, PHPMail sends out as "apache@.< > yourdomain.com>", so this may result in NEUTRAL grades if you have SPF > set for . I believe the outbound email address is set > via PHP settings. However, using an external SMTP server bypasses this > with a return address of "zendto@" or whatever you may > have configured. > > Also, enabling 'SMTPdebug' might help you figure things out. > > > > _______________________________________________ > ZendTo mailing listZendTo at zend.tohttp://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: -------------- next part -------------- A non-text attachment was scrubbed... Name: bjpjlnkpgjhkkimh.png Type: image/png Size: 99317 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: screen.png Type: image/png Size: 205935 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: epinddpimojjkpbl.png Type: image/png Size: 132770 bytes Desc: not available URL: From john.thurston at alaska.gov Thu Oct 11 22:03:20 2018 From: john.thurston at alaska.gov (John Thurston) Date: Thu, 11 Oct 2018 13:03:20 -0800 Subject: [ZendTo] Error: failed to add ---- record References: <7014be42-a282-4430-7f3a-f477e3ef159a@alaska.gov> Message-ID: I'm running 5.11 on CentOS. While looking in the logs to try to figure out a problem, I noticed many "Error: failed to add " lines. Since March, I have recorded: 233 "pickup" 106 "authdata" They seem to come in clumps. What is the cause of these errors, and how should I go about making them stop? -- 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 Fri Oct 12 00:03:31 2018 From: john.thurston at alaska.gov (John Thurston) Date: Thu, 11 Oct 2018 15:03:31 -0800 Subject: [ZendTo] Multi-cpu or thread use References: Message-ID: With the enabling of encryption in ZendTo, I've seen an increase in memory and CPU utilization. I'm running 5.11 on CentOS on VMWare. Today, I had the host bumped up to 3GB of ram (from 2GB). This seems a lot, but I duno how much clamav is using or if I have httpd rigged for multi-process or multi-thread. Does php work with either? Anyway... If I ask for another virtual process to be thrown at this, is the php going to be able to take advantage of it? That is, will it be able to virus scan one big file while simultaneously encrypting another? Will it matter how the work arrives? That is, if a user drops two files, is that going to be handled sequentially in one httpd process? But if two users on different httpd processes each drop one file, might they be handled in parallel? -- 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 guard1976 at gmail.com Fri Oct 12 14:36:58 2018 From: guard1976 at gmail.com (Jan H.) Date: Fri, 12 Oct 2018 16:36:58 +0300 Subject: [ZendTo] Restricting access by LDAP group membership in version 5.15-1 does not work In-Reply-To: References: Message-ID: Hi, everybody. Restricting access by LDAP group membership in version 5.15-1 does not work. When enabling this restrictions, the banner is displayed that says " Authorization Failed. Sorry, you are not authorized to use this service." but it is still possible to execute Drop-off (and other). -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrm at medicine.wisc.edu Fri Oct 12 15:28:38 2018 From: mrm at medicine.wisc.edu (MICHAEL R MASSE) Date: Fri, 12 Oct 2018 14:28:38 +0000 Subject: [ZendTo] manually retrieve an encrypted file? References: Message-ID: Is there a way as the administrator of the system hosting my Zendto service that I can decrypt a file that's been uploaded if I have the passphrase? I have direct access to the sqlite database to get the key as well, but I'm not sure what to do with either. I'm running 5.15-1 and the system works fine except one single user is trying to receive a file from someone outside of the system and when they try to download this specific file after typing in the passphrase they just get a http 500 error. The sender does not receive any errors when uploading. It actually doesn't matter if the recipient types a correct passphrase or not, they always get an http 500 error on this particular file. As an administrator if I try to download the file and regardless of the passphrase I enter (correct or not) I get an http 500 error as well. This does not happen for anyone else for any other files in the system sent before or after. Also, for every other file on the system, if an incorrect passphrase is used, the system says it's incorrect like it should instead of giving an http 500 error. I told the person to have their sender send the file again, and it again throws an http 500 error. It's only a 2mb file so there's nothing weird about it. After telling them to upload the file twice and having it fail I'd like to just decrypt the file that's there and manually give it to the recipient since he's local, and then worry about troubleshooting the problem later. -Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From gm.pawanthakur at gmail.com Sun Oct 14 22:45:46 2018 From: gm.pawanthakur at gmail.com (Pawan Thakur) Date: Mon, 15 Oct 2018 03:15:46 +0530 Subject: [ZendTo] New Installation - Admin Login - SMTP Configuration issues on AWS In-Reply-To: References: <1fab1671-a584-192d-05d7-513472516fa7@gmail.com> <8e751c16-be79-bb10-6b28-a5ca356ea887@gmail.com> Message-ID: Hello Kris, The downloads strangely, starts but then gives network timeout. I verified the folder permissions .. Drop-off Folder Permissions look like this. Any help appreciated, I am stuck. Thanks, Pawan On 10/11/2018 10:27 PM, Kris Lou via ZendTo wrote: > Verify that the uploaded file exists?? If I recall, ClamAV and apache > need write access to the uploads directory. The installer should > already deal with this, but doesn't hurt to check. > > > Kris Lou > klou at themusiclink.net > > On Thu, Oct 11, 2018 at 8:47 AM, Pawan Thakur via ZendTo > > wrote: > > Hello Kris, > > Thanks a lot for your swift reply. It helped me. > > While emails are still an issue, I created users and I can access > the system and that's progress. > > 2 Issues with uploads > > 1. While uploading to the server, It gets stuck here. > > Screen > > I later checked my outbox, there was an entry and I could see the > generated file link as well. > > 2. I could see the file and the link here. But clicking on the > file / download all button goes into a loop and nothing happens. > It's hardly a 4 KB file. > > > > === > > I started looking into this issue. Logs show messages about failed > emails ( which I know is to be fixed ) but though it says Download > is completed but nothing happened. > > *Note: > *https://zend.to/clamavpermissions.php > > The memory issue**was there from CLAMAV and I configured SWAP and > did an external setup for it. I am not using SELinux*. * > > *I am just going to debug the Emails but any help related to these > files not working would be appreciated* > > Thanks, > Pawan* > * > > On 10/10/2018 10:49 PM, Kris Lou via ZendTo wrote: >> >> 1. I see in preferences file admin Users admin1, admin2 and >> so on. How to access the system as an admin ? is there a >> default Password ? If not, How can I create one ? >> >> >> This depends upon your authentication backend >> (https://zend.to/authentication.php >> ). There's a(n) >> /opt/zendto/bin/README.txt which should document the >> commands/scripts needed to create local users (admin1, admin2, >> etc.), but "adduser.php" is probably the one you're looking for. >> Execute that from CLI to add your first user and specify it as an >> Admin User in preferences.php. >> >> 2. I am trying to setup the email using basic SMTP, it is >> throwing an error. I created a one page php script to send >> mail with same settings and that works. Can some one please >> share a Snippet or screen shot of how can I setup SMTP >> >> >> I push emails to an external SMTP server, with only >> 'defaultEmailDomain', 'SMTPserver', 'SMTPport', 'SMTPsecure', and >> 'SMTPcharset' specified.? No local configuration required. >> >> For the previous 3-4 months, ALL of those settings except >> 'defaultEmailDomain' and 'SMTPcharset' were commented out, so it >> used the default PHPMail but still worked.? I would think that >> you still need Postfix or Sendmail on your local Zendto server, >> but still no local configuration required. >> >> Side note:? By default, PHPMail sends out as >> "apache@.>", >> so this may result in NEUTRAL grades if you have SPF set for >> >. I believe the outbound >> email address is set via PHP settings.? However, using an >> external SMTP server bypasses this with a return address of >> "zendto@>" or whatever you >> may have configured. >> >> Also, enabling 'SMTPdebug' might help you figure things out. >> >> >> >> _______________________________________________ >> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hdnlcjlflmgcabbf.png Type: image/png Size: 235848 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fpfepppbbiapjgme.png Type: image/png Size: 6674 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: screen.png Type: image/png Size: 205935 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: epinddpimojjkpbl.png Type: image/png Size: 132770 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bjpjlnkpgjhkkimh.png Type: image/png Size: 99317 bytes Desc: not available URL: From guard1976 at gmail.com Mon Oct 15 16:41:33 2018 From: guard1976 at gmail.com (Jan H.) Date: Mon, 15 Oct 2018 18:41:33 +0300 Subject: [ZendTo] Restricting access by LDAP group membership in version 5.15-1 does not work In-Reply-To: References: Message-ID: Everything works. You just need to uncomment the lines: 'authLDAPServers2' = > array(), 'authLDAPServers3' = > array(), in the case of a single domain ??, 12 ???. 2018 ?. ? 16:37, Jan H. via ZendTo : > Hi, everybody. > Restricting access by LDAP group membership in version 5.15-1 does not > work. When enabling this restrictions, the banner is displayed that says " > Authorization Failed. Sorry, you are not authorized to use this service." > but it is still possible to execute Drop-off (and other). > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto > -------------- next part -------------- An HTML attachment was scrubbed... URL: From klou at themusiclink.net Mon Oct 15 18:23:57 2018 From: klou at themusiclink.net (Kris Lou) Date: Mon, 15 Oct 2018 10:23:57 -0700 Subject: [ZendTo] New Installation - Admin Login - SMTP Configuration issues on AWS In-Reply-To: References: <1fab1671-a584-192d-05d7-513472516fa7@gmail.com> <8e751c16-be79-bb10-6b28-a5ca356ea887@gmail.com> Message-ID: It looks like everything is correct, but there may be some transport errors. Or maybe AWS is blocking something. I'd check the HTTP logs and also see what the client browser console says. You might get some clues there, but it'll probably be easier to just spin up a local VM where you can verify that everything works in a more controlled environment. Kris Lou klou at themusiclink.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From douglagm at gmail.com Wed Oct 17 11:29:00 2018 From: douglagm at gmail.com (Gregg Douglas) Date: Wed, 17 Oct 2018 12:29:00 +0200 Subject: [ZendTo] Zend.To Website Down References: Message-ID: Hi, I have been trying to access the https://zend.to website since yesterday and I keep on getting "Connection Timed out". Also the yum repo is timing out. Are there problems with the site ? Regards Gregg -------------- next part -------------- An HTML attachment was scrubbed... URL: From Massimo.Forni at turboden.it Wed Oct 17 12:10:25 2018 From: Massimo.Forni at turboden.it (Massimo Forni) Date: Wed, 17 Oct 2018 11:10:25 +0000 Subject: [ZendTo] Zend.To Website Down In-Reply-To: References: <0A6BAE18ABEE3E4ABF2F406E9A6BB9780176CFFE@MailBox.turboden.local> Message-ID: Yep, I can confirm connection refused from Italy From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Gregg Douglas via ZendTo Sent: 17 October 2018 12:29 To: zendto at zend.to Cc: Gregg Douglas Subject: [ZendTo] Zend.To Website Down Hi, I have been trying to access the https://zend.to website since yesterday and I keep on getting "Connection Timed out". Also the yum repo is timing out. Are there problems with the site ? Regards Gregg -- Massimo Forni ICT Specialist, Advisor to Managing Director for ICT ________________________________ Turboden S.p.A. I via Cernaia 10 I 25124 Brescia I Italy t. +390303552001 I f. +390303552011 www.turboden.com Confidentiality notice: this message, together with its attachments, may contain strictly confidential and/or legally privileged information and it is destined solely to the intended addressee(s), who only may use it under his/their responsibility. Opinions, conclusions and other information contained in this message, that do not relate to the official business of this firm, shall be considered as not given or endorsed by it. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. Any use, disclosure, copying or distribution of the contents of this communication by a not-intended recipient or in violation of the purposes of this communication is strictly prohibited and may be unlawful. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Wed Oct 17 12:26:20 2018 From: Jules at Zend.To (Jules Field) Date: Wed, 17 Oct 2018 12:26:20 +0100 Subject: [ZendTo] Zend.To Website Down In-Reply-To: References: <0A6BAE18ABEE3E4ABF2F406E9A6BB9780176CFFE@MailBox.turboden.local> Message-ID: <245ba30f-c4c4-79c2-2bcf-bd7c770b4455@Zend.To> Many thanks for the report. It's back up now. Cheers, Jules. On 17/10/2018 12:10, Massimo Forni via ZendTo wrote: > > Yep, I can confirm connection refused from Italy > > *From:*ZendTo [mailto:zendto-bounces at zend.to] *On Behalf Of *Gregg > Douglas via ZendTo > *Sent:* 17 October 2018 12:29 > *To:* zendto at zend.to > *Cc:* Gregg Douglas > *Subject:* [ZendTo] Zend.To Website Down > > Hi, > > I have been trying to access the https://zend.to website since > yesterday and I keep on getting "Connection Timed out". > > Also the yum repo is timing out. > > Are there problems with the site ? > > Regards > > Gregg > > -- > *Massimo Forni* > ICT Specialist, Advisor to Managing Director for ICT > > ------------------------------------------------------------------------ > > Turboden S.p.A. *I* via Cernaia 10 *I* 25124 Brescia *I* Italy > t. +390303552001 *I* f. +390303552011 > www.turboden.com > > > *Confidentiality notice*: this message, together with its attachments, > may contain strictly confidential and/or legally privileged > information and it is destined solely to the intended addressee(s), > who only may use it under his/their responsibility. Opinions, > conclusions and other information contained in this message, that do > not relate to the official business of this firm, shall be considered > as not given or endorsed by it. If you have received this > communication in error, please notify us immediately by responding to > this email and then delete it from your system. Any use, disclosure, > copying or distribution of the contents of this communication by a > not-intended recipient or in violation of the purposes of this > communication is strictly prohibited and may be unlawful. > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM IMPORTANT: This email is intended for the use of the individual addressee(s) named above and may contain information that is confidential, privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational religious beliefs. If you are not the intended recipient, any dissemination, distribution or copying of this email is not authorised (either explicitly or implicitly) and constitutes an irritating social faux pas. Unless the word absquatulation has been used in its correct context somewhere other than in this warning, it does not have any legal or no grammatical use and may be ignored. No animals were harmed in the transmission of this email, although the kelpie next door is living on borrowed time, let me tell you. Those of you with an overwhelming fear of the unknown will be gratified to learn that there is no hidden message revealed by reading this warning backwards, so just ignore that Alert Notice from Microsoft. However, by pouring a complete circle of salt around yourself and your computer you can ensure that no harm befalls you and your pets. If you have received this email in error, please add some nutmeg and egg whites, whisk and place in a warm oven for 40 minutes. www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From douglagm at gmail.com Wed Oct 17 12:40:59 2018 From: douglagm at gmail.com (Gregg Douglas) Date: Wed, 17 Oct 2018 13:40:59 +0200 Subject: [ZendTo] Zend.To Website Down In-Reply-To: References: <0A6BAE18ABEE3E4ABF2F406E9A6BB9780176CFFE@MailBox.turboden.local> <245ba30f-c4c4-79c2-2bcf-bd7c770b4455@Zend.To> Message-ID: Yes, I can access it. You had me worried there for a moment :) Thanks a million On Wed, Oct 17, 2018 at 1:26 PM Jules Field via ZendTo wrote: > Many thanks for the report. It's back up now. > > Cheers, > Jules. > > On 17/10/2018 12:10, Massimo Forni via ZendTo wrote: > > Yep, I can confirm connection refused from Italy > > > > *From:* ZendTo [mailto:zendto-bounces at zend.to ] *On > Behalf Of *Gregg Douglas via ZendTo > *Sent:* 17 October 2018 12:29 > *To:* zendto at zend.to > *Cc:* Gregg Douglas > *Subject:* [ZendTo] Zend.To Website Down > > > > Hi, > > > > I have been trying to access the https://zend.to website since yesterday > and I keep on getting "Connection Timed out". > > > > Also the yum repo is timing out. > > > > Are there problems with the site ? > > > > Regards > > Gregg > > > -- > *Massimo Forni* > ICT Specialist, Advisor to Managing Director for ICT > > ------------------------------ > > Turboden S.p.A. *I* via Cernaia 10 *I* 25124 Brescia *I* Italy > t. +390303552001 *I* f. +390303552011 > www.turboden.com > > > *Confidentiality notice*: this message, together with its attachments, > may contain strictly confidential and/or legally privileged information and > it is destined solely to the intended addressee(s), who only may use it > under his/their responsibility. Opinions, conclusions and other information > contained in this message, that do not relate to the official business of > this firm, shall be considered as not given or endorsed by it. If you have > received this communication in error, please notify us immediately by > responding to this email and then delete it from your system. Any use, > disclosure, copying or distribution of the contents of this communication > by a not-intended recipient or in violation of the purposes of this > communication is strictly prohibited and may be unlawful. > > _______________________________________________ > ZendTo mailing listZendTo at zend.tohttp://jul.es/mailman/listinfo/zendto > > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > IMPORTANT: This email is intended for the use of the individual > addressee(s) named above and may contain information that is > confidential, privileged or unsuitable for overly sensitive persons > with low self-esteem, no sense of humour or irrational religious > beliefs. If you are not the intended recipient, any dissemination, > distribution or copying of this email is not authorised (either > explicitly or implicitly) and constitutes an irritating social faux > pas. > > Unless the word absquatulation has been used in its correct context > somewhere other than in this warning, it does not have any legal > or no grammatical use and may be ignored. No animals were harmed > in the transmission of this email, although the kelpie next door > is living on borrowed time, let me tell you. Those of you with an > overwhelming fear of the unknown will be gratified to learn that > there is no hidden message revealed by reading this warning backwards, > so just ignore that Alert Notice from Microsoft. > > However, by pouring a complete circle of salt around yourself and > your computer you can ensure that no harm befalls you and your pets. > If you have received this email in error, please add some nutmeg > and egg whites, whisk and place in a warm oven for 40 minutes. > www.Zend.To > Twitter: @JulesFM > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto > -------------- next part -------------- An HTML attachment was scrubbed... URL: From burnsr at william.jewell.edu Wed Oct 17 13:28:52 2018 From: burnsr at william.jewell.edu (Richard H. Burns) Date: Wed, 17 Oct 2018 12:28:52 +0000 Subject: [ZendTo] Zend.To Website Down In-Reply-To: References: <0A6BAE18ABEE3E4ABF2F406E9A6BB9780176CFFE@MailBox.turboden.local> <245ba30f-c4c4-79c2-2bcf-bd7c770b4455@Zend.To> , <3E26C596-C4F9-4F69-8AA6-A92BEA84A92F@william.jewell.edu> Message-ID: The site does NOT come up for me. Richard Burns Server and Systems Administrator Office 816.415.7633 William Jewell College | www.jewell.edu [X] On Oct 17, 2018, at 7:26 AM, Gregg Douglas via ZendTo > wrote: Yes, I can access it. You had me worried there for a moment :) Thanks a million On Wed, Oct 17, 2018 at 1:26 PM Jules Field via ZendTo > wrote: Many thanks for the report. It's back up now. Cheers, Jules. On 17/10/2018 12:10, Massimo Forni via ZendTo wrote: Yep, I can confirm connection refused from Italy From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Gregg Douglas via ZendTo Sent: 17 October 2018 12:29 To: zendto at zend.to Cc: Gregg Douglas Subject: [ZendTo] Zend.To Website Down Hi, I have been trying to access the https://zend.to website since yesterday and I keep on getting "Connection Timed out". Also the yum repo is timing out. Are there problems with the site ? Regards Gregg -- Massimo Forni ICT Specialist, Advisor to Managing Director for ICT ________________________________ Turboden S.p.A. I via Cernaia 10 I 25124 Brescia I Italy t. +390303552001 I f. +390303552011 www.turboden.com Confidentiality notice: this message, together with its attachments, may contain strictly confidential and/or legally privileged information and it is destined solely to the intended addressee(s), who only may use it under his/their responsibility. Opinions, conclusions and other information contained in this message, that do not relate to the official business of this firm, shall be considered as not given or endorsed by it. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. Any use, disclosure, copying or distribution of the contents of this communication by a not-intended recipient or in violation of the purposes of this communication is strictly prohibited and may be unlawful. _______________________________________________ ZendTo mailing list ZendTo at zend.to http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM IMPORTANT: This email is intended for the use of the individual addressee(s) named above and may contain information that is confidential, privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational religious beliefs. If you are not the intended recipient, any dissemination, distribution or copying of this email is not authorised (either explicitly or implicitly) and constitutes an irritating social faux pas. Unless the word absquatulation has been used in its correct context somewhere other than in this warning, it does not have any legal or no grammatical use and may be ignored. No animals were harmed in the transmission of this email, although the kelpie next door is living on borrowed time, let me tell you. Those of you with an overwhelming fear of the unknown will be gratified to learn that there is no hidden message revealed by reading this warning backwards, so just ignore that Alert Notice from Microsoft. However, by pouring a complete circle of salt around yourself and your computer you can ensure that no harm befalls you and your pets. If you have received this email in error, please add some nutmeg and egg whites, whisk and place in a warm oven for 40 minutes. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Thu Oct 18 15:32:18 2018 From: Jules at Zend.To (Jules Field) Date: Thu, 18 Oct 2018 15:32:18 +0100 Subject: [ZendTo] manually retrieve an encrypted file? In-Reply-To: References: Message-ID: Mike, I have seen 1 other instance of this. It appears to be caused by the encryption process failing. Take a look in the Apache logs and let me know what error message you see in the error_log. I need to improve the checking of values read from the header I add to the encrypted file, to ensure that things like the hashing and encryption algorithm names are valid before I try to use them. I haven't managed to reproduce this problem myself, but I'm pretty sure this is what is happening. By the time I come to decrypt the data, if it's damaged by that point then I can't retrieve it, but I can flag the error a lot better than currently! One thing to try: given the ClaimID look in the /var/zendto/dropoffs directory for the files that belong to that ClaimID. The filenames will be random, and each file should be a bit longer than the original version uploaded. See if you can work out which one is the problem file. Is that file actually encrypted *at all*? The "file" command will help you here. Do a "file *" in the relevant dropoff directory, and it *should* say something like they are all just "data". If it identifies one as a Word document, zip file, PDF file anything like that, then the file didn't get encrypted for some reason. If that is the case, please can you look back through your zendto.log file (either in /var/zendto or /var/log/zendto) to see if anything odd happened when the drop-off was originally uploaded. Please can you let me know what you find? Also, I am going to write you a command-line utility so retrieve the files from a drop-off given the claim ID and the passphrase. It will probably just write all the files with their original names into the current directory. Even for unencrypted drop-offs, it would still be a useful tool. I'll make it prompt for the passphrase if one is needed (i.e. if the drop-off is encrypted). Cheers, Jules. On 12/10/2018 15:28, MICHAEL R MASSE via ZendTo wrote: > > Is there a way as the administrator of the system hosting my Zendto > service that I can decrypt a file that?s been uploaded if I have the > passphrase?? I have direct access to the sqlite database to get the > key as well, but I?m not sure what to do with either. > > I?m running 5.15-1 and the system works fine except one single user is > trying to receive a file from someone outside of the system and when > they try to download this specific file after typing in the passphrase > they just get a http 500 error.??? The sender does not receive any > errors when uploading.?? It actually doesn?t matter if the recipient > types a correct passphrase or not, they always get an http 500 error > on this particular file.??? As an administrator if I try to download > the file and regardless of the passphrase I enter (correct or not) I > get an http 500 error as well.? This does not happen for anyone else > for any other files in the system sent before or after.??? Also, for > every other file on the system, if an incorrect passphrase is used, > the system says it?s incorrect like it should instead of giving an > http 500 error.?? I told the person to have their sender send the file > again, and it again throws an http 500 error. ???It?s only a 2mb file > so there?s nothing weird about it.??? After telling them to upload the > file twice and having it fail I?d like to just decrypt the file that?s > there and manually give it to the recipient since he?s local, and then > worry about troubleshooting the problem later. > > -Mike > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'What happened in the past that was painful, has a great deal to do with what we are today.' - William Glasser www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From douglagm at gmail.com Fri Oct 19 07:22:13 2018 From: douglagm at gmail.com (Gregg Douglas) Date: Fri, 19 Oct 2018 08:22:13 +0200 Subject: [ZendTo] Text Box for Add Recipient Name and Email References: Message-ID: Hi, Here is something aesthetic that can be corrected: The Text Box for both the Recipient Name and email address in the "Add Recipient Popup Box" ends on the border of the pop-up. Can it perhaps be moved inwards a bit ? I noticed this from 5.13, I upgraded to 5.15-1 hoping this has been adjusted. I will try paste the image below and attach it to this email, not sure it will display correctly. Regards Gregg [image: image.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 30003 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Zendto_add_recipients.png Type: image/png Size: 20115 bytes Desc: not available URL: From Jules at Zend.To Fri Oct 19 11:43:22 2018 From: Jules at Zend.To (Jules Field) Date: Fri, 19 Oct 2018 11:43:22 +0100 Subject: [ZendTo] Text Box for Add Recipient Name and Email In-Reply-To: References: Message-ID: <8bac5849-ecd1-78a6-0fe8-e3b1d86cf6a5@Zend.To> Gregg, Please can you try totally clearing your browser cache, I suspect you're using out of date cached CSS styling. Browsers are way too aggressive at caching CSS, refreshing a page doesn't usually fetch new CSS files in my experience. It certainly shouldn't look like that, and doesn't in any browser I have tried. Cheers, Jules. On 19/10/2018 07:22, Gregg Douglas via ZendTo wrote: > Hi, > > Here is something aesthetic that can be corrected:?The Text Box for > both the Recipient Name and email address in the "Add Recipient Popup > Box" ends on the border of the pop-up. Can it perhaps be moved inwards > a bit ? > > I noticed this from 5.13, I upgraded to 5.15-1 hoping this has been > adjusted. > > I will try paste the image below and attach it to this email, not sure > it will display correctly. > > Regards > Gregg > > > image.png > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'The best and most beautiful things in life cannot be seen or even touched; they must be felt with the heart.' - Helen Keller www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 30003 bytes Desc: not available URL: From mrm at medicine.wisc.edu Fri Oct 19 18:00:04 2018 From: mrm at medicine.wisc.edu (MICHAEL R MASSE) Date: Fri, 19 Oct 2018 17:00:04 +0000 Subject: [ZendTo] manually retrieve an encrypted file? In-Reply-To: References: Message-ID: When I run the file command on the file that is sitting in the drop-offs folder with the claim ID in question, it says: raw G3 data, byte-padded When looking at the zendto.log file at the time the file was uploaded, it looks normal with no hint of anything wrong. Here?s what it says with the email addresses obfiscated: 2018-10-10 21:13:19 108.85.190.41 [ZendTo]: Info: successfully delivered notification email to RECIPIENT at EMAIL.ADDRESS for claimID q3j8nGdByjV8MwSq 2018-10-10 21:13:19 108.85.190.41 [ZendTo]: Info: new encrypted dropoff q3j8nGdByjV8MwSq of 1 file created for external user SENDER SENDER at EMAIL.ADDRESS A command line utility would be fantastic! -MIke From: ZendTo On Behalf Of Jules Field via ZendTo Sent: Thursday, October 18, 2018 9:32 AM To: MICHAEL R MASSE via ZendTo Cc: Jules Field Subject: Re: [ZendTo] manually retrieve an encrypted file? Mike, I have seen 1 other instance of this. It appears to be caused by the encryption process failing. Take a look in the Apache logs and let me know what error message you see in the error_log. I need to improve the checking of values read from the header I add to the encrypted file, to ensure that things like the hashing and encryption algorithm names are valid before I try to use them. I haven't managed to reproduce this problem myself, but I'm pretty sure this is what is happening. By the time I come to decrypt the data, if it's damaged by that point then I can't retrieve it, but I can flag the error a lot better than currently! One thing to try: given the ClaimID look in the /var/zendto/dropoffs directory for the files that belong to that ClaimID. The filenames will be random, and each file should be a bit longer than the original version uploaded. See if you can work out which one is the problem file. Is that file actually encrypted *at all*? The "file" command will help you here. Do a "file *" in the relevant dropoff directory, and it *should* say something like they are all just "data". If it identifies one as a Word document, zip file, PDF file anything like that, then the file didn't get encrypted for some reason. If that is the case, please can you look back through your zendto.log file (either in /var/zendto or /var/log/zendto) to see if anything odd happened when the drop-off was originally uploaded. Please can you let me know what you find? Also, I am going to write you a command-line utility so retrieve the files from a drop-off given the claim ID and the passphrase. It will probably just write all the files with their original names into the current directory. Even for unencrypted drop-offs, it would still be a useful tool. I'll make it prompt for the passphrase if one is needed (i.e. if the drop-off is encrypted). Cheers, Jules. On 12/10/2018 15:28, MICHAEL R MASSE via ZendTo wrote: Is there a way as the administrator of the system hosting my Zendto service that I can decrypt a file that?s been uploaded if I have the passphrase? I have direct access to the sqlite database to get the key as well, but I?m not sure what to do with either. I?m running 5.15-1 and the system works fine except one single user is trying to receive a file from someone outside of the system and when they try to download this specific file after typing in the passphrase they just get a http 500 error. The sender does not receive any errors when uploading. It actually doesn?t matter if the recipient types a correct passphrase or not, they always get an http 500 error on this particular file. As an administrator if I try to download the file and regardless of the passphrase I enter (correct or not) I get an http 500 error as well. This does not happen for anyone else for any other files in the system sent before or after. Also, for every other file on the system, if an incorrect passphrase is used, the system says it?s incorrect like it should instead of giving an http 500 error. I told the person to have their sender send the file again, and it again throws an http 500 error. It?s only a 2mb file so there?s nothing weird about it. After telling them to upload the file twice and having it fail I?d like to just decrypt the file that?s there and manually give it to the recipient since he?s local, and then worry about troubleshooting the problem later. -Mike _______________________________________________ ZendTo mailing list ZendTo at zend.to http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'What happened in the past that was painful, has a great deal to do with what we are today.' - William Glasser www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From TZimmerman at fsu.edu Mon Oct 22 19:21:25 2018 From: TZimmerman at fsu.edu (Travis Zimmerman) Date: Mon, 22 Oct 2018 18:21:25 +0000 Subject: [ZendTo] Using alternate AD attribute References: Message-ID: We have two e-mail domains at my university (@fsu.edu for faculty/staff and @my.fsu.edu for students), this causes problems when logging in with just their username so we are switching to using their e-mail address, since the newer versions of ZendTo support this. We have two separate ADs for the domains, but the student domain is using a different attribute (userPrincipalName). Is there a way for me to use a different attribute for just one of the domains? ------------------------------------------------------------------- Travis Zimmerman tzimmerman at fsu.edu 850-645-8030 Linux Enterprise Applications & Systems its-linuxadmins at fsu.edu Information Technology Services, Florida State University From Jules at Zend.To Tue Oct 23 15:02:07 2018 From: Jules at Zend.To (Jules Field) Date: Tue, 23 Oct 2018 15:02:07 +0100 Subject: [ZendTo] manually retrieve an encrypted file? In-Reply-To: References: Message-ID: Michael, I've written a command-line utility "extractdropoff" which just takes a ClaimID on the command-line. If the drop-off is encrypted, it will prompt you to enter the passphrase (which it won't echo). It then saves the files in the current directory. Nice and simple. :-) It will be in the next release. Cheers, Jules. On 19/10/2018 18:00, MICHAEL R MASSE via ZendTo wrote: > > When I run the file command on the file that is sitting in the > drop-offs folder with the claim ID in question, it says: > > raw G3 data, byte-padded > > When looking at the zendto.log file at the time the file was uploaded, > it looks normal with no hint of anything wrong.?? Here?s what it says > with the email addresses obfiscated: > > 2018-10-10 21:13:19 108.85.190.41 [ZendTo]: Info: successfully > delivered notification email to RECIPIENT at EMAIL.ADDRESS for claimID > q3j8nGdByjV8MwSq > > 2018-10-10 21:13:19 108.85.190.41 [ZendTo]: Info: new encrypted > dropoff q3j8nGdByjV8MwSq of 1 file created for external user SENDER > SENDER at EMAIL.ADDRESS > > A command line utility would be fantastic! > > -MIke > > *From:*ZendTo *On Behalf Of *Jules Field via > ZendTo > *Sent:* Thursday, October 18, 2018 9:32 AM > *To:* MICHAEL R MASSE via ZendTo > *Cc:* Jules Field > *Subject:* Re: [ZendTo] manually retrieve an encrypted file? > > Mike, > > I have seen 1 other instance of this. It appears to be caused by the > encryption process failing. Take a look in the Apache logs and let me > know what error message you see in the error_log. I need to improve > the checking of values read from the header I add to the encrypted > file, to ensure that things like the hashing and encryption algorithm > names are valid before I try to use them. > > I haven't managed to reproduce this problem myself, but I'm pretty > sure this is what is happening. By the time I come to decrypt the > data, if it's damaged by that point then I can't retrieve it, but I > can flag the error a lot better than currently! > > One thing to try: given the ClaimID look in the /var/zendto/dropoffs > directory for the files that belong to that ClaimID. The filenames > will be random, and each file should be a bit longer than the original > version uploaded. See if you can work out which one is the problem > file. Is that file actually encrypted *at all*? The "file" command > will help you here. Do a "file *" in the relevant dropoff directory, > and it *should* say something like they are all just "data". If it > identifies one as a Word document, zip file, PDF file anything like > that, then the file didn't get encrypted for some reason. > > If that is the case, please can you look back through your zendto.log > file (either in /var/zendto or /var/log/zendto) to see if anything odd > happened when the drop-off was originally uploaded. > > Please can you let me know what you find? > > Also, I am going to write you a command-line utility so retrieve the > files from a drop-off given the claim ID and the passphrase. It will > probably just write all the files with their original names into the > current directory. Even for unencrypted drop-offs, it would still be a > useful tool. I'll make it prompt for the passphrase if one is needed > (i.e. if the drop-off is encrypted). > > Cheers, > Jules. > > On 12/10/2018 15:28, MICHAEL R MASSE via ZendTo wrote: > > Is there a way as the administrator of the system hosting my > Zendto service that I can decrypt a file that?s been uploaded if I > have the passphrase?? I have direct access to the sqlite database > to get the key as well, but I?m not sure what to do with either. > > I?m running 5.15-1 and the system works fine except one single > user is trying to receive a file from someone outside of the > system and when they try to download this specific file after > typing in the passphrase they just get a http 500 error.??? The > sender does not receive any errors when uploading.?? It actually > doesn?t matter if the recipient types a correct passphrase or not, > they always get an http 500 error on this particular file.??? As > an administrator if I try to download the file and regardless of > the passphrase I enter (correct or not) I get an http 500 error as > well.? This does not happen for anyone else for any other files in > the system sent before or after.??? Also, for every other file on > the system, if an incorrect passphrase is used, the system says > it?s incorrect like it should instead of giving an http 500 > error.?? I told the person to have their sender send the file > again, and it again throws an http 500 error. ???It?s only a 2mb > file so there?s nothing weird about it.??? After telling them to > upload the file twice and having it fail I?d like to just decrypt > the file that?s there and manually give it to the recipient since > he?s local, and then worry about troubleshooting the problem later. > > -Mike > > > > _______________________________________________ > > ZendTo mailing list > > ZendTo at zend.to > > http://jul.es/mailman/listinfo/zendto > > > > Jules > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > 'What happened in the past that was painful, has a great deal to > do with what we are today.' - William Glasser > 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 '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 Jules at Zend.To Tue Oct 23 15:08:02 2018 From: Jules at Zend.To (Jules Field) Date: Tue, 23 Oct 2018 15:08:02 +0100 Subject: [ZendTo] Error: failed to add ---- record In-Reply-To: References: <7014be42-a282-4430-7f3a-f477e3ef159a@alaska.gov> Message-ID: <913a04af-7204-0b7b-61ec-6a44fe352fb8@Zend.To> John, It means it's not at all happy about your ZendTo database. This might either be in /var/zendto/zendto.sqlite, or else on a MySQL server. I have improved the SQLite code a fair bit recently to stop DB locking problems, which may be what you're seeing. I'm going to release a new version very shortly, which will hopefully help with this. One thing you might want to try in the mean time is setting very small size limits for (or disabling altogether) the checksum and particularly the encryption features. That should help until I get the new version out to you. Cheers, Jules. On 11/10/2018 22:03, John Thurston via ZendTo wrote: > I'm running 5.11 on CentOS. While looking in the logs to try to figure > out a problem, I noticed many "Error: failed to add " lines. > > Since March, I have recorded: > ? 233 "pickup" > ? 106 "authdata" > They seem to come in clumps. > > What is the cause of these errors, and how should I go about making > them stop? > Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM The current UK shipping forecast: Biscay: Northeast 3 or 4, occasionally 5 until later. Moderate, occasionally rough at first. Fair. Good occasionally poor. www.Zend.To Twitter: @JulesFM From Jules at Zend.To Tue Oct 23 15:20:08 2018 From: Jules at Zend.To (Jules Field) Date: Tue, 23 Oct 2018 15:20:08 +0100 Subject: [ZendTo] Multi-cpu or thread use In-Reply-To: References: Message-ID: <7d9bac35-a629-3f94-73a7-ef7d4def3e5e@Zend.To> John, The folks that know about such things appear to strongly advise against trying to use threads in a web server environment. If 1 user drops 10 files in 1 drop-off, they will be virus scanned, checksummed and encrypted sequentially. But saying that, all the files are virus-scanned together to reduce the "startup cost" of clamdscan. This will pretty much only utilise 1 CPU core. If 10 users each drop files (into different drop-offs, of course), then each user will be handled in parallel with the others, potentially using at least 10 CPU cores. So the time a user has to wait at the end of the upload process is governed much more by the size of their drop-off. Provided you have fewer simultaneous users (all at the end of the upload process) than you have CPU cores, the number of users should make little difference to the time they each have to wait. As for RAM requirements, have a look at the output of "top" when your ZendTo VM is reasonably busy, and see if it's actively using any swap. If it's using all/most of the RAM, but has plenty listed in buffers+cached while having little swap in use, you've got enough. Hope that helps, Jules. On 12/10/2018 00:03, John Thurston via ZendTo wrote: > With the enabling of encryption in ZendTo, I've seen an increase in > memory and CPU utilization. I'm running 5.11 on CentOS on VMWare. > > Today, I had the host bumped up to 3GB of ram (from 2GB). This seems a > lot, but I duno how much clamav is using or if I have httpd rigged for > multi-process or multi-thread. Does php work with either? Anyway... > > If I ask for another virtual process to be thrown at this, is the php > going to be able to take advantage of it? That is, will it be able to > virus scan one big file while simultaneously encrypting another? > > Will it matter how the work arrives? That is, if a user drops two > files, is that going to be handled sequentially in one httpd process? > But if two users on different httpd processes each drop one file, > might they be handled in parallel? > > Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'All the art of living lies in a fine mingling of letting go, and holding on.' - Henry Ellis www.Zend.To Twitter: @JulesFM From azshane at gmail.com Wed Oct 24 20:51:32 2018 From: azshane at gmail.com (Shane) Date: Wed, 24 Oct 2018 12:51:32 -0700 Subject: [ZendTo] lock down recipient References: Message-ID: Hello I've just finished installing zend.to in my centos 7. is it possible to lock down the users who login to send files to one particular recipient, not be able to add any other email address? I browsed through preferences.php and couldn't find any reference to it unless I missed something. Also is it possible to lock down to allow only Excel files to be uploaded? thanks i shane -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Thu Oct 25 12:06:24 2018 From: Jules at Zend.To (Jules Field) Date: Thu, 25 Oct 2018 12:06:24 +0100 Subject: [ZendTo] lock down recipient In-Reply-To: References: Message-ID: Shane, On 24/10/2018 20:51, Shane via ZendTo wrote: > Hello > > I've just finished installing zend.to > > in my centos 7. is it possible > to lock down the users who login to send files to one particular > recipient, not be able to add any other email address?? I browsed through > preferences.php and couldn't find any reference to it unless I missed > something. Not currently, no. You could hard-wire into the template /opt/zendto/templates/new_dropoff.tpl like this: * Right near the top, put your fixed recipient info into the variables "presetToName" and "presetToEmail". * Search for 'id="addRecipients"'. Add to that tag an attribute 'style="display:none"'. That would stop it appearing, which may be enough for your needs. > > Also is it possible to lock down to allow only Excel files to be uploaded? No. There's pretty much no way of *reliably* detecting that a file is an Excel file. And don't suggest *.xls or *.xlsx. Then people just rename their p**n/w*r*z before sending it. Sorry! Jules. > > thanks i > shane > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Cfd6cebc05dc946b2713108d639ea34bd%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=i%2FQ4BIYymCnsMKYR%2B71Hvn%2FMYIcvFlcQ4T5sFU1YYuA%3D&reserved=0 Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'In Flanders fields the poppies blow Between the crosses, row on row, That mark our place: and in the sky The larks still bravely singing fly Scarce heard amid the guns below. We are the dead: Short days ago, We lived, felt dawn, saw sunset glow, Loved and were loved: and now we lie In Flanders fields! Take up our quarrel with the foe To you, from failing hands, we throw The torch: be yours to hold it high If ye break faith with us who die, We shall not sleep, though poppies grow In Flanders fields.' Lieutenant Colonel John McCrae Composed at the battlefront on May 3, 1915 during the second battle of Ypres, Belgium www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From KLE at msktd.com Thu Oct 25 13:36:35 2018 From: KLE at msktd.com (Ken Etter) Date: Thu, 25 Oct 2018 08:36:35 -0400 Subject: [ZendTo] Zend.to error during drop-off References: <5BD1B8D3020000130012D8F6@mail.msktd.com> Message-ID: Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From KLE at msktd.com Thu Oct 25 13:38:53 2018 From: KLE at msktd.com (Ken Etter) Date: Thu, 25 Oct 2018 08:38:53 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1B95D020000130012D8FC@mail.msktd.com> Message-ID: I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From KLE at msktd.com Thu Oct 25 14:26:01 2018 From: KLE at msktd.com (Ken Etter) Date: Thu, 25 Oct 2018 09:26:01 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1B95D020000130012D8FC@mail.msktd.com> <5BD1C469020000130012D903@mail.msktd.com> Message-ID: Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: http://jul.es/pipermail/zendto/2018-June/003208.html Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From gdm at sangabriel.com Thu Oct 25 14:31:29 2018 From: gdm at sangabriel.com (Gray McCord) Date: Thu, 25 Oct 2018 08:31:29 -0500 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1B95D020000130012D8FC@mail.msktd.com> <5BD1C469020000130012D903@mail.msktd.com> <023a01d46c67$09765bd0$1c631370$@sangabriel.com> Message-ID: I've seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List Cc: Ken Etter Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: http://jul.es/pipermail/zendto/2018-June/003208.html Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo > 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo > 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10425 bytes Desc: not available URL: From Jules at Zend.To Thu Oct 25 15:17:11 2018 From: Jules at Zend.To (Jules Field) Date: Thu, 25 Oct 2018 15:17:11 +0100 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1B95D020000130012D8FC@mail.msktd.com> Message-ID: Ken, The problem here appears to be the encryption using massive amounts of RAM to generate the actual encryption key from the passphrase you type in. If you upgrade to the latest beta, I have tweaked the encryption so it uses a lot less RAM. Otherwise, do a "free -m" or look at the output of "top" to see what memory is in use. If you want to just edit the code for the memory reduction tweak, look in /opt/zendto/lib/NSSUtils.c. In there, you will find 2 occurrences of "MODERATE" (in caps). Change those to "INTERACTIVE" and then restart Apache. That will tell you very quickly if it's the RAM problem. Cheers, Jules. On 25/10/2018 13:38, Ken Etter via ZendTo wrote: > I am running this on Ubuntu 16.04.5 LTS if that matters. > > Ken > >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> > Just upgraded my Zend.To installation from 4.x to 5.15-1.? Everything > appeared to go ok.? But when I click drop-off files, I get an error > that states:? "Sorry, I failed to drop-off your files!? Note that you > cannot drop-off directories, only files."? I'm not dropping off a > directory, just a single file.? I tried a couple different file types > - same error each time.? Any suggestions for fixing this?? Thanks! > > *Ken Etter*, System Administrator > Architectural Group > 260.432.9337|msktd.com > > > > > _______________________________________________ > 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: Shannon: Variable 3 or 4, becoming north 5 to 7, perhaps gale 8 later. Moderate, becoming rough or very rough. Rain then squally showers. Good, occasionally poor. www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: not available URL: From KLE at msktd.com Thu Oct 25 15:28:32 2018 From: KLE at msktd.com (Ken Etter) Date: Thu, 25 Oct 2018 10:28:32 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1B95D020000130012D8FC@mail.msktd.com> <5BD1D310020000130012D916@mail.msktd.com> Message-ID: Jules, Thanks for the quick reply. /opt/zendto/lib/NSSUtils.c does not exist. /opt/zendto/lib/NSSUtils.php does exist. So I edited that and restarted apache. No change - still get the error. # free -m total used free shared buff/cache available Mem: 2000 673 833 10 492 1158 Swap: 2047 0 2047 Doesn't look like a memory issue. Thoughts? Ken >>> Jules Field 10/25/2018 10:17 AM >>> > Ken, The problem here appears to be the encryption using massive amounts of RAM to generate the actual encryption key from the passphrase you type in. If you upgrade to the latest beta, I have tweaked the encryption so it uses a lot less RAM. Otherwise, do a "free -m" or look at the output of "top" to see what memory is in use. If you want to just edit the code for the memory reduction tweak, look in /opt/zendto/lib/NSSUtils.c. In there, you will find 2 occurrences of "MODERATE" (in caps). Change those to "INTERACTIVE" and then restart Apache. That will tell you very quickly if it's the RAM problem. Cheers, Jules. On 25/10/2018 13:38, Ken Etter via ZendTo wrote: I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo ( mailto:zendto at zend.to) 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com _______________________________________________ZendTo mailing listZendTo at zend.tohttp://jul.es/mailman/listinfo/zendto Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACMThe current UK shipping forecast:Shannon: Variable 3 or 4, becoming north 5 to 7, perhaps gale 8 later.Moderate, becoming rough or very rough. Rain then squally showers. Good,occasionally poor.www.Zend.ToTwitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From KLE at msktd.com Thu Oct 25 15:34:25 2018 From: KLE at msktd.com (Ken Etter) Date: Thu, 25 Oct 2018 10:34:25 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1B95D020000130012D8FC@mail.msktd.com> <5BD1C469020000130012D903@mail.msktd.com> <023a01d46c67$09765bd0$1c631370$@sangabriel.com> <5BD1D471020000130012D922@mail.msktd.com> Message-ID: /opt/zendto is owned by root. Changed it to www-data, but that did not fix it. >>> Gray McCord via ZendTo 10/25/2018 9:31 AM >>> I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List Cc: Ken Etter Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: http://jul.es/pipermail/zendto/2018-June/003208.html Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From KLE at msktd.com Thu Oct 25 15:44:45 2018 From: KLE at msktd.com (Ken Etter) Date: Thu, 25 Oct 2018 10:44:45 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: <5BD1D310020000130012D916@mail.msktd.com> References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1B95D020000130012D8FC@mail.msktd.com> <5BD1D310020000130012D916@mail.msktd.com> <5BD1D6DD020000130012D929@mail.msktd.com> Message-ID: I don't see any instructions on the website for trying out the beta version. Not sure how to do that. Ken >>> Ken Etter 10/25/2018 10:28 AM >>> Jules, Thanks for the quick reply. /opt/zendto/lib/NSSUtils.c does not exist. /opt/zendto/lib/NSSUtils.php does exist. So I edited that and restarted apache. No change - still get the error. # free -m total used free shared buff/cache available Mem: 2000 673 833 10 492 1158 Swap: 2047 0 2047 Doesn't look like a memory issue. Thoughts? Ken >>> Jules Field 10/25/2018 10:17 AM >>> > Ken, The problem here appears to be the encryption using massive amounts of RAM to generate the actual encryption key from the passphrase you type in. If you upgrade to the latest beta, I have tweaked the encryption so it uses a lot less RAM. Otherwise, do a "free -m" or look at the output of "top" to see what memory is in use. If you want to just edit the code for the memory reduction tweak, look in /opt/zendto/lib/NSSUtils.c. In there, you will find 2 occurrences of "MODERATE" (in caps). Change those to "INTERACTIVE" and then restart Apache. That will tell you very quickly if it's the RAM problem. Cheers, Jules. On 25/10/2018 13:38, Ken Etter via ZendTo wrote: I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo ( mailto:zendto at zend.to) 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com _______________________________________________ZendTo mailing listZendTo at zend.tohttp://jul.es/mailman/listinfo/zendto Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACMThe current UK shipping forecast:Shannon: Variable 3 or 4, becoming north 5 to 7, perhaps gale 8 later.Moderate, becoming rough or very rough. Rain then squally showers. Good,occasionally poor.www.Zend.ToTwitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From Jules at Zend.To Thu Oct 25 15:48:46 2018 From: Jules at Zend.To (Jules Field) Date: Thu, 25 Oct 2018 15:48:46 +0100 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1B95D020000130012D8FC@mail.msktd.com> <5BD1D310020000130012D916@mail.msktd.com> <5BD1D6DD020000130012D929@mail.msktd.com> Message-ID: <14645dba-d787-608b-5fca-3d9ff46e2b50@Zend.To> Ken, As it doesn't appear to be a RAM problem, the beta won't help you anyway. How did you upgrade from 4.x to 5.15 ? The safest, quickest and easiest way is to start again with a new server/VM. Set it all up with my Installer, get everything working, then port across your database and drop-offs (if you want to). To see exactly why this might be failing, check the ZendTo log (either in /var/zendto/zendto.log or else /var/log/zendto/zendto.log). And then check your web server error logs (either in /var/log/httpd or /var/log/apache2 depending on what Linux variant you are using). One of those logs should give some clues. Let me know how you get on. Cheers, Jules. P.S. Sorry, yes, it wouldn't be NSSUtils.c as I wrote it in PHP. My bad. Long day. :( On 25/10/2018 15:44, Ken Etter wrote: > I don't see any instructions on the website for trying out the beta > version.? Not sure how to do that. > Ken > >>> Ken Etter 10/25/2018 10:28 AM >>> > Jules, > Thanks for the quick reply. > > /opt/zendto/lib/NSSUtils.c does not exist. > /opt/zendto/lib/NSSUtils.php does exist.? So I edited that and > restarted apache.? No change - still get the error. > > # free -m > ????????????? total??????? used??????? free????? shared buff/cache?? > available > Mem:?????????? 2000???????? 673???????? 833 10???????? 492??????? 1158 > Swap:????????? 2047?????????? 0??????? 2047 > > Doesn't look like a memory issue.? Thoughts? > > Ken > > >>> Jules Field 10/25/2018 10:17 AM >>> > > Ken, > > The problem here appears to be the encryption using massive amounts of > RAM to generate the actual encryption key from the passphrase you type in. > If you upgrade to the latest beta, I have tweaked the encryption so it > uses a lot less RAM. > Otherwise, do a "free -m" or look at the output of "top" to see what > memory is in use. > If you want to just edit the code for the memory reduction tweak, look > in /opt/zendto/lib/NSSUtils.c. In there, you will find 2 occurrences > of "MODERATE" (in caps). Change those to "INTERACTIVE" and then > restart Apache. > That will tell you very quickly if it's the RAM problem. > Cheers, > Jules. > On 25/10/2018 13:38, Ken Etter via ZendTo wrote: >> I am running this on Ubuntu 16.04.5 LTS if that matters. >> >> Ken >> >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> >> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything >> appeared to go ok. But when I click drop-off files, I get an error >> that states: "Sorry, I failed to drop-off your files! Note that you >> cannot drop-off directories, only files." I'm not dropping off a >> directory, just a single file. I tried a couple different file types >> - same error each time. Any suggestions for fixing this? Thanks! >> >> *Ken Etter*, System Administrator >> Architectural Group >> 260.432.9337|msktd.com >> >> >> >> >> _______________________________________________ >> 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: > Shannon: Variable 3 or 4, becoming north 5 to 7, perhaps gale 8 later. > Moderate, becoming rough or very rough. Rain then squally showers. Good, > occasionally poor. > > www.Zend.To > Twitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'If I were a Brazilian without land or money or the means to feed my children, I would be burning the rain forest too.' - Sting www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: not available URL: From Jules at Zend.To Thu Oct 25 15:53:05 2018 From: Jules at Zend.To (Jules Field) Date: Thu, 25 Oct 2018 15:53:05 +0100 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1B95D020000130012D8FC@mail.msktd.com> <5BD1C469020000130012D903@mail.msktd.com> <023a01d46c67$09765bd0$1c631370$@sangabriel.com> Message-ID: Yes, those directories do need to be writable by whatever user and group your web server is running as. If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise ??? restorecon -FRv /opt/zendto /var/zendto to reset all the SELinux attributes to the values configured by my Installer. Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by ??? setenforce permissive ??? systemctl restart httpd ??? systemctl restart clamd at scan To switch it back to "enforcing", you then do ??? setenforce enforcing ??? systemctl restart httpd ??? systemctl restart clamd at scan Cheers, Jules. On 25/10/2018 14:31, Gray McCord via ZendTo wrote: > > I?ve seen that message as well. Check the file permissions on the > /opt/zendto directories. Seems like I needed to make them writeable by > the apache user, but I could be mistaken. > > Gray McCord > > /Adapt, Mutate, Migrate, or Die/ > > -C. Darwin > > *From:* ZendTo *On Behalf Of *Ken Etter via > ZendTo > *Sent:* Thursday, October 25, 2018 8:26 AM > *To:* ZendTo List > *Cc:* Ken Etter > *Subject:* Re: [ZendTo] Zend.to error during drop-off > > Going back through the mailing list archives, I see that I am having > exactly the same problem as Kevin O'Connor in this thread: > http://jul.es/pipermail/zendto/2018-June/003208.html > > > Files are uploaded, but I get that error message and the email is not > sent. > > There is no stated resolution in that thread.? Any suggestions or do I > have to rebuild a brand new Zend.To server? > > Zend.To has been fairly solid for me...a bit of a pain to find this > upgrade to be so fragile. > > Ken > > >>> Ken Etter via ZendTo > 10/25/2018 > 8:38 AM >>> > > I am running this on Ubuntu 16.04.5 LTS if that matters. > > > Ken > > >>> Ken Etter via ZendTo > 10/25/2018 > 8:36 AM >>> > > Just upgraded my Zend.To installation from 4.x to 5.15-1.? Everything > appeared to go ok.? But when I click drop-off files, I get an error > that states:? "Sorry, I failed to drop-off your files!? Note that you > cannot drop-off directories, only files."? I'm not dropping off a > directory, just a single file.? I tried a couple different file types > - same error each time.? Any suggestions for fixing this?? Thanks! > > > > *Ken Etter*, System Administrator > > Architectural Group > > 260.432.9337?| msktd.com > > > > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10425 bytes Desc: not available URL: From KLE at msktd.com Thu Oct 25 15:59:12 2018 From: KLE at msktd.com (Ken Etter) Date: Thu, 25 Oct 2018 10:59:12 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: <5BD1D8DE0200007600407AB5@mail.msktd.com> References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1B95D020000130012D8FC@mail.msktd.com> <5BD1C469020000130012D903@mail.msktd.com> <023a01d46c67$09765bd0$1c631370$@sangabriel.com> <705D5031020000C3C84B1EE2@mail.msktd.com> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> Message-ID: None of that helps. I'm building a new system. This is a production system. I never had problems in the past with upgrading so I went ahead and did it. Bad move. Unless anyone has any other ideas, I will just keep working on setting up the new system. I have to get something running again for my users. Ken >>> Jules Field via ZendTo 10/25/2018 10:53 AM >>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise restorecon -FRv /opt/zendto /var/zendto to reset all the SELinux attributes to the values configured by my Installer. Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by setenforce permissive systemctl restart httpd systemctl restart clamd at scan To switch it back to "enforcing", you then do setenforce enforcing systemctl restart httpd systemctl restart clamd at scan Cheers, Jules. On 25/10/2018 14:31, Gray McCord via ZendTo wrote: I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo ( mailto:zendto-bounces at zend.to) On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List ( mailto:zendto at zend.to) Cc: Ken Etter ( mailto:KLE at msktd.com) Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: http://jul.es/pipermail/zendto/2018-June/003208.html ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fpipermail%2Fzendto%2F2018-June%2F003208.html&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=%2FMQVOSO5ZjLwkrQ991eChCvoSfFOLwm3yUcnFSzoRc0%3D&reserved=0) Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmsktd.com%2F&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=XsZydsv5daB1usPtdakyqf%2BjPxBLH9n8NbGcrjhC34Y%3D&reserved=0) _______________________________________________ZendTo mailing listZendTo at zend.tohttps://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDg T%2B09ppjkZZ0%3D&reserved=0) Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'The past is supposed to be a place of reference, not a place ofresidence! There is a reason why your car has a big windshield anda small rearview mirror. You are supposed to keep your eyes on whereyou are going, and just occasionally check out where you have been.' - Willie Jolleywww.Zend.ToTwitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From Jules at Zend.To Thu Oct 25 16:15:01 2018 From: Jules at Zend.To (Jules Field) Date: Thu, 25 Oct 2018 16:15:01 +0100 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <023a01d46c67$09765bd0$1c631370$@sangabriel.com> <705D5031020000C3C84B1EE2@mail.msktd.com> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> Message-ID: <43f7fe6f-fb01-fbc2-20e8-69aad2903060@Zend.To> Do you have PHP 7.2 installed? My Installer can be run in stages, and those stages can be run independently. So you might want to download the Installer, unpack it and wander into it. In what will obviously be the right sub-dir for your OS, you will see the numbered scripts. # cd install.ZendTo/CentOS-RedHat/ # ls 1-devtools.sh? 3-clamav.sh??? 5-httpd-php.sh? 7-zendto.sh CentOS6? RHEL7 2-php.sh?????? 4-firewall.sh? 6-email.sh????? 8-selinux.sh RHEL5 # If your web server is already working nicely, then you can probably skip stage 1 (though it won't do any harm). If you haven't installed PHP 7.2 along with things like the sodium extension, then run stage 2 which installs PHP. (Grab a backup copy of your ZendTo installation first, as it may have to remove the *whole* of PHP first which can also remove ZendTo and other PHP applications in the process, before it can install the correct version). Stages 3 and 5 shouldn't do any damage, but will add any new settings they need for PHP and so on. Stage 7 does the actual ZendTo installation itself, which it will do as an upgrade if it finds a zendto RPM already installed. Well worth running. Stage 8 is only relevant if you are using SELinux, and won't do anything if you're not. Since version 4, ZendTo no longer needs any form of custom-built PHP or anything like that. So there's no recompiling to be done. Then if you have a previous preferences.php and/or zendto.conf, you need to use ??? /opt/zendto/bin/upgrade_preferences_php and ??? /opt/zendto/bin/upgrade_zendto_conf to upgrade those files. Also, if you have done an RPM upgrade from ZendTo 4, you probably have a whole stack of *.rpmnew files in /opt/zendto/templates. You want to move each of those into place so they replace your old *.tpl files. As I said, it really is faster/easier/better to build v5 from scratch, its requirements are so different from v4. Hope that helps, Jules. On 25/10/2018 15:59, Ken Etter wrote: > None of that helps.? I'm building a new system.? This is a production > system.??I?never had problems in the past with upgrading so I went > ahead and did it.? Bad move.? Unless anyone has any other ideas, I > will just keep working on setting up the new system.? I have to get > something running again for my users. > > Ken > >>> Jules Field via ZendTo 10/25/2018 10:53 AM >>> > > Yes, those directories do need to be writable by whatever user and group your > web server is running as. > > If you are using SELinux (most likely if you are using CentOS or > RedHat), then I would also advise > restorecon -FRv /opt/zendto /var/zendto > > to reset all the SELinux attributes to the values configured by my > Installer. > Also, if you think it might be an SELinux problem, you can switch it > into "permissive" mode by > setenforce permissive > > systemctl restart httpd > > systemctl restart clamd at scan > > To switch it back to "enforcing", you then do > setenforce enforcing > > systemctl restart httpd > > systemctl restart clamd at scan > > Cheers, > Jules. > On 25/10/2018 14:31, Gray McCord via ZendTo wrote: >> I?ve seen that message as well. Check the file permissions on the >> /opt/zendto directories. Seems like I needed to make them writeable >> by the apache user, but I could be mistaken. >> Gray McCord >> /Adapt, Mutate, Migrate, or Die/ >> -C. Darwin >> *From:* ZendTo *On Behalf Of *Ken Etter via >> ZendTo >> *Sent:* Thursday, October 25, 2018 8:26 AM >> *To:* ZendTo List >> *Cc:* Ken Etter >> *Subject:* Re: [ZendTo] Zend.to error during drop-off >> Going back through the mailing list archives, I see that I am having >> exactly the same problem as Kevin O'Connor in this thread: >> http://jul.es/pipermail/zendto/2018-June/003208.html >> >> Files are uploaded, but I get that error message and the email is not >> sent. >> There is no stated resolution in that thread. Any suggestions or do I >> have to rebuild a brand new Zend.To server? >> Zend.To has been fairly solid for me...a bit of a pain to find this >> upgrade to be so fragile. >> Ken >> >>> Ken Etter via ZendTo > 10/25/2018 >> 8:38 AM >>> >> I am running this on Ubuntu 16.04.5 LTS if that matters. >> >> Ken >> >>> Ken Etter via ZendTo > 10/25/2018 >> 8:36 AM >>> >> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything >> appeared to go ok. But when I click drop-off files, I get an error >> that states: "Sorry, I failed to drop-off your files! Note that you >> cannot drop-off directories, only files." I'm not dropping off a >> directory, just a single file. I tried a couple different file types >> - same error each time. Any suggestions for fixing this? Thanks! >> >> >> *Ken Etter*, System Administrator >> Architectural Group >> 260.432.9337 | msktd.com >> >> >> >> _______________________________________________ >> ZendTo mailing list >> ZendTo at zend.to >> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 > > 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 Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM IMPORTANT: This email is intended for the use of the individual addressee(s) named above and may contain information that is confidential, privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational religious beliefs. If you are not the intended recipient, any dissemination, distribution or copying of this email is not authorised (either explicitly or implicitly) and constitutes an irritating social faux pas. Unless the word absquatulation has been used in its correct context somewhere other than in this warning, it does not have any legal or no grammatical use and may be ignored. No animals were harmed in the transmission of this email, although the kelpie next door is living on borrowed time, let me tell you. Those of you with an overwhelming fear of the unknown will be gratified to learn that there is no hidden message revealed by reading this warning backwards, so just ignore that Alert Notice from Microsoft. However, by pouring a complete circle of salt around yourself and your computer you can ensure that no harm befalls you and your pets. If you have received this email in error, please add some nutmeg and egg whites, whisk and place in a warm oven for 40 minutes. www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: not available URL: From kle at msktd.com Thu Oct 25 16:22:08 2018 From: kle at msktd.com (Ken Etter) Date: Thu, 25 Oct 2018 11:22:08 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: <5BD1DDFE0200009B00407B87@mail.msktd.com> References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <023a01d46c67$09765bd0$1c631370$@sangabriel.com> <705D5031020000C3C84B1EE2@mail.msktd.com> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <43f7fe6f-fb01-fbc2-20e8-69aad2903060@Zend.To> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> Message-ID: Yep, PHP 7.2 is installed. I've run through the installer multiple times now. No change, still get the error. Ken >>> Jules Field 10/25/2018 11:15 AM >>> > Do you have PHP 7.2 installed? My Installer can be run in stages, and those stages can be run independently. So you might want to download the Installer, unpack it and wander into it. In what will obviously be the right sub-dir for your OS, you will see the numbered scripts. # cd install.ZendTo/CentOS-RedHat/ # ls 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 # If your web server is already working nicely, then you can probably skip stage 1 (though it won't do any harm). If you haven't installed PHP 7.2 along with things like the sodium extension, then run stage 2 which installs PHP. (Grab a backup copy of your ZendTo installation first, as it may have to remove the *whole* of PHP first which can also remove ZendTo and other PHP applications in the process, before it can install the correct version). Stages 3 and 5 shouldn't do any damage, but will add any new settings they need for PHP and so on. Stage 7 does the actual ZendTo installation itself, which it will do as an upgrade if it finds a zendto RPM already installed. Well worth running. Stage 8 is only relevant if you are using SELinux, and won't do anything if you're not. Since version 4, ZendTo no longer needs any form of custom-built PHP or anything like that. So there's no recompiling to be done. Then if you have a previous preferences.php and/or zendto.conf, you need to use /opt/zendto/bin/upgrade_preferences_php and /opt/zendto/bin/upgrade_zendto_conf to upgrade those files. Also, if you have done an RPM upgrade from ZendTo 4, you probably have a whole stack of *.rpmnew files in /opt/zendto/templates. You want to move each of those into place so they replace your old *.tpl files. As I said, it really is faster/easier/better to build v5 from scratch, its requirements are so different from v4. Hope that helps, Jules. On 25/10/2018 15:59, Ken Etter wrote: None of that helps. I'm building a new system. This is a production system. I never had problems in the past with upgrading so I went ahead and did it. Bad move. Unless anyone has any other ideas, I will just keep working on setting up the new system. I have to get something running again for my users. Ken >>> Jules Field via ZendTo ( mailto:zendto at zend.to) 10/25/2018 10:53 AM >>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise restorecon -FRv /opt/zendto /var/zendto to reset all the SELinux attributes to the values configured by my Installer. Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by setenforce permissive systemctl restart httpd systemctl restart clamd at scan To switch it back to "enforcing", you then do setenforce enforcing systemctl restart httpd systemctl restart clamd at scan Cheers, Jules. On 25/10/2018 14:31, Gray McCord via ZendTo wrote: I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo ( mailto:zendto-bounces at zend.to) On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List ( mailto:zendto at zend.to) Cc: Ken Etter ( mailto:KLE at msktd.com) Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: http://jul.es/pipermail/zendto/2018-June/003208.html ( https://emea01.safel inks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fpipermail%2Fzendto%2F2018-June%2F003208.html&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=%2FMQVOSO5ZjLwkrQ991eChCvoSfFOLwm3yUcnFSzoRc0%3D&reserved=0) Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmsktd.com%2F&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=XsZydsv5daB1usPtdakyqf%2BjPxBLH9n8NbGcrjhC34Y%3D&reserved=0) _______________________________________________ZendTo mailing listZendTo at zend.tohttps://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0) Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'The past is supposed to be a place of reference, not a place ofresidence! There is a reason why your car has a big windshield anda small rearview mirror. You are supposed to keep your eyes on whereyou are going, and just occasionally check out where you have been.' - Willie Jolleywww.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACMIMPORTANT: This email is intended for the use of the individualaddressee(s) named above and may contain information that isconfidential, privileged or unsuitable for overly sensitive personswith low self-esteem, no sense of humour or irrational religiousbeliefs. If you are not the intended recipient, any dissemination,distribution or copying of this email is not authorised (eitherexplicitly or implicitly) and constitutes an irritating social fauxpas.Unless the word absquatulation has been used in its correct contextsomewhere other than in this warning, it does not have any legalor no grammatical use and may be ignored. No animals were harmedin the transmission of this email, although the kelpie next dooris living on borrowed time, let me tell you. Those of you with anoverwhelming fear of the unknown will be gratified to learn thatthere is no hidden message revealed by reading this warning backwards,so just ignore that Alert Notice from Microsoft.However, by pouring a complete circle of salt around yourself andyour computer you can ensure that no harm befalls you and your pets.If you have received this email in error, please add some nutmegand egg whites, whisk and place in a warm oven for 40 minutes.www.Zend.ToTwitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From Jules at Zend.To Thu Oct 25 16:41:03 2018 From: Jules at Zend.To (Jules Field) Date: Thu, 25 Oct 2018 16:41:03 +0100 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <705D5031020000C3C84B1EE2@mail.msktd.com> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <43f7fe6f-fb01-fbc2-20e8-69aad2903060@Zend.To> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> Message-ID: <0ebb65e4-8426-00ba-2670-26a0df7c8694@Zend.To> Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. Then "pwconv" so the change takes effect. Then try this ??? su - apache (or whatever user your Apache is running as) ??? clamdscan /var/zendto/* ??? clamdscan --fdpass /var/zendto/* ??? exit What happened? Did the virus scans both complete successfully? If not, and you're running CentOS/RedHat 7, try this and then give the above another try: ??? groupmems --group virusgroup --add apache ??? systemctl restart httpd I added that extra groupmems command to the Installer a day or two ago when I discovered that RedHat/CentOS had changed their group membership rules in an update. Any improvement? Cheers, Jules. P.S. Otherwise, if you can give me remote ssh access I can login myself and take a look for you. I would be interested to see what it is, if it's not any of the above. On 25/10/2018 16:22, Ken Etter wrote: > Yep, PHP 7.2 is installed.? I've run through the installer multiple > times now.? No change, still get the error. > Ken > >>> Jules Field 10/25/2018 11:15 AM >>> > > Do you have PHP 7.2 installed? > > My Installer can be run in stages, and those stages can be run > independently. > So you might want to download the Installer, unpack it and wander into > it. In what will obviously be the right sub-dir for your OS, you will > see the numbered scripts. > # cd install.ZendTo/CentOS-RedHat/ > > # ls > > 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 > > 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 > > # > > If your web server is already working nicely, then you can probably > skip stage 1 (though it won't do any harm). > If you haven't installed PHP 7.2 along with things like the sodium > extension, then run stage 2 which installs PHP. (Grab a backup copy of > your ZendTo installation first, as it may have to remove the *whole* > of PHP first which can also remove ZendTo and other PHP applications > in the process, before it can install the correct version). > Stages 3 and 5 shouldn't do any damage, but will add any new settings > they need for PHP and so on. > Stage 7 does the actual ZendTo installation itself, which it will do > as an upgrade if it finds a zendto RPM already installed. Well worth > running. > Stage 8 is only relevant if you are using SELinux, and won't do > anything if you're not. > Since version 4, ZendTo no longer needs any form of custom-built PHP > or anything like that. So there's no recompiling to be done. > Then if you have a previous preferences.php and/or zendto.conf, you > need to use > /opt/zendto/bin/upgrade_preferences_php > and > /opt/zendto/bin/upgrade_zendto_conf > to upgrade those files. > Also, if you have done an RPM upgrade from ZendTo 4, you probably have > a whole stack of *.rpmnew files in /opt/zendto/templates. You want to > move each of those into place so they replace your old *.tpl files. > As I said, it really is faster/easier/better to build v5 from scratch, > its requirements are so different from v4. > Hope that helps, > Jules. > On 25/10/2018 15:59, Ken Etter wrote: >> None of that helps. I'm building a new system. This is a production >> system. I never had problems in the past with upgrading so I went >> ahead and did it. Bad move. Unless anyone has any other ideas, I will >> just keep working on setting up the new system. I have to get >> something running again for my users. >> >> Ken >> >>> Jules Field via ZendTo 10/25/2018 10:53 AM >>> >> > Yes, those directories do need to be writable by whatever user and >> group your web server is running as. >> >> If you are using SELinux (most likely if you are using CentOS or >> RedHat), then I would also advise >> restorecon -FRv /opt/zendto /var/zendto >> >> to reset all the SELinux attributes to the values configured by my >> Installer. >> Also, if you think it might be an SELinux problem, you can switch it >> into "permissive" mode by >> setenforce permissive >> >> systemctl restart httpd >> >> systemctl restart clamd at scan >> >> To switch it back to "enforcing", you then do >> setenforce enforcing >> >> systemctl restart httpd >> >> systemctl restart clamd at scan >> >> Cheers, >> Jules. >> On 25/10/2018 14:31, Gray McCord via ZendTo wrote: >>> I?ve seen that message as well. Check the file permissions on the >>> /opt/zendto directories. Seems like I needed to make them writeable >>> by the apache user, but I could be mistaken. >>> Gray McCord >>> /Adapt, Mutate, Migrate, or Die/ >>> -C. Darwin >>> *From:* ZendTo *On Behalf Of *Ken Etter via >>> ZendTo >>> *Sent:* Thursday, October 25, 2018 8:26 AM >>> *To:* ZendTo List >>> *Cc:* Ken Etter >>> *Subject:* Re: [ZendTo] Zend.to error during drop-off >>> Going back through the mailing list archives, I see that I am having >>> exactly the same problem as Kevin O'Connor in this thread: >>> http://jul.es/pipermail/zendto/2018-June/003208.html >>> >>> Files are uploaded, but I get that error message and the email is >>> not sent. >>> There is no stated resolution in that thread. Any suggestions or do >>> I have to rebuild a brand new Zend.To server? >>> Zend.To has been fairly solid for me...a bit of a pain to find this >>> upgrade to be so fragile. >>> Ken >>> >>> Ken Etter via ZendTo > >>> 10/25/2018 8:38 AM >>> >>> I am running this on Ubuntu 16.04.5 LTS if that matters. >>> >>> Ken >>> >>> Ken Etter via ZendTo > >>> 10/25/2018 8:36 AM >>> >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything >>> appeared to go ok. But when I click drop-off files, I get an error >>> that states: "Sorry, I failed to drop-off your files! Note that you >>> cannot drop-off directories, only files." I'm not dropping off a >>> directory, just a single file. I tried a couple different file types >>> - same error each time. Any suggestions for fixing this? Thanks! >>> >>> >>> *Ken Etter*, System Administrator >>> Architectural Group >>> 260.432.9337 | msktd.com >>> >>> >>> >>> _______________________________________________ >>> ZendTo mailing list >>> ZendTo at zend.to >>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 >> >> 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 > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > IMPORTANT: This email is intended for the use of the individual > addressee(s) named above and may contain information that is > confidential, privileged or unsuitable for overly sensitive persons > with low self-esteem, no sense of humour or irrational religious > beliefs. If you are not the intended recipient, any dissemination, > distribution or copying of this email is not authorised (either > explicitly or implicitly) and constitutes an irritating social faux > pas. > > Unless the word absquatulation has been used in its correct context > somewhere other than in this warning, it does not have any legal > or no grammatical use and may be ignored. No animals were harmed > in the transmission of this email, although the kelpie next door > is living on borrowed time, let me tell you. Those of you with an > overwhelming fear of the unknown will be gratified to learn that > there is no hidden message revealed by reading this warning backwards, > so just ignore that Alert Notice from Microsoft. > > However, by pouring a complete circle of salt around yourself and > your computer you can ensure that no harm befalls you and your pets. > If you have received this email in error, please add some nutmeg > and egg whites, whisk and place in a warm oven for 40 minutes. > > www.Zend.To > Twitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'It's very unlikely indeed he will ever recover consciousness, and if he does he won't be the Julian you knew.' - A hospital consultant I proved very wrong in 2007 :-) www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: not available URL: From kle at msktd.com Thu Oct 25 16:47:30 2018 From: kle at msktd.com (Ken Etter) Date: Thu, 25 Oct 2018 11:47:30 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: <5BD1E4180200002500407BED@mail.msktd.com> References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <705D5031020000C3C84B1EE2@mail.msktd.com> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <43f7fe6f-fb01-fbc2-20e8-69aad2903060@Zend.To> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <0ebb65e4-8426-00ba-2670-26a0df7c8694@Zend.To> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1E592020000130012D942@mail.msktd.com> Message-ID: I'm running Ubuntu 16.04.5 clamdscan /var/zendto/* <-- this one failed with permission denied clamdscan --fdpass /var/zendto/* <-- this one displayed some warnings, then got to /var/zendto/cache: OK and then seemed to hang. Ken >>> Jules Field 10/25/2018 11:41 AM >>> > Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. Then "pwconv" so the change takes effect. Then try this su - apache (or whatever user your Apache is running as) clamdscan /var/zendto/* clamdscan --fdpass /var/zendto/* exit What happened? Did the virus scans both complete successfully? If not, and you're running CentOS/RedHat 7, try this and then give the above another try: groupmems --group virusgroup --add apache systemctl restart httpd I added that extra groupmems command to the Installer a day or two ago when I discovered that RedHat/CentOS had changed their group membership rules in an update. Any improvement? Cheers, Jules. P.S. Otherwise, if you can give me remote ssh access I can login myself and take a look for you. I would be interested to see what it is, if it's not any of the above. On 25/10/2018 16:22, Ken Etter wrote: Yep, PHP 7.2 is installed. I've run through the installer multiple times now. No change, still get the error. Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:15 AM >>> > Do you have PHP 7.2 installed? My Installer can be run in stages, and those stages can be run independently. So you might want to download the Installer, unpack it and wander into it. In what will obviously be the right sub-dir for your OS, you will see the numbered scripts. # cd install.ZendTo/CentOS-RedHat/ # ls 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 # If your web server is already working nicely, then you can probably skip stage 1 (though it won't do any harm). If you haven't installed PHP 7.2 along with things like the sodium extension, then run stage 2 which installs PHP. (Grab a backup copy of your ZendTo installation first, as it may have to remove the *whole* of PHP first which can also remove ZendTo and other PHP applications in the process, before it can install the correct version). Stages 3 and 5 shouldn't do any damage, but will add any new settings they need for PHP and so on. Stage 7 does the actual ZendTo installation itself, which it will do as an upgrade if it finds a zendto RPM already installed. Well worth running. Stage 8 is only relevant if you are using SELinux, and won't do anything if you're not. Since version 4, ZendTo no longer needs any form of custom-built PHP or anything like that. So there's no recompiling to be done. Then if you have a previous preferences.php and/or zendto.conf, you need to use /opt/zendto/bin/upgrade_preferences_php and /opt/zendto/bin/upgrade_zendto_conf to upgrade those files. Also, if you have done an RPM upgrade from ZendTo 4, you probably have a whole stack of *.rpmnew files in /opt/zendto/templates. You want to move each of those into place so they replace your old *.tpl files. As I said, it really is faster/easier/better to build v5 from scratch, its requirements are so different from v4. Hope that helps, Jules. On 25/10/2018 15:59, Ken Etter wrote: None of that helps. I'm building a new system. This is a production system. I never had problems in the past with upgrading so I went ahead and did it. Bad move. Unless anyone has any other ideas, I will just keep working on setting up the new system. I have to get something running again for my users. Ken >>> Jules Field via ZendTo ( mailto:zendto at zend.to) 10/25/2018 10:53 AM >>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise restorecon -FRv /opt/zendto /var/zendto to reset all the SELinux attributes to the values configured by my Installer. Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by setenforce permissive systemctl restart httpd systemctl restart clamd at scan To switch it back to "enforcing", you then do setenforce enforcing systemctl restart httpd systemctl restart clamd at scan Cheers, Jules. On 25/10/2018 14:31, Gray McCord via ZendTo wrote: I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo ( mailto:zendto-bounces at zend.to) On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List ( mailto:zendto at zend.to) Cc: Ken Etter ( mailto:KLE at msktd.com) Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: http://jul.es/pipermail/zendto/2018-June/003208.html ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fpipermail%2Fzendto%2F2018-June%2F003208.html&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=%2FMQVOSO5ZjLwkrQ991eChCvoSfFOLwm3yUcnFSzoRc0%3D&reserved=0) Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmsktd.com%2F&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=XsZydsv5daB1usPtdakyqf%2BjPxBLH9n8NbGcrjhC34Y%3D&reserved=0) _______________________________________________ZendTo mailing listZendTo at zend.tohttps://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0) Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'The past is supposed to be a place of reference, not a place ofresidence! There is a reason why your car has a big windshield anda small rearview mirror. You are supposed to keep your eyes on whereyou are going, and just occasionally check out where you have been.' - Willie Jolleywww.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACMIMPORTANT: This email is intended for the use of the individualaddressee(s) named above and may contain information that isconfidential, privileged or unsuitable for overly sensitive personswith low sel f-esteem, no sense of humour or irrational religiousbeliefs. If you are not the intended recipient, any dissemination,distribution or copying of this email is not authorised (eitherexplicitly or implicitly) and constitutes an irritating social fauxpas.Unless the word absquatulation has been used in its correct contextsomewhere other than in this warning, it does not have any legalor no grammatical use and may be ignored. No animals were harmedin the transmission of this email, although the kelpie next dooris living on borrowed time, let me tell you. Those of you with anoverwhelming fear of the unknown will be gratified to learn thatthere is no hidden message revealed by reading this warning backwards,so just ignore that Alert Notice from Microsoft.However, by pouring a complete circle of salt around yourself andyour computer you can ensure that no harm befalls you and your pets.If you have received this email in error, please add some nutmegand egg whites, whisk and place in a warm oven for 40 minutes.www.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'It's very unlikely indeed he will ever recover consciousness, and if he does he won't be the Julian you knew.' - A hospital consultant I proved very wrong in 2007 :-)www.Zend.ToTwitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From gdm at sangabriel.com Thu Oct 25 16:48:04 2018 From: gdm at sangabriel.com (Gray McCord) Date: Thu, 25 Oct 2018 10:48:04 -0500 Subject: [ZendTo] {Disarmed} Re: Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <705D5031020000C3C84B1EE2@mail.msktd.com> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <43f7fe6f-fb01-fbc2-20e8-69aad2903060@Zend.To> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <0ebb65e4-8426-00ba-2670-26a0df7c8694@Zend.To> Message-ID: Jules, you triggered something I found a few weeks ago: a problem with the latest clamd update on my Centos 7 Zendto systems. After updating to clamd v100.1, uploads failed in Zendto. The error was that the clamd daemon could not access the needed socket file in /var/run/clamd.scan The problem was that the update apparently changed something that altered the group used by the clamd daemon to "virusgroup" from "clamscan" Changing the group owner of /var/run/clamd.scan to "clamscan" fixed it BUT Every time the system rebooted, the /var/run/clamd.scan directory was recreated with the wrong group owner "virusgroup" The fix required editing a template file, /usr/lib/tmpfiles.d/clamd.scan.conf, and changing the contents: From: d /run/clamd.scan 0710 clamscan virusgroup To: d /run/clamd.scan 0710 clamscan clamscan That fixes it! Maybe this is the issue? Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo on behalf of Jules Field via ZendTo Organization: ZendTo Reply-To: ZendTo Users Date: Thursday, October 25, 2018 at 10:41 AM To: Ken Etter , ZendTo List Cc: Jules Field Subject: {Disarmed} Re: [ZendTo] Zend.to error during drop-off Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. Then "pwconv" so the change takes effect. Then try this su - apache (or whatever user your Apache is running as) clamdscan /var/zendto/* clamdscan --fdpass /var/zendto/* exit What happened? Did the virus scans both complete successfully? If not, and you're running CentOS/RedHat 7, try this and then give the above another try: groupmems --group virusgroup --add apache systemctl restart httpd I added that extra groupmems command to the Installer a day or two ago when I discovered that RedHat/CentOS had changed their group membership rules in an update. Any improvement? Cheers, Jules. P.S. Otherwise, if you can give me remote ssh access I can login myself and take a look for you. I would be interested to see what it is, if it's not any of the above. On 25/10/2018 16:22, Ken Etter wrote: Yep, PHP 7.2 is installed. I've run through the installer multiple times now. No change, still get the error. Ken >>> Jules Field 10/25/2018 11:15 AM >>> > Do you have PHP 7.2 installed? My Installer can be run in stages, and those stages can be run independently. So you might want to download the Installer, unpack it and wander into it. In what will obviously be the right sub-dir for your OS, you will see the numbered scripts. # cd install.ZendTo/CentOS-RedHat/ # ls 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 # If your web server is already working nicely, then you can probably skip stage 1 (though it won't do any harm). If you haven't installed PHP 7.2 along with things like the sodium extension, then run stage 2 which installs PHP. (Grab a backup copy of your ZendTo installation first, as it may have to remove the *whole* of PHP first which can also remove ZendTo and other PHP applications in the process, before it can install the correct version). Stages 3 and 5 shouldn't do any damage, but will add any new settings they need for PHP and so on. Stage 7 does the actual ZendTo installation itself, which it will do as an upgrade if it finds a zendto RPM already installed. Well worth running. Stage 8 is only relevant if you are using SELinux, and won't do anything if you're not. Since version 4, ZendTo no longer needs any form of custom-built PHP or anything like that. So there's no recompiling to be done. Then if you have a previous preferences.php and/or zendto.conf, you need to use /opt/zendto/bin/upgrade_preferences_php and /opt/zendto/bin/upgrade_zendto_conf to upgrade those files. Also, if you have done an RPM upgrade from ZendTo 4, you probably have a whole stack of *.rpmnew files in /opt/zendto/templates. You want to move each of those into place so they replace your old *.tpl files. As I said, it really is faster/easier/better to build v5 from scratch, its requirements are so different from v4. Hope that helps, Jules. On 25/10/2018 15:59, Ken Etter wrote: None of that helps. I'm building a new system. This is a production system. I never had problems in the past with upgrading so I went ahead and did it. Bad move. Unless anyone has any other ideas, I will just keep working on setting up the new system. I have to get something running again for my users. Ken >>> Jules Field via ZendTo 10/25/2018 10:53 AM >>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise restorecon -FRv /opt/zendto /var/zendto to reset all the SELinux attributes to the values configured by my Installer. Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by setenforce permissive systemctl restart httpd systemctl restart clamd at scan To switch it back to "enforcing", you then do setenforce enforcing systemctl restart httpd systemctl restart clamd at scan Cheers, Jules. On 25/10/2018 14:31, Gray McCord via ZendTo wrote: I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List Cc: Ken Etter Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: MailScanner has detected a possible fraud attempt from "emea01.safelinks.protection.outlook.com" claiming to be http://jul.es/pipermail/zendto/2018-June/003208.html Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | MailScanner has detected a possible fraud attempt from "emea01.safelinks.protection.outlook.com" claiming to be msktd.com _______________________________________________ ZendTo mailing list ZendTo at zend.to https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 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 Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM IMPORTANT: This email is intended for the use of the individual addressee(s) named above and may contain information that is confidential, privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational religious beliefs. If you are not the intended recipient, any dissemination, distribution or copying of this email is not authorised (either explicitly or implicitly) and constitutes an irritating social faux pas. Unless the word absquatulation has been used in its correct context somewhere other than in this warning, it does not have any legal or no grammatical use and may be ignored. No animals were harmed in the transmission of this email, although the kelpie next door is living on borrowed time, let me tell you. Those of you with an overwhelming fear of the unknown will be gratified to learn that there is no hidden message revealed by reading this warning backwards, so just ignore that Alert Notice from Microsoft. However, by pouring a complete circle of salt around yourself and your computer you can ensure that no harm befalls you and your pets. If you have received this email in error, please add some nutmeg and egg whites, whisk and place in a warm oven for 40 minutes. www.Zend.To Twitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'It's very unlikely indeed he will ever recover consciousness, and if he does he won't be the Julian you knew.' ? - A hospital consultant I proved very wrong in 2007 :-) www.Zend.To Twitter: @JulesFM _______________________________________________ ZendTo mailing list ZendTo at zend.to http://jul.es/mailman/listinfo/zendto -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10426 bytes Desc: not available URL: From kbe2 at lehigh.edu Thu Oct 25 17:13:42 2018 From: kbe2 at lehigh.edu (Keith Erekson) Date: Thu, 25 Oct 2018 12:13:42 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <705D5031020000C3C84B1EE2@mail.msktd.com> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <43f7fe6f-fb01-fbc2-20e8-69aad2903060@Zend.To> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <0e bb65e4-8426-00ba-2670-26a0df7c8694@Zend.To> <77028A24-566D-467E-A686-7FE28DDAB946@lehigh.edu> Message-ID: Easier to use "chsh www-data" or whatever your Apache user is. ~Keith > On Oct 25, 2018, at 11:41 AM, Jules Field via ZendTo wrote: > > Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. > Then "pwconv" so the change takes effect. > Then try this > su - apache (or whatever user your Apache is running as) > clamdscan /var/zendto/* > clamdscan --fdpass /var/zendto/* > exit > What happened? Did the virus scans both complete successfully? > > If not, and you're running CentOS/RedHat 7, try this and then give the above another try: > groupmems --group virusgroup --add apache > systemctl restart httpd > > I added that extra groupmems command to the Installer a day or two ago when I discovered that RedHat/CentOS had changed their group membership rules in an update. > > Any improvement? > > Cheers, > Jules. > > P.S. Otherwise, if you can give me remote ssh access I can login myself and take a look for you. I would be interested to see what it is, if it's not any of the above. > >> On 25/10/2018 16:22, Ken Etter wrote: >> Yep, PHP 7.2 is installed. I've run through the installer multiple times now. No change, still get the error. >> Ken >> >>> Jules Field 10/25/2018 11:15 AM >>> >> > Do you have PHP 7.2 installed? >> >> My Installer can be run in stages, and those stages can be run independently. >> So you might want to download the Installer, unpack it and wander into it. In what will obviously be the right sub-dir for your OS, you will see the numbered scripts. >> # cd install.ZendTo/CentOS-RedHat/ >> >> # ls >> >> 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 >> >> 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 >> >> # >> >> If your web server is already working nicely, then you can probably skip stage 1 (though it won't do any harm). >> If you haven't installed PHP 7.2 along with things like the sodium extension, then run stage 2 which installs PHP. (Grab a backup copy of your ZendTo installation first, as it may have to remove the *whole* of PHP first which can also remove ZendTo and other PHP applications in the process, before it can install the correct version). >> Stages 3 and 5 shouldn't do any damage, but will add any new settings they need for PHP and so on. >> Stage 7 does the actual ZendTo installation itself, which it will do as an upgrade if it finds a zendto RPM already installed. Well worth running. >> Stage 8 is only relevant if you are using SELinux, and won't do anything if you're not. >> Since version 4, ZendTo no longer needs any form of custom-built PHP or anything like that. So there's no recompiling to be done. >> Then if you have a previous preferences.php and/or zendto.conf, you need to use >> /opt/zendto/bin/upgrade_preferences_php >> and >> /opt/zendto/bin/upgrade_zendto_conf >> to upgrade those files. >> Also, if you have done an RPM upgrade from ZendTo 4, you probably have a whole stack of *.rpmnew files in /opt/zendto/templates. You want to move each of those into place so they replace your old *.tpl files. >> As I said, it really is faster/easier/better to build v5 from scratch, its requirements are so different from v4. >> Hope that helps, >> Jules. >>> On 25/10/2018 15:59, Ken Etter wrote: >>> None of that helps. I'm building a new system. This is a production system. I never had problems in the past with upgrading so I went ahead and did it. Bad move. Unless anyone has any other ideas, I will just keep working on setting up the new system. I have to get something running again for my users. >>> >>> Ken >>> >>> Jules Field via ZendTo 10/25/2018 10:53 AM >>> >>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. >>> >>> If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise >>> restorecon -FRv /opt/zendto /var/zendto >>> >>> to reset all the SELinux attributes to the values configured by my Installer. >>> Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by >>> setenforce permissive >>> >>> systemctl restart httpd >>> >>> systemctl restart clamd at scan >>> >>> To switch it back to "enforcing", you then do >>> setenforce enforcing >>> >>> systemctl restart httpd >>> >>> systemctl restart clamd at scan >>> >>> Cheers, >>> Jules. >>>> On 25/10/2018 14:31, Gray McCord via ZendTo wrote: >>>> I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. >>>> Gray McCord >>>> Adapt, Mutate, Migrate, or Die >>>> -C. Darwin >>>> From: ZendTo On Behalf Of Ken Etter via ZendTo >>>> Sent: Thursday, October 25, 2018 8:26 AM >>>> To: ZendTo List >>>> Cc: Ken Etter >>>> Subject: Re: [ZendTo] Zend.to error during drop-off >>>> Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: http://jul.es/pipermail/zendto/2018-June/003208.html >>>> Files are uploaded, but I get that error message and the email is not sent. >>>> There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? >>>> Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. >>>> Ken >>>> >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> >>>> I am running this on Ubuntu 16.04.5 LTS if that matters. >>>> >>>> Ken >>>> >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> >>>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! >>>> >>>> >>>> Ken Etter, System Administrator >>>> Architectural Group >>>> 260.432.9337 | msktd.com >>>> >>>> >>>> >>>> _______________________________________________ >>>> ZendTo mailing list >>>> ZendTo at zend.to >>>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 >>> >>> 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 >> >> Jules >> >> -- >> Julian Field MEng CEng CITP MBCS MIEEE MACM >> >> IMPORTANT: This email is intended for the use of the individual >> addressee(s) named above and may contain information that is >> confidential, privileged or unsuitable for overly sensitive persons >> with low self-esteem, no sense of humour or irrational religious >> beliefs. If you are not the intended recipient, any dissemination, >> distribution or copying of this email is not authorised (either >> explicitly or implicitly) and constitutes an irritating social faux >> pas. >> >> Unless the word absquatulation has been used in its correct context >> somewhere other than in this warning, it does not have any legal >> or no grammatical use and may be ignored. No animals were harmed >> in the transmission of this email, although the kelpie next door >> is living on borrowed time, let me tell you. Those of you with an >> overwhelming fear of the unknown will be gratified to learn that >> there is no hidden message revealed by reading this warning backwards, >> so just ignore that Alert Notice from Microsoft. >> >> However, by pouring a complete circle of salt around yourself and >> your computer you can ensure that no harm befalls you and your pets. >> If you have received this email in error, please add some nutmeg >> and egg whites, whisk and place in a warm oven for 40 minutes. >> >> www.Zend.To >> Twitter: @JulesFM > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'It's very unlikely indeed he will ever recover consciousness, and > if he does he won't be the Julian you knew.' > - A hospital consultant I proved very wrong in 2007 :-) > > www.Zend.To > Twitter: @JulesFM > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Thu Oct 25 17:43:06 2018 From: Jules at Zend.To (Jules Field) Date: Thu, 25 Oct 2018 17:43:06 +0100 Subject: [ZendTo] {Disarmed} Re: Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <43f7fe6f-fb01-fbc2-20e8-69aad2903060@Zend.To> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <0ebb65e4-8426-00ba-2670-26a0df7c8694@Zend.To> Message-ID: Adding "apache" to the "virusgroup" is a safer way of fixing this problem. Cheers, Jules. On 25/10/2018 16:48, Gray McCord via ZendTo wrote: > > Jules, you triggered something I found a few weeks ago: a problem with > the latest clamd update on my Centos 7 Zendto systems. > > After updating to clamd v100.1, uploads failed in Zendto. The error > was that the clamd daemon could not access the needed socket file in > /var/run/clamd.scan > > The problem was that the update apparently changed something that > altered the group used by the clamd daemon to "virusgroup" from > "clamscan" Changing the group owner of /var/run/clamd.scan to > "clamscan" fixed it BUT > > Every time the system rebooted, the /var/run/clamd.scan directory was > recreated with the wrong group owner "virusgroup" > > The fix required editing a template file, > /usr/lib/tmpfiles.d/clamd.scan.conf, and changing the contents: > > From: > > d /run/clamd.scan 0710 clamscan virusgroup > > To: > > d /run/clamd.scan 0710 clamscan clamscan > > That fixes it! > > Maybe this is the issue? > > Gray McCord > > /Adapt, Mutate, Migrate, or Die/ > > -C. Darwin > > *From: *ZendTo on behalf of Jules Field via > ZendTo > *Organization: *ZendTo > *Reply-To: *ZendTo Users > *Date: *Thursday, October 25, 2018 at 10:41 AM > *To: *Ken Etter , ZendTo List > *Cc: *Jules Field > *Subject: *{Disarmed} Re: [ZendTo] Zend.to error during drop-off > > Edit your /etc/passwd file to set the shell for your Apache user to > /bin/bash. > Then "pwconv" so the change takes effect. > Then try this > ??? su - apache (or whatever user your Apache is running as) > ??? clamdscan /var/zendto/* > ??? clamdscan --fdpass /var/zendto/* > ??? exit > What happened? Did the virus scans both complete successfully? > > If not, and you're running CentOS/RedHat 7, try this and then give the > above another try: > ??? groupmems --group virusgroup --add apache > ??? systemctl restart httpd > > I added that extra groupmems command to the Installer a day or two ago > when I discovered that RedHat/CentOS had changed their group > membership rules in an update. > > Any improvement? > > Cheers, > Jules. > > P.S. Otherwise, if you can give me remote ssh access I can login > myself and take a look for you. I would be interested to see what it > is, if it's not any of the above. > > On 25/10/2018 16:22, Ken Etter wrote: > > Yep, PHP 7.2 is installed.? I've run through the installer > multiple times now.? No change, still get the error. > > Ken > > >>> Jules Field 10/25/2018 > 11:15 AM >>> > > > Do you have PHP 7.2 installed? > > My Installer can be run in stages, and those stages can be run > independently. > > So you might want to download the Installer, unpack it and wander > into it. In what will obviously be the right sub-dir for your OS, > you will see the numbered scripts. > > # cd install.ZendTo/CentOS-RedHat/ > > # ls > > 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 > > 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 > > # > > If your web server is already working nicely, then you can > probably skip stage 1 (though it won't do any harm). > > If you haven't installed PHP 7.2 along with things like the sodium > extension, then run stage 2 which installs PHP. (Grab a backup > copy of your ZendTo installation first, as it may have to remove > the *whole* of PHP first which can also remove ZendTo and other > PHP applications in the process, before it can install the correct > version). > > Stages 3 and 5 shouldn't do any damage, but will add any new > settings they need for PHP and so on. > > Stage 7 does the actual ZendTo installation itself, which it will > do as an upgrade if it finds a zendto RPM already installed. Well > worth running. > > Stage 8 is only relevant if you are using SELinux, and won't do > anything if you're not. > > Since version 4, ZendTo no longer needs any form of custom-built > PHP or anything like that. So there's no recompiling to be done. > > Then if you have a previous preferences.php and/or zendto.conf, > you need to use > > /opt/zendto/bin/upgrade_preferences_php > > and > > /opt/zendto/bin/upgrade_zendto_conf > > to upgrade those files. > > Also, if you have done an RPM upgrade from ZendTo 4, you probably > have a whole stack of *.rpmnew files in /opt/zendto/templates. You > want to move each of those into place so they replace your old > *.tpl files. > > As I said, it really is faster/easier/better to build v5 from > scratch, its requirements are so different from v4. > > Hope that helps, > > Jules. > > On 25/10/2018 15:59, Ken Etter wrote: > > None of that helps. I'm building a new system. This is a > production system. I never had problems in the past with > upgrading so I went ahead and did it. Bad move. Unless anyone > has any other ideas, I will just keep working on setting up > the new system. I have to get something running again for my > users. > > Ken > > >>> Jules Field via ZendTo > 10/25/2018 10:53 AM >>> > > > Yes, those directories do need to be writable by whatever user and group > your web server is running as. > > If you are using SELinux (most likely if you are using CentOS > or RedHat), then I would also advise > > restorecon -FRv /opt/zendto /var/zendto > > to reset all the SELinux attributes to the values configured > by my Installer. > > Also, if you think it might be an SELinux problem, you can > switch it into "permissive" mode by > > setenforce permissive > > systemctl restart httpd > > systemctl restart clamd at scan > > To switch it back to "enforcing", you then do > > setenforce enforcing > > systemctl restart httpd > > systemctl restart clamd at scan > > Cheers, > > Jules. > > On 25/10/2018 14:31, Gray McCord via ZendTo wrote: > > I?ve seen that message as well. Check the file permissions > on the /opt/zendto directories. Seems like I needed to > make them writeable by the apache user, but I could be > mistaken. > > Gray McCord > > /Adapt, Mutate, Migrate, or Die/ > > -C. Darwin > > *From:*ZendTo > *On Behalf Of *Ken Etter > via ZendTo > *Sent:* Thursday, October 25, 2018 8:26 AM > *To:* ZendTo List > *Cc:* Ken Etter > *Subject:* Re: [ZendTo] Zend.to error during drop-off > > Going back through the mailing list archives, I see that I > am having exactly the same problem as Kevin O'Connor in > this thread: *MailScanner has detected a possible fraud > attempt from "emea01.safelinks.protection.outlook.com" > claiming to be* > http://jul.es/pipermail/zendto/2018-June/003208.html > > > Files are uploaded, but I get that error message and the > email is not sent. > > There is no stated resolution in that thread. Any > suggestions or do I have to rebuild a brand new Zend.To > server? > > Zend.To has been fairly solid for me...a bit of a pain to > find this upgrade to be so fragile. > > Ken > > >>> Ken Etter via ZendTo > 10/25/2018 8:38 AM >>> > > I am running this on Ubuntu 16.04.5 LTS if that matters. > > > Ken > > >>> Ken Etter via ZendTo > 10/25/2018 8:36 AM >>> > > Just upgraded my Zend.To installation from 4.x to 5.15-1. > Everything appeared to go ok. But when I click drop-off > files, I get an error that states: "Sorry, I failed to > drop-off your files! Note that you cannot drop-off > directories, only files." I'm not dropping off a > directory, just a single file. I tried a couple different > file types - same error each time. Any suggestions for > fixing this? Thanks! > > > > > *Ken Etter*, System Administrator > > Architectural Group > > 260.432.9337 | *MailScanner has detected a possible fraud > attempt from "emea01.safelinks.protection.outlook.com" > claiming to be* msktd.com > > > cid:part9.1CF91C30.CC17F0DE at Zend.To > > > _______________________________________________ > > ZendTo mailing list > > ZendTo at zend.to > > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 > > 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 > > Jules > > -- > > Julian Field MEng CEng CITP MBCS MIEEE MACM > > IMPORTANT: This email is intended for the use of the individual > > addressee(s) named above and may contain information that is > > confidential, privileged or unsuitable for overly sensitive persons > > with low self-esteem, no sense of humour or irrational religious > > beliefs. If you are not the intended recipient, any dissemination, > > distribution or copying of this email is not authorised (either > > explicitly or implicitly) and constitutes an irritating social faux > > pas. > > Unless the word absquatulation has been used in its correct context > > somewhere other than in this warning, it does not have any legal > > or no grammatical use and may be ignored. No animals were harmed > > in the transmission of this email, although the kelpie next door > > is living on borrowed time, let me tell you. Those of you with an > > overwhelming fear of the unknown will be gratified to learn that > > there is no hidden message revealed by reading this warning backwards, > > so just ignore that Alert Notice from Microsoft. > > However, by pouring a complete circle of salt around yourself and > > your computer you can ensure that no harm befalls you and your pets. > > If you have received this email in error, please add some nutmeg > > and egg whites, whisk and place in a warm oven for 40 minutes. > > www.Zend.To > > Twitter: @JulesFM > > > > Jules > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > 'It's very unlikely indeed he will ever recover consciousness, and > if he does he won't be the Julian you knew.' > ? - A hospital consultant I proved very wrong in 2007 :-) > 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 'They went with songs to the battle, they were young. Straight of limb, true of eye, steady and aglow. They were staunch to the end against odds uncounted, They fell with their faces to the foe. They shall grow not old, as we that are left grow old: Age shall not weary them, nor the years condemn. At the going down of the sun and in the morning, We will remember them. They mingle not with their laughing comrades again; They sit no more at familiar tables of home; They have no lot in our labour of the day-time; They sleep beyond England's foam.' - Ode of Remembrance, Laurence Binyon www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Thu Oct 25 17:45:02 2018 From: Jules at Zend.To (Jules Field) Date: Thu, 25 Oct 2018 17:45:02 +0100 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <0ebb65e4-8426-00ba-2670-26a0df7c8694@Zend.To> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1E592020000130012D942@mail.msktd.com> Message-ID: Please can you send us the entire output of both commands. Screenshot or copy-and-paste will do. Also, send us the entire output of "ls -al /var/zendto". Then I can compare what you've got with my Ubuntu 16.04 test machine, which I know works. Cheers, Jules. On 25/10/2018 16:47, Ken Etter wrote: > I'm running Ubuntu 16.04.5 > > clamdscan /var/zendto/* <-- this one failed with permission denied > clamdscan --fdpass /var/zendto/*? <-- this one displayed some > warnings, then got to /var/zendto/cache: OK and then seemed to hang. > > Ken > >>> Jules Field 10/25/2018 11:41 AM >>> > > Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. > > Then "pwconv" so the change takes effect. > Then try this > su - apache (or whatever user your Apache is running as) > > clamdscan /var/zendto/* > > clamdscan --fdpass /var/zendto/* > > exit > > What happened? Did the virus scans both complete successfully? > If not, and you're running CentOS/RedHat 7, try this and then give the > above another try: > groupmems --group virusgroup --add apache > > systemctl restart httpd > > I added that extra groupmems command to the Installer a day or two ago > when I discovered that RedHat/CentOS had changed their group > membership rules in an update. > Any improvement? > Cheers, > Jules. > P.S. Otherwise, if you can give me remote ssh access I can login > myself and take a look for you. I would be interested to see what it > is, if it's not any of the above. > On 25/10/2018 16:22, Ken Etter wrote: >> Yep, PHP 7.2 is installed. I've run through the installer multiple >> times now. No change, still get the error. >> Ken >> >>> Jules Field 10/25/2018 11:15 AM >>> >> > Do you have PHP 7.2 installed? >> >> My Installer can be run in stages, and those stages can be run >> independently. >> So you might want to download the Installer, unpack it and wander >> into it. In what will obviously be the right sub-dir for your OS, you >> will see the numbered scripts. >> # cd install.ZendTo/CentOS-RedHat/ >> >> # ls >> >> 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 >> >> 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 >> >> # >> >> If your web server is already working nicely, then you can probably >> skip stage 1 (though it won't do any harm). >> If you haven't installed PHP 7.2 along with things like the sodium >> extension, then run stage 2 which installs PHP. (Grab a backup copy >> of your ZendTo installation first, as it may have to remove the >> *whole* of PHP first which can also remove ZendTo and other PHP >> applications in the process, before it can install the correct version). >> Stages 3 and 5 shouldn't do any damage, but will add any new settings >> they need for PHP and so on. >> Stage 7 does the actual ZendTo installation itself, which it will do >> as an upgrade if it finds a zendto RPM already installed. Well worth >> running. >> Stage 8 is only relevant if you are using SELinux, and won't do >> anything if you're not. >> Since version 4, ZendTo no longer needs any form of custom-built PHP >> or anything like that. So there's no recompiling to be done. >> Then if you have a previous preferences.php and/or zendto.conf, you >> need to use >> /opt/zendto/bin/upgrade_preferences_php >> and >> /opt/zendto/bin/upgrade_zendto_conf >> to upgrade those files. >> Also, if you have done an RPM upgrade from ZendTo 4, you probably >> have a whole stack of *.rpmnew files in /opt/zendto/templates. You >> want to move each of those into place so they replace your old *.tpl >> files. >> As I said, it really is faster/easier/better to build v5 from >> scratch, its requirements are so different from v4. >> Hope that helps, >> Jules. >> On 25/10/2018 15:59, Ken Etter wrote: >>> None of that helps. I'm building a new system. This is a production >>> system. I never had problems in the past with upgrading so I went >>> ahead and did it. Bad move. Unless anyone has any other ideas, I >>> will just keep working on setting up the new system. I have to get >>> something running again for my users. >>> >>> Ken >>> >>> Jules Field via ZendTo 10/25/2018 10:53 AM >>> >>> > Yes, those directories do need to be writable by whatever user and group your >>> web server is running as. >>> >>> If you are using SELinux (most likely if you are using CentOS or >>> RedHat), then I would also advise >>> restorecon -FRv /opt/zendto /var/zendto >>> >>> to reset all the SELinux attributes to the values configured by my >>> Installer. >>> Also, if you think it might be an SELinux problem, you can switch it >>> into "permissive" mode by >>> setenforce permissive >>> >>> systemctl restart httpd >>> >>> systemctl restart clamd at scan >>> >>> To switch it back to "enforcing", you then do >>> setenforce enforcing >>> >>> systemctl restart httpd >>> >>> systemctl restart clamd at scan >>> >>> Cheers, >>> Jules. >>> On 25/10/2018 14:31, Gray McCord via ZendTo wrote: >>>> I?ve seen that message as well. Check the file permissions on the >>>> /opt/zendto directories. Seems like I needed to make them writeable >>>> by the apache user, but I could be mistaken. >>>> Gray McCord >>>> /Adapt, Mutate, Migrate, or Die/ >>>> -C. Darwin >>>> *From:* ZendTo *On Behalf Of *Ken Etter >>>> via ZendTo >>>> *Sent:* Thursday, October 25, 2018 8:26 AM >>>> *To:* ZendTo List >>>> *Cc:* Ken Etter >>>> *Subject:* Re: [ZendTo] Zend.to error during drop-off >>>> Going back through the mailing list archives, I see that I am >>>> having exactly the same problem as Kevin O'Connor in this thread: >>>> http://jul.es/pipermail/zendto/2018-June/003208.html >>>> >>>> Files are uploaded, but I get that error message and the email is >>>> not sent. >>>> There is no stated resolution in that thread. Any suggestions or do >>>> I have to rebuild a brand new Zend.To server? >>>> Zend.To has been fairly solid for me...a bit of a pain to find this >>>> upgrade to be so fragile. >>>> Ken >>>> >>> Ken Etter via ZendTo > >>>> 10/25/2018 8:38 AM >>> >>>> I am running this on Ubuntu 16.04.5 LTS if that matters. >>>> >>>> Ken >>>> >>> Ken Etter via ZendTo > >>>> 10/25/2018 8:36 AM >>> >>>> Just upgraded my Zend.To installation from 4.x to 5.15-1. >>>> Everything appeared to go ok. But when I click drop-off files, I >>>> get an error that states: "Sorry, I failed to drop-off your files! >>>> Note that you cannot drop-off directories, only files." I'm not >>>> dropping off a directory, just a single file. I tried a couple >>>> different file types - same error each time. Any suggestions for >>>> fixing this? Thanks! >>>> >>>> >>>> *Ken Etter*, System Administrator >>>> Architectural Group >>>> 260.432.9337 | msktd.com >>>> >>>> >>>> >>>> _______________________________________________ >>>> ZendTo mailing list >>>> ZendTo at zend.to >>>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 >>> >>> 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 >> >> Jules >> >> -- >> Julian Field MEng CEng CITP MBCS MIEEE MACM >> >> IMPORTANT: This email is intended for the use of the individual >> addressee(s) named above and may contain information that is >> confidential, privileged or unsuitable for overly sensitive persons >> with low self-esteem, no sense of humour or irrational religious >> beliefs. If you are not the intended recipient, any dissemination, >> distribution or copying of this email is not authorised (either >> explicitly or implicitly) and constitutes an irritating social faux >> pas. >> >> Unless the word absquatulation has been used in its correct context >> somewhere other than in this warning, it does not have any legal >> or no grammatical use and may be ignored. No animals were harmed >> in the transmission of this email, although the kelpie next door >> is living on borrowed time, let me tell you. Those of you with an >> overwhelming fear of the unknown will be gratified to learn that >> there is no hidden message revealed by reading this warning backwards, >> so just ignore that Alert Notice from Microsoft. >> >> However, by pouring a complete circle of salt around yourself and >> your computer you can ensure that no harm befalls you and your pets. >> If you have received this email in error, please add some nutmeg >> and egg whites, whisk and place in a warm oven for 40 minutes. >> >> www.Zend.To >> Twitter: @JulesFM > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'It's very unlikely indeed he will ever recover consciousness, and > if he does he won't be the Julian you knew.' > - A hospital consultant I proved very wrong in 2007 :-) > > www.Zend.To > Twitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'They went with songs to the battle, they were young. Straight of limb, true of eye, steady and aglow. They were staunch to the end against odds uncounted, They fell with their faces to the foe. They shall grow not old, as we that are left grow old: Age shall not weary them, nor the years condemn. At the going down of the sun and in the morning, We will remember them. They mingle not with their laughing comrades again; They sit no more at familiar tables of home; They have no lot in our labour of the day-time; They sleep beyond England's foam.' - Ode of Remembrance, Laurence Binyon www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: not available URL: From kle at msktd.com Thu Oct 25 17:57:37 2018 From: kle at msktd.com (Ken Etter) Date: Thu, 25 Oct 2018 12:57:37 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: <5BD1E4180200002500407BED@mail.msktd.com> References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <705D5031020000C3C84B1EE2@mail.msktd.com> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <43f7fe6f-fb01-fbc2-20e8-69aad2903060@Zend.To> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <0ebb65e4-8426-00ba-2670-26a0df7c8694@Zend.To> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> Message-ID: Jules, I just finished setting up a brand new VM and I get the same error message! This makes no sense! Any thoughts? * installed Ubuntu 16.04.3 as a basic server * configured networking * installed openssh-server * patched server to 16.04.5 * downloaded your installer and ran it used most defaults except I had to specify the smtp server and the address of the site the site address defaulted to https://server_name and I changed it to https://transfer.msktd.com * modified preferences.php and zendto.conf for my settings * reboot * login to site and attempt a drop off and I get the same error as my upgraded site What could possibly be wrong in what I did? Ken >>> Jules Field 10/25/2018 11:41 AM >>> > Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. Then "pwconv" so the change takes effect. Then try this su - apache (or whatever user your Apache is running as) clamdscan /var/zendto/* clamdscan --fdpass /var/zendto/* exit What happened? Did the virus scans both complete successfully? If not, and you're running CentOS/RedHat 7, try this and then give the above another try: groupmems --group virusgroup --add apache systemctl restart httpd I added that extra groupmems command to the Installer a day or two ago when I discovered that RedHat/CentOS had changed their group membership rules in an update. Any improvement? Cheers, Jules. P.S. Otherwise, if you can give me remote ssh access I can login myself and take a look for you. I would be interested to see what it is, if it's not any of the above. On 25/10/2018 16:22, Ken Etter wrote: Yep, PHP 7.2 is installed. I've run through the installer multiple times now. No change, still get the error. Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:15 AM >>> > Do you have PHP 7.2 installed? My Installer can be run in stages, and those stages can be run independently. So you might want to download the Installer, unpack it and wander into it. In what will obviously be the right sub-dir for your OS, you will see the numbered scripts. # cd install.ZendTo/CentOS-RedHat/ # ls 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 # If your web server is already working nicely, then you can probably skip stage 1 (though it won't do any harm). If you haven't installed PHP 7.2 along with things like the sodium extension, then run stage 2 which installs PHP. (Grab a backup copy of your ZendTo installation first, as it may have to remove the *whole* of PHP first which can also remove ZendTo and other PHP applications in the process, before it can install the correct version). Stages 3 and 5 shouldn't do any damage, but will add any new settings they need for PHP and so on. Stage 7 does the actual ZendTo installation itself, which it will do as an upgrade if it finds a zendto RPM already installed. Well worth running. Stage 8 is only relevant if you are using SELinux, and won't do anything if you're not. Since version 4, ZendTo no longer needs any form of custom-built PHP or anything like that. So there's no recompiling to be done. Then if you have a previous preferences.php and/or zendto.conf, you need to use /opt/zendto/bin/upgrade_preferences_php and /opt/zendto/bin/upgrade_zendto_conf to upgrade those files. Also, if you have done an RPM upgrade from ZendTo 4, you probably have a whole stack of *.rpmnew files in /opt/zendto/templates. You want to move each of those into place so they replace your old *.tpl files. As I said, it really is faster/easier/better to build v5 from scratch, its requirements are so different from v4. Hope that helps, Jules. On 25/10/2018 15:59, Ken Etter wrote: None of that helps. I'm building a new system. This is a production system. I never had problems in the past with upgrading so I went ahead and did it. Bad move. Unless anyone has any other ideas, I will just keep working on setting up the new system. I have to get something running again for my users. Ken >>> Jules Field via ZendTo ( mailto:zendto at zend.to) 10/25/2018 10:53 AM >>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise restorecon -FRv /opt/zendto /var/zendto to reset all the SELinux attributes to the values configured by my Installer. Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by setenforce permissive systemctl restart httpd systemctl restart clamd at scan To switch it back to "enforcing", you then do setenforce enforcing systemctl restart httpd systemctl restart clamd at scan Cheers, Jules. On 25/10/2018 14:31, Gray McCord via ZendTo wrote: I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo ( mailto:zendto-bounces at zend.to) On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List ( mailto:zendto at zend.to) Cc: Ken Etter ( mailto:KLE at msktd.com) Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: http://jul.es/pipermail/zendto/2018-June/003208.html ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fpipermail%2Fzendto%2F2018-June%2F003208.html&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=%2FMQVOSO5ZjLwkrQ991eChCvoSfFOLwm3yUcnFSzoRc0%3D&reserved=0) Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmsktd.com%2F&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=XsZydsv5daB1usPtdakyqf%2BjPxBLH9n8NbGcrjhC34Y%3D&reserved=0) _______________________________________________ZendTo mailing listZendTo at zend.tohttps://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0) Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'The past is supposed to be a place of reference, not a place ofresidence! There is a reason why your car has a big windshi eld anda small rearview mirror. You are supposed to keep your eyes on whereyou are going, and just occasionally check out where you have been.' - Willie Jolleywww.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACMIMPORTANT: This email is intended for the use of the individualaddressee(s) named above and may contain information that isconfidential, privileged or unsuitable for overly sensitive personswith low self-esteem, no sense of humour or irrational religiousbeliefs. If you are not the intended recipient, any dissemination,distribution or copying of this email is not authorised (eitherexplicitly or implicitly) and constitutes an irritating social fauxpas.Unless the word absquatulation has been used in its correct contextsomewhere other than in this warning, it does not have any legalor no grammatical use and may be ignored. No animals were harmedin the transmission of this email, although the kelpie next dooris living on borrowed time, let me tell you. Those of you with anoverwhelming fear of the unknown will be gratified to learn thatthere is no hidden message revealed by reading this warning backwards,so just ignore that Alert Notice from Microsoft.However, by pouring a complete circle of salt around yourself andyour computer you can ensure that no harm befalls you and your pets.If you have received this email in error, please add some nutmegand egg whites, whisk and place in a warm oven for 40 minutes.www.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'It's very unlikely indeed he will ever recover consciousness, and if he does he won't be the Julian you knew.' - A hospital consultant I proved very wrong in 2007 :-)www.Zend.ToTwitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From kle at msktd.com Thu Oct 25 19:01:06 2018 From: kle at msktd.com (Ken Etter) Date: Thu, 25 Oct 2018 14:01:06 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: <5BD1F601020000130012D950@mail.msktd.com> References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <705D5031020000C3C84B1EE2@mail.msktd.com> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <43f7fe6f-fb01-fbc2-20e8-69aad2903060@Zend.To> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <0ebb65e4-8426-00ba-2670-26a0df7c8694@Zend.To> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <5BD204E2020000130012D963@mail.msktd.com> Message-ID: I mentioned below that I am getting the same error on the new VM. I am, but I noticed that the file is not uploaded....it was uploaded on my upgraded VM. I've been through the logs multiple times now and the only problem I see is complaints about the certificate...which makes sense since I haven't done that yet. I reverted the upgraded VM back to the snapshot I had taken before starting this process. So it is back to version 4.28 and functioning and my users have something to use for the moment. I am completely out of ideas. Makes no sense that a completely new install would fail like this. If no one has any other thoughts, I may just have to find a replacement. Ken >>> Ken Etter 10/25/2018 12:57 PM >>> Jules, I just finished setting up a brand new VM and I get the same error message! This makes no sense! Any thoughts? * installed Ubuntu 16.04.3 as a basic server * configured networking * installed openssh-server * patched server to 16.04.5 * downloaded your installer and ran it used most defaults except I had to specify the smtp server and the address of the site the site address defaulted to https://server_name and I changed it to https://transfer.msktd.com * modified preferences.php and zendto.conf for my settings * reboot * login to site and attempt a drop off and I get the same error as my upgraded site What could possibly be wrong in what I did? Ken >>> Jules Field 10/25/2018 11:41 AM >>> > Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. Then "pwconv" so the change takes effect. Then try this su - apache (or whatever user your Apache is running as) clamdscan /var/zendto/* clamdscan --fdpass /var/zendto/* exit What happened? Did the virus scans both complete successfully? If not, and you're running CentOS/RedHat 7, try this and then give the above another try: groupmems --group virusgroup --add apache systemctl restart httpd I added that extra groupmems command to the Installer a day or two ago when I discovered that RedHat/CentOS had changed their group membership rules in an update. Any improvement? Cheers, Jules. P.S. Otherwise, if you can give me remote ssh access I can login myself and take a look for you. I would be interested to see what it is, if it's not any of the above. On 25/10/2018 16:22, Ken Etter wrote: Yep, PHP 7.2 is installed. I've run through the installer multiple times now. No change, still get the error. Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:15 AM >>> > Do you have PHP 7.2 installed? My Installer can be run in stages, and those stages can be run independently. So you might want to download the Installer, unpack it and wander into it. In what will obviously be the right sub-dir for your OS, you will see the numbered scripts. # cd install.ZendTo/CentOS-RedHat/ # ls 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 # If your web server is already working nicely, then you can probably skip stage 1 (though it won't do any harm). If you haven't installed PHP 7.2 along with things like the sodium extension, then run stage 2 which installs PHP. (Grab a backup copy of your ZendTo installation first, as it may have to remove the *whole* of PHP first which can also remove ZendTo and other PHP applications in the process, before it can install the correct version). Stages 3 and 5 shouldn't do any damage, but will add any new settings they need for PHP and so on. Stage 7 does the actual ZendTo installation itself, which it will do as an upgrade if it finds a zendto RPM already installed. Well worth running. Stage 8 is only relevant if you are using SELinux, and won't do anything if you're not. Since version 4, ZendTo no longer needs any form of custom-built PHP or anything like that. So there's no recompiling to be done. Then if you have a previous preferences.php and/or zendto.conf, you need to use /opt/zendto/bin/upgrade_preferences_php and /opt/zendto/bin/upgrade_zendto_conf to upgrade those files. Also, if you have done an RPM upgrade from ZendTo 4, you probably have a whole stack of *.rpmnew files in /opt/zendto/templates. You want to move each of those into place so they replace your old *.tpl files. As I said, it really is faster/easier/better to build v5 from scratch, its requirements are so different from v4. Hope that helps, Jules. On 25/10/2018 15:59, Ken Etter wrote: None of that helps. I'm building a new system. This is a production system. I never had problems in the past with upgrading so I went ahead and did it. Bad move. Unless anyone has any other ideas, I will just keep working on setting up the new system. I have to get something running again for my users. Ken >>> Jules Field via ZendTo ( mailto:zendto at zend.to) 10/25/2018 10:53 AM >>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise restorecon -FRv /opt/zendto /var/zendto to reset all the SELinux attributes to the values configured by my Installer. Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by setenforce permissive systemctl restart httpd systemctl restart clamd at scan To switch it back to "enforcing", you then do setenforce enforcing systemctl restart httpd systemctl restart clamd at scan Cheers, Jules. On 25/10/2018 14:31, Gray McCord via ZendTo wrote: I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo ( mailto:zendto-bounces at zend.to) On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List ( mailto:zendto at zend.to) Cc: Ken Etter ( mailto:KLE at msktd.com) Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: http://jul.es/pipermail/zendto/2018-June/003208.html ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fpipermail%2Fzendto%2F2018-June%2F003208.html&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=%2FMQVOSO5ZjLwkrQ991eChCvoSfFOLwm3yUcnFSzoRc0%3D&reserved=0) Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmsktd.com%2F&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=XsZydsv5daB1usPtdakyqf%2BjPxBLH9n8NbGcrjhC34Y%3D&reserved=0) _______________________________________________ZendTo mailing listZendTo at zend.tohttps://emea01.safelinks.protection.outlook.com /?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0) Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'The past is supposed to be a place of reference, not a place ofresidence! There is a reason why your car has a big windshield anda small rearview mirror. You are supposed to keep your eyes on whereyou are going, and just occasionally check out where you have been.' - Willie Jolleywww.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACMIMPORTANT: This email is intended for the use of the individualaddressee(s) named above and may contain information that isconfidential, privileged or unsuitable for overly sensitive personswith low self-esteem, no sense of humour or irrational religiousbeliefs. If you are not the intended recipient, any dissemination,distribution or copying of this email is not authorised (eitherexplicitly or implicitly) and constitutes an irritating social fauxpas.Unless the word absquatulation has been used in its correct contextsomewhere other than in this warning, it does not have any legalor no grammatical use and may be ignored. No animals were harmedin the transmission of this email, although the kelpie next dooris living on borrowed time, let me tell you. Those of you with anoverwhelming fear of the unknown will be gratified to learn thatthere is no hidden message revealed by reading this warning backwards,so just ignore that Alert Notice from Microsoft.However, by pouring a complete circle of salt around yourself andyour computer you can ensure that no harm befalls you and your pets.If you have received this email in error, please add some nutmegand egg whites, whisk and place in a warm oven for 40 minutes.www.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'It's very unlikely indeed he will ever recover consciousness, and if he does he won't be the Julian you knew.' - A hospital consultant I proved very wrong in 2007 :-)www.Zend.ToTwitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From kle at msktd.com Thu Oct 25 20:35:16 2018 From: kle at msktd.com (Ken Etter) Date: Thu, 25 Oct 2018 15:35:16 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: <5BD2171E0200002600407FC9@mail.msktd.com> References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <0ebb65e4-8426-00ba-2670-26a0df7c8694@Zend.To> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1E592020000130012D942@mail.msktd.com> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1E592020000130012D942@mail.msktd.com> <19E72A8D020000417314B811@mail.msktd.com> <1D917A620200008CC84B1EE2@mail.msktd.com> <5BD2171E0200002600407FC9@mail.msktd.com> <5BD21AF4020000130012D974@mail.msktd.com> Message-ID: Jules, I had to get my system working for users, so I can do this now on the upgraded system. But I ran it on the new VM system and no errors. But I still cannot upload. Ken www-data at vs8:~$ clamdscan /var/zendto/* /var/zendto/cache: OK /var/zendto/dropoffs: OK /var/zendto/incoming: OK /var/zendto/library: OK /var/zendto/rrd: OK /var/zendto/templates_c: OK /var/zendto/zendto.log: OK /var/zendto/zendto.sqlite: OK ----------- SCAN SUMMARY ----------- Infected files: 0 Time: 0.311 sec (0 m 0 s) www-data at vs8:~$ clamdscan --fdpass /var/zendto/* /var/zendto/cache: OK /var/zendto/dropoffs: OK /var/zendto/incoming: OK /var/zendto/library: OK /var/zendto/rrd: OK /var/zendto/templates_c: OK /var/zendto/zendto.log: OK /var/zendto/zendto.sqlite: OK ----------- SCAN SUMMARY ----------- Infected files: 0 Time: 0.032 sec (0 m 0 s) www-data at vs8:~$ ls -al /var/zendto total 64 drwxrwxr-x 8 root www-data 4096 Oct 25 08:36 . drwxr-xr-x 15 root root 4096 Oct 25 07:23 .. drwxr-xr-x 3 www-data www-data 4096 Oct 25 07:49 cache drwxr-xr-x 2 www-data www-data 4096 Oct 5 07:04 dropoffs drwxr-xr-x 2 www-data www-data 4096 Oct 5 07:04 incoming drwxr-xr-x 2 www-data www-data 4096 Oct 5 07:04 library drwxr-xr-x 2 www-data www-data 4096 Oct 25 07:23 rrd drwxr-xr-x 2 www-data www-data 4096 Oct 25 08:33 templates_c -rw-r--r-- 1 www-data www-data 84 Oct 25 07:49 zendto.log -rw-r--r-- 1 www-data www-data 23552 Oct 25 07:49 zendto.sqlite >>> Jules Field 10/25/2018 12:45 PM >>> > Please can you send us the entire output of both commands. Screenshot or copy-and-paste will do. Also, send us the entire output of "ls -al /var/zendto". Then I can compare what you've got with my Ubuntu 16.04 test machine, which I know works. Cheers, Jules. On 25/10/2018 16:47, Ken Etter wrote: I'm running Ubuntu 16.04.5 clamdscan /var/zendto/* <-- this one failed with permission denied clamdscan --fdpass /var/zendto/* <-- this one displayed some warnings, then got to /var/zendto/cache: OK and then seemed to hang. Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:41 AM >>> > Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. Then "pwconv" so the change takes effect. Then try this su - apache (or whatever user your Apache is running as) clamdscan /var/zendto/* clamdscan --fdpass /var/zendto/* exit What happened? Did the virus scans both complete successfully? If not, and you're running CentOS/RedHat 7, try this and then give the above another try: groupmems --group virusgroup --add apache systemctl restart httpd I added that extra groupmems command to the Installer a day or two ago when I discovered that RedHat/CentOS had changed their group membership rules in an update. Any improvement? Cheers, Jules. P.S. Otherwise, if you can give me remote ssh access I can login myself and take a look for you. I would be interested to see what it is, if it's not any of the above. On 25/10/2018 16:22, Ken Etter wrote: Yep, PHP 7.2 is installed. I've run through the installer multiple times now. No change, still get the error. Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:15 AM >>> > Do you have PHP 7.2 installed? My Installer can be run in stages, and those stages can be run independently. So you might want to download the Installer, unpack it and wander into it. In what will obviously be the right sub-dir for your OS, you will see the numbered scripts. # cd install.ZendTo/CentOS-RedHat/ # ls 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 # If your web server is already working nicely, then you can probably skip stage 1 (though it won't do any harm). If you haven't installed PHP 7.2 along with things like the sodium extension, then run stage 2 which installs PHP. (Grab a backup copy of your ZendTo in stallation first, as it may have to remove the *whole* of PHP first which can also remove ZendTo and other PHP applications in the process, before it can install the correct version). Stages 3 and 5 shouldn't do any damage, but will add any new settings they need for PHP and so on. Stage 7 does the actual ZendTo installation itself, which it will do as an upgrade if it finds a zendto RPM already installed. Well worth running. Stage 8 is only relevant if you are using SELinux, and won't do anything if you're not. Since version 4, ZendTo no longer needs any form of custom-built PHP or anything like that. So there's no recompiling to be done. Then if you have a previous preferences.php and/or zendto.conf, you need to use /opt/zendto/bin/upgrade_preferences_php and /opt/zendto/bin/upgrade_zendto_conf to upgrade those files. Also, if you have done an RPM upgrade from ZendTo 4, you probably have a whole stack of *.rpmnew files in /opt/zendto/templates. You want to move each of those into place so they replace your old *.tpl files. As I said, it really is faster/easier/better to build v5 from scratch, its requirements are so different from v4. Hope that helps, Jules. On 25/10/2018 15:59, Ken Etter wrote: None of that helps. I'm building a new system. This is a production system. I never had problems in the past with upgrading so I went ahead and did it. Bad move. Unless anyone has any other ideas, I will just keep working on setting up the new system. I have to get something running again for my users. Ken >>> Jules Field via ZendTo ( mailto:zendto at zend.to) 10/25/2018 10:53 AM >>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise restorecon -FRv /opt/zendto /var/zendto to reset all the SELinux attributes to the values configured by my Installer. Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by setenforce permissive systemctl restart httpd systemctl restart clamd at scan To switch it back to "enforcing", you then do setenforce enforcing systemctl restart httpd systemctl restart clamd at scan Cheers, Jules. On 25/10/2018 14:31, Gray McCord via ZendTo wrote: I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo ( mailto:zendto-bounces at zend.to) On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List ( mailto:zendto at zend.to) Cc: Ken Etter ( mailto:KLE at msktd.com) Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: http://jul.es/pipermail/zendto/2018-June/003208.html ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fpipermail%2Fzendto%2F2018-June%2F003208.html&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=%2FMQVOSO5ZjLwkrQ991eChCvoSfFOLwm3yUcnFSzoRc0%3D&reserved=0) Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmsktd.com%2F&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=XsZydsv5daB1usPtdakyqf%2BjPxBLH9n8NbGcrjhC34Y%3D&reserved=0) _______________________________________________ZendTo mailing listZendTo at zend.tohttps://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0) Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'The past is supposed to be a place of reference, not a place ofresidence! There is a reason why your car has a big windshield anda small rearview mirror. You are supposed to keep your eyes on whereyou are going, and just occasionally check out where you have been.' - Willie Jolleywww.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACMIMPORTANT: This email is intended for the use of the individualaddressee(s) named above and may contain information that isconfidential, privileged or unsuitable for overly sensitive personswith low self-esteem, no sense of humour or irrational religiousbeliefs. If you are not the intended recipient, any dissemination,distribution or copying of this email is not authorised (eitherexplicitly or implicitly) and constitutes an irritating social fauxpas.Unless the word absquatulation has been used in its correct contextsomewhere other than in this warning, it does not have any legalor no grammatical use and may be ignored. No animals were harmedin the transmission of this email, although the kelpie next dooris living on borrowed time, let me tell you. Those of you with anoverwhelming fear of the unknown will be gratified to learn thatthere is no hidden message revealed by reading this warning backwards,so just ignore that Alert Notice from Microsoft.However, by pouring a complete circle of salt around yourself andyour computer you can ensure that no harm befalls you and your pets.If you have received this email in error, please add some nutmegand egg whites, whisk and place in a warm oven for 40 minutes.www.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'It's very unlikely indeed he will ever recover consciousness, and if he does he won't be the Julian you knew.' - A hospital consultant I proved very wrong in 2007 :-)www.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'They went with songs to the battle, they were young. Straight of limb, true of eye, steady and aglow. They were staunch to the end against odds uncounted, They fell with their faces to the foe. They shall grow not old, as we that are left grow old: Age shall not weary them, nor the years condemn. At the going down of the sun and in the morning, We will remember them. They mingle not with their laughing comrades again; They sit no more at familiar tables of home; They have no lot in our labour of the day-time; They sleep beyond England's foam.' - Ode of Remembrance, Laurence Binyonwww.Zend.ToTwitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From kle at msktd.com Thu Oct 25 20:38:38 2018 From: kle at msktd.com (Ken Etter) Date: Thu, 25 Oct 2018 15:38:38 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <0ebb65e4-8426-00ba-2670-26a0df7c8694@Zend.To> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1E592020000130012D942@mail.msktd.com> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1E592020000130012D942@mail.msktd.com> <19E72A8D020000417314B811@mail.msktd.com> <1D917A620200008CC84B1EE2@mail.msktd.com> <5BD2171E0200002600407FC9@mail.msktd.com> <5BD21AF4020000130012D974@mail.msktd.com> <5BD21BBE020000130012D97A@mail.msktd.com> Message-ID: "can't do this now on the upgraded system" not "can". Is it a Monday? >>> Ken Etter via ZendTo 10/25/2018 3:35 PM >>> Jules, I had to get my system working for users, so I can do this now on the upgraded system. But I ran it on the new VM system and no errors. But I still cannot upload. Ken www-data at vs8:~$ clamdscan /var/zendto/* /var/zendto/cache: OK /var/zendto/dropoffs: OK /var/zendto/incoming: OK /var/zendto/library: OK /var/zendto/rrd: OK /var/zendto/templates_c: OK /var/zendto/zendto.log: OK /var/zendto/zendto.sqlite: OK ----------- SCAN SUMMARY ----------- Infected files: 0 Time: 0.311 sec (0 m 0 s) www-data at vs8:~$ clamdscan --fdpass /var/zendto/* /var/zendto/cache: OK /var/zendto/dropoffs: OK /var/zendto/incoming: OK /var/zendto/library: OK /var/zendto/rrd: OK /var/zendto/templates_c: OK /var/zendto/zendto.log: OK /var/zendto/zendto.sqlite: OK ----------- SCAN SUMMARY ----------- Infected files: 0 Time: 0.032 sec (0 m 0 s) www-data at vs8:~$ ls -al /var/zendto total 64 drwxrwxr-x 8 root www-data 4096 Oct 25 08:36 . drwxr-xr-x 15 root root 4096 Oct 25 07:23 .. drwxr-xr-x 3 www-data www-data 4096 Oct 25 07:49 cache drwxr-xr-x 2 www-data www-data 4096 Oct 5 07:04 dropoffs drwxr-xr-x 2 www-data www-data 4096 Oct 5 07:04 incoming drwxr-xr-x 2 www-data www-data 4096 Oct 5 07:04 library drwxr-xr-x 2 www-data www-data 4096 Oct 25 07:23 rrd drwxr-xr-x 2 www-data www-data 4096 Oct 25 08:33 templates_c -rw-r--r-- 1 www-data www-data 84 Oct 25 07:49 zendto.log -rw-r--r-- 1 www-data www-data 23552 Oct 25 07:49 zendto.sqlite >>> Jules Field 10/25/2018 12:45 PM >>> > Please can you send us the entire output of both commands. Screenshot or copy-and-paste will do. Also, send us the entire output of "ls -al /var/zendto". Then I can compare what you've got with my Ubuntu 16.04 test machine, which I know works. Cheers, Jules. On 25/10/2018 16:47, Ken Etter wrote: I'm running Ubuntu 16.04.5 clamdscan /var/zendto/* <-- this one failed with permission denied clamdscan --fdpass /var/zendto/* <-- this one displayed some warnings, then got to /var/zendto/cache: OK and then seemed to hang. Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:41 AM >>> > Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. Then "pwconv" so the change takes effect. Then try this su - apache (or whatever user your Apache is running as) clamdscan /var/zendto/* clamdscan --fdpass /var/zendto/* exit What happened? Did the virus scans both complete successfully? If not, and you're running CentOS/RedHat 7, try this and then give the above another try: groupmems --group virusgroup --add apache systemctl restart httpd I added that extra groupmems command to the Installer a day or two ago when I discovered that RedHat/CentOS had changed their group membership rules in an update. Any improvement? Cheers, Jules. P.S. Otherwise, if you can give me remote ssh access I can login myself and take a look for you. I would be interested to see what it is, if it's not any of the above. On 25/10/2018 16:22, Ken Etter wrote: Yep, PHP 7.2 is installed. I've run through the installer multiple times now. No change, still get the error. Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:15 AM >>> > Do you have PHP 7.2 installed? My Installer can be run in stages, and those stages can be run independently. So you might want to download the Installer, unpack it and wander into it. In what will obviously be the right sub-dir for your OS, you will see the numbered scripts. # cd install.ZendTo/CentOS-RedHat/ # ls 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 # If your web server is already working nicely, then you can probably skip stage 1 (though it won't do any harm). If you haven't i nstalled PHP 7.2 along with things like the sodium extension, then run stage 2 which installs PHP. (Grab a backup copy of your ZendTo installation first, as it may have to remove the *whole* of PHP first which can also remove ZendTo and other PHP applications in the process, before it can install the correct version). Stages 3 and 5 shouldn't do any damage, but will add any new settings they need for PHP and so on. Stage 7 does the actual ZendTo installation itself, which it will do as an upgrade if it finds a zendto RPM already installed. Well worth running. Stage 8 is only relevant if you are using SELinux, and won't do anything if you're not. Since version 4, ZendTo no longer needs any form of custom-built PHP or anything like that. So there's no recompiling to be done. Then if you have a previous preferences.php and/or zendto.conf, you need to use /opt/zendto/bin/upgrade_preferences_php and /opt/zendto/bin/upgrade_zendto_conf to upgrade those files. Also, if you have done an RPM upgrade from ZendTo 4, you probably have a whole stack of *.rpmnew files in /opt/zendto/templates. You want to move each of those into place so they replace your old *.tpl files. As I said, it really is faster/easier/better to build v5 from scratch, its requirements are so different from v4. Hope that helps, Jules. On 25/10/2018 15:59, Ken Etter wrote: None of that helps. I'm building a new system. This is a production system. I never had problems in the past with upgrading so I went ahead and did it. Bad move. Unless anyone has any other ideas, I will just keep working on setting up the new system. I have to get something running again for my users. Ken >>> Jules Field via ZendTo ( mailto:zendto at zend.to) 10/25/2018 10:53 AM >>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise restorecon -FRv /opt/zendto /var/zendto to reset all the SELinux attributes to the values configured by my Installer. Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by setenforce permissive systemctl restart httpd systemctl restart clamd at scan To switch it back to "enforcing", you then do setenforce enforcing systemctl restart httpd systemctl restart clamd at scan Cheers, Jules. On 25/10/2018 14:31, Gray McCord via ZendTo wrote: I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo ( mailto:zendto-bounces at zend.to) On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List ( mailto:zendto at zend.to) Cc: Ken Etter ( mailto:KLE at msktd.com) Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: http://jul.es/pipermail/zendto/2018-June/003208.html ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fpipermail%2Fzendto%2F2018-June%2F003208.html&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=%2FMQVOSO5ZjLwkrQ991eChCvoSfFOLwm3yUcnFSzoRc0%3D&reserved=0) Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To inst allation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmsktd.com%2F&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=XsZydsv5daB1usPtdakyqf%2BjPxBLH9n8NbGcrjhC34Y%3D&reserved=0) _______________________________________________ZendTo mailing listZendTo at zend.tohttps://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0) Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'The past is supposed to be a place of reference, not a place ofresidence! There is a reason why your car has a big windshield anda small rearview mirror. You are supposed to keep your eyes on whereyou are going, and just occasionally check out where you have been.' - Willie Jolleywww.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACMIMPORTANT: This email is intended for the use of the individualaddressee(s) named above and may contain information that isconfidential, privileged or unsuitable for overly sensitive personswith low self-esteem, no sense of humour or irrational religiousbeliefs. If you are not the intended recipient, any dissemination,distribution or copying of this email is not authorised (eitherexplicitly or implicitly) and constitutes an irritating social fauxpas.Unless the word absquatulation has been used in its correct contextsomewhere other than in this warning, it does not have any legalor no grammatical use and may be ignored. No animals were harmedin the transmission of this email, although the kelpie next dooris living on borrowed time, let me tell you. Those of you with anoverwhelming fear of the unknown will be gratified to learn thatthere is no hidden message revealed by reading this warning backwards,so just ignore that Alert Notice from Microsoft.However, by pouring a complete circle of salt around yourself andyour computer you can ensure that no harm befalls you and your pets.If you have received this email in error, please add some nutmegand egg whites, whisk and place in a warm oven for 40 minutes.www.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'It's very unlikely indeed he will ever recover consciousness, and if he does he won't be the Julian you knew.' - A hospital consultant I proved very wrong in 2007 :-)www.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'They went with songs to the battle, they were young. Straight of limb, true of eye, steady and aglow. They were staunch to the end against odds uncounted, They fell with their faces to the foe. They shall grow not old, as we that are left grow old: Age shall not weary them, nor the years condemn. At the going down of the sun and in the morning, We will remember them. They mingle not with their laughing comrades again; They sit no more at familiar tables of home; They have no lot in our labour of the day-time; They sleep beyond England's foam.' - Ode of Remembrance, Laurence Binyonwww.Zend.ToTwitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From azshane at gmail.com Thu Oct 25 23:54:34 2018 From: azshane at gmail.com (Shane) Date: Thu, 25 Oct 2018 15:54:34 -0700 Subject: [ZendTo] lock down recipient In-Reply-To: References: Message-ID: Jules Thank you. That worked great. On Thu, Oct 25, 2018 at 4:07 AM Jules Field via ZendTo wrote: > Shane, > > On 24/10/2018 20:51, Shane via ZendTo wrote: > > Hello > > I've just finished installing zend.to > > in my centos 7. is it possible > to lock down the users who login to send files to one particular > recipient, not be able to add any other email address? I browsed through > preferences.php and couldn't find any reference to it unless I missed > something. > > Not currently, no. > You could hard-wire into the template > /opt/zendto/templates/new_dropoff.tpl like this: > * Right near the top, put your fixed recipient info into the variables " > presetToName" and "presetToEmail". > * Search for 'id="addRecipients"'. Add to that tag an attribute ' > style="display:none"'. > That would stop it appearing, which may be enough for your needs. > > > Also is it possible to lock down to allow only Excel files to be uploaded? > > No. There's pretty much no way of *reliably* detecting that a file is an > Excel file. > And don't suggest *.xls or *.xlsx. Then people just rename their > p**n/w*r*z before sending it. > > Sorry! > Jules. > > > thanks i > shane > > _______________________________________________ > ZendTo mailing listZendTo at zend.tohttps://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Cfd6cebc05dc946b2713108d639ea34bd%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=i%2FQ4BIYymCnsMKYR%2B71Hvn%2FMYIcvFlcQ4T5sFU1YYuA%3D&reserved=0 > > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'In Flanders fields the poppies blow > Between the crosses, row on row, > That mark our place: and in the sky > The larks still bravely singing fly > Scarce heard amid the guns below. > > We are the dead: Short days ago, > We lived, felt dawn, saw sunset glow, > Loved and were loved: and now we lie > In Flanders fields! > > Take up our quarrel with the foe > To you, from failing hands, we throw > The torch: be yours to hold it high > If ye break faith with us who die, > We shall not sleep, though poppies grow > In Flanders fields.' Lieutenant Colonel John McCrae > > Composed at the battlefront on May 3, 1915 > during the second battle of Ypres, Belgium > www.Zend.To > Twitter: @JulesFM > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Fri Oct 26 09:20:41 2018 From: Jules at Zend.To (Jules Field) Date: Fri, 26 Oct 2018 09:20:41 +0100 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <0ebb65e4-8426-00ba-2670-26a0df7c8694@Zend.To> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> Message-ID: Ken, This is really odd. I did thoroughly test the Installer on every supported version of every flavour of Linux that I say it works on. I've got dozens of old VMs to prove it. :-/ I'm downloading 16.04.3 (amd64) right now, and will walk through the same steps as you listed below. I'll let you know the results as soon as I've built it. Cheers, Jules. On 25/10/2018 17:57, Ken Etter wrote: > Jules, > I just finished setting up a brand new VM and I get the same error > message!? This makes no sense!? Any thoughts? > * installed Ubuntu 16.04.3 as a basic server > * configured networking > * installed openssh-server > * patched server to 16.04.5 > * downloaded your installer and ran it > ????????used most defaults except I had to specify the smtp server and > the address of the site > ????????the site address defaulted to https://server_name and I > changed it to https://transfer.msktd.com > * modified preferences.php and zendto.conf for my settings > * reboot > * login to site and attempt a drop off and I get the same error as my > upgraded site > > What could possibly be wrong in what I did? > > Ken > >>> Jules Field 10/25/2018 11:41 AM >>> > > Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. > > Then "pwconv" so the change takes effect. > Then try this > su - apache (or whatever user your Apache is running as) > > clamdscan /var/zendto/* > > clamdscan --fdpass /var/zendto/* > > exit > > What happened? Did the virus scans both complete successfully? > If not, and you're running CentOS/RedHat 7, try this and then give the > above another try: > groupmems --group virusgroup --add apache > > systemctl restart httpd > > I added that extra groupmems command to the Installer a day or two ago > when I discovered that RedHat/CentOS had changed their group > membership rules in an update. > Any improvement? > Cheers, > Jules. > P.S. Otherwise, if you can give me remote ssh access I can login > myself and take a look for you. I would be interested to see what it > is, if it's not any of the above. > On 25/10/2018 16:22, Ken Etter wrote: >> Yep, PHP 7.2 is installed. I've run through the installer multiple >> times now. No change, still get the error. >> Ken >> >>> Jules Field 10/25/2018 11:15 AM >>> >> > Do you have PHP 7.2 installed? >> >> My Installer can be run in stages, and those stages can be run >> independently. >> So you might want to download the Installer, unpack it and wander >> into it. In what will obviously be the right sub-dir for your OS, you >> will see the numbered scripts. >> # cd install.ZendTo/CentOS-RedHat/ >> >> # ls >> >> 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 >> >> 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 >> >> # >> >> If your web server is already working nicely, then you can probably >> skip stage 1 (though it won't do any harm). >> If you haven't installed PHP 7.2 along with things like the sodium >> extension, then run stage 2 which installs PHP. (Grab a backup copy >> of your ZendTo installation first, as it may have to remove the >> *whole* of PHP first which can also remove ZendTo and other PHP >> applications in the process, before it can install the correct version). >> Stages 3 and 5 shouldn't do any damage, but will add any new settings >> they need for PHP and so on. >> Stage 7 does the actual ZendTo installation itself, which it will do >> as an upgrade if it finds a zendto RPM already installed. Well worth >> running. >> Stage 8 is only relevant if you are using SELinux, and won't do >> anything if you're not. >> Since version 4, ZendTo no longer needs any form of custom-built PHP >> or anything like that. So there's no recompiling to be done. >> Then if you have a previous preferences.php and/or zendto.conf, you >> need to use >> /opt/zendto/bin/upgrade_preferences_php >> and >> /opt/zendto/bin/upgrade_zendto_conf >> to upgrade those files. >> Also, if you have done an RPM upgrade from ZendTo 4, you probably >> have a whole stack of *.rpmnew files in /opt/zendto/templates. You >> want to move each of those into place so they replace your old *.tpl >> files. >> As I said, it really is faster/easier/better to build v5 from >> scratch, its requirements are so different from v4. >> Hope that helps, >> Jules. >> On 25/10/2018 15:59, Ken Etter wrote: >>> None of that helps. I'm building a new system. This is a production >>> system. I never had problems in the past with upgrading so I went >>> ahead and did it. Bad move. Unless anyone has any other ideas, I >>> will just keep working on setting up the new system. I have to get >>> something running again for my users. >>> >>> Ken >>> >>> Jules Field via ZendTo 10/25/2018 10:53 AM >>> >>> > Yes, those directories do need to be writable by whatever user and group your >>> web server is running as. >>> >>> If you are using SELinux (most likely if you are using CentOS or >>> RedHat), then I would also advise >>> restorecon -FRv /opt/zendto /var/zendto >>> >>> to reset all the SELinux attributes to the values configured by my >>> Installer. >>> Also, if you think it might be an SELinux problem, you can switch it >>> into "permissive" mode by >>> setenforce permissive >>> >>> systemctl restart httpd >>> >>> systemctl restart clamd at scan >>> >>> To switch it back to "enforcing", you then do >>> setenforce enforcing >>> >>> systemctl restart httpd >>> >>> systemctl restart clamd at scan >>> >>> Cheers, >>> Jules. >>> On 25/10/2018 14:31, Gray McCord via ZendTo wrote: >>>> I?ve seen that message as well. Check the file permissions on the >>>> /opt/zendto directories. Seems like I needed to make them writeable >>>> by the apache user, but I could be mistaken. >>>> Gray McCord >>>> /Adapt, Mutate, Migrate, or Die/ >>>> -C. Darwin >>>> *From:* ZendTo *On Behalf Of *Ken Etter >>>> via ZendTo >>>> *Sent:* Thursday, October 25, 2018 8:26 AM >>>> *To:* ZendTo List >>>> *Cc:* Ken Etter >>>> *Subject:* Re: [ZendTo] Zend.to error during drop-off >>>> Going back through the mailing list archives, I see that I am >>>> having exactly the same problem as Kevin O'Connor in this thread: >>>> http://jul.es/pipermail/zendto/2018-June/003208.html >>>> >>>> Files are uploaded, but I get that error message and the email is >>>> not sent. >>>> There is no stated resolution in that thread. Any suggestions or do >>>> I have to rebuild a brand new Zend.To server? >>>> Zend.To has been fairly solid for me...a bit of a pain to find this >>>> upgrade to be so fragile. >>>> Ken >>>> >>> Ken Etter via ZendTo > >>>> 10/25/2018 8:38 AM >>> >>>> I am running this on Ubuntu 16.04.5 LTS if that matters. >>>> >>>> Ken >>>> >>> Ken Etter via ZendTo > >>>> 10/25/2018 8:36 AM >>> >>>> Just upgraded my Zend.To installation from 4.x to 5.15-1. >>>> Everything appeared to go ok. But when I click drop-off files, I >>>> get an error that states: "Sorry, I failed to drop-off your files! >>>> Note that you cannot drop-off directories, only files." I'm not >>>> dropping off a directory, just a single file. I tried a couple >>>> different file types - same error each time. Any suggestions for >>>> fixing this? Thanks! >>>> >>>> >>>> *Ken Etter*, System Administrator >>>> Architectural Group >>>> 260.432.9337 | msktd.com >>>> >>>> >>>> >>>> _______________________________________________ >>>> ZendTo mailing list >>>> ZendTo at zend.to >>>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 >>> >>> 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 >> >> Jules >> >> -- >> Julian Field MEng CEng CITP MBCS MIEEE MACM >> >> IMPORTANT: This email is intended for the use of the individual >> addressee(s) named above and may contain information that is >> confidential, privileged or unsuitable for overly sensitive persons >> with low self-esteem, no sense of humour or irrational religious >> beliefs. If you are not the intended recipient, any dissemination, >> distribution or copying of this email is not authorised (either >> explicitly or implicitly) and constitutes an irritating social faux >> pas. >> >> Unless the word absquatulation has been used in its correct context >> somewhere other than in this warning, it does not have any legal >> or no grammatical use and may be ignored. No animals were harmed >> in the transmission of this email, although the kelpie next door >> is living on borrowed time, let me tell you. Those of you with an >> overwhelming fear of the unknown will be gratified to learn that >> there is no hidden message revealed by reading this warning backwards, >> so just ignore that Alert Notice from Microsoft. >> >> However, by pouring a complete circle of salt around yourself and >> your computer you can ensure that no harm befalls you and your pets. >> If you have received this email in error, please add some nutmeg >> and egg whites, whisk and place in a warm oven for 40 minutes. >> >> www.Zend.To >> Twitter: @JulesFM > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'It's very unlikely indeed he will ever recover consciousness, and > if he does he won't be the Julian you knew.' > - A hospital consultant I proved very wrong in 2007 :-) > > www.Zend.To > Twitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'Is the Holocaust an aberration, or a reflection of who we really are?' - Holocaust Museum, Berlin www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: not available URL: From Jules at Zend.To Fri Oct 26 10:39:16 2018 From: Jules at Zend.To (Jules Field) Date: Fri, 26 Oct 2018 10:39:16 +0100 Subject: [ZendTo] lock down recipient In-Reply-To: References: Message-ID: <32772b45-f415-cfcb-482a-32cd415440b1@Zend.To> Shane, Be careful when you upgrade in future. When you upgrade, apt or yum/rpm will notice that you have modified that template. It will create a new one for you (yum/rpm will call it new_dropoff.tpl.rpmnew). You will need to make your change to the new one, then move it into place to overwrite the old one. I frequently have to change that particular template file as it's so complicated. The apt/yum/rpm command will tell you that it's got a new version of that particular file. But it tends to output rather a lot anyway, so it's very easy to miss the line that tells you about this file. Cheers, Jules. On 25/10/2018 23:54, Shane via ZendTo wrote: > Jules > > Thank you. That worked great. > > On Thu, Oct 25, 2018 at 4:07 AM Jules Field via ZendTo > wrote: > > Shane, > > On 24/10/2018 20:51, Shane via ZendTo wrote: >> Hello >> >> I've just finished installing zend.to >> >> in my centos 7. is it possible >> to lock down the users who login to send files to one particular >> recipient, not be able to add any other email address?? I browsed >> through >> preferences.php and couldn't find any reference to it unless I >> missed something. > Not currently, no. > You could hard-wire into the template > /opt/zendto/templates/new_dropoff.tpl like this: > * Right near the top, put your fixed recipient info into the > variables "presetToName" and "presetToEmail". > * Search for 'id="addRecipients"'. Add to that tag an > attribute 'style="display:none"'. > That would stop it appearing, which may be enough for your needs. > >> >> Also is it possible to lock down to allow only Excel files to be >> uploaded? > No. There's pretty much no way of *reliably* detecting that a file > is an Excel file. > And don't suggest *.xls or *.xlsx. Then people just rename their > p**n/w*r*z before sending it. > > Sorry! > Jules. > >> >> thanks i >> shane >> >> _______________________________________________ >> ZendTo mailing list >> ZendTo at zend.to >> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Cfd6cebc05dc946b2713108d639ea34bd%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=i%2FQ4BIYymCnsMKYR%2B71Hvn%2FMYIcvFlcQ4T5sFU1YYuA%3D&reserved=0 > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'In Flanders fields the poppies blow > Between the crosses, row on row, > That mark our place: and in the sky > The larks still bravely singing fly > Scarce heard amid the guns below. > > We are the dead: Short days ago, > We lived, felt dawn, saw sunset glow, > Loved and were loved: and now we lie > In Flanders fields! > > Take up our quarrel with the foe > To you, from failing hands, we throw > The torch: be yours to hold it high > If ye break faith with us who die, > We shall not sleep, though poppies grow > In Flanders fields.' Lieutenant Colonel John McCrae > > Composed at the battlefront on May 3, 1915 > during the second battle of Ypres, Belgium > > 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 'They went with songs to the battle, they were young. Straight of limb, true of eye, steady and aglow. They were staunch to the end against odds uncounted, They fell with their faces to the foe. They shall grow not old, as we that are left grow old: Age shall not weary them, nor the years condemn. At the going down of the sun and in the morning, We will remember them. They mingle not with their laughing comrades again; They sit no more at familiar tables of home; They have no lot in our labour of the day-time; They sleep beyond England's foam.' - Ode of Remembrance, Laurence Binyon www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From douglagm at gmail.com Fri Oct 26 11:03:49 2018 From: douglagm at gmail.com (Gregg Douglas) Date: Fri, 26 Oct 2018 12:03:49 +0200 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1D8DE0200007600407AB5@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <0ebb65e4-8426-00ba-2670-26a0df7c8694@Zend.To> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> Message-ID: Hi, I had a similar issue with the exact same error message. In our environment they rolled out Azure AIP and there was a bug in the software which caused the ZendTo error. Can I maybe suggest, trying to upload a file from a "virgin" Windows Desktop, maybe even use FireFox on the ZendTo server to upload a file? Regards Gregg On Fri, Oct 26, 2018 at 11:17 AM Jules Field via ZendTo wrote: > Ken, > > This is really odd. I did thoroughly test the Installer on every supported > version of every flavour of Linux that I say it works on. I've got dozens > of old VMs to prove it. :-/ > > I'm downloading 16.04.3 (amd64) right now, and will walk through the same > steps as you listed below. > > I'll let you know the results as soon as I've built it. > > Cheers, > Jules. > > On 25/10/2018 17:57, Ken Etter wrote: > > Jules, > I just finished setting up a brand new VM and I get the same error > message! This makes no sense! Any thoughts? > * installed Ubuntu 16.04.3 as a basic server > * configured networking > * installed openssh-server > * patched server to 16.04.5 > * downloaded your installer and ran it > used most defaults except I had to specify the smtp server and the > address of the site > the site address defaulted to https://server_name and I changed > it to https://transfer.msktd.com > * modified preferences.php and zendto.conf for my settings > * reboot > * login to site and attempt a drop off and I get the same error as my > upgraded site > > What could possibly be wrong in what I did? > > Ken > >>> Jules Field 10/25/2018 11:41 AM >>> > > Edit your /etc/passwd file to set the shell for your Apache user to > /bin/bash. > > Then "pwconv" so the change takes effect. > Then try this > su - apache (or whatever user your Apache is running as) > > clamdscan /var/zendto/* > > clamdscan --fdpass /var/zendto/* > > exit > > What happened? Did the virus scans both complete successfully? > If not, and you're running CentOS/RedHat 7, try this and then give the > above another try: > groupmems --group virusgroup --add apache > > systemctl restart httpd > > I added that extra groupmems command to the Installer a day or two ago > when I discovered that RedHat/CentOS had changed their group membership > rules in an update. > Any improvement? > Cheers, > Jules. > P.S. Otherwise, if you can give me remote ssh access I can login myself > and take a look for you. I would be interested to see what it is, if it's > not any of the above. > On 25/10/2018 16:22, Ken Etter wrote: > > Yep, PHP 7.2 is installed. I've run through the installer multiple times > now. No change, still get the error. > Ken > >>> Jules Field 10/25/2018 11:15 AM >>> > > Do you have PHP 7.2 installed? > > My Installer can be run in stages, and those stages can be run > independently. > So you might want to download the Installer, unpack it and wander into it. > In what will obviously be the right sub-dir for your OS, you will see the > numbered scripts. > # cd install.ZendTo/CentOS-RedHat/ > > # ls > > 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 > > 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 > > # > > If your web server is already working nicely, then you can probably skip > stage 1 (though it won't do any harm). > If you haven't installed PHP 7.2 along with things like the sodium > extension, then run stage 2 which installs PHP. (Grab a backup copy of your > ZendTo installation first, as it may have to remove the *whole* of PHP > first which can also remove ZendTo and other PHP applications in the > process, before it can install the correct version). > Stages 3 and 5 shouldn't do any damage, but will add any new settings they > need for PHP and so on. > Stage 7 does the actual ZendTo installation itself, which it will do as an > upgrade if it finds a zendto RPM already installed. Well worth running. > Stage 8 is only relevant if you are using SELinux, and won't do anything > if you're not. > Since version 4, ZendTo no longer needs any form of custom-built PHP or > anything like that. So there's no recompiling to be done. > Then if you have a previous preferences.php and/or zendto.conf, you need > to use > /opt/zendto/bin/upgrade_preferences_php > and > /opt/zendto/bin/upgrade_zendto_conf > to upgrade those files. > Also, if you have done an RPM upgrade from ZendTo 4, you probably have a > whole stack of *.rpmnew files in /opt/zendto/templates. You want to move > each of those into place so they replace your old *.tpl files. > As I said, it really is faster/easier/better to build v5 from scratch, its > requirements are so different from v4. > Hope that helps, > Jules. > On 25/10/2018 15:59, Ken Etter wrote: > > None of that helps. I'm building a new system. This is a production > system. I never had problems in the past with upgrading so I went ahead and > did it. Bad move. Unless anyone has any other ideas, I will just keep > working on setting up the new system. I have to get something running again > for my users. > > Ken > >>> Jules Field via ZendTo 10/25/2018 > 10:53 AM >>> > > Yes, those directories do need to be writable by whatever user and group > your web server is running as. > > If you are using SELinux (most likely if you are using CentOS or RedHat), > then I would also advise > restorecon -FRv /opt/zendto /var/zendto > > to reset all the SELinux attributes to the values configured by my > Installer. > Also, if you think it might be an SELinux problem, you can switch it into > "permissive" mode by > setenforce permissive > > systemctl restart httpd > > systemctl restart clamd at scan > > To switch it back to "enforcing", you then do > setenforce enforcing > > systemctl restart httpd > > systemctl restart clamd at scan > > Cheers, > Jules. > On 25/10/2018 14:31, Gray McCord via ZendTo wrote: > > I?ve seen that message as well. Check the file permissions on the > /opt/zendto directories. Seems like I needed to make them writeable by the > apache user, but I could be mistaken. > Gray McCord > *Adapt, Mutate, Migrate, or Die* > -C. Darwin > *From:* ZendTo *On > Behalf Of *Ken Etter via ZendTo > *Sent:* Thursday, October 25, 2018 8:26 AM > *To:* ZendTo List > *Cc:* Ken Etter > *Subject:* Re: [ZendTo] Zend.to error during drop-off > Going back through the mailing list archives, I see that I am having > exactly the same problem as Kevin O'Connor in this thread: > http://jul.es/pipermail/zendto/2018-June/003208.html > > Files are uploaded, but I get that error message and the email is not sent. > There is no stated resolution in that thread. Any suggestions or do I have > to rebuild a brand new Zend.To server? > Zend.To has been fairly solid for me...a bit of a pain to find this > upgrade to be so fragile. > Ken > >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> > I am running this on Ubuntu 16.04.5 LTS if that matters. > > Ken > >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> > Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything > appeared to go ok. But when I click drop-off files, I get an error that > states: "Sorry, I failed to drop-off your files! Note that you cannot > drop-off directories, only files." I'm not dropping off a directory, just a > single file. I tried a couple different file types - same error each time. > Any suggestions for fixing this? Thanks! > > > *Ken Etter*, System Administrator > Architectural Group > 260.432.9337 | msktd.com > > > > > _______________________________________________ > ZendTo mailing listZendTo at zend.tohttps://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 > > > 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 > > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > IMPORTANT: This email is intended for the use of the individual > addressee(s) named above and may contain information that is > confidential, privileged or unsuitable for overly sensitive persons > with low self-esteem, no sense of humour or irrational religious > beliefs. If you are not the intended recipient, any dissemination, > distribution or copying of this email is not authorised (either > explicitly or implicitly) and constitutes an irritating social faux > pas. > > Unless the word absquatulation has been used in its correct context > somewhere other than in this warning, it does not have any legal > or no grammatical use and may be ignored. No animals were harmed > in the transmission of this email, although the kelpie next door > is living on borrowed time, let me tell you. Those of you with an > overwhelming fear of the unknown will be gratified to learn that > there is no hidden message revealed by reading this warning backwards, > so just ignore that Alert Notice from Microsoft. > > However, by pouring a complete circle of salt around yourself and > your computer you can ensure that no harm befalls you and your pets. > If you have received this email in error, please add some nutmeg > and egg whites, whisk and place in a warm oven for 40 minutes. > www.Zend.To > Twitter: @JulesFM > > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'It's very unlikely indeed he will ever recover consciousness, and > if he does he won't be the Julian you knew.' > - A hospital consultant I proved very wrong in 2007 :-) > www.Zend.To > Twitter: @JulesFM > > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'Is the Holocaust an aberration, or a reflection of who we really are?' > - Holocaust Museum, Berlin > www.Zend.To > Twitter: @JulesFM > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: not available URL: From Jules at Zend.To Fri Oct 26 12:26:16 2018 From: Jules at Zend.To (Jules Field) Date: Fri, 26 Oct 2018 12:26:16 +0100 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <0ebb65e4-8426-00ba-2670-26a0df7c8694@Zend.To> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> Message-ID: <7b4ae0e0-c1df-866e-ded2-b1462a3b36ca@Zend.To> Ken, I have just built a ZendTo VM from scratch using the exact same version of Ubuntu you did, and the current production release of ZendTo (as installed by my Installer). It worked absolutely fine for me. Attached is the PDF log of what I did, so you can read through it. I didn't have to change the server name, as I had already set the FQDN to the same name in the Ubuntu networking setup (as documented in the PDF). And I didn't touch *anything* after running the Installer, including zendto.conf, preferences.php and the Apache config. I would be starting to suspect your preferences.php settings. What happens if you check the serverRoot is right, and make sure that Apache config matches. Otherwise just use the preferences.php as the Installer leaves it. On a VM with only 1GB, the current production release probably won't be able to encrypt a drop-off. I've reduced the memory requirements for that in the latest betas, but in the mean time you will probably need at least 2GB RAM to be able to use encryption. Cheers, Jules. On 26/10/2018 09:20, Jules Field wrote: > Ken, > > This is really odd. I did thoroughly test the Installer on every > supported version of every flavour of Linux that I say it works on. > I've got dozens of old VMs to prove it. :-/ > > I'm downloading 16.04.3 (amd64) right now, and will walk through the > same steps as you listed below. > > I'll let you know the results as soon as I've built it. > > Cheers, > Jules. > > On 25/10/2018 17:57, Ken Etter wrote: >> Jules, >> I just finished setting up a brand new VM and I get the same error >> message!? This makes no sense!? Any thoughts? >> * installed Ubuntu 16.04.3 as a basic server >> * configured networking >> * installed openssh-server >> * patched server to 16.04.5 >> * downloaded your installer and ran it >> ????????used most defaults except I had to specify the smtp server >> and the address of the site >> ????????the site address defaulted to https://server_name and I >> changed it to https://transfer.msktd.com >> * modified preferences.php and zendto.conf for my settings >> * reboot >> * login to site and attempt a drop off and I get the same error as my >> upgraded site >> >> What could possibly be wrong in what I did? >> >> Ken >> >>> Jules Field 10/25/2018 11:41 AM >>> >> > Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. >> >> Then "pwconv" so the change takes effect. >> Then try this >> su - apache (or whatever user your Apache is running as) >> >> clamdscan /var/zendto/* >> >> clamdscan --fdpass /var/zendto/* >> >> exit >> >> What happened? Did the virus scans both complete successfully? >> If not, and you're running CentOS/RedHat 7, try this and then give >> the above another try: >> groupmems --group virusgroup --add apache >> >> systemctl restart httpd >> >> I added that extra groupmems command to the Installer a day or two >> ago when I discovered that RedHat/CentOS had changed their group >> membership rules in an update. >> Any improvement? >> Cheers, >> Jules. >> P.S. Otherwise, if you can give me remote ssh access I can login >> myself and take a look for you. I would be interested to see what it >> is, if it's not any of the above. >> On 25/10/2018 16:22, Ken Etter wrote: >>> Yep, PHP 7.2 is installed. I've run through the installer multiple >>> times now. No change, still get the error. >>> Ken >>> >>> Jules Field 10/25/2018 11:15 AM >>> >>> > Do you have PHP 7.2 installed? >>> >>> My Installer can be run in stages, and those stages can be run >>> independently. >>> So you might want to download the Installer, unpack it and wander >>> into it. In what will obviously be the right sub-dir for your OS, >>> you will see the numbered scripts. >>> # cd install.ZendTo/CentOS-RedHat/ >>> >>> # ls >>> >>> 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 >>> >>> 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 >>> >>> # >>> >>> If your web server is already working nicely, then you can probably >>> skip stage 1 (though it won't do any harm). >>> If you haven't installed PHP 7.2 along with things like the sodium >>> extension, then run stage 2 which installs PHP. (Grab a backup copy >>> of your ZendTo installation first, as it may have to remove the >>> *whole* of PHP first which can also remove ZendTo and other PHP >>> applications in the process, before it can install the correct version). >>> Stages 3 and 5 shouldn't do any damage, but will add any new >>> settings they need for PHP and so on. >>> Stage 7 does the actual ZendTo installation itself, which it will do >>> as an upgrade if it finds a zendto RPM already installed. Well worth >>> running. >>> Stage 8 is only relevant if you are using SELinux, and won't do >>> anything if you're not. >>> Since version 4, ZendTo no longer needs any form of custom-built PHP >>> or anything like that. So there's no recompiling to be done. >>> Then if you have a previous preferences.php and/or zendto.conf, you >>> need to use >>> /opt/zendto/bin/upgrade_preferences_php >>> and >>> /opt/zendto/bin/upgrade_zendto_conf >>> to upgrade those files. >>> Also, if you have done an RPM upgrade from ZendTo 4, you probably >>> have a whole stack of *.rpmnew files in /opt/zendto/templates. You >>> want to move each of those into place so they replace your old *.tpl >>> files. >>> As I said, it really is faster/easier/better to build v5 from >>> scratch, its requirements are so different from v4. >>> Hope that helps, >>> Jules. >>> On 25/10/2018 15:59, Ken Etter wrote: >>>> None of that helps. I'm building a new system. This is a production >>>> system. I never had problems in the past with upgrading so I went >>>> ahead and did it. Bad move. Unless anyone has any other ideas, I >>>> will just keep working on setting up the new system. I have to get >>>> something running again for my users. >>>> >>>> Ken >>>> >>> Jules Field via ZendTo 10/25/2018 10:53 AM >>> >>>> > Yes, those directories do need to be writable by whatever user and >>>> group your web server is running as. >>>> >>>> If you are using SELinux (most likely if you are using CentOS or >>>> RedHat), then I would also advise >>>> restorecon -FRv /opt/zendto /var/zendto >>>> >>>> to reset all the SELinux attributes to the values configured by my >>>> Installer. >>>> Also, if you think it might be an SELinux problem, you can switch >>>> it into "permissive" mode by >>>> setenforce permissive >>>> >>>> systemctl restart httpd >>>> >>>> systemctl restart clamd at scan >>>> >>>> To switch it back to "enforcing", you then do >>>> setenforce enforcing >>>> >>>> systemctl restart httpd >>>> >>>> systemctl restart clamd at scan >>>> >>>> Cheers, >>>> Jules. >>>> On 25/10/2018 14:31, Gray McCord via ZendTo wrote: >>>>> I?ve seen that message as well. Check the file permissions on the >>>>> /opt/zendto directories. Seems like I needed to make them >>>>> writeable by the apache user, but I could be mistaken. >>>>> Gray McCord >>>>> /Adapt, Mutate, Migrate, or Die/ >>>>> -C. Darwin >>>>> *From:* ZendTo *On Behalf Of *Ken Etter >>>>> via ZendTo >>>>> *Sent:* Thursday, October 25, 2018 8:26 AM >>>>> *To:* ZendTo List >>>>> *Cc:* Ken Etter >>>>> *Subject:* Re: [ZendTo] Zend.to error during drop-off >>>>> Going back through the mailing list archives, I see that I am >>>>> having exactly the same problem as Kevin O'Connor in this thread: >>>>> http://jul.es/pipermail/zendto/2018-June/003208.html >>>>> >>>>> Files are uploaded, but I get that error message and the email is >>>>> not sent. >>>>> There is no stated resolution in that thread. Any suggestions or >>>>> do I have to rebuild a brand new Zend.To server? >>>>> Zend.To has been fairly solid for me...a bit of a pain to find >>>>> this upgrade to be so fragile. >>>>> Ken >>>>> >>> Ken Etter via ZendTo > >>>>> 10/25/2018 8:38 AM >>> >>>>> I am running this on Ubuntu 16.04.5 LTS if that matters. >>>>> >>>>> Ken >>>>> >>> Ken Etter via ZendTo > >>>>> 10/25/2018 8:36 AM >>> >>>>> Just upgraded my Zend.To installation from 4.x to 5.15-1. >>>>> Everything appeared to go ok. But when I click drop-off files, I >>>>> get an error that states: "Sorry, I failed to drop-off your files! >>>>> Note that you cannot drop-off directories, only files." I'm not >>>>> dropping off a directory, just a single file. I tried a couple >>>>> different file types - same error each time. Any suggestions for >>>>> fixing this? Thanks! >>>>> >>>>> >>>>> *Ken Etter*, System Administrator >>>>> Architectural Group >>>>> 260.432.9337 | msktd.com >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> ZendTo mailing list >>>>> ZendTo at zend.to >>>>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 >>>> >>>> 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 >>> >>> Jules >>> >>> -- >>> Julian Field MEng CEng CITP MBCS MIEEE MACM >>> >>> IMPORTANT: This email is intended for the use of the individual >>> addressee(s) named above and may contain information that is >>> confidential, privileged or unsuitable for overly sensitive persons >>> with low self-esteem, no sense of humour or irrational religious >>> beliefs. If you are not the intended recipient, any dissemination, >>> distribution or copying of this email is not authorised (either >>> explicitly or implicitly) and constitutes an irritating social faux >>> pas. >>> >>> Unless the word absquatulation has been used in its correct context >>> somewhere other than in this warning, it does not have any legal >>> or no grammatical use and may be ignored. No animals were harmed >>> in the transmission of this email, although the kelpie next door >>> is living on borrowed time, let me tell you. Those of you with an >>> overwhelming fear of the unknown will be gratified to learn that >>> there is no hidden message revealed by reading this warning backwards, >>> so just ignore that Alert Notice from Microsoft. >>> >>> However, by pouring a complete circle of salt around yourself and >>> your computer you can ensure that no harm befalls you and your pets. >>> If you have received this email in error, please add some nutmeg >>> and egg whites, whisk and place in a warm oven for 40 minutes. >>> >>> www.Zend.To >>> Twitter: @JulesFM >> >> Jules >> >> -- >> Julian Field MEng CEng CITP MBCS MIEEE MACM >> >> 'It's very unlikely indeed he will ever recover consciousness, and >> if he does he won't be the Julian you knew.' >> - A hospital consultant I proved very wrong in 2007 :-) >> >> www.Zend.To >> Twitter: @JulesFM > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'Is the Holocaust an aberration, or a reflection of who we really are?' > - Holocaust Museum, Berlin > > www.Zend.To > Twitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'Named must your fear be before banish it you can.' - Yoda www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: KenEtter.pdf Type: application/pdf Size: 44014 bytes Desc: not available URL: From Jules at Zend.To Fri Oct 26 15:29:19 2018 From: Jules at Zend.To (Jules Field) Date: Fri, 26 Oct 2018 15:29:19 +0100 Subject: [ZendTo] =?utf-8?q?Calling_all_translators_=28for_5=2E16=29_?= =?utf-8?q?=E2=80=94_just_1_phrase?= Message-ID: <7890c015-0255-5790-7dea-e9ce5a9c1bf8@Zend.To> To my wonderful translators out there: Please can you translate this phrase for me. It is shown as a warning near the top of the dialog box where the sender enters the passphrase if they have asked for the drop-off to be encrypted. There is a break in the middle as this text sets the width of that dialog box. If you don't split it up, it gets way too long and so the dialog box becomes far too wide and looks wrong. The phrase is: "This passphrase will not be sent to the recipients.
You need to do this yourself." Here is a screenshot of where it appears: Many thanks all! Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'It's in Apple's DNA that technology alone is not enough. It's technology married with liberal arts, married with the humanities, that yields us the result that makes our hearts sing.' - Steve Jobs www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: abflabpcpeihndch.png Type: image/png Size: 27877 bytes Desc: not available URL: From azshane at gmail.com Sun Oct 28 19:47:57 2018 From: azshane at gmail.com (Shane) Date: Sun, 28 Oct 2018 12:47:57 -0700 Subject: [ZendTo] lock down recipient In-Reply-To: References: <32772b45-f415-cfcb-482a-32cd415440b1@Zend.To> Message-ID: Thanks for heads up on this. I will make a note of this for future upgrade. On Fri, Oct 26, 2018 at 2:39 AM Jules Field via ZendTo wrote: > Shane, > > Be careful when you upgrade in future. > > When you upgrade, apt or yum/rpm will notice that you have modified that > template. > It will create a new one for you (yum/rpm will call it > new_dropoff.tpl.rpmnew). > You will need to make your change to the new one, then move it into place > to overwrite the old one. > > I frequently have to change that particular template file as it's so > complicated. > > The apt/yum/rpm command will tell you that it's got a new version of that > particular file. But it tends to output rather a lot anyway, so it's very > easy to miss the line that tells you about this file. > > Cheers, > Jules. > > On 25/10/2018 23:54, Shane via ZendTo wrote: > > Jules > > Thank you. That worked great. > > On Thu, Oct 25, 2018 at 4:07 AM Jules Field via ZendTo > wrote: > >> Shane, >> >> On 24/10/2018 20:51, Shane via ZendTo wrote: >> >> Hello >> >> I've just finished installing zend.to >> >> in my centos 7. is it possible >> to lock down the users who login to send files to one particular >> recipient, not be able to add any other email address? I browsed through >> preferences.php and couldn't find any reference to it unless I missed >> something. >> >> Not currently, no. >> You could hard-wire into the template >> /opt/zendto/templates/new_dropoff.tpl like this: >> * Right near the top, put your fixed recipient info into the variables " >> presetToName" and "presetToEmail". >> * Search for 'id="addRecipients"'. Add to that tag an attribute ' >> style="display:none"'. >> That would stop it appearing, which may be enough for your needs. >> >> >> Also is it possible to lock down to allow only Excel files to be uploaded? >> >> No. There's pretty much no way of *reliably* detecting that a file is an >> Excel file. >> And don't suggest *.xls or *.xlsx. Then people just rename their >> p**n/w*r*z before sending it. >> >> Sorry! >> Jules. >> >> >> thanks i >> shane >> >> _______________________________________________ >> ZendTo mailing listZendTo at zend.tohttps://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Cfd6cebc05dc946b2713108d639ea34bd%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=i%2FQ4BIYymCnsMKYR%2B71Hvn%2FMYIcvFlcQ4T5sFU1YYuA%3D&reserved=0 >> >> >> Jules >> >> -- >> Julian Field MEng CEng CITP MBCS MIEEE MACM >> >> 'In Flanders fields the poppies blow >> Between the crosses, row on row, >> That mark our place: and in the sky >> The larks still bravely singing fly >> Scarce heard amid the guns below. >> >> We are the dead: Short days ago, >> We lived, felt dawn, saw sunset glow, >> Loved and were loved: and now we lie >> In Flanders fields! >> >> Take up our quarrel with the foe >> To you, from failing hands, we throw >> The torch: be yours to hold it high >> If ye break faith with us who die, >> We shall not sleep, though poppies grow >> In Flanders fields.' Lieutenant Colonel John McCrae >> >> Composed at the battlefront on May 3, 1915 >> during the second battle of Ypres, Belgium >> www.Zend.To >> Twitter: @JulesFM >> >> _______________________________________________ >> ZendTo mailing list >> ZendTo at zend.to >> http://jul.es/mailman/listinfo/zendto >> > > _______________________________________________ > ZendTo mailing listZendTo at zend.tohttp://jul.es/mailman/listinfo/zendto > > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'They went with songs to the battle, they were young. > Straight of limb, true of eye, steady and aglow. > They were staunch to the end against odds uncounted, > They fell with their faces to the foe. > > They shall grow not old, as we that are left grow old: > Age shall not weary them, nor the years condemn. > At the going down of the sun and in the morning, > We will remember them. > > They mingle not with their laughing comrades again; > They sit no more at familiar tables of home; > They have no lot in our labour of the day-time; > They sleep beyond England's foam.' > - Ode of Remembrance, Laurence Binyon > www.Zend.To > Twitter: @JulesFM > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkeller at psi.de Mon Oct 29 07:43:44 2018 From: mkeller at psi.de (Michael Keller) Date: Mon, 29 Oct 2018 08:43:44 +0100 Subject: [ZendTo] =?utf-8?q?Calling_all_translators_=28for_5=2E16=29_?= =?utf-8?q?=E2=80=94_just_1_phrase?= In-Reply-To: References: <7890c015-0255-5790-7dea-e9ce5a9c1bf8@Zend.To> <1004486597.152199.1540799025615.JavaMail.tbone@infra-abg-mcr1.psi.de> Message-ID: Hi Jules, here the german translation. "Dieses Kennwort wird nicht an die Empf?nger gesendet.
Das m?ssen sie selbst tun." Best regards Michael Am 26.10.18 um 16:29 schrieb Jules Field via ZendTo: > To my wonderful translators out there: > > Please can you translate this phrase for me. It is shown as a warning near the top of the dialog box where the sender enters the passphrase if they have asked for the drop-off to be encrypted. > > There is a break in the middle as this text sets the width of that dialog box. If you don't split it up, it gets way too long and so the dialog box becomes far too wide and looks wrong. > > The phrase is: > > "This passphrase will not be sent to the recipients.
You need to do this yourself." > > Here is a screenshot of where it appears: > > > Many thanks all! > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'It's in Apple's DNA that technology alone is not enough. It's > technology married with liberal arts, married with the humanities, > that yields us the result that makes our hearts sing.' - Steve Jobs > > 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: mkeller at psi.de-certificate-1.pem Type: application/octet-stream Size: 2325 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3795 bytes Desc: not available URL: From kle at msktd.com Mon Oct 29 14:06:07 2018 From: kle at msktd.com (Ken Etter) Date: Mon, 29 Oct 2018 10:06:07 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: <5BD2F9E402000022004084CF@mail.msktd.com> References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1DA40020000130012D92F@mail.msktd.com> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <0ebb65e4-8426-00ba-2670-26a0df7c8694@Zend.To> <5BD1DDFE0200009B00407B87@mail.msktd.com> <5BD1DFA0020000130012D935@mail.msktd.com> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <7b4ae0e0-c1df-866e-ded2-b1462a3b36ca@Zend.To> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <19BE5BFC0200006B7314B811@mail.msktd.com> <5BD2F9E402000022004084CF@mail.msktd.com> <5BD713CF020000130012DBDA@mail.msktd.com> Message-ID: Jules, Something doesn't seem clear here. You mention changing the FQDN of the server. Why should that even be necessary? I run multiple web servers on the same server and the site addresses do not have anything at all to do with the server name or the server FQDN. For ZendTo to work properly does the site address have to match the server FQDN? Ken >>> Jules Field 10/26/2018 7:26 AM >>> > Ken, I have just built a ZendTo VM from scratch using the exact same version of Ubuntu you did, and the current production release of ZendTo (as installed by my Installer). It worked absolutely fine for me. Attached is the PDF log of what I did, so you can read through it. I didn't have to change the server name, as I had already set the FQDN to the same name in the Ubuntu networking setup (as documented in the PDF). And I didn't touch *anything* after running the Installer, including zendto.conf, preferences.php and the Apache config. I would be starting to suspect your preferences.php settings. What happens if you check the serverRoot is right, and make sure that Apache config matches. Otherwise just use the preferences.php as the Installer leaves it. On a VM with only 1GB, the current production release probably won't be able to encrypt a drop-off. I've reduced the memory requirements for that in the latest betas, but in the mean time you will probably need at least 2GB RAM to be able to use encryption. Cheers, Jules. On 26/10/2018 09:20, Jules Field wrote: Ken, This is really odd. I did thoroughly test the Installer on every supported version of every flavour of Linux that I say it works on. I've got dozens of old VMs to prove it. :-/ I'm downloading 16.04.3 (amd64) right now, and will walk through the same steps as you listed below. I'll let you know the results as soon as I've built it. Cheers, Jules. On 25/10/2018 17:57, Ken Etter wrote: Jules, I just finished setting up a brand new VM and I get the same error message! This makes no sense! Any thoughts? * installed Ubuntu 16.04.3 as a basic server * configured networking * installed openssh-server * patched server to 16.04.5 * downloaded your installer and ran it used most defaults except I had to specify the smtp server and the address of the site the site address defaulted to https://server_name and I changed it to https://transfer.msktd.com * modified preferences.php and zendto.conf for my settings * reboot * login to site and attempt a drop off and I get the same error as my upgraded site What could possibly be wrong in what I did? Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:41 AM >>> > Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. Then "pwconv" so the change takes effect. Then try this su - apache (or whatever user your Apache is running as) clamdscan /var/zendto/* clamdscan --fdpass /var/zendto/* exit What happened? Did the virus scans both complete successfully? If not, and you're running CentOS/RedHat 7, try this and then give the above another try: groupmems --group virusgroup --add apache systemctl restart httpd I added that extra groupmems command to the Installer a day or two ago when I discovered that RedHat/CentOS had changed their group membership rules in an update. Any improvement? Cheers, Jules. P.S. Otherwise, if you can give me remote ssh access I can login myself and take a look for you. I would be interested to see what it is, if it's not any of the above. On 25/10/2018 16:22, Ken Etter wrote: Yep, PHP 7.2 is installed. I've run through the installer multiple times now. No change, still get the error. Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:15 AM >>> > Do you have PHP 7.2 installed? My Installer can be run in stages, and those stages can be run independently. So you might want to download the Installer, unpack it and wander into it. In what will obviously be the right sub -dir for your OS, you will see the numbered scripts. # cd install.ZendTo/CentOS-RedHat/ # ls 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 # If your web server is already working nicely, then you can probably skip stage 1 (though it won't do any harm). If you haven't installed PHP 7.2 along with things like the sodium extension, then run stage 2 which installs PHP. (Grab a backup copy of your ZendTo installation first, as it may have to remove the *whole* of PHP first which can also remove ZendTo and other PHP applications in the process, before it can install the correct version). Stages 3 and 5 shouldn't do any damage, but will add any new settings they need for PHP and so on. Stage 7 does the actual ZendTo installation itself, which it will do as an upgrade if it finds a zendto RPM already installed. Well worth running. Stage 8 is only relevant if you are using SELinux, and won't do anything if you're not. Since version 4, ZendTo no longer needs any form of custom-built PHP or anything like that. So there's no recompiling to be done. Then if you have a previous preferences.php and/or zendto.conf, you need to use /opt/zendto/bin/upgrade_preferences_php and /opt/zendto/bin/upgrade_zendto_conf to upgrade those files. Also, if you have done an RPM upgrade from ZendTo 4, you probably have a whole stack of *.rpmnew files in /opt/zendto/templates. You want to move each of those into place so they replace your old *.tpl files. As I said, it really is faster/easier/better to build v5 from scratch, its requirements are so different from v4. Hope that helps, Jules. On 25/10/2018 15:59, Ken Etter wrote: None of that helps. I'm building a new system. This is a production system. I never had problems in the past with upgrading so I went ahead and did it. Bad move. Unless anyone has any other ideas, I will just keep working on setting up the new system. I have to get something running again for my users. Ken >>> Jules Field via ZendTo ( mailto:zendto at zend.to) 10/25/2018 10:53 AM >>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise restorecon -FRv /opt/zendto /var/zendto to reset all the SELinux attributes to the values configured by my Installer. Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by setenforce permissive systemctl restart httpd systemctl restart clamd at scan To switch it back to "enforcing", you then do setenforce enforcing systemctl restart httpd systemctl restart clamd at scan Cheers, Jules. On 25/10/2018 14:31, Gray McCord via ZendTo wrote: I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo ( mailto:zendto-bounces at zend.to) On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List ( mailto:zendto at zend.to) Cc: Ken Etter ( mailto:KLE at msktd.com) Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: http://jul.es/pipermail/zendto/2018-June/003208.html ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fpipermail%2Fzendto%2F2018-June%2F003208.html&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=%2FMQVOSO5ZjLwkrQ991eChCvoSfFOLwm3yUcnFSzoRc0%3D&reserved=0) Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmsktd.com%2F&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=XsZydsv5daB1usPtdakyqf%2BjPxBLH9n8NbGcrjhC34Y%3D&reserved=0) _______________________________________________ZendTo mailing listZendTo at zend.tohttps://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0) Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'The past is supposed to be a place of reference, not a place ofresidence! There is a reason why your car has a big windshield anda small rearview mirror. You are supposed to keep your eyes on whereyou are going, and just occasionally check out where you have been.' - Willie Jolleywww.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACMIMPORTANT: This email is intended for the use of the individualaddressee(s) named above and may contain information that isconfidential, privileged or unsuitable for overly sensitive personswith low self-esteem, no sense of humour or irrational religiousbeliefs. If you are not the intended recipient, any dissemination,distribution or copying of this email is not authorised (eitherexplicitly or implicitly) and constitutes an irritating social fauxpas.Unless the word absquatulation has been used in its correct contextsomewhere other than in this warning, it does not have any legalor no grammatical use and may be ignored. No animals were harmedin the transmission of this email, although the kelpie next dooris living on borrowed time, let me tell you. Those of you with anoverwhelming fear of the unknown will be gratified to learn thatthere is no hidden message revealed by reading this warning backwards,so just ignore that Alert Notice from Microsoft.However, by pouring a complete circle of salt around yourself andyour computer you can ensure that no harm befalls you and your pets.If you have received this email in error, please add some nutmegand egg whites, whisk and place in a warm oven for 40 minutes.www.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'It's very unlikely indeed he will ever recover consciousness, and if he does he won't be the Julian you knew.' - A hospital consultant I proved very wrong in 2007 :-)www.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'Is the Holocaust an aberration, or a reflection of who we really are?' - Holocaust Museum, Berlinwww.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'Named must your fear be before banish it you can.' - Yodawww.Zend.ToTwitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From Jules at Zend.To Mon Oct 29 14:16:46 2018 From: Jules at Zend.To (Jules Field) Date: Mon, 29 Oct 2018 14:16:46 +0000 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <7b4ae0e0-c1df-866e-ded2-b1462a3b36ca@Zend.To> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <19BE5BFC0200006B7314B811@mail.msktd.com> <5BD2F9E402000022004084CF@mail.msktd.com> <5BD713CF020000130012DBDA@mail.msktd.com> Message-ID: <12b1fe6e-2537-28ee-64d1-5c0ce75c378a@Zend.To> Ken, I only changed the FQDN to set the domain name. As Ubuntu set itself up, I didn't appear to have a domain name set, so "hostname --fqdn" was just giving "kenetter" as it had no domain name. So I set the domain name as per those instructions in order to get a fully-qualified name out of "hostname --fqdn" before starting to install ZendTo. If the ZendTo Installer cannot deduce a likely DNS domain name, it tends to make some wrong decisions when setting up the preferences.php and internaldomains.conf files. For a pain-free installation, I tend to set that first, so that at least it has *a* domain name, even if it's not the same one as the website is going to have. Having the output of "hostname --fqdn" contain no dots at all is not a good sign of a "well setup" server. :) That actual hostname and such like is irrelevant to ZendTo. What's important is that the serverRoot in preferences.php matches up with what Apache thinks it's serving it as. You can put ZendTo on a server that has lots of other sites on it as well, that's no problem at all. Do you want to send me (off list) your Apache config for ZendTo, in addition to the preferences.php, zendto.conf and internaldomains.conf files? It's either something odd in there, or else your Ubuntu 16.04.3 system isn't anything like as "vanilla" as you think it is. Out of interest, why start with 16.04.3? That's not the latest 16.04 media available from Canonical, I had to go and hunt for it to reproduce your steps. Cheers, Jules. On 29/10/2018 14:06, Ken Etter wrote: > Jules, > Something doesn't seem clear here.? You mention changing the FQDN of > the server.? Why should that even be necessary?? I run multiple web > servers on the same server and the site addresses do not have anything > at all to do with the server name or the server FQDN.? For ZendTo to > work properly does the site address have to match the server FQDN? > > Ken > >>> Jules Field 10/26/2018 7:26 AM >>> > > Ken, > > I have just built a ZendTo VM from scratch using the exact same > version of Ubuntu you did, and the current production release of > ZendTo (as installed by my Installer). > It worked absolutely fine for me. > Attached is the PDF log of what I did, so you can read through it. > I didn't have to change the server name, as I had already set the FQDN > to the same name in the Ubuntu networking setup (as documented in the > PDF). > And I didn't touch *anything* after running the Installer, including > zendto.conf, preferences.php and the Apache config. > I would be starting to suspect your preferences.php settings. What > happens if you check the serverRoot is right, and make sure that > Apache config matches. Otherwise just use the preferences.php as the > Installer leaves it. > On a VM with only 1GB, the current production release probably won't > be able to encrypt a drop-off. I've reduced the memory requirements > for that in the latest betas, but in the mean time you will probably > need at least 2GB RAM to be able to use encryption. > Cheers, > Jules. > On 26/10/2018 09:20, Jules Field wrote: >> Ken, >> >> This is really odd. I did thoroughly test the Installer on every >> supported version of every flavour of Linux that I say it works on. >> I've got dozens of old VMs to prove it. :-/ >> I'm downloading 16.04.3 (amd64) right now, and will walk through the >> same steps as you listed below. >> I'll let you know the results as soon as I've built it. >> Cheers, >> Jules. >> On 25/10/2018 17:57, Ken Etter wrote: >>> Jules, >>> I just finished setting up a brand new VM and I get the same error >>> message! This makes no sense! Any thoughts? >>> * installed Ubuntu 16.04.3 as a basic server >>> * configured networking >>> * installed openssh-server >>> * patched server to 16.04.5 >>> * downloaded your installer and ran it >>> used most defaults except I had to specify the smtp server and the >>> address of the site >>> the site address defaulted to https://server_name and I changed it >>> to https://transfer.msktd.com >>> * modified preferences.php and zendto.conf for my settings >>> * reboot >>> * login to site and attempt a drop off and I get the same error as >>> my upgraded site >>> >>> What could possibly be wrong in what I did? >>> >>> Ken >>> >>> Jules Field 10/25/2018 11:41 AM >>> >>> > Edit your /etc/passwd file to set the shell for your Apache user to >>> /bin/bash. >>> >>> Then "pwconv" so the change takes effect. >>> Then try this >>> su - apache (or whatever user your Apache is running as) >>> >>> clamdscan /var/zendto/* >>> >>> clamdscan --fdpass /var/zendto/* >>> >>> exit >>> >>> What happened? Did the virus scans both complete successfully? >>> If not, and you're running CentOS/RedHat 7, try this and then give >>> the above another try: >>> groupmems --group virusgroup --add apache >>> >>> systemctl restart httpd >>> >>> I added that extra groupmems command to the Installer a day or two >>> ago when I discovered that RedHat/CentOS had changed their group >>> membership rules in an update. >>> Any improvement? >>> Cheers, >>> Jules. >>> P.S. Otherwise, if you can give me remote ssh access I can login >>> myself and take a look for you. I would be interested to see what it >>> is, if it's not any of the above. >>> On 25/10/2018 16:22, Ken Etter wrote: >>>> Yep, PHP 7.2 is installed. I've run through the installer multiple >>>> times now. No change, still get the error. >>>> Ken >>>> >>> Jules Field 10/25/2018 11:15 AM >>> >>>> > Do you have PHP 7.2 installed? >>>> >>>> My Installer can be run in stages, and those stages can be run >>>> independently. >>>> So you might want to download the Installer, unpack it and wander >>>> into it. In what will obviously be the right sub-dir for your OS, >>>> you will see the numbered scripts. >>>> # cd install.ZendTo/CentOS-RedHat/ >>>> >>>> # ls >>>> >>>> 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 >>>> >>>> 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 >>>> >>>> # >>>> >>>> If your web server is already working nicely, then you can probably >>>> skip stage 1 (though it won't do any harm). >>>> If you haven't installed PHP 7.2 along with things like the sodium >>>> extension, then run stage 2 which installs PHP. (Grab a backup copy >>>> of your ZendTo installation first, as it may have to remove the >>>> *whole* of PHP first which can also remove ZendTo and other PHP >>>> applications in the process, before it can install the correct >>>> version). >>>> Stages 3 and 5 shouldn't do any damage, but will add any new >>>> settings they need for PHP and so on. >>>> Stage 7 does the actual ZendTo installation itself, which it will >>>> do as an upgrade if it finds a zendto RPM already installed. Well >>>> worth running. >>>> Stage 8 is only relevant if you are using SELinux, and won't do >>>> anything if you're not. >>>> Since version 4, ZendTo no longer needs any form of custom-built >>>> PHP or anything like that. So there's no recompiling to be done. >>>> Then if you have a previous preferences.php and/or zendto.conf, you >>>> need to use >>>> /opt/zendto/bin/upgrade_preferences_php >>>> and >>>> /opt/zendto/bin/upgrade_zendto_conf >>>> to upgrade those files. >>>> Also, if you have done an RPM upgrade from ZendTo 4, you probably >>>> have a whole stack of *.rpmnew files in /opt/zendto/templates. You >>>> want to move each of those into place so they replace your old >>>> *.tpl files. >>>> As I said, it really is faster/easier/better to build v5 from >>>> scratch, its requirements are so different from v4. >>>> Hope that helps, >>>> Jules. >>>> On 25/10/2018 15:59, Ken Etter wrote: >>>>> None of that helps. I'm building a new system. This is a >>>>> production system. I never had problems in the past with upgrading >>>>> so I went ahead and did it. Bad move. Unless anyone has any other >>>>> ideas, I will just keep working on setting up the new system. I >>>>> have to get something running again for my users. >>>>> >>>>> Ken >>>>> >>> Jules Field via ZendTo 10/25/2018 10:53 AM >>> >>>>> > Yes, those directories do need to be writable by whatever user and >>>>> group your web server is running as. >>>>> >>>>> If you are using SELinux (most likely if you are using CentOS or >>>>> RedHat), then I would also advise >>>>> restorecon -FRv /opt/zendto /var/zendto >>>>> >>>>> to reset all the SELinux attributes to the values configured by my >>>>> Installer. >>>>> Also, if you think it might be an SELinux problem, you can switch >>>>> it into "permissive" mode by >>>>> setenforce permissive >>>>> >>>>> systemctl restart httpd >>>>> >>>>> systemctl restart clamd at scan >>>>> >>>>> To switch it back to "enforcing", you then do >>>>> setenforce enforcing >>>>> >>>>> systemctl restart httpd >>>>> >>>>> systemctl restart clamd at scan >>>>> >>>>> Cheers, >>>>> Jules. >>>>> On 25/10/2018 14:31, Gray McCord via ZendTo wrote: >>>>>> I?ve seen that message as well. Check the file permissions on the >>>>>> /opt/zendto directories. Seems like I needed to make them >>>>>> writeable by the apache user, but I could be mistaken. >>>>>> Gray McCord >>>>>> /Adapt, Mutate, Migrate, or Die/ >>>>>> -C. Darwin >>>>>> *From:* ZendTo *On Behalf Of *Ken Etter >>>>>> via ZendTo >>>>>> *Sent:* Thursday, October 25, 2018 8:26 AM >>>>>> *To:* ZendTo List >>>>>> *Cc:* Ken Etter >>>>>> *Subject:* Re: [ZendTo] Zend.to error during drop-off >>>>>> Going back through the mailing list archives, I see that I am >>>>>> having exactly the same problem as Kevin O'Connor in this thread: >>>>>> http://jul.es/pipermail/zendto/2018-June/003208.html >>>>>> >>>>>> Files are uploaded, but I get that error message and the email is >>>>>> not sent. >>>>>> There is no stated resolution in that thread. Any suggestions or >>>>>> do I have to rebuild a brand new Zend.To server? >>>>>> Zend.To has been fairly solid for me...a bit of a pain to find >>>>>> this upgrade to be so fragile. >>>>>> Ken >>>>>> >>> Ken Etter via ZendTo > >>>>>> 10/25/2018 8:38 AM >>> >>>>>> I am running this on Ubuntu 16.04.5 LTS if that matters. >>>>>> >>>>>> Ken >>>>>> >>> Ken Etter via ZendTo > >>>>>> 10/25/2018 8:36 AM >>> >>>>>> Just upgraded my Zend.To installation from 4.x to 5.15-1. >>>>>> Everything appeared to go ok. But when I click drop-off files, I >>>>>> get an error that states: "Sorry, I failed to drop-off your >>>>>> files! Note that you cannot drop-off directories, only files." >>>>>> I'm not dropping off a directory, just a single file. I tried a >>>>>> couple different file types - same error each time. Any >>>>>> suggestions for fixing this? Thanks! >>>>>> >>>>>> >>>>>> *Ken Etter*, System Administrator >>>>>> Architectural Group >>>>>> 260.432.9337 | msktd.com >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> ZendTo mailing list >>>>>> ZendTo at zend.to >>>>>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 >>>>> >>>>> 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 >>>> >>>> Jules >>>> >>>> -- >>>> Julian Field MEng CEng CITP MBCS MIEEE MACM >>>> >>>> IMPORTANT: This email is intended for the use of the individual >>>> addressee(s) named above and may contain information that is >>>> confidential, privileged or unsuitable for overly sensitive persons >>>> with low self-esteem, no sense of humour or irrational religious >>>> beliefs. If you are not the intended recipient, any dissemination, >>>> distribution or copying of this email is not authorised (either >>>> explicitly or implicitly) and constitutes an irritating social faux >>>> pas. >>>> >>>> Unless the word absquatulation has been used in its correct context >>>> somewhere other than in this warning, it does not have any legal >>>> or no grammatical use and may be ignored. No animals were harmed >>>> in the transmission of this email, although the kelpie next door >>>> is living on borrowed time, let me tell you. Those of you with an >>>> overwhelming fear of the unknown will be gratified to learn that >>>> there is no hidden message revealed by reading this warning backwards, >>>> so just ignore that Alert Notice from Microsoft. >>>> >>>> However, by pouring a complete circle of salt around yourself and >>>> your computer you can ensure that no harm befalls you and your pets. >>>> If you have received this email in error, please add some nutmeg >>>> and egg whites, whisk and place in a warm oven for 40 minutes. >>>> >>>> www.Zend.To >>>> Twitter: @JulesFM >>> >>> Jules >>> >>> -- >>> Julian Field MEng CEng CITP MBCS MIEEE MACM >>> >>> 'It's very unlikely indeed he will ever recover consciousness, and >>> if he does he won't be the Julian you knew.' >>> - A hospital consultant I proved very wrong in 2007 :-) >>> >>> www.Zend.To >>> Twitter: @JulesFM >> >> Jules >> >> -- >> Julian Field MEng CEng CITP MBCS MIEEE MACM >> >> 'Is the Holocaust an aberration, or a reflection of who we really are?' >> - Holocaust Museum, Berlin >> >> www.Zend.To >> Twitter: @JulesFM > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'Named must your fear be before banish it you can.' - Yoda > > www.Zend.To > Twitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM IMPORTANT: This email is intended for the use of the individual addressee(s) named above and may contain information that is confidential, privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational religious beliefs. If you are not the intended recipient, any dissemination, distribution or copying of this email is not authorised (either explicitly or implicitly) and constitutes an irritating social faux pas. Unless the word absquatulation has been used in its correct context somewhere other than in this warning, it does not have any legal or no grammatical use and may be ignored. No animals were harmed in the transmission of this email, although the kelpie next door is living on borrowed time, let me tell you. Those of you with an overwhelming fear of the unknown will be gratified to learn that there is no hidden message revealed by reading this warning backwards, so just ignore that Alert Notice from Microsoft. However, by pouring a complete circle of salt around yourself and your computer you can ensure that no harm befalls you and your pets. If you have received this email in error, please add some nutmeg and egg whites, whisk and place in a warm oven for 40 minutes. www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: not available URL: From kle at msktd.com Mon Oct 29 15:22:41 2018 From: kle at msktd.com (Ken Etter) Date: Mon, 29 Oct 2018 11:22:41 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: <5BD72483020000ED00409C78@mail.msktd.com> References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <7b4ae0e0-c1df-866e-ded2-b1462a3b36ca@Zend.To> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <19BE5BFC0200006B7314B811@mail.msktd.com> <5BD2F9E402000022004084CF@mail.msktd.com> <5BD713CF020000130012DBDA@mail.msktd.com> <12b1fe6e-2537-28ee-64d1-5c0ce75c378a@Zend.To> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <19BE5BFC0200006B7314B811@mail.msktd.com> <5BD2F9E402000022004084CF@mail.msktd.com> <5BD713CF020000130012DBDA@mail.msktd.com> <11B4C0E1020000F0C84B1EE2@mail.msktd.com> <5BD72483020000ED00409C78@mail.msktd.com> <5BD725C1020000130012DBF2@mail.msktd.com> Message-ID: I started with that because I already had a downloaded copy. I just completed another test install and got the same results - error - failed to drop-off files. I'll send the files off list. Thanks. Ken >>> Jules Field 10/29/2018 10:16 AM >>> > Ken, I only changed the FQDN to set the domain name. As Ubuntu set itself up, I didn't appear to have a domain name set, so "hostname --fqdn" was just giving "kenetter" as it had no domain name. So I set the domain name as per those instructions in order to get a fully-qualified name out of "hostname --fqdn" before starting to install ZendTo. If the ZendTo Installer cannot deduce a likely DNS domain name, it tends to make some wrong decisions when setting up the preferences.php and internaldomains.conf files. For a pain-free installation, I tend to set that first, so that at least it has *a* domain name, even if it's not the same one as the website is going to have. Having the output of "hostname --fqdn" contain no dots at all is not a good sign of a "well setup" server. :) That actual hostname and such like is irrelevant to ZendTo. What's important is that the serverRoot in preferences.php matches up with what Apache thinks it's serving it as. You can put ZendTo on a server that has lots of other sites on it as well, that's no problem at all. Do you want to send me (off list) your Apache config for ZendTo, in addition to the preferences.php, zendto.conf and internaldomains.conf files? It's either something odd in there, or else your Ubuntu 16.04.3 system isn't anything like as "vanilla" as you think it is. Out of interest, why start with 16.04.3? That's not the latest 16.04 media available from Canonical, I had to go and hunt for it to reproduce your steps. Cheers, Jules. On 29/10/2018 14:06, Ken Etter wrote: Jules, Something doesn't seem clear here. You mention changing the FQDN of the server. Why should that even be necessary? I run multiple web servers on the same server and the site addresses do not have anything at all to do with the server name or the server FQDN. For ZendTo to work properly does the site address have to match the server FQDN? Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/26/2018 7:26 AM >>> > Ken, I have just built a ZendTo VM from scratch using the exact same version of Ubuntu you did, and the current production release of ZendTo (as installed by my Installer). It worked absolutely fine for me. Attached is the PDF log of what I did, so you can read through it. I didn't have to change the server name, as I had already set the FQDN to the same name in the Ubuntu networking setup (as documented in the PDF). And I didn't touch *anything* after running the Installer, including zendto.conf, preferences.php and the Apache config. I would be starting to suspect your preferences.php settings. What happens if you check the serverRoot is right, and make sure that Apache config matches. Otherwise just use the preferences.php as the Installer leaves it. On a VM with only 1GB, the current production release probably won't be able to encrypt a drop-off. I've reduced the memory requirements for that in the latest betas, but in the mean time you will probably need at least 2GB RAM to be able to use encryption. Cheers, Jules. On 26/10/2018 09:20, Jules Field wrote: Ken, This is really odd. I did thoroughly test the Installer on every supported version of every flavour of Linux that I say it works on. I've got dozens of old VMs to prove it. :-/ I'm downloading 16.04.3 (amd64) right now, and will walk through the same steps as you listed below. I'll let you know the results as soon as I've built it. Cheers, Jules. On 25/10/2018 17:57, Ken Etter wrote: Jules, I just finished setting up a brand new VM and I get the same error message! This makes no sense! Any thoughts? * installed Ubuntu 16.04.3 as a basic server * configured networking * installed openssh-server * patched server to 16.04.5 * downloaded your installer and ran it used most defaults except I had to specify the smtp server and the address of the site the site address defaulted to https://server_name and I changed it to https://transfer.msktd.com * modified preferences.php and zendto.conf for my settings * reboot * login to site and attempt a drop off and I get the same error as my upgraded site What could possibly be wrong in what I did? Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:41 AM >>> > Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. Then "pwconv" so the change takes effect. Then try this su - apache (or whatever user your Apache is running as) clamdscan /var/zendto/* clamdscan --fdpass /var/zendto/* exit What happened? Did the virus scans both complete successfully? If not, and you're running CentOS/RedHat 7, try this and then give the above another try: groupmems --group virusgroup --add apache systemctl restart httpd I added that extra groupmems command to the Installer a day or two ago when I discovered that RedHat/CentOS had changed their group membership rules in an update. Any improvement? Cheers, Jules. P.S. Otherwise, if you can give me remote ssh access I can login myself and take a look for you. I would be interested to see what it is, if it's not any of the above. On 25/10/2018 16:22, Ken Etter wrote: Yep, PHP 7.2 is installed. I've run through the installer multiple times now. No change, still get the error. Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:15 AM >>> > Do you have PHP 7.2 installed? My Installer can be run in stages, and those stages can be run independently. So you might want to download the Installer, unpack it and wander into it. In what will obviously be the right sub-dir for your OS, you will see the numbered scripts. # cd install.ZendTo/CentOS-RedHat/ # ls 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 # If your web server is already working nicely, then you can probably skip stage 1 (though it won't do any harm). If you haven't installed PHP 7.2 along with things like the sodium extension, then run stage 2 which installs PHP. (Grab a backup copy of your ZendTo installation first, as it may have to remove the *whole* of PHP first which can also remove ZendTo and other PHP applications in the process, before it can install the correct version). Stages 3 and 5 shouldn't do any damage, but will add any new settings they need for PHP and so on. Stage 7 does the actual ZendTo installation itself, which it will do as an upgrade if it finds a zendto RPM already installed. Well worth running. Stage 8 is only relevant if you are using SELinux, and won't do anything if you're not. Since version 4, ZendTo no longer needs any form of custom-built PHP or anything like that. So there's no recompiling to be done. Then if you have a previous preferences.php and/or zendto.conf, you need to use /opt/zendto/bin/upgrade_preferences_php and /opt/zendto/bin/upgrade_zendto_conf to upgrade those files. Also, if you have done an RPM upgrade from ZendTo 4, you probably have a whole stack of *.rpmnew files in /opt/zendto/templates. You want to move each of those into place so they replace your old *.tpl files. As I said, it really is faster/easier/better to build v5 from scratch, its requirements are so different from v4. Hope that helps, Jules. On 25/10/2018 15:59, Ken Etter wrote: None of that helps. I'm building a new system. This is a production system. I never had problems in the past with upgrading so I went ahead and did it. Bad move. Unless anyone has any other ideas, I will just keep working on setting up the new system. I have to get something running again for my users. Ken >>> Jules Field via ZendTo ( mailto:zendto at zend.to) 10/25/2018 10:53 AM >>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise restorecon -FRv /opt/zendto /var/zendto to reset all the SELinux attributes to the values configured by my Installer. Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by setenforce permissive systemctl restart httpd systemctl restart clamd at scan To switch it back to "enforcing", you then do setenforce enforcing systemctl restart httpd systemctl restart clamd at scan Cheers, Jules. On 25/10/2018 14:31, Gray McCord via ZendTo wrote: I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo ( mailto:zendto-bounces at zend.to) On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List ( mailto:zendto at zend.to) Cc: Ken Etter ( mailto:KLE at msktd.com) Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: http://jul.es/pipermail/zendto/2018-June/003208.html ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fpipermail%2Fzendto%2F2018-June%2F003208.html&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=%2FMQVOSO5ZjLwkrQ991eChCvoSfFOLwm3yUcnFSzoRc0%3D&reserved=0) Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmsktd.com%2F&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=XsZydsv5daB1usPtdakyqf%2BjPxBLH9n8NbGcrjhC34Y%3D&reserved=0) _______________________________________________ZendTo mailing listZendTo at zend.tohttps://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0) Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'The past is supposed to be a place of reference, not a place ofresidence! There is a reason why your car has a big windshield anda small rearview mirror. You are supposed to keep your eyes on whereyou are going, and just occasionally check out where you have been.' - Willie Jolleywww.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACMIMPORTANT: This ema il is intended for the use of the individualaddressee(s) named above and may contain information that isconfidential, privileged or unsuitable for overly sensitive personswith low self-esteem, no sense of humour or irrational religiousbeliefs. If you are not the intended recipient, any dissemination,distribution or copying of this email is not authorised (eitherexplicitly or implicitly) and constitutes an irritating social fauxpas.Unless the word absquatulation has been used in its correct contextsomewhere other than in this warning, it does not have any legalor no grammatical use and may be ignored. No animals were harmedin the transmission of this email, although the kelpie next dooris living on borrowed time, let me tell you. Those of you with anoverwhelming fear of the unknown will be gratified to learn thatthere is no hidden message revealed by reading this warning backwards,so just ignore that Alert Notice from Microsoft.However, by pouring a complete circle of salt around yourself andyour computer you can ensure that no harm befalls you and your pets.If you have received this email in error, please add some nutmegand egg whites, whisk and place in a warm oven for 40 minutes.www.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'It's very unlikely indeed he will ever recover consciousness, and if he does he won't be the Julian you knew.' - A hospital consultant I proved very wrong in 2007 :-)www.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'Is the Holocaust an aberration, or a reflection of who we really are?' - Holocaust Museum, Berlinwww.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'Named must your fear be before banish it you can.' - Yodawww.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACMIMPORTANT: This email is intended for the use of the individualaddressee(s) named above and may contain information that isconfidential, privileged or unsuitable for overly sensitive personswith low self-esteem, no sense of humour or irrational religiousbeliefs. If you are not the intended recipient, any dissemination,distribution or copying of this email is not authorised (eitherexplicitly or implicitly) and constitutes an irritating social fauxpas.Unless the word absquatulation has been used in its correct contextsomewhere other than in this warning, it does not have any legalor no grammatical use and may be ignored. No animals were harmedin the transmission of this email, although the kelpie next dooris living on borrowed time, let me tell you. Those of you with anoverwhelming fear of the unknown will be gratified to learn thatthere is no hidden message revealed by reading this warning backwards,so just ignore that Alert Notice from Microsoft.However, by pouring a complete circle of salt around yourself andyour computer you can ensure that no harm befalls you and your pets.If you have received this email in error, please add some nutmegand egg whites, whisk and place in a warm oven for 40 minutes.www.Zend.ToTwitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From gdm at sangabriel.com Mon Oct 29 16:46:49 2018 From: gdm at sangabriel.com (Gray McCord) Date: Mon, 29 Oct 2018 11:46:49 -0500 Subject: [ZendTo] {Disarmed} Re: Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <7b4ae0e0-c1df-866e-ded2-b1462a3b36ca@Zend.To> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <19BE5BFC0200006B7314B811@mail.msktd.com> <5BD2F9E402000022004084CF@mail.msktd.com> <5BD713CF020000130012DBDA@mail.msktd.com> <12b1fe6e-2537-28ee-64d1-5c0ce75c378a@Zend.To> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <19BE5BFC0200006B7314B811@mail.msktd.com> <5BD2F9E402000022004084CF@mail.msktd.com> <5BD713CF020000130012DBDA@mail.msktd.com> <11B4C0E1020000F0C84B1EE2@mail.msktd.com> <5BD72483020000ED00409C78@mail.msktd.com> <5BD725C1020000130012DBF2@mail.msktd.com> Message-ID: I think I mentioned this before, but I had this problem when clamd was updated to v100.1 on my Centos7 server. Adding the apache user (in my case ?apache? ) to the ?virusgroup? group cleared up the problem, which was the clamd daemon being unable to properly access its socket file. Prior to the v100 versions of clamd, the scanner user and group were the same: ?clamscan:clamscan?. With the new version this changed to ?clamscan:virusgroup? for some reason and it broke my Zendto. (Thanks to Jules for pointing me to a much more safe and simple solution to a problem I originally overcomplicated! ?) This may not be your problem, but it?s worth a try. Good Luck! Gray Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo on behalf of Ken Etter via ZendTo Reply-To: ZendTo Users Date: Monday, October 29, 2018 at 11:17 AM To: Jules Field , ZendTo List Cc: Ken Etter Subject: {Disarmed} Re: [ZendTo] Zend.to error during drop-off I started with that because I already had a downloaded copy. I just completed another test install and got the same results - error - failed to drop-off files. I'll send the files off list. Thanks. Ken >>> Jules Field 10/29/2018 10:16 AM >>> > Ken, I only changed the FQDN to set the domain name. As Ubuntu set itself up, I didn't appear to have a domain name set, so "hostname --fqdn" was just giving "kenetter" as it had no domain name. So I set the domain name as per those instructions in order to get a fully-qualified name out of "hostname --fqdn" before starting to install ZendTo. If the ZendTo Installer cannot deduce a likely DNS domain name, it tends to make some wrong decisions when setting up the preferences.php and internaldomains.conf files. For a pain-free installation, I tend to set that first, so that at least it has *a* domain name, even if it's not the same one as the website is going to have. Having the output of "hostname --fqdn" contain no dots at all is not a good sign of a "well setup" server. :) That actual hostname and such like is irrelevant to ZendTo. What's important is that the serverRoot in preferences.php matches up with what Apache thinks it's serving it as. You can put ZendTo on a server that has lots of other sites on it as well, that's no problem at all. Do you want to send me (off list) your Apache config for ZendTo, in addition to the preferences.php, zendto.conf and internaldomains.conf files? It's either something odd in there, or else your Ubuntu 16.04.3 system isn't anything like as "vanilla" as you think it is. Out of interest, why start with 16.04.3? That's not the latest 16.04 media available from Canonical, I had to go and hunt for it to reproduce your steps. Cheers, Jules. On 29/10/2018 14:06, Ken Etter wrote: Jules, Something doesn't seem clear here. You mention changing the FQDN of the server. Why should that even be necessary? I run multiple web servers on the same server and the site addresses do not have anything at all to do with the server name or the server FQDN. For ZendTo to work properly does the site address have to match the server FQDN? Ken >>> Jules Field 10/26/2018 7:26 AM >>> > Ken, I have just built a ZendTo VM from scratch using the exact same version of Ubuntu you did, and the current production release of ZendTo (as installed by my Installer). It worked absolutely fine for me. Attached is the PDF log of what I did, so you can read through it. I didn't have to change the server name, as I had already set the FQDN to the same name in the Ubuntu networking setup (as documented in the PDF). And I didn't touch *anything* after running the Installer, including zendto.conf, preferences.php and the Apache config. I would be starting to suspect your preferences.php settings. What happens if you check the serverRoot is right, and make sure that Apache config matches. Otherwise just use the preferences.php as the Installer leaves it. On a VM with only 1GB, the current production release probably won't be able to encrypt a drop-off. I've reduced the memory requirements for that in the latest betas, but in the mean time you will probably need at least 2GB RAM to be able to use encryption. Cheers, Jules. On 26/10/2018 09:20, Jules Field wrote: Ken, This is really odd. I did thoroughly test the Installer on every supported version of every flavour of Linux that I say it works on. I've got dozens of old VMs to prove it. :-/ I'm downloading 16.04.3 (amd64) right now, and will walk through the same steps as you listed below. I'll let you know the results as soon as I've built it. Cheers, Jules. On 25/10/2018 17:57, Ken Etter wrote: Jules, I just finished setting up a brand new VM and I get the same error message! This makes no sense! Any thoughts? * installed Ubuntu 16.04.3 as a basic server * configured networking * installed openssh-server * patched server to 16.04.5 * downloaded your installer and ran it used most defaults except I had to specify the smtp server and the address of the site the site address defaulted to https://server_name and I changed it to https://transfer.msktd.com * modified preferences.php and zendto.conf for my settings * reboot * login to site and attempt a drop off and I get the same error as my upgraded site What could possibly be wrong in what I did? Ken >>> Jules Field 10/25/2018 11:41 AM >>> > Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. Then "pwconv" so the change takes effect. Then try this su - apache (or whatever user your Apache is running as) clamdscan /var/zendto/* clamdscan --fdpass /var/zendto/* exit What happened? Did the virus scans both complete successfully? If not, and you're running CentOS/RedHat 7, try this and then give the above another try: groupmems --group virusgroup --add apache systemctl restart httpd I added that extra groupmems command to the Installer a day or two ago when I discovered that RedHat/CentOS had changed their group membership rules in an update. Any improvement? Cheers, Jules. P.S. Otherwise, if you can give me remote ssh access I can login myself and take a look for you. I would be interested to see what it is, if it's not any of the above. On 25/10/2018 16:22, Ken Etter wrote: Yep, PHP 7.2 is installed. I've run through the installer multiple times now. No change, still get the error. Ken >>> Jules Field 10/25/2018 11:15 AM >>> > Do you have PHP 7.2 installed? My Installer can be run in stages, and those stages can be run independently. So you might want to download the Installer, unpack it and wander into it. In what will obviously be the right sub-dir for your OS, you will see the numbered scripts. # cd install.ZendTo/CentOS-RedHat/ # ls 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 # If your web server is already working nicely, then you can probably skip stage 1 (though it won't do any harm). If you haven't installed PHP 7.2 along with things like the sodium extension, then run stage 2 which installs PHP. (Grab a backup copy of your ZendTo installation first, as it may have to remove the *whole* of PHP first which can also remove ZendTo and other PHP applications in the process, before it can install the correct version). Stages 3 and 5 shouldn't do any damage, but will add any new settings they need for PHP and so on. Stage 7 does the actual ZendTo installation itself, which it will do as an upgrade if it finds a zendto RPM already installed. Well worth running. Stage 8 is only relevant if you are using SELinux, and won't do anything if you're not. Since version 4, ZendTo no longer needs any form of custom-built PHP or anything like that. So there's no recompiling to be done. Then if you have a previous preferences.php and/or zendto.conf, you need to use /opt/zendto/bin/upgrade_preferences_php and /opt/zendto/bin/upgrade_zendto_conf to upgrade those files. Also, if you have done an RPM upgrade from ZendTo 4, you probably have a whole stack of *.rpmnew files in /opt/zendto/templates. You want to move each of those into place so they replace your old *.tpl files. As I said, it really is faster/easier/better to build v5 from scratch, its requirements are so different from v4. Hope that helps, Jules. On 25/10/2018 15:59, Ken Etter wrote: None of that helps. I'm building a new system. This is a production system. I never had problems in the past with upgrading so I went ahead and did it. Bad move. Unless anyone has any other ideas, I will just keep working on setting up the new system. I have to get something running again for my users. Ken >>> Jules Field via ZendTo 10/25/2018 10:53 AM >>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise restorecon -FRv /opt/zendto /var/zendto to reset all the SELinux attributes to the values configured by my Installer. Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by setenforce permissive systemctl restart httpd systemctl restart clamd at scan To switch it back to "enforcing", you then do setenforce enforcing systemctl restart httpd systemctl restart clamd at scan Cheers, Jules. On 25/10/2018 14:31, Gray McCord via ZendTo wrote: I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List Cc: Ken Etter Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: MailScanner has detected a possible fraud attempt from "emea01.safelinks.protection.outlook.com" claiming to be http://jul.es/pipermail/zendto/2018-June/003208.html Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | MailScanner has detected a possible fraud attempt from "emea01.safelinks.protection.outlook.com" claiming to be msktd.com _______________________________________________ ZendTo mailing list ZendTo at zend.to https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 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 Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM IMPORTANT: This email is intended for the use of the individual addressee(s) named above and may contain information that is confidential, privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational religious beliefs. If you are not the intended recipient, any dissemination, distribution or copying of this email is not authorised (either explicitly or implicitly) and constitutes an irritating social faux pas. Unless the word absquatulation has been used in its correct context somewhere other than in this warning, it does not have any legal or no grammatical use and may be ignored. No animals were harmed in the transmission of this email, although the kelpie next door is living on borrowed time, let me tell you. Those of you with an overwhelming fear of the unknown will be gratified to learn that there is no hidden message revealed by reading this warning backwards, so just ignore that Alert Notice from Microsoft. However, by pouring a complete circle of salt around yourself and your computer you can ensure that no harm befalls you and your pets. If you have received this email in error, please add some nutmeg and egg whites, whisk and place in a warm oven for 40 minutes. www.Zend.To Twitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'It's very unlikely indeed he will ever recover consciousness, and if he does he won't be the Julian you knew.' ? - A hospital consultant I proved very wrong in 2007 :-) www.Zend.To Twitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'Is the Holocaust an aberration, or a reflection of who we really are?' - Holocaust Museum, Berlin www.Zend.To Twitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'Named must your fear be before banish it you can.' - Yoda www.Zend.To Twitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM IMPORTANT: This email is intended for the use of the individual addressee(s) named above and may contain information that is confidential, privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational religious beliefs. If you are not the intended recipient, any dissemination, distribution or copying of this email is not authorised (either explicitly or implicitly) and constitutes an irritating social faux pas. Unless the word absquatulation has been used in its correct context somewhere other than in this warning, it does not have any legal or no grammatical use and may be ignored. No animals were harmed in the transmission of this email, although the kelpie next door is living on borrowed time, let me tell you. Those of you with an overwhelming fear of the unknown will be gratified to learn that there is no hidden message revealed by reading this warning backwards, so just ignore that Alert Notice from Microsoft. However, by pouring a complete circle of salt around yourself and your computer you can ensure that no harm befalls you and your pets. If you have received this email in error, please add some nutmeg and egg whites, whisk and place in a warm oven for 40 minutes. www.Zend.To Twitter: @JulesFM _______________________________________________ ZendTo mailing list ZendTo at zend.to http://jul.es/mailman/listinfo/zendto -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10426 bytes Desc: not available URL: From kle at msktd.com Mon Oct 29 17:27:36 2018 From: kle at msktd.com (Ken Etter) Date: Mon, 29 Oct 2018 13:27:36 -0400 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <7b4ae0e0-c1df-866e-ded2-b1462a3b36ca@Zend.To> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <19BE5BFC0200006B7314B811@mail.msktd.com> <5BD2F9E402000022004084CF@mail.msktd.com> <5BD713CF020000130012DBDA@mail.msktd.com> <12b1fe6e-2537-28ee-64d1-5c0ce75c378a@Zend.To> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <19BE5BFC0200006B7314B811@mail.msktd.com> <5BD2F9E402000022004084CF@mail.msktd.com> <5BD713CF020000130012DBDA@mail.msktd.com> <11B4C0E1020000F0C84B1EE2@mail.msktd.com> <5BD72483020000ED00409C78@mail.msktd.com> <5BD725C1020000130012DBF2@mail.msktd.com> <5BD74308020000130012DC09@mail.msktd.com> Message-ID: Unbelievable! I have been so stupid! Sorry to have wasted your time Jules! I owe you one! I have no idea what went wrong with the upgrade...probably something screwy left over. But I now see why the new installs kept failing... I much prefer using SLES over Ubuntu. I was still using Ubuntu for Zend.To as a hold-over from the days you provided pre-built VMs. Thinking I was screwing up my Ubuntu install somehow, I setup SLES and got the exact same error. That made no sense, I couldn't be screwing up both...then it struck me! Since my existing production Zend.To site is up and running and I don't want to change the site name, I was testing the new sites using the ip address instead of the site name. I modified my hosts file to point to my new server and used the site name to get to it and all works - no error. Tried it with both the Ubuntu and SLES new setups and both work. I can't believe I have been so dense. Ken >>> Ken Etter via ZendTo 10/29/2018 11:22 AM >>> I started with that because I already had a downloaded copy. I just completed another test install and got the same results - error - failed to drop-off files. I'll send the files off list. Thanks. Ken >>> Jules Field 10/29/2018 10:16 AM >>> > Ken, I only changed the FQDN to set the domain name. As Ubuntu set itself up, I didn't appear to have a domain name set, so "hostname --fqdn" was just giving "kenetter" as it had no domain name. So I set the domain name as per those instructions in order to get a fully-qualified name out of "hostname --fqdn" before starting to install ZendTo. If the ZendTo Installer cannot deduce a likely DNS domain name, it tends to make some wrong decisions when setting up the preferences.php and internaldomains.conf files. For a pain-free installation, I tend to set that first, so that at least it has *a* domain name, even if it's not the same one as the website is going to have. Having the output of "hostname --fqdn" contain no dots at all is not a good sign of a "well setup" server. :) That actual hostname and such like is irrelevant to ZendTo. What's important is that the serverRoot in preferences.php matches up with what Apache thinks it's serving it as. You can put ZendTo on a server that has lots of other sites on it as well, that's no problem at all. Do you want to send me (off list) your Apache config for ZendTo, in addition to the preferences.php, zendto.conf and internaldomains.conf files? It's either something odd in there, or else your Ubuntu 16.04.3 system isn't anything like as "vanilla" as you think it is. Out of interest, why start with 16.04.3? That's not the latest 16.04 media available from Canonical, I had to go and hunt for it to reproduce your steps. Cheers, Jules. On 29/10/2018 14:06, Ken Etter wrote: Jules, Something doesn't seem clear here. You mention changing the FQDN of the server. Why should that even be necessary? I run multiple web servers on the same server and the site addresses do not have anything at all to do with the server name or the server FQDN. For ZendTo to work properly does the site address have to match the server FQDN? Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/26/2018 7:26 AM >>> > Ken, I have just built a ZendTo VM from scratch using the exact same version of Ubuntu you did, and the current production release of ZendTo (as installed by my Installer). It worked absolutely fine for me. Attached is the PDF log of what I did, so you can read through it. I didn't have to change the server name, as I had already set the FQDN to the same name in the Ubuntu networking setup (as documented in the PDF). And I didn't touch *anything* after running the Installer, including zendto.conf, preferences.php and the Apache config. I would be starting to suspect your preferences.php settings. What happens if you check the serverRoot is right, and make sure that Apache config matches. Otherwise just use the preferences.p hp as the Installer leaves it. On a VM with only 1GB, the current production release probably won't be able to encrypt a drop-off. I've reduced the memory requirements for that in the latest betas, but in the mean time you will probably need at least 2GB RAM to be able to use encryption. Cheers, Jules. On 26/10/2018 09:20, Jules Field wrote: Ken, This is really odd. I did thoroughly test the Installer on every supported version of every flavour of Linux that I say it works on. I've got dozens of old VMs to prove it. :-/ I'm downloading 16.04.3 (amd64) right now, and will walk through the same steps as you listed below. I'll let you know the results as soon as I've built it. Cheers, Jules. On 25/10/2018 17:57, Ken Etter wrote: Jules, I just finished setting up a brand new VM and I get the same error message! This makes no sense! Any thoughts? * installed Ubuntu 16.04.3 as a basic server * configured networking * installed openssh-server * patched server to 16.04.5 * downloaded your installer and ran it used most defaults except I had to specify the smtp server and the address of the site the site address defaulted to https://server_name and I changed it to https://transfer.msktd.com * modified preferences.php and zendto.conf for my settings * reboot * login to site and attempt a drop off and I get the same error as my upgraded site What could possibly be wrong in what I did? Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:41 AM >>> > Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. Then "pwconv" so the change takes effect. Then try this su - apache (or whatever user your Apache is running as) clamdscan /var/zendto/* clamdscan --fdpass /var/zendto/* exit What happened? Did the virus scans both complete successfully? If not, and you're running CentOS/RedHat 7, try this and then give the above another try: groupmems --group virusgroup --add apache systemctl restart httpd I added that extra groupmems command to the Installer a day or two ago when I discovered that RedHat/CentOS had changed their group membership rules in an update. Any improvement? Cheers, Jules. P.S. Otherwise, if you can give me remote ssh access I can login myself and take a look for you. I would be interested to see what it is, if it's not any of the above. On 25/10/2018 16:22, Ken Etter wrote: Yep, PHP 7.2 is installed. I've run through the installer multiple times now. No change, still get the error. Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:15 AM >>> > Do you have PHP 7.2 installed? My Installer can be run in stages, and those stages can be run independently. So you might want to download the Installer, unpack it and wander into it. In what will obviously be the right sub-dir for your OS, you will see the numbered scripts. # cd install.ZendTo/CentOS-RedHat/ # ls 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 # If your web server is already working nicely, then you can probably skip stage 1 (though it won't do any harm). If you haven't installed PHP 7.2 along with things like the sodium extension, then run stage 2 which installs PHP. (Grab a backup copy of your ZendTo installation first, as it may have to remove the *whole* of PHP first which can also remove ZendTo and other PHP applications in the process, before it can install the correct version). Stages 3 and 5 shouldn't do any damage, but will add any new settings they need for PHP and so on. Stage 7 does the actual ZendTo installation itself, which it will do as an upgrade if it finds a zendto RPM already installed. Well worth running. Stage 8 is only relevant if you are using SELinux, and won't do anything if you're not. Since version 4, ZendTo no longer needs any form of custom-built PHP or anything like that. So there's no recompiling to be done. Then if you have a previous preferences .php and/or zendto.conf, you need to use /opt/zendto/bin/upgrade_preferences_php and /opt/zendto/bin/upgrade_zendto_conf to upgrade those files. Also, if you have done an RPM upgrade from ZendTo 4, you probably have a whole stack of *.rpmnew files in /opt/zendto/templates. You want to move each of those into place so they replace your old *.tpl files. As I said, it really is faster/easier/better to build v5 from scratch, its requirements are so different from v4. Hope that helps, Jules. On 25/10/2018 15:59, Ken Etter wrote: None of that helps. I'm building a new system. This is a production system. I never had problems in the past with upgrading so I went ahead and did it. Bad move. Unless anyone has any other ideas, I will just keep working on setting up the new system. I have to get something running again for my users. Ken >>> Jules Field via ZendTo ( mailto:zendto at zend.to) 10/25/2018 10:53 AM >>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise restorecon -FRv /opt/zendto /var/zendto to reset all the SELinux attributes to the values configured by my Installer. Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by setenforce permissive systemctl restart httpd systemctl restart clamd at scan To switch it back to "enforcing", you then do setenforce enforcing systemctl restart httpd systemctl restart clamd at scan Cheers, Jules. On 25/10/2018 14:31, Gray McCord via ZendTo wrote: I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo ( mailto:zendto-bounces at zend.to) On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List ( mailto:zendto at zend.to) Cc: Ken Etter ( mailto:KLE at msktd.com) Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: http://jul.es/pipermail/zendto/2018-June/003208.html ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fpipermail%2Fzendto%2F2018-June%2F003208.html&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=%2FMQVOSO5ZjLwkrQ991eChCvoSfFOLwm3yUcnFSzoRc0%3D&reserved=0) Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Administrator Architectural Group 260.432.9337 | msktd.com ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmsktd.com%2F&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=XsZydsv5daB1usPtdakyqf%2BjPxBLH9n8NbGcrjhC34Y%3D&reserved=0) _______________________________________________ZendTo mailing listZendTo at zend.tohttps://emea01.safelin ks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0) Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'The past is supposed to be a place of reference, not a place ofresidence! There is a reason why your car has a big windshield anda small rearview mirror. You are supposed to keep your eyes on whereyou are going, and just occasionally check out where you have been.' - Willie Jolleywww.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACMIMPORTANT: This email is intended for the use of the individualaddressee(s) named above and may contain information that isconfidential, privileged or unsuitable for overly sensitive personswith low self-esteem, no sense of humour or irrational religiousbeliefs. If you are not the intended recipient, any dissemination,distribution or copying of this email is not authorised (eitherexplicitly or implicitly) and constitutes an irritating social fauxpas.Unless the word absquatulation has been used in its correct contextsomewhere other than in this warning, it does not have any legalor no grammatical use and may be ignored. No animals were harmedin the transmission of this email, although the kelpie next dooris living on borrowed time, let me tell you. Those of you with anoverwhelming fear of the unknown will be gratified to learn thatthere is no hidden message revealed by reading this warning backwards,so just ignore that Alert Notice from Microsoft.However, by pouring a complete circle of salt around yourself andyour computer you can ensure that no harm befalls you and your pets.If you have received this email in error, please add some nutmegand egg whites, whisk and place in a warm oven for 40 minutes.www.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'It's very unlikely indeed he will ever recover consciousness, and if he does he won't be the Julian you knew.' - A hospital consultant I proved very wrong in 2007 :-)www.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'Is the Holocaust an aberration, or a reflection of who we really are?' - Holocaust Museum, Berlinwww.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACM'Named must your fear be before banish it you can.' - Yodawww.Zend.ToTwitter: @JulesFM Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACMIMPORTANT: This email is intended for the use of the individualaddressee(s) named above and may contain information that isconfidential, privileged or unsuitable for overly sensitive personswith low self-esteem, no sense of humour or irrational religiousbeliefs. If you are not the intended recipient, any dissemination,distribution or copying of this email is not authorised (eitherexplicitly or implicitly) and constitutes an irritating social fauxpas.Unless the word absquatulation has been used in its correct contextsomewhere other than in this warning, it does not have any legalor no grammatical use and may be ignored. No animals were harmedin the transmission of this email, although the kelpie next dooris living on borrowed time, let me tell you. Those of you with anoverwhelming fear of the unknown will be gratified to learn thatthere is no hidden message revealed by reading this warning backwards,so just ignore that Alert Notice from Microsoft.However, by pouring a complete circle of salt around yourself andyour computer you can ensure that no harm befalls you and your pets.If you have received this email in error, please add some nutmega nd egg whites, whisk and place in a warm oven for 40 minutes.www.Zend.ToTwitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From kle at msktd.com Mon Oct 29 17:28:56 2018 From: kle at msktd.com (Ken Etter) Date: Mon, 29 Oct 2018 13:28:56 -0400 Subject: [ZendTo] {Disarmed} Re: Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <7b4ae0e0-c1df-866e-ded2-b1462a3b36ca@Zend.To> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <19BE5BFC0200006B7314B811@mail.msktd.com> <5BD2F9E402000022004084CF@mail.msktd.com> <5BD713CF020000130012DBDA@mail.msktd.com> <12b1fe6e-2537-28ee-64d1-5c0ce75c378a@Zend.To> <275750470200009C7314B811@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <19BE5BFC0200006B7314B811@mail.msktd.com> <5BD2F9E402000022004084CF@mail.msktd.com> <5BD713CF020000130012DBDA@mail.msktd.com> <11B4C0E1020000F0C84B1EE2@mail.msktd.com> <5BD72483020000ED00409C78@mail.msktd.com> <5BD725C1020000130012DBF2@mail.msktd.com> <5BD74358020000130012DC0F@mail.msktd.com> Message-ID: Gray, Yep, you did and I checked that and it wasn't it. Turns out it was me making a stupid mistake. Ken >>> Gray McCord via ZendTo 10/29/2018 12:46 PM >>> I think I mentioned this before, but I had this problem when clamd was updated to v100.1 on my Centos7 server. Adding the apache user (in my case ?apache? ) to the ?virusgroup? group cleared up the problem, which was the clamd daemon being unable to properly access its socket file. Prior to the v100 versions of clamd, the scanner user and group were the same: ?clamscan:clamscan?. With the new version this changed to ?clamscan:virusgroup? for some reason and it broke my Zendto. (Thanks to Jules for pointing me to a much more safe and simple solution to a problem I originally overcomplicated! ??) This may not be your problem, but it?s worth a try. Good Luck! Gray Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo on behalf of Ken Etter via ZendTo Reply-To: ZendTo Users Date: Monday, October 29, 2018 at 11:17 AM To: Jules Field , ZendTo List Cc: Ken Etter Subject: {Disarmed} Re: [ZendTo] Zend.to error during drop-off I started with that because I already had a downloaded copy. I just completed another test install and got the same results - error - failed to drop-off files. I'll send the files off list. Thanks. Ken >>> Jules Field 10/29/2018 10:16 AM >>> > Ken, I only changed the FQDN to set the domain name. As Ubuntu set itself up, I didn't appear to have a domain name set, so "hostname --fqdn" was just giving "kenetter" as it had no domain name. So I set the domain name as per those instructions in order to get a fully-qualified name out of "hostname --fqdn" before starting to install ZendTo. If the ZendTo Installer cannot deduce a likely DNS domain name, it tends to make some wrong decisions when setting up the preferences.php and internaldomains.conf files. For a pain-free installation, I tend to set that first, so that at least it has *a* domain name, even if it's not the same one as the website is going to have. Having the output of "hostname --fqdn" contain no dots at all is not a good sign of a "well setup" server. :) That actual hostname and such like is irrelevant to ZendTo. What's important is that the serverRoot in preferences.php matches up with what Apache thinks it's serving it as. You can put ZendTo on a server that has lots of other sites on it as well, that's no problem at all. Do you want to send me (off list) your Apache config for ZendTo, in addition to the preferences.php, zendto.conf and internaldomains.conf files? It's either something odd in there, or else your Ubuntu 16.04.3 system isn't anything like as "vanilla" as you think it is. Out of interest, why start with 16.04.3? That's not the latest 16.04 media available from Canonical, I had to go and hunt for it to reproduce your steps. Cheers, Jules. On 29/10/2018 14:06, Ken Etter wrote: Jules, Something doesn't seem clear here. You mention changing the FQDN of the server. Why should that even be necessary? I run multiple web servers on the same server and the site addresses do not have anything at all to do with the server name or the server FQDN. For ZendTo to work properly does the site address have to match the server FQDN? Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/26/2018 7:26 AM >>> > Ken, I have just built a ZendTo VM from scratch using the exact same version of Ubuntu you did, and the current production release of ZendTo (as installed by my Installer). It worked absolutely fine for me. Attached is the PDF log of what I did, so you can read through it. I didn't have to change the server name, as I had already set the FQDN to the same name in the Ubuntu networking setup (as documented in the PDF). And I didn't touch *anythin g* after running the Installer, including zendto.conf, preferences.php and the Apache config. I would be starting to suspect your preferences.php settings. What happens if you check the serverRoot is right, and make sure that Apache config matches. Otherwise just use the preferences.php as the Installer leaves it. On a VM with only 1GB, the current production release probably won't be able to encrypt a drop-off. I've reduced the memory requirements for that in the latest betas, but in the mean time you will probably need at least 2GB RAM to be able to use encryption. Cheers, Jules. On 26/10/2018 09:20, Jules Field wrote: Ken, This is really odd. I did thoroughly test the Installer on every supported version of every flavour of Linux that I say it works on. I've got dozens of old VMs to prove it. :-/ I'm downloading 16.04.3 (amd64) right now, and will walk through the same steps as you listed below. I'll let you know the results as soon as I've built it. Cheers, Jules. On 25/10/2018 17:57, Ken Etter wrote: Jules, I just finished setting up a brand new VM and I get the same error message! This makes no sense! Any thoughts? * installed Ubuntu 16.04.3 as a basic server * configured networking * installed openssh-server * patched server to 16.04.5 * downloaded your installer and ran it used most defaults except I had to specify the smtp server and the address of the site the site address defaulted to https://server_name and I changed it to https://transfer.msktd.com * modified preferences.php and zendto.conf for my settings * reboot * login to site and attempt a drop off and I get the same error as my upgraded site What could possibly be wrong in what I did? Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:41 AM >>> > Edit your /etc/passwd file to set the shell for your Apache user to /bin/bash. Then "pwconv" so the change takes effect. Then try this su - apache (or whatever user your Apache is running as) clamdscan /var/zendto/* clamdscan --fdpass /var/zendto/* exit What happened? Did the virus scans both complete successfully? If not, and you're running CentOS/RedHat 7, try this and then give the above another try: groupmems --group virusgroup --add apache systemctl restart httpd I added that extra groupmems command to the Installer a day or two ago when I discovered that RedHat/CentOS had changed their group membership rules in an update. Any improvement? Cheers, Jules. P.S. Otherwise, if you can give me remote ssh access I can login myself and take a look for you. I would be interested to see what it is, if it's not any of the above. On 25/10/2018 16:22, Ken Etter wrote: Yep, PHP 7.2 is installed. I've run through the installer multiple times now. No change, still get the error. Ken >>> Jules Field ( mailto:Jules at Zend.To) 10/25/2018 11:15 AM >>> > Do you have PHP 7.2 installed? My Installer can be run in stages, and those stages can be run independently. So you might want to download the Installer, unpack it and wander into it. In what will obviously be the right sub-dir for your OS, you will see the numbered scripts. # cd install.ZendTo/CentOS-RedHat/ # ls 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 # If your web server is already working nicely, then you can probably skip stage 1 (though it won't do any harm). If you haven't installed PHP 7.2 along with things like the sodium extension, then run stage 2 which installs PHP. (Grab a backup copy of your ZendTo installation first, as it may have to remove the *whole* of PHP first which can also remove ZendTo and other PHP applications in the process, before it can install the correct version). Stages 3 and 5 shouldn't do any damage, but will add any new settings they need for PHP and so on. Stage 7 does the actual ZendTo installation itself, which it will do as an upgrade if it finds a zendto R PM already installed. Well worth running. Stage 8 is only relevant if you are using SELinux, and won't do anything if you're not. Since version 4, ZendTo no longer needs any form of custom-built PHP or anything like that. So there's no recompiling to be done. Then if you have a previous preferences.php and/or zendto.conf, you need to use /opt/zendto/bin/upgrade_preferences_php and /opt/zendto/bin/upgrade_zendto_conf to upgrade those files. Also, if you have done an RPM upgrade from ZendTo 4, you probably have a whole stack of *.rpmnew files in /opt/zendto/templates. You want to move each of those into place so they replace your old *.tpl files. As I said, it really is faster/easier/better to build v5 from scratch, its requirements are so different from v4. Hope that helps, Jules. On 25/10/2018 15:59, Ken Etter wrote: None of that helps. I'm building a new system. This is a production system. I never had problems in the past with upgrading so I went ahead and did it. Bad move. Unless anyone has any other ideas, I will just keep working on setting up the new system. I have to get something running again for my users. Ken >>> Jules Field via ZendTo ( mailto:zendto at zend.to) 10/25/2018 10:53 AM >>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. If you are using SELinux (most likely if you are using CentOS or RedHat), then I would also advise restorecon -FRv /opt/zendto /var/zendto to reset all the SELinux attributes to the values configured by my Installer. Also, if you think it might be an SELinux problem, you can switch it into "permissive" mode by setenforce permissive systemctl restart httpd systemctl restart clamd at scan To switch it back to "enforcing", you then do setenforce enforcing systemctl restart httpd systemctl restart clamd at scan Cheers, Jules. On 25/10/2018 14:31, Gray McCord via ZendTo wrote: I?ve seen that message as well. Check the file permissions on the /opt/zendto directories. Seems like I needed to make them writeable by the apache user, but I could be mistaken. Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin From: ZendTo ( mailto:zendto-bounces at zend.to) On Behalf Of Ken Etter via ZendTo Sent: Thursday, October 25, 2018 8:26 AM To: ZendTo List ( mailto:zendto at zend.to) Cc: Ken Etter ( mailto:KLE at msktd.com) Subject: Re: [ZendTo] Zend.to error during drop-off Going back through the mailing list archives, I see that I am having exactly the same problem as Kevin O'Connor in this thread: MailScanner has detected a possible fraud attempt from "emea01.safelinks.protection.outlook.com" claiming to be http://jul.es/pipermail/zendto/2018-June/003208.html ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fpipermail%2Fzendto%2F2018-June%2F003208.html&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=%2FMQVOSO5ZjLwkrQ991eChCvoSfFOLwm3yUcnFSzoRc0%3D&reserved=0) Files are uploaded, but I get that error message and the email is not sent. There is no stated resolution in that thread. Any suggestions or do I have to rebuild a brand new Zend.To server? Zend.To has been fairly solid for me...a bit of a pain to find this upgrade to be so fragile. Ken >>> Ken Etter via ZendTo 10/25/2018 8:38 AM >>> I am running this on Ubuntu 16.04.5 LTS if that matters. Ken >>> Ken Etter via ZendTo 10/25/2018 8:36 AM >>> Just upgraded my Zend.To installation from 4.x to 5.15-1. Everything appeared to go ok. But when I click drop-off files, I get an error that states: "Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files." I'm not dropping off a directory, just a single file. I tried a couple different file types - same error each time. Any suggestions for fixing this? Thanks! Ken Etter, System Admin istrator Architectural Group 260.432.9337 | MailScanner has detected a possible fraud attempt from "emea01.safelinks.protection.outlook.com" claiming to be msktd.com ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmsktd.com%2F&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=XsZydsv5daB1usPtdakyqf%2BjPxBLH9n8NbGcrjhC34Y%3D&reserved=0) _______________________________________________ZendTo mailing listZendTo at zend.tohttps://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 ( https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0) Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'The past is supposed to be a place of reference, not a place ofresidence! There is a reason why your car has a big windshield anda small rearview mirror. You are supposed to keep your eyes on whereyou are going, and just occasionally check out where you have been.' - Willie Jolley www.Zend.ToTwitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM IMPORTANT: This email is intended for the use of the individualaddressee(s) named above and may contain information that isconfidential, privileged or unsuitable for overly sensitive personswith low self-esteem, no sense of humour or irrational religiousbeliefs. If you are not the intended recipient, any dissemination,distribution or copying of this email is not authorised (eitherexplicitly or implicitly) and constitutes an irritating social fauxpas. Unless the word absquatulation has been used in its correct contextsomewhere other than in this warning, it does not have any legalor no grammatical use and may be ignored. No animals were harmedin the transmission of this email, although the kelpie next dooris living on borrowed time, let me tell you. Those of you with anoverwhelming fear of the unknown will be gratified to learn thatthere is no hidden message revealed by reading this warning backwards,so just ignore that Alert Notice from Microsoft. However, by pouring a complete circle of salt around yourself andyour computer you can ensure that no harm befalls you and your pets.If you have received this email in error, please add some nutmegand egg whites, whisk and place in a warm oven for 40 minutes. www.Zend.ToTwitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'It's very unlikely indeed he will ever recover consciousness, and if he does he won't be the Julian you knew.' - A hospital consultant I proved very wrong in 2007 :-) www.Zend.ToTwitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'Is the Holocaust an aberration, or a reflection of who we really are?' - Holocaust Museum, Berlin www.Zend.ToTwitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'Named must your fear be before banish it you can.' - Yoda www.Zend.ToTwitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM IMPORTANT: This email is intended for the use of the individualaddressee(s) named above and may contain information that isconfidential, privileged or unsuitable for overly sensitive personswith low self-esteem, no sense of humour or irrational religiousbeliefs. If you are not the intended recipient, any dissemination,distribution or copying of this email is not authorised (eitherexplicitly or implicitly) and constitutes an irritating social fauxpas. Unless the word absquatulation has been used in its correct contextsomewhere other than in this warning, it does not have any legalor no grammatical use and may be ignored . No animals were harmedin the transmission of this email, although the kelpie next dooris living on borrowed time, let me tell you. Those of you with anoverwhelming fear of the unknown will be gratified to learn thatthere is no hidden message revealed by reading this warning backwards,so just ignore that Alert Notice from Microsoft. However, by pouring a complete circle of salt around yourself andyour computer you can ensure that no harm befalls you and your pets.If you have received this email in error, please add some nutmegand egg whites, whisk and place in a warm oven for 40 minutes. www.Zend.ToTwitter: @JulesFM _______________________________________________ ZendTo mailing list ZendTo at zend.to http://jul.es/mailman/listinfo/zendto -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: Portable Network Graphics Format URL: From Jules at Zend.To Tue Oct 30 11:10:55 2018 From: Jules at Zend.To (Jules Field) Date: Tue, 30 Oct 2018 11:10:55 +0000 Subject: [ZendTo] Zend.to error during drop-off In-Reply-To: References: <5BD1B8D3020000130012D8F6@mail.msktd.com> <5BD1E4180200002500407BED@mail.msktd.com> <5BD1F601020000130012D950@mail.msktd.com> <19BE5BFC0200006B7314B811@mail.msktd.com> <5BD2F9E402000022004084CF@mail.msktd.com> <5BD713CF020000130012DBDA@mail.msktd.com> <11B4C0E1020000F0C84B1EE2@mail.msktd.com> <5BD72483020000ED00409C78@mail.msktd.com> <5BD725C1020000130012DBF2@mail.msktd.com> <5BD74308020000130012DC09@mail.msktd.com> Message-ID: <268021fc-3d3c-1967-1ee2-ca47ac2de3c5@Zend.To> Ken, That's a cracker! "Modifying /etc/hosts for fun and profit!" Or not. The good bit is that we got to the bottom of it in the end. Given the time of year, I was starting to wonder if your VMs were haunted..... :-) That's given me a good laugh this morning, thank you! ;-) Cheers, Jules. On 29/10/2018 17:27, Ken Etter wrote: > Unbelievable!? I have been so stupid! Sorry to have wasted your time > Jules!? I owe you one! > I have no idea what went wrong with the upgrade...probably something > screwy left over. > But I now see why the new installs kept failing... > I much prefer using SLES over Ubuntu.? I was still using Ubuntu for > Zend.To as a hold-over from the days you provided pre-built VMs.? > Thinking I was screwing up my Ubuntu install somehow,?I setup SLES and > got the exact same error.? That made no sense, I couldn't be screwing > up both...then it struck me! Since my existing production Zend.To site > is up and running and I don't want to change the site name, I was > testing the new sites using the ip address instead of the site name.? > I modified my hosts file to point to my new server?and used the site > name to get to it and all works - no error.? Tried it with both the > Ubuntu and SLES new setups and both work.? I can't believe I have been > so dense.? > > Ken > >>> Ken Etter via ZendTo 10/29/2018 11:22 AM >>> > I started with that because I already had a downloaded copy. > I just completed another test install and got the same results - error > - failed to drop-off files. > I'll send the files off list.? Thanks. > > Ken > >>> Jules Field 10/29/2018 10:16 AM >>> > > Ken, > > I only changed the FQDN to set the domain name. As Ubuntu set itself > up, I didn't appear to have a domain name set, so "hostname --fqdn" > was just giving "kenetter" as it had no domain name. So I set the > domain name as per those instructions in order to get a > fully-qualified name out of "hostname --fqdn" before starting to > install ZendTo. > If the ZendTo Installer cannot deduce a likely DNS domain name, it > tends to make some wrong decisions when setting up the preferences.php > and internaldomains.conf files. For a pain-free installation, I tend > to set that first, so that at least it has *a* domain name, even if > it's not the same one as the website is going to have. Having the > output of "hostname --fqdn" contain no dots at all is not a good sign > of a "well setup" server. :) > That actual hostname and such like is irrelevant to ZendTo. What's > important is that the serverRoot in preferences.php matches up with > what Apache thinks it's serving it as. > You can put ZendTo on a server that has lots of other sites on it as > well, that's no problem at all. > Do you want to send me (off list) your Apache config for ZendTo, in > addition to the preferences.php, zendto.conf and internaldomains.conf > files? It's either something odd in there, or else your Ubuntu 16.04.3 > system isn't anything like as "vanilla" as you think it is. > Out of interest, why start with 16.04.3? That's not the latest 16.04 > media available from Canonical, I had to go and hunt for it to > reproduce your steps. > Cheers, > Jules. > On 29/10/2018 14:06, Ken Etter wrote: >> Jules, >> Something doesn't seem clear here. You mention changing the FQDN of >> the server. Why should that even be necessary? I run multiple web >> servers on the same server and the site addresses do not have >> anything at all to do with the server name or the server FQDN. For >> ZendTo to work properly does the site address have to match the >> server FQDN? >> >> Ken >> >>> Jules Field 10/26/2018 7:26 AM >>> >> > Ken, >> >> I have just built a ZendTo VM from scratch using the exact same >> version of Ubuntu you did, and the current production release of >> ZendTo (as installed by my Installer). >> It worked absolutely fine for me. >> Attached is the PDF log of what I did, so you can read through it. >> I didn't have to change the server name, as I had already set the >> FQDN to the same name in the Ubuntu networking setup (as documented >> in the PDF). >> And I didn't touch *anything* after running the Installer, including >> zendto.conf, preferences.php and the Apache config. >> I would be starting to suspect your preferences.php settings. What >> happens if you check the serverRoot is right, and make sure that >> Apache config matches. Otherwise just use the preferences.php as the >> Installer leaves it. >> On a VM with only 1GB, the current production release probably won't >> be able to encrypt a drop-off. I've reduced the memory requirements >> for that in the latest betas, but in the mean time you will probably >> need at least 2GB RAM to be able to use encryption. >> Cheers, >> Jules. >> On 26/10/2018 09:20, Jules Field wrote: >>> Ken, >>> >>> This is really odd. I did thoroughly test the Installer on every >>> supported version of every flavour of Linux that I say it works on. >>> I've got dozens of old VMs to prove it. :-/ >>> I'm downloading 16.04.3 (amd64) right now, and will walk through the >>> same steps as you listed below. >>> I'll let you know the results as soon as I've built it. >>> Cheers, >>> Jules. >>> On 25/10/2018 17:57, Ken Etter wrote: >>>> Jules, >>>> I just finished setting up a brand new VM and I get the same error >>>> message! This makes no sense! Any thoughts? >>>> * installed Ubuntu 16.04.3 as a basic server >>>> * configured networking >>>> * installed openssh-server >>>> * patched server to 16.04.5 >>>> * downloaded your installer and ran it >>>> used most defaults except I had to specify the smtp server and the >>>> address of the site >>>> the site address defaulted to https://server_name and I changed it >>>> to https://transfer.msktd.com >>>> * modified preferences.php and zendto.conf for my settings >>>> * reboot >>>> * login to site and attempt a drop off and I get the same error as >>>> my upgraded site >>>> >>>> What could possibly be wrong in what I did? >>>> >>>> Ken >>>> >>> Jules Field 10/25/2018 11:41 AM >>> >>>> > Edit your /etc/passwd file to set the shell for your Apache user >>>> to /bin/bash. >>>> >>>> Then "pwconv" so the change takes effect. >>>> Then try this >>>> su - apache (or whatever user your Apache is running as) >>>> >>>> clamdscan /var/zendto/* >>>> >>>> clamdscan --fdpass /var/zendto/* >>>> >>>> exit >>>> >>>> What happened? Did the virus scans both complete successfully? >>>> If not, and you're running CentOS/RedHat 7, try this and then give >>>> the above another try: >>>> groupmems --group virusgroup --add apache >>>> >>>> systemctl restart httpd >>>> >>>> I added that extra groupmems command to the Installer a day or two >>>> ago when I discovered that RedHat/CentOS had changed their group >>>> membership rules in an update. >>>> Any improvement? >>>> Cheers, >>>> Jules. >>>> P.S. Otherwise, if you can give me remote ssh access I can login >>>> myself and take a look for you. I would be interested to see what >>>> it is, if it's not any of the above. >>>> On 25/10/2018 16:22, Ken Etter wrote: >>>>> Yep, PHP 7.2 is installed. I've run through the installer multiple >>>>> times now. No change, still get the error. >>>>> Ken >>>>> >>> Jules Field 10/25/2018 11:15 AM >>> >>>>> > Do you have PHP 7.2 installed? >>>>> >>>>> My Installer can be run in stages, and those stages can be run >>>>> independently. >>>>> So you might want to download the Installer, unpack it and wander >>>>> into it. In what will obviously be the right sub-dir for your OS, >>>>> you will see the numbered scripts. >>>>> # cd install.ZendTo/CentOS-RedHat/ >>>>> >>>>> # ls >>>>> >>>>> 1-devtools.sh 3-clamav.sh 5-httpd-php.sh 7-zendto.sh CentOS6 RHEL7 >>>>> >>>>> 2-php.sh 4-firewall.sh 6-email.sh 8-selinux.sh RHEL5 >>>>> >>>>> # >>>>> >>>>> If your web server is already working nicely, then you can >>>>> probably skip stage 1 (though it won't do any harm). >>>>> If you haven't installed PHP 7.2 along with things like the sodium >>>>> extension, then run stage 2 which installs PHP. (Grab a backup >>>>> copy of your ZendTo installation first, as it may have to remove >>>>> the *whole* of PHP first which can also remove ZendTo and other >>>>> PHP applications in the process, before it can install the correct >>>>> version). >>>>> Stages 3 and 5 shouldn't do any damage, but will add any new >>>>> settings they need for PHP and so on. >>>>> Stage 7 does the actual ZendTo installation itself, which it will >>>>> do as an upgrade if it finds a zendto RPM already installed. Well >>>>> worth running. >>>>> Stage 8 is only relevant if you are using SELinux, and won't do >>>>> anything if you're not. >>>>> Since version 4, ZendTo no longer needs any form of custom-built >>>>> PHP or anything like that. So there's no recompiling to be done. >>>>> Then if you have a previous preferences.php and/or zendto.conf, >>>>> you need to use >>>>> /opt/zendto/bin/upgrade_preferences_php >>>>> and >>>>> /opt/zendto/bin/upgrade_zendto_conf >>>>> to upgrade those files. >>>>> Also, if you have done an RPM upgrade from ZendTo 4, you probably >>>>> have a whole stack of *.rpmnew files in /opt/zendto/templates. You >>>>> want to move each of those into place so they replace your old >>>>> *.tpl files. >>>>> As I said, it really is faster/easier/better to build v5 from >>>>> scratch, its requirements are so different from v4. >>>>> Hope that helps, >>>>> Jules. >>>>> On 25/10/2018 15:59, Ken Etter wrote: >>>>>> None of that helps. I'm building a new system. This is a >>>>>> production system. I never had problems in the past with >>>>>> upgrading so I went ahead and did it. Bad move. Unless anyone has >>>>>> any other ideas, I will just keep working on setting up the new >>>>>> system. I have to get something running again for my users. >>>>>> >>>>>> Ken >>>>>> >>> Jules Field via ZendTo 10/25/2018 10:53 AM >>> >>>>>> > Yes, those directories do need to be writable by whatever user and group your web server is running as. >>>>>> >>>>>> If you are using SELinux (most likely if you are using CentOS or >>>>>> RedHat), then I would also advise >>>>>> restorecon -FRv /opt/zendto /var/zendto >>>>>> >>>>>> to reset all the SELinux attributes to the values configured by >>>>>> my Installer. >>>>>> Also, if you think it might be an SELinux problem, you can switch >>>>>> it into "permissive" mode by >>>>>> setenforce permissive >>>>>> >>>>>> systemctl restart httpd >>>>>> >>>>>> systemctl restart clamd at scan >>>>>> >>>>>> To switch it back to "enforcing", you then do >>>>>> setenforce enforcing >>>>>> >>>>>> systemctl restart httpd >>>>>> >>>>>> systemctl restart clamd at scan >>>>>> >>>>>> Cheers, >>>>>> Jules. >>>>>> On 25/10/2018 14:31, Gray McCord via ZendTo wrote: >>>>>>> I?ve seen that message as well. Check the file permissions on >>>>>>> the /opt/zendto directories. Seems like I needed to make them >>>>>>> writeable by the apache user, but I could be mistaken. >>>>>>> Gray McCord >>>>>>> /Adapt, Mutate, Migrate, or Die/ >>>>>>> -C. Darwin >>>>>>> *From:* ZendTo *On Behalf Of *Ken Etter >>>>>>> via ZendTo >>>>>>> *Sent:* Thursday, October 25, 2018 8:26 AM >>>>>>> *To:* ZendTo List >>>>>>> *Cc:* Ken Etter >>>>>>> *Subject:* Re: [ZendTo] Zend.to error during drop-off >>>>>>> Going back through the mailing list archives, I see that I am >>>>>>> having exactly the same problem as Kevin O'Connor in this >>>>>>> thread: http://jul.es/pipermail/zendto/2018-June/003208.html >>>>>>> >>>>>>> Files are uploaded, but I get that error message and the email >>>>>>> is not sent. >>>>>>> There is no stated resolution in that thread. Any suggestions or >>>>>>> do I have to rebuild a brand new Zend.To server? >>>>>>> Zend.To has been fairly solid for me...a bit of a pain to find >>>>>>> this upgrade to be so fragile. >>>>>>> Ken >>>>>>> >>> Ken Etter via ZendTo > >>>>>>> 10/25/2018 8:38 AM >>> >>>>>>> I am running this on Ubuntu 16.04.5 LTS if that matters. >>>>>>> >>>>>>> Ken >>>>>>> >>> Ken Etter via ZendTo > >>>>>>> 10/25/2018 8:36 AM >>> >>>>>>> Just upgraded my Zend.To installation from 4.x to 5.15-1. >>>>>>> Everything appeared to go ok. But when I click drop-off files, I >>>>>>> get an error that states: "Sorry, I failed to drop-off your >>>>>>> files! Note that you cannot drop-off directories, only files." >>>>>>> I'm not dropping off a directory, just a single file. I tried a >>>>>>> couple different file types - same error each time. Any >>>>>>> suggestions for fixing this? Thanks! >>>>>>> >>>>>>> >>>>>>> *Ken Etter*, System Administrator >>>>>>> Architectural Group >>>>>>> 260.432.9337 | msktd.com >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> ZendTo mailing list >>>>>>> ZendTo at zend.to >>>>>>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Ca244c38af7594fe02f4008d63a8489e3%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=xP3P4EW7oR3QO73%2Bha6sE0Qt7F6lTIDgT%2B09ppjkZZ0%3D&reserved=0 >>>>>> >>>>>> 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 >>>>> >>>>> Jules >>>>> >>>>> -- >>>>> Julian Field MEng CEng CITP MBCS MIEEE MACM >>>>> >>>>> IMPORTANT: This email is intended for the use of the individual >>>>> addressee(s) named above and may contain information that is >>>>> confidential, privileged or unsuitable for overly sensitive persons >>>>> with low self-esteem, no sense of humour or irrational religious >>>>> beliefs. If you are not the intended recipient, any dissemination, >>>>> distribution or copying of this email is not authorised (either >>>>> explicitly or implicitly) and constitutes an irritating social faux >>>>> pas. >>>>> >>>>> Unless the word absquatulation has been used in its correct context >>>>> somewhere other than in this warning, it does not have any legal >>>>> or no grammatical use and may be ignored. No animals were harmed >>>>> in the transmission of this email, although the kelpie next door >>>>> is living on borrowed time, let me tell you. Those of you with an >>>>> overwhelming fear of the unknown will be gratified to learn that >>>>> there is no hidden message revealed by reading this warning backwards, >>>>> so just ignore that Alert Notice from Microsoft. >>>>> >>>>> However, by pouring a complete circle of salt around yourself and >>>>> your computer you can ensure that no harm befalls you and your pets. >>>>> If you have received this email in error, please add some nutmeg >>>>> and egg whites, whisk and place in a warm oven for 40 minutes. >>>>> >>>>> www.Zend.To >>>>> Twitter: @JulesFM >>>> >>>> Jules >>>> >>>> -- >>>> Julian Field MEng CEng CITP MBCS MIEEE MACM >>>> >>>> 'It's very unlikely indeed he will ever recover consciousness, and >>>> if he does he won't be the Julian you knew.' >>>> - A hospital consultant I proved very wrong in 2007 :-) >>>> >>>> www.Zend.To >>>> Twitter: @JulesFM >>> >>> Jules >>> >>> -- >>> Julian Field MEng CEng CITP MBCS MIEEE MACM >>> >>> 'Is the Holocaust an aberration, or a reflection of who we really are?' >>> - Holocaust Museum, Berlin >>> >>> www.Zend.To >>> Twitter: @JulesFM >> >> Jules >> >> -- >> Julian Field MEng CEng CITP MBCS MIEEE MACM >> >> 'Named must your fear be before banish it you can.' - Yoda >> >> www.Zend.To >> Twitter: @JulesFM > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > IMPORTANT: This email is intended for the use of the individual > addressee(s) named above and may contain information that is > confidential, privileged or unsuitable for overly sensitive persons > with low self-esteem, no sense of humour or irrational religious > beliefs. If you are not the intended recipient, any dissemination, > distribution or copying of this email is not authorised (either > explicitly or implicitly) and constitutes an irritating social faux > pas. > > Unless the word absquatulation has been used in its correct context > somewhere other than in this warning, it does not have any legal > or no grammatical use and may be ignored. No animals were harmed > in the transmission of this email, although the kelpie next door > is living on borrowed time, let me tell you. Those of you with an > overwhelming fear of the unknown will be gratified to learn that > there is no hidden message revealed by reading this warning backwards, > so just ignore that Alert Notice from Microsoft. > > However, by pouring a complete circle of salt around yourself and > your computer you can ensure that no harm befalls you and your pets. > If you have received this email in error, please add some nutmeg > and egg whites, whisk and place in a warm oven for 40 minutes. > > www.Zend.To > Twitter: @JulesFM Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'The best and most beautiful things in life cannot be seen or even touched; they must be felt with the heart.' - Helen Keller www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMAGE.png Type: image/png Size: 10425 bytes Desc: not available URL: From ebbernardi at gmail.com Tue Oct 30 14:36:51 2018 From: ebbernardi at gmail.com (Everton Bruno Bernardi) Date: Tue, 30 Oct 2018 11:36:51 -0300 Subject: [ZendTo] =?utf-8?q?Calling_all_translators_=28for_5=2E16=29_?= =?utf-8?q?=E2=80=94_just_1_phrase?= In-Reply-To: References: <7890c015-0255-5790-7dea-e9ce5a9c1bf8@Zend.To> Message-ID: Hi there Jules. Here is the pt-br translation: "Essa palavra-chave n?o ser? enviada aos destinat?rios.
Voc? precisa fazer o envio manualmente." Warm regards. Everton Bernardi On Fri, Oct 26, 2018 at 11:29 AM Jules Field via ZendTo wrote: > To my wonderful translators out there: > > Please can you translate this phrase for me. It is shown as a warning near > the top of the dialog box where the sender enters the passphrase if they > have asked for the drop-off to be encrypted. > > There is a break in the middle as this text sets the width of that dialog > box. If you don't split it up, it gets way too long and so the dialog box > becomes far too wide and looks wrong. > > The phrase is: > > "This passphrase will not be sent to the recipients.
You need to do > this yourself." > > Here is a screenshot of where it appears: > > > Many thanks all! > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'It's in Apple's DNA that technology alone is not enough. It's > technology married with liberal arts, married with the humanities, > that yields us the result that makes our hearts sing.' - Steve Jobs > www.Zend.To > Twitter: @JulesFM > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto > -- *Everton Bruno Bernardi * -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: abflabpcpeihndch.png Type: image/png Size: 27877 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: abflabpcpeihndch.png Type: image/png Size: 27877 bytes Desc: not available URL: From Jules at Zend.To Tue Oct 30 17:18:44 2018 From: Jules at Zend.To (Jules Field) Date: Tue, 30 Oct 2018 17:18:44 +0000 Subject: [ZendTo] =?utf-8?q?Calling_all_translators_=28for_5=2E16=29_?= =?utf-8?q?=E2=80=94_just_1_phrase?= In-Reply-To: References: <7890c015-0255-5790-7dea-e9ce5a9c1bf8@Zend.To> Message-ID: <5524fe8a-ff27-7222-fd5b-9d29a88310d8@Zend.To> Everton, Many thanks for that. At Marcel Richter's suggestion, I have also now added a similar line to the decryption passphrase dialog box. So please can you translate this for me too? "You can ask the sender
for the decryption passphrase." Thanks! Jules. On 30/10/2018 14:36, Everton Bruno Bernardi via ZendTo wrote: > Hi there Jules. > > Here is the pt-br translation: > > "Essa palavra-chave n?o ser? enviada aos destinat?rios.
Voc? > precisa fazer o envio manualmente." > > Warm regards. > > > Everton Bernardi > > On Fri, Oct 26, 2018 at 11:29 AM Jules Field via ZendTo > > wrote: > > To my wonderful translators out there: > > Please can you translate this phrase for me. It is shown as a > warning near the top of the dialog box where the sender enters the > passphrase if they have asked for the drop-off to be encrypted. > > There is a break in the middle as this text sets the width of that > dialog box. If you don't split it up, it gets way too long and so > the dialog box becomes far too wide and looks wrong. > > The phrase is: > > "This passphrase will not be sent to the recipients.
You need > to do this yourself." > > Here is a screenshot of where it appears: > > > Many thanks all! > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'It's in Apple's DNA that technology alone is not enough. It's > technology married with liberal arts, married with the humanities, > that yields us the result that makes our hearts sing.' - Steve Jobs > > www.Zend.To > Twitter: @JulesFM > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto > > > > -- > /Everton Bruno Bernardi / > > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'The owls are not what they appear.' - David Lynch (indirectly) www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Tue Oct 30 17:19:50 2018 From: Jules at Zend.To (Jules Field) Date: Tue, 30 Oct 2018 17:19:50 +0000 Subject: [ZendTo] =?utf-8?q?Calling_all_translators_=28for_5=2E16=29_?= =?utf-8?q?=E2=80=94_just_1_phrase?= In-Reply-To: References: <7890c015-0255-5790-7dea-e9ce5a9c1bf8@Zend.To> <1004486597.152199.1540799025615.JavaMail.tbone@infra-abg-mcr1.psi.de> Message-ID: <3bb23391-4ea1-ba42-f75d-684f2dfc6247@Zend.To> Michael, Many thanks for that. At Marcel Richter's suggestion, I have also now added a similar line to the decryption passphrase dialog box. So please can you translate this for me too? "You can ask the sender
for the decryption passphrase." Thanks! Jules. On 29/10/2018 07:43, Michael Keller via ZendTo wrote: > Hi Jules, > > here the german translation. > > "Dieses Kennwort wird nicht an die Empf?nger gesendet.
Das m?ssen > sie selbst tun." > > Best regards > > Michael > > > Am 26.10.18 um 16:29 schrieb Jules Field via ZendTo: >> To my wonderful translators out there: >> >> Please can you translate this phrase for me. It is shown as a warning >> near the top of the dialog box where the sender enters the passphrase >> if they have asked for the drop-off to be encrypted. >> >> There is a break in the middle as this text sets the width of that >> dialog box. If you don't split it up, it gets way too long and so the >> dialog box becomes far too wide and looks wrong. >> >> The phrase is: >> >> "This passphrase will not be sent to the recipients.
You need to >> do this yourself." >> >> Here is a screenshot of where it appears: >> >> >> Many thanks all! >> >> Jules >> >> -- >> Julian Field MEng CEng CITP MBCS MIEEE MACM >> >> 'It's in Apple's DNA that technology alone is not enough. It's >> ? technology married with liberal arts, married with the humanities, >> ? that yields us the result that makes our hearts sing.' - Steve Jobs >> >> 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 'The owls are not what they appear.' - David Lynch (indirectly) www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From gdm at sangabriel.com Tue Oct 30 22:02:04 2018 From: gdm at sangabriel.com (Gray McCord) Date: Tue, 30 Oct 2018 17:02:04 -0500 Subject: [ZendTo] main.js question References: <0908E127-0ED2-4436-A8F1-642246460847@sangabriel.com> Message-ID: If I make a change to the main.js file in v5.15, will it be overwritten when I update future versions using yum update? The reason I ask is that I need to be able to modify the presentation of the javascript version of the login form for narrow (ie mobile) displays, and I want to make the following change to line 27 to add an id to the div following the loginForm div: From: $(loginForm).after( ?? $('
', { 'style': 'height:30px' }) ); To: $(loginForm).after( ?? $('
', { 'id' : 'jsloginafter' , 'style': 'height:30px' }) ); This is so I can format it with css. Thanks! Gray McCord Adapt, Mutate, Migrate, or Die -C. Darwin -------------- next part -------------- An HTML attachment was scrubbed... URL: From azshane at gmail.com Tue Oct 30 22:37:55 2018 From: azshane at gmail.com (Shane) Date: Tue, 30 Oct 2018 15:37:55 -0700 Subject: [ZendTo] lock down recipient In-Reply-To: References: Message-ID: Jules Since I have i configured the zendto that external users can only drop files for a particular recipient, this is working great. However I noticed when they login to zendto, in main page, there are options: Drop Off, Request a drop off, and pick up. How can I hide the "Request a drop off" and "Pickup" option so it won't be visible to authorized users who login. Thanks. Shane On Thu, Oct 25, 2018 at 4:07 AM Jules Field via ZendTo wrote: > Shane, > > On 24/10/2018 20:51, Shane via ZendTo wrote: > > Hello > > I've just finished installing zend.to > > in my centos 7. is it possible > to lock down the users who login to send files to one particular > recipient, not be able to add any other email address? I browsed through > preferences.php and couldn't find any reference to it unless I missed > something. > > Not currently, no. > You could hard-wire into the template > /opt/zendto/templates/new_dropoff.tpl like this: > * Right near the top, put your fixed recipient info into the variables " > presetToName" and "presetToEmail". > * Search for 'id="addRecipients"'. Add to that tag an attribute ' > style="display:none"'. > That would stop it appearing, which may be enough for your needs. > > > Also is it possible to lock down to allow only Excel files to be uploaded? > > No. There's pretty much no way of *reliably* detecting that a file is an > Excel file. > And don't suggest *.xls or *.xlsx. Then people just rename their > p**n/w*r*z before sending it. > > Sorry! > Jules. > > > thanks i > shane > > _______________________________________________ > ZendTo mailing listZendTo at zend.tohttps://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Cfd6cebc05dc946b2713108d639ea34bd%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=i%2FQ4BIYymCnsMKYR%2B71Hvn%2FMYIcvFlcQ4T5sFU1YYuA%3D&reserved=0 > > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'In Flanders fields the poppies blow > Between the crosses, row on row, > That mark our place: and in the sky > The larks still bravely singing fly > Scarce heard amid the guns below. > > We are the dead: Short days ago, > We lived, felt dawn, saw sunset glow, > Loved and were loved: and now we lie > In Flanders fields! > > Take up our quarrel with the foe > To you, from failing hands, we throw > The torch: be yours to hold it high > If ye break faith with us who die, > We shall not sleep, though poppies grow > In Flanders fields.' Lieutenant Colonel John McCrae > > Composed at the battlefront on May 3, 1915 > during the second battle of Ypres, Belgium > www.Zend.To > Twitter: @JulesFM > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Wed Oct 31 09:32:23 2018 From: Jules at Zend.To (Jules Field) Date: Wed, 31 Oct 2018 09:32:23 +0000 Subject: [ZendTo] main.js question In-Reply-To: References: <0908E127-0ED2-4436-A8F1-642246460847@sangabriel.com> Message-ID: <343788ad-6e48-6853-c695-025451bd9f19@Zend.To> Gray, Yes, it would be overwritten. However, I have just added that 'id' field, with the name you have given below, to the code, so the next time you upgrade the id will be there for you already. Just put your CSS into www/css/local.css and you should be good to go. Cheers, Jules. On 30/10/2018 22:02, Gray McCord via ZendTo wrote: > > If I make a change to the main.js file in v5.15, will it be > overwritten when I update future versions using yum update? The reason > I ask is that I need to be able to modify the presentation of the > javascript version of the login form for narrow (ie mobile) displays, > and I want to make the following change to line 27 to add an id to the > div following the loginForm div: > > From: > > $(loginForm).after( > ?? $(*'
'*, { *'style'*: *'height:30px' *}) > ); > > To: > > $(loginForm).after( ?? $(*'
'*, { *'id' *: *'jsloginafter' *, *'style'*: *'height:30px' *}) ); > > This is so I can format it with css. > > Thanks! > > Gray McCord > > /Adapt, Mutate, Migrate, or Die/ > > -C. Darwin > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'When I read Shakespeare I am struck with wonder That such trivial people should muse and thunder In such lovely language.' - D.H. Lawrence www.Zend.To Twitter: @JulesFM -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Wed Oct 31 09:36:33 2018 From: Jules at Zend.To (Jules Field) Date: Wed, 31 Oct 2018 09:36:33 +0000 Subject: [ZendTo] lock down recipient In-Reply-To: References: Message-ID: <2476120c-16a7-d5da-0266-9e8c3ee56202@Zend.To> Shane, That page is in /opt/zendto/templates/main_menu.tpl. If you just comment out this bit (starts at line 33 in my current version of the file): ? ??? {call name=button href="req.php" text=$request_t width="100%"} ??? {t escape=no}Ask another person to send you some files.{/t} ? ? ??? {call name=button href="pickup.php" text=$pickup_t width="100%"} ??? {t escape=no}Pick-up (download) a file dropped-off for you.{/t} ? those buttons will disappear. If you comment it out by putting {* at the start and *} at the end, the templating engine will never even send that HTML to the browsers at all, which is nicer than using HTML comments. Cheers, Jules. On 30/10/2018 22:37, Shane via ZendTo wrote: > Jules > > Since I have i configured the zendto that external users can only drop > files for a particular recipient, this is working great. However I > noticed when they login to zendto, in main page, > there are options:? Drop Off, Request a drop off, and pick up.? How > can I hide the "Request a drop off" and "Pickup" option so it won't be > visible to authorized users who login. > > Thanks. > Shane > > > On Thu, Oct 25, 2018 at 4:07 AM Jules Field via ZendTo > wrote: > > Shane, > > On 24/10/2018 20:51, Shane via ZendTo wrote: >> Hello >> >> I've just finished installing zend.to >> >> in my centos 7. is it possible >> to lock down the users who login to send files to one particular >> recipient, not be able to add any other email address?? I browsed >> through >> preferences.php and couldn't find any reference to it unless I >> missed something. > Not currently, no. > You could hard-wire into the template > /opt/zendto/templates/new_dropoff.tpl like this: > * Right near the top, put your fixed recipient info into the > variables "presetToName" and "presetToEmail". > * Search for 'id="addRecipients"'. Add to that tag an > attribute 'style="display:none"'. > That would stop it appearing, which may be enough for your needs. > >> >> Also is it possible to lock down to allow only Excel files to be >> uploaded? > No. There's pretty much no way of *reliably* detecting that a file > is an Excel file. > And don't suggest *.xls or *.xlsx. Then people just rename their > p**n/w*r*z before sending it. > > Sorry! > Jules. > >> >> thanks i >> shane >> >> _______________________________________________ >> ZendTo mailing list >> ZendTo at zend.to >> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjul.es%2Fmailman%2Flistinfo%2Fzendto&data=01%7C01%7CJules%40ecs.soton.ac.uk%7Cfd6cebc05dc946b2713108d639ea34bd%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=i%2FQ4BIYymCnsMKYR%2B71Hvn%2FMYIcvFlcQ4T5sFU1YYuA%3D&reserved=0 > > Jules > > -- > Julian Field MEng CEng CITP MBCS MIEEE MACM > > 'In Flanders fields the poppies blow > Between the crosses, row on row, > That mark our place: and in the sky > The larks still bravely singing fly > Scarce heard amid the guns below. > > We are the dead: Short days ago, > We lived, felt dawn, saw sunset glow, > Loved and were loved: and now we lie > In Flanders fields! > > Take up our quarrel with the foe > To you, from failing hands, we throw > The torch: be yours to hold it high > If ye break faith with us who die, > We shall not sleep, though poppies grow > In Flanders fields.' Lieutenant Colonel John McCrae > > Composed at the battlefront on May 3, 1915 > during the second battle of Ypres, Belgium > > 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 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From TZimmerman at fsu.edu Wed Oct 31 14:49:57 2018 From: TZimmerman at fsu.edu (Travis Zimmerman) Date: Wed, 31 Oct 2018 14:49:57 +0000 Subject: [ZendTo] Using the IMAP auth and e-mails don't show up from users' address References: <2c4ce7d5-448a-d5e3-f5cb-af9117a28c8d@fsu.edu> Message-ID: I configured the IMAP authentication to allow my university's students to login to our ZendTo server, but when they drop off files the From field is showing the e-mail address configured in zendto.conf instead of the student's address. The student's address ends up in the Reply-To field, which normally wouldn't be a problem except sometimes automated systems reply back to the drop off e-mails and they ignore the Reply-To. I have SMTPsetFromToSender => TRUE, users that login via LDAP or AD appear to work as expected. BTW I am using the IMAP authentication with Office365 and in order to get it to login correctly I had to change the imap_open line. $mbox = @imap_open('{'.$this->_imapServer.'}INBOX', $uname, $password, OP_READONLY,1,array('DISABLE_AUTHENTICATOR' => 'PLAIN')); So don't know if you want to add this to the documentation somewhere or incorporate into the NSSIMAPAuthenticator code. ------------------------------------------------------------------- Travis Zimmerman tzimmerman at fsu.edu 850-645-8030 Linux Enterprise Applications & Systems its-linuxadmins at fsu.edu Information Technology Services, Florida State University From Jules at Zend.To Wed Oct 31 15:33:53 2018 From: Jules at Zend.To (Jules Field) Date: Wed, 31 Oct 2018 15:33:53 +0000 Subject: [ZendTo] Using the IMAP auth and e-mails don't show up from users' address In-Reply-To: References: <2c4ce7d5-448a-d5e3-f5cb-af9117a28c8d@fsu.edu> Message-ID: <8ede9f8c-b5df-df2e-4c24-9cf2403e45ad@Zend.To> Travis, If you are authenticating users against Office365, then why not do that with AD? I don't quite see why you need to use the IMAP authenticator at all. If it's a separate AD forest for some reason, then that's okay, ZendTo will happily do 3 different AD forests with independent setups. So "SMTPsetFromToSender'=>TRUE" works as expected if they login via LDAP or AD, but doesn't if they login via IMAP? What we do here for the "From" address is use an address whose email is just automatically trashed, ie. a "no-reply" address. Then automated stuff that is replying (incorrectly) to the "From:" or (validly/correctly) to the envelope sender will just be thrown away. Any human-generated replies will go to the right user. Thanks for the info about the option you need to pass to O365. I guess that's going to need yet another preferences.php setting. Cheers, Jules. On 31/10/2018 14:49, Travis Zimmerman via ZendTo wrote: > I configured the IMAP authentication to allow my university's students > to login to our ZendTo server, but when they drop off files the From > field is showing the e-mail address configured in zendto.conf instead of > the student's address. The student's address ends up in the Reply-To > field, which normally wouldn't be a problem except sometimes automated > systems reply back to the drop off e-mails and they ignore the Reply-To. > > I have SMTPsetFromToSender => TRUE, users that login via LDAP or AD > appear to work as expected. > > BTW I am using the IMAP authentication with Office365 and in order to > get it to login correctly I had to change the imap_open line. > $mbox = @imap_open('{'.$this->_imapServer.'}INBOX', $uname, $password, > OP_READONLY,1,array('DISABLE_AUTHENTICATOR' => 'PLAIN')); > > So don't know if you want to add this to the documentation somewhere or > incorporate into the NSSIMAPAuthenticator code. > > ------------------------------------------------------------------- > Travis Zimmerman tzimmerman at fsu.edu 850-645-8030 > Linux Enterprise Applications & Systems its-linuxadmins at fsu.edu > Information Technology Services, Florida State University > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'Named must your fear be before banish it you can.' - Yoda www.Zend.To Twitter: @JulesFM From TZimmerman at fsu.edu Wed Oct 31 16:09:47 2018 From: TZimmerman at fsu.edu (Travis Zimmerman) Date: Wed, 31 Oct 2018 16:09:47 +0000 Subject: [ZendTo] Using the IMAP auth and e-mails don't show up from users' address In-Reply-To: References: <2c4ce7d5-448a-d5e3-f5cb-af9117a28c8d@fsu.edu> <8ede9f8c-b5df-df2e-4c24-9cf2403e45ad@Zend.To> Message-ID: I tried to use my university's AD for the students (there is a previous e-mail I sent to the ZendTo mailing list about a week ago), but due to how our Microsoft Admins configured it they needed to use an alternate attribute. Yes. When I login to LDAP or AD and drop off a file, the e-mail sent to the recipient will show my e-mail address in the From field. If I login using the IMAP auth the From field lists the servers default e-mail from zendto.conf and the Reply-To field has the IMAP account's e-mail address. ------------------------------------------------------------------- Travis Zimmerman tzimmerman at fsu.edu 850-645-8030 Linux Enterprise Applications & Systems its-linuxadmins at fsu.edu Information Technology Services, Florida State University On 10/31/18 11:33 AM, Jules Field via ZendTo wrote: > Travis, > > If you are authenticating users against Office365, then why not do > that with AD? > I don't quite see why you need to use the IMAP authenticator at all. > If it's a separate AD forest for some reason, then that's okay, ZendTo > will happily do 3 different AD forests with independent setups. > > So "SMTPsetFromToSender'=>TRUE" works as expected if they login via > LDAP or AD, but doesn't if they login via IMAP? > > What we do here for the "From" address is use an address whose email > is just automatically trashed, ie. a "no-reply" address. Then > automated stuff that is replying (incorrectly) to the "From:" or > (validly/correctly) to the envelope sender will just be thrown away. > Any human-generated replies will go to the right user. > > Thanks for the info about the option you need to pass to O365. I guess > that's going to need yet another preferences.php setting. > > Cheers, > Jules. > > On 31/10/2018 14:49, Travis Zimmerman via ZendTo wrote: >> I configured the IMAP authentication to allow my university's students >> to login to our ZendTo server, but when they drop off files the From >> field is showing the e-mail address configured in zendto.conf instead of >> the student's address. The student's address ends up in the Reply-To >> field, which normally wouldn't be a problem except sometimes automated >> systems reply back to the drop off e-mails and they ignore the Reply-To. >> >> I have SMTPsetFromToSender => TRUE, users that login via LDAP or AD >> appear to work as expected. >> >> BTW I am using the IMAP authentication with Office365 and in order to >> get it to login correctly I had to change the imap_open line. >> $mbox = @imap_open('{'.$this->_imapServer.'}INBOX', $uname, $password, >> OP_READONLY,1,array('DISABLE_AUTHENTICATOR' => 'PLAIN')); >> >> So don't know if you want to add this to the documentation somewhere or >> incorporate into the NSSIMAPAuthenticator code. >> >> ------------------------------------------------------------------- >> Travis Zimmerman??? tzimmerman at fsu.edu???? 850-645-8030 >> Linux Enterprise Applications & Systems its-linuxadmins at fsu.edu >> Information Technology Services, Florida State University >> >> _______________________________________________ >> ZendTo mailing list >> ZendTo at zend.to >> https://urldefense.proofpoint.com/v2/url?u=http-3A__jul.es_mailman_listinfo_zendto&d=DwICAg&c=HPMtquzZjKY31rtkyGRFnQ&r=TZ3x4Nnv5Pp03uwRWF9UlLOaC296m8a1MGVEkWJljsg&m=5u9mHQwWyo_tYTeW__SOzvefpnCjf4YQxPsJSnNZ3t0&s=2lT413dnsMw6bu9-9TLNGGhRMyhC3YK11szRGuK1xtw&e= >> > > Jules > From TZimmerman at fsu.edu Wed Oct 31 20:56:13 2018 From: TZimmerman at fsu.edu (Travis Zimmerman) Date: Wed, 31 Oct 2018 20:56:13 +0000 Subject: [ZendTo] Using the IMAP auth and e-mails don't show up from users' address In-Reply-To: References: <2c4ce7d5-448a-d5e3-f5cb-af9117a28c8d@fsu.edu> <8ede9f8c-b5df-df2e-4c24-9cf2403e45ad@Zend.To> Message-ID: I realized I should mention that we are using e-mail addresses to login to our ZendTo service to differentiate between our two domains. Don't know if that would effect how e-mails are sent. Doesn't seem to be a problem for our faculty/staff (AD, username at fsu.edu), just the students (IMAP, username at my.fsu.edu). ------------------------------------------------------------------- Travis Zimmerman tzimmerman at fsu.edu 850-645-8030 Linux Enterprise Applications & Systems its-linuxadmins at fsu.edu Information Technology Services, Florida State University On 10/31/18 12:09 PM, Travis Zimmerman via ZendTo wrote: > I tried to use my university's AD for the students (there is a previous > e-mail I sent to the ZendTo mailing list about a week ago), but due to > how our Microsoft Admins configured it they needed to use an alternate > attribute. > > Yes. When I login to LDAP or AD and drop off a file, the e-mail sent to > the recipient will show my e-mail address in the From field. If I login > using the IMAP auth the From field lists the servers default e-mail from > zendto.conf and the Reply-To field has the IMAP account's e-mail address. > > ------------------------------------------------------------------- > Travis Zimmerman tzimmerman at fsu.edu 850-645-8030 > Linux Enterprise Applications & Systems its-linuxadmins at fsu.edu > Information Technology Services, Florida State University > > On 10/31/18 11:33 AM, Jules Field via ZendTo wrote: >> Travis, >> >> If you are authenticating users against Office365, then why not do >> that with AD? >> I don't quite see why you need to use the IMAP authenticator at all. >> If it's a separate AD forest for some reason, then that's okay, ZendTo >> will happily do 3 different AD forests with independent setups. >> >> So "SMTPsetFromToSender'=>TRUE" works as expected if they login via >> LDAP or AD, but doesn't if they login via IMAP? >> >> What we do here for the "From" address is use an address whose email >> is just automatically trashed, ie. a "no-reply" address. Then >> automated stuff that is replying (incorrectly) to the "From:" or >> (validly/correctly) to the envelope sender will just be thrown away. >> Any human-generated replies will go to the right user. >> >> Thanks for the info about the option you need to pass to O365. I guess >> that's going to need yet another preferences.php setting. >> >> Cheers, >> Jules. >> >> On 31/10/2018 14:49, Travis Zimmerman via ZendTo wrote: >>> I configured the IMAP authentication to allow my university's students >>> to login to our ZendTo server, but when they drop off files the From >>> field is showing the e-mail address configured in zendto.conf instead of >>> the student's address. The student's address ends up in the Reply-To >>> field, which normally wouldn't be a problem except sometimes automated >>> systems reply back to the drop off e-mails and they ignore the Reply-To. >>> >>> I have SMTPsetFromToSender => TRUE, users that login via LDAP or AD >>> appear to work as expected. >>> >>> BTW I am using the IMAP authentication with Office365 and in order to >>> get it to login correctly I had to change the imap_open line. >>> $mbox = @imap_open('{'.$this->_imapServer.'}INBOX', $uname, $password, >>> OP_READONLY,1,array('DISABLE_AUTHENTICATOR' => 'PLAIN')); >>> >>> So don't know if you want to add this to the documentation somewhere or >>> incorporate into the NSSIMAPAuthenticator code. >>> >>> ------------------------------------------------------------------- >>> Travis Zimmerman??? tzimmerman at fsu.edu???? 850-645-8030 >>> Linux Enterprise Applications & Systems its-linuxadmins at fsu.edu >>> Information Technology Services, Florida State University >>> >>> _______________________________________________ >>> ZendTo mailing list >>> ZendTo at zend.to >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__jul.es_mailman_listinfo_zendto&d=DwICAg&c=HPMtquzZjKY31rtkyGRFnQ&r=TZ3x4Nnv5Pp03uwRWF9UlLOaC296m8a1MGVEkWJljsg&m=5u9mHQwWyo_tYTeW__SOzvefpnCjf4YQxPsJSnNZ3t0&s=2lT413dnsMw6bu9-9TLNGGhRMyhC3YK11szRGuK1xtw&e= >>> >> Jules >> > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > https://urldefense.proofpoint.com/v2/url?u=http-3A__jul.es_mailman_listinfo_zendto&d=DwIGaQ&c=HPMtquzZjKY31rtkyGRFnQ&r=TZ3x4Nnv5Pp03uwRWF9UlLOaC296m8a1MGVEkWJljsg&m=nldSAFYLL3YRHIJw6WEEK5gmzqlolpYwjz642dolMxk&s=YAnfXHzTncnerKooAJbUFFL3V98t9jArpAfFUJ5gayo&e=