RE: [dspace-tech] SMTP over TLS Failed

2020-12-08 Thread Cameron, Jacob 
That should have said TLS 1.0 and 1.1 support.


--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.

From: dspace-tech@googlegroups.com  On Behalf Of 
Cameron, Jacob
Sent: Tuesday, December 8, 2020 8:54 AM
To: Humberto Blanco Castillo ; DSpace Technical Support 

Subject: RE: [dspace-tech] SMTP over TLS Failed

Hello Humberto,

Microsoft has ended TLS 1.0 and TLS 1.2 support for all their mail products.  
You need to ensure you are using TLS 1.2 or higher on your server or the 
messages will fail.


--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.

From: dspace-tech@googlegroups.com 
mailto:dspace-tech@googlegroups.com>> On Behalf 
Of Humberto Blanco Castillo
Sent: Tuesday, December 8, 2020 8:26 AM
To: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: [dspace-tech] SMTP over TLS Failed

Caution: This email was sent from someone outside of the University of 
Lethbridge. Do not click on links or open attachments unless you know they are 
safe. Suspicious emails should be forwarded to 
phish...@uleth.ca.

My dspace server was working with the following configuration

mail.server = outlook.office365.com
mail.server.username = myu...@mydomain.com
mail.server.password = mypassword
mail.server.port = 587
mail.from.address = myu...@mydomain.com
mail.feedback.recipient = ${mail.from.address}
mail.admin = ${mail.from.address}
mail.alert.recipient = ${mail.from.address}
mail.registration.notify = ${mail.from.address}

mail.extraproperties =  mail.smtp.starttls.enable=true, \
mail.smtp.socketFactory.port=587, \
mail.smtp.socketFactory.fallback=false

But a few days ago it stopped working,:

About to send test email:
 - To: myu...@mydomain.com
 - Subject: DSpace test email
 - Server: outlook.office365.com


Error sending email:
 - Error: javax.mail.SendFailedException: Send failure 
(javax.mail.MessagingException: Could not convert socket to TLS 
(javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is 
disabled or cipher suites are inappropriate)))


the only modification its that now we are working with openjdk
openjdk version "1.8.0_272"
OpenJDK Runtime Environment (build 1.8.0_272-b10)
OpenJDK 64-Bit Server VM (build 25.272-b10, mixed mode)


Any knows why of this error, or giveme any ligtha about this?

really appreciate your help



Humberto,


--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/f92ecb2e-d98d-4535-944a-d7b7e1eba897n%40googlegroups.com.
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit

RE: [dspace-tech] SMTP over TLS Failed

2020-12-08 Thread Cameron, Jacob 
Hello Humberto,

Microsoft has ended TLS 1.0 and TLS 1.2 support for all their mail products.  
You need to ensure you are using TLS 1.2 or higher on your server or the 
messages will fail.


--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.

From: dspace-tech@googlegroups.com  On Behalf Of 
Humberto Blanco Castillo
Sent: Tuesday, December 8, 2020 8:26 AM
To: DSpace Technical Support 
Subject: [dspace-tech] SMTP over TLS Failed

Caution: This email was sent from someone outside of the University of 
Lethbridge. Do not click on links or open attachments unless you know they are 
safe. Suspicious emails should be forwarded to 
phish...@uleth.ca.

My dspace server was working with the following configuration

mail.server = outlook.office365.com
mail.server.username = myu...@mydomain.com
mail.server.password = mypassword
mail.server.port = 587
mail.from.address = myu...@mydomain.com
mail.feedback.recipient = ${mail.from.address}
mail.admin = ${mail.from.address}
mail.alert.recipient = ${mail.from.address}
mail.registration.notify = ${mail.from.address}

mail.extraproperties =  mail.smtp.starttls.enable=true, \
mail.smtp.socketFactory.port=587, \
mail.smtp.socketFactory.fallback=false

But a few days ago it stopped working,:

About to send test email:
 - To: myu...@mydomain.com
 - Subject: DSpace test email
 - Server: outlook.office365.com


Error sending email:
 - Error: javax.mail.SendFailedException: Send failure 
(javax.mail.MessagingException: Could not convert socket to TLS 
(javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is 
disabled or cipher suites are inappropriate)))


the only modification its that now we are working with openjdk
openjdk version "1.8.0_272"
OpenJDK Runtime Environment (build 1.8.0_272-b10)
OpenJDK 64-Bit Server VM (build 25.272-b10, mixed mode)


Any knows why of this error, or giveme any ligtha about this?

really appreciate your help



Humberto,


--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/f92ecb2e-d98d-4535-944a-d7b7e1eba897n%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/QB1PR01MB3908DF0263E484EF3720CD0984CD0%40QB1PR01MB3908.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] SMTP over TLS Failed

2020-12-08 Thread Jose Blanco 
Humberto,

I'm not sure, but from googling around I see that "You may get this error
when you are trying to send an e-mail using gmail server in java."

Try making this change:

mail.extraproperties =  mail.smtp.starttls.enable=true, \
mail.smtp.socketFactory.port=587, \
mail.smtp.socketFactory.fallback=false*, \*
*mail.smtp.ssl.trust=smtp.gmail.com
*

I saw this suggestion here:
http://javainfinite.com/error-and-solution/javax-mail-messagingexception-could-not-convert-socket-to-tls/

Maybe it's not the gmail server but the mail server you are using,  so
smtp.gmail.com might need to be *outlook.office365.com
*.

This is really just a guess.

Hope it helps.
-Jose

On Tue, Dec 8, 2020 at 10:25 AM Humberto Blanco Castillo <
hblanc...@gmail.com> wrote:

> My dspace server was working with the following configuration
>
> *mail.server = outlook.office365.com *
> *mail.server.username = myu...@mydomain.com *
> *mail.server.password = mypassword*
> *mail.server.port = 587*
> *mail.from.address = myu...@mydomain.com *
> *mail.feedback.recipient = ${mail.from.address}*
> *mail.admin = ${mail.from.address}*
> *mail.alert.recipient = ${mail.from.address}*
> *mail.registration.notify = ${mail.from.address}*
>
> *mail.extraproperties =  mail.smtp.starttls.enable=true, \*
>
> *mail.smtp.socketFactory.port=587, \*
> *mail.smtp.socketFactory.fallback=false*
>
> But a few days ago it stopped working,:
>
> *About to send test email:*
> * - To: myu...@mydomain.com *
> * - Subject: DSpace test email*
> * - Server: outlook.office365.com *
>
>
> *Error sending email:*
> * - Error: javax.mail.SendFailedException: Send failure
> (javax.mail.MessagingException: Could not convert socket to TLS
> (javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is
> disabled or cipher suites are inappropriate)))*
>
>
> the only modification its that now we are working with openjdk
> *openjdk version "1.8.0_272"*
> *OpenJDK Runtime Environment (build 1.8.0_272-b10)*
> *OpenJDK 64-Bit Server VM (build 25.272-b10, mixed mode)*
>
>
> Any knows why of this error, or giveme any ligtha about this?
>
> really appreciate your help
>
>
>
> Humberto,
>
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/f92ecb2e-d98d-4535-944a-d7b7e1eba897n%40googlegroups.com
> 
> .
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-u3B-t_6L0FV%3DYwuPGOkSK3MRMv_Mi2_BUfDzNK1upe%3Dw%40mail.gmail.com.

[dspace-tech] SMTP over TLS Failed

2020-12-08 Thread Humberto Blanco Castillo 
My dspace server was working with the following configuration

*mail.server = outlook.office365.com*
*mail.server.username = myu...@mydomain.com*
*mail.server.password = mypassword*
*mail.server.port = 587*
*mail.from.address = myu...@mydomain.com*
*mail.feedback.recipient = ${mail.from.address}*
*mail.admin = ${mail.from.address}*
*mail.alert.recipient = ${mail.from.address}*
*mail.registration.notify = ${mail.from.address}*

*mail.extraproperties =  mail.smtp.starttls.enable=true, \*

*mail.smtp.socketFactory.port=587, \*
*mail.smtp.socketFactory.fallback=false*

But a few days ago it stopped working,:

*About to send test email:*
* - To: myu...@mydomain.com*
* - Subject: DSpace test email*
* - Server: outlook.office365.com*


*Error sending email:*
* - Error: javax.mail.SendFailedException: Send failure 
(javax.mail.MessagingException: Could not convert socket to TLS 
(javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is 
disabled or cipher suites are inappropriate)))*


the only modification its that now we are working with openjdk
*openjdk version "1.8.0_272"*
*OpenJDK Runtime Environment (build 1.8.0_272-b10)*
*OpenJDK 64-Bit Server VM (build 25.272-b10, mixed mode)*


Any knows why of this error, or giveme any ligtha about this?

really appreciate your help



Humberto,


-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/f92ecb2e-d98d-4535-944a-d7b7e1eba897n%40googlegroups.com.

Re: [dspace-tech] Recent-submissions homepage error in DSpace 6.3

2020-12-08 Thread Carl A Jones 
Hi Jose,

Thanks, much, for the suggestions. We’ll check those out. 

Carl

> On Dec 7, 2020, at 6:01 PM, Jose Blanco  wrote:
> 
> I remember having this issue, and I think it was a migration that had not 
> run.  You can check your database to make sure you have a table named site:
> 
> => \d site
> Table "public.site"
>  Column | Type | Modifiers 
> +--+---
>  uuid   | uuid | not null
> 
> Indexes:
> "site_pkey" PRIMARY KEY, btree (uuid)
> Foreign-key constraints:
> "site_uuid_fkey" FOREIGN KEY (uuid) REFERENCES dspaceobject(uuid)
> 
> And also, In the config area take a look at this file: hibernate.cfg.xml
> 
> You should have this in the file:
> 
> 
> Hope this helps!
> -Jose
> 
> On Mon, Dec 7, 2020 at 5:11 PM Carl Jones  wrote:
> Hi, 
> 
> We've upgraded from 1.8 to 6.3 a couple of months ago and are experiencing a 
> similar error with the 'Recently Added' list when we try to hit the 'View 
> more' link at the site homepage.  Tim Donohue mentioned this could be because 
> of a missing virtual Site Object that represents our system as a whole.  We 
> get the following Stack Trace (similar to what was reported by Donna Barber 
> back in February of this year):
> 
> Java stacktrace: java.lang.NullPointerException at 
> org.dspace.app.xmlui.aspect.discovery.recentSubmissions.RecentSubmissionTransformer.setMainTitle(RecentSubmissionTransformer.java:154)
>  at 
> org.dspace.app.xmlui.aspect.discovery.recentSubmissions.RecentSubmissionTransformer.addBody(RecentSubmissionTransformer.java:124)
>  at 
> org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:234)
>  at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source) at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:607) at 
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
>  at com.sun.proxy.$Proxy493.startElement(Unknown Source) at 
> org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87) 
> at 
> org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94) 
> at 
> org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251)
>  at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source) at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:607) 
> 
> 
> I followed the suggestion to run 'bin/database info' but as far as I can tell 
> the database update checks all come back as Successful. 
> 
> I'm attaching the stack trace and database info output.
> 
> I was curious if there were any other things I might check before passing 
> this onto our sysadmin for further investigation into what might cause a 
> missing virtual Site object problem?
> 
> Thanks,
> 
> Carl
> On Wednesday, February 19, 2020 at 6:50:34 PM UTC-5 
> donna@canterbury.ac.nz wrote:
> Hi Tim,
> 
>  
> 
> Thanks very much for pointing us in the right direction. We think we’ve now 
> resolved the issue by following the instructions for a post you responded to 
> in 2015.
> 
>  
> 
> The registry update was being ignored, and when I tried to run it separately, 
> we were getting the error:
> 
>  
> 
> Caused by: java.sql.BatchUpdateException: Batch entry 0 update 
> public.bitstreamformatregistry set description=NULL, internal='FALSE', 
> mimetype='application/vnd.openxmlformats-officedocument.wordprocessingml.document',
>  short_description=NULL, support_level=-1 where bitstream_format_id=52 was 
> aborted: ERROR: value too long for type character varying(48) 
> 
>  
> 
> Which led me to your 2015 reply to a post about the change of the 
> bitstreamformatregistry table’s mimetype column switching from 48 to 256 
> characters in DSpace 1.5. We’ve been on DSpace since 1.4, so we’ve obviously 
> been hauling this problem along for a while!
> 
>  
> 
> After altering the column character length on the 5.6 database the registry 
> update task was initially ignored, but this time when we ran 
> [dspace]/bin/dspace database migrate ignored, it completed successfully. We 
> now have an entry in the site table, and the recent submissions are working – 
> yay!
> 
>  
> 
> Hopefully there aren’t any other left-over issues that we haven’t identified, 
> but as far as we can tell, all is well. J
> 
>  
> 
> Thanks again,
> Donna
> 
>  
> 
> From: Tim Donohue  
> Sent: Wednesday, 19 February 2020 9:51 AM
> To: Donna Barber ; DSpace Technical Support 
> 
> Subject: Re: [dspace-tech] Recent-submissions homepage error in DSpace 6.3
> 
>  
> 
> Hi Donna,
> 
> I'd recommend checking that all the Database migrations ran successfully when 
> you upgraded to 6.3.  That error seems to be returning a "null" Site object 
> on the homepage.  The Site object is a virtual object that represents your 
> site as a