Actually both gmail and internal mail servers works as expected with OM To use gmail you need to check your settings against [1] In case of internal mail server configuration depends on server configuration
[1] https://support.google.com/a/answer/176600?hl=en On Wed, 26 Sep 2018 at 18:59, <[email protected]> wrote: > I have tried with gmail first. It did not work. > > 192.168.10.216 is the IP address of my VM on which OpenMeetings setup is > running. So I tried using that IP as mail.smtp.server parameter value > thinking that it might use mail server of the VM.( I read this somewhere > while searching for the solution, so tried it) It still doesn’t work. > > If I get mail server running in another container, then can I use that as > a mail server (considering there is connectivity between 2 containers) in > the configuration? > > > > Best Regards, > > Dhanashree Kulkarni > > > > brown-iposs GmbH > > Friedrich-Breuer-Straße 120 > > 53225 Bonn > > Germany > > > > Fon +49 (0) 228 299 799 80 > > Fax +49 (0) 228 299 799 84 > > mailto:[email protected] <[email protected]> > > www.brown-iposs.eu > > www.facebook.com/browniposs > > www.facebook.com/wimap4g > > > > Directors: Dr. Bernd Schröder, Karsten Schmeling > > Trade register: 14385, Country court Bonn > > VAT-ID: DE814670174 > > > > Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte > Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail > irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und > vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte > Weitergabe dieser Mail ist nicht gestattet. > > > > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and destroy this e-mail. Any > unauthorised copying, disclosure or distribution of the material in this > e-mail is strictly forbidden. > > > > *Von:* Maxim Solodovnik [mailto:[email protected]] > *Gesendet:* Wednesday, September 26, 2018 1:48 PM > *An:* Openmeetings user-list <[email protected]> > *Betreff:* Re: smtp error > > > > This is weird .... > > The issue might be specific to mail server you are using ... > > > > Is this publicly available server? (i.e. gmail) > > If this mail server is installed on your server which one is it? postfix, > exim, some other? > > > > On Wed, 26 Sep 2018 at 14:38, <[email protected]> wrote: > > Yes. mail.smtp.starttls.enable is set to *True* and still the issue > persists. I also tried using 465 and 25. It also gives error. > > > > > > Best Regards, > > Dhanashree Kulkarni > > > > brown-iposs GmbH > > Friedrich-Breuer-Straße 120 > > 53225 Bonn > > Germany > > > > Fon +49 (0) 228 299 799 80 > > Fax +49 (0) 228 299 799 84 > > mailto:[email protected] <[email protected]> > > www.brown-iposs.eu > > www.facebook.com/browniposs > > www.facebook.com/wimap4g > > > > Directors: Dr. Bernd Schröder, Karsten Schmeling > > Trade register: 14385, Country court Bonn > > VAT-ID: DE814670174 > > > > Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte > Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail > irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und > vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte > Weitergabe dieser Mail ist nicht gestattet. > > > > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and destroy this e-mail. Any > unauthorised copying, disclosure or distribution of the material in this > e-mail is strictly forbidden. > > > > *Von:* Maxim Solodovnik [mailto:[email protected]] > *Gesendet:* Wednesday, September 26, 2018 9:35 AM > *An:* Openmeetings user-list <[email protected]> > *Betreff:* Re: smtp error > > > > And the issue is reproducible with TLS enabled? > > > > On Wed, 26 Sep 2018 at 14:23, <[email protected]> wrote: > > I have *enabled* it in the configuration. > > > > Best Regards, > > Dhanashree Kulkarni > > > > brown-iposs GmbH > > Friedrich-Breuer-Straße 120 > > 53225 Bonn > > Germany > > > > Fon +49 (0) 228 299 799 80 > > Fax +49 (0) 228 299 799 84 > > mailto:[email protected] <[email protected]> > > www.brown-iposs.eu > > www.facebook.com/browniposs > > www.facebook.com/wimap4g > > > > Directors: Dr. Bernd Schröder, Karsten Schmeling > > Trade register: 14385, Country court Bonn > > VAT-ID: DE814670174 > > > > Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte > Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail > irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und > vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte > Weitergabe dieser Mail ist nicht gestattet. > > > > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and destroy this e-mail. Any > unauthorised copying, disclosure or distribution of the material in this > e-mail is strictly forbidden. > > > > *Von:* Maxim Solodovnik [mailto:[email protected]] > *Gesendet:* Tuesday, September 25, 2018 4:43 PM > *An:* Openmeetings user-list <[email protected]> > *Betreff:* Re: smtp error > > > > The error reported is "Must issue a STARTTLS command first" > > > > What value do you have for mail.smtp.starttls.enable? > > > > On Tue, 25 Sep 2018 at 20:14, <[email protected]> wrote: > > Hello, > > I am also facing the same issue…. > > In my Administration à Configutation, I have setup: > > > > mail.smtp.server > > 192.168.10.216.nip.io > > mail.smtp.port > > 587 > > mail.smtp.system.email > > [email protected] > > mail.smtp.user > > [email protected] > > mail.smtp.pass > > <password for [email protected]> > > > > > > > > > > where 192.168.10.216.nip.io is the domain I am using for OpenMeetings > inside OpenShift VM. > > > > I am running OpenMeetings as a docker container inside OpenShift PaaS > environment. When I try to send invitation, this is the error I receive: > > com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a STARTTLS > command first. p11-v6sm2705618wrd.74 - gsmtp > > > > at > com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:2358) > > at > com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:1823) > > at > com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1300) > > at javax.mail.Transport.send0(Transport.java:255) > > at javax.mail.Transport.send(Transport.java:124) > > at > org.apache.openmeetings.core.mail.MailHandler.lambda$send$0(MailHandler.java:251) > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > > at java.lang.Thread.run(Thread.java:748) > > > > What am I missing here? > > Thank you. > > > > > > Best Regards, > > Dhanashree Kulkarni > > > > brown-iposs GmbH > > Friedrich-Breuer-Straße 120 > > 53225 Bonn > > Germany > > > > Fon +49 (0) 228 299 799 80 > > Fax +49 (0) 228 299 799 84 > > mailto:[email protected] <[email protected]> > > www.brown-iposs.eu > > www.facebook.com/browniposs > > www.facebook.com/wimap4g > > > > Directors: Dr. Bernd Schröder, Karsten Schmeling > > Trade register: 14385, Country court Bonn > > VAT-ID: DE814670174 > > > > Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte > Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail > irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und > vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte > Weitergabe dieser Mail ist nicht gestattet. > > > > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and destroy this e-mail. Any > unauthorised copying, disclosure or distribution of the material in this > e-mail is strictly forbidden. > > > > > > > -- > > WBR > Maxim aka solomax > > > > > -- > > WBR > Maxim aka solomax > > > > > -- > > WBR > Maxim aka solomax > -- WBR Maxim aka solomax
