Hello all
I am attempting to configure an OJS install (2.4.6) on an Amazon Web Services EC-2 instance. Everything (that I have tried so far, which is most of the OJS functionality) is working fine, but I do not seem to be able to send emails from within OJS.
I am using Amazon SES service, attempting to use their SMTP interface.
I have followed all the required steps from the AWS side to configure SES. Including obtaining SMTP credentials. I have confirmed the email address that I am attempting to send to (it is my own address), and the commandline AWS SES tool can successfully send to it. I know that I am in the SES sandbox at the moment, but the address should still work.
When it comes to configuring OJS, I have the following in my config.inc.php file
; Use SMTP for sending mail instead of mail() smtp = On
; SMTP server settings smtp_server = email-smtp.us-west-2.amazonaws.com smtp_port = 465 {according to AWS documentation, this port for TLS
; Enable SMTP authentication ; Supported mechanisms: tls, ssl smtp_auth = tls smtp_username = xxxxxx_obfuscated smtp_password = xxxxxx_obfuscated ; Allow envelope sender to be specified ; (may not be possible with some server configurations) allow_envelope_sender = On
; Default envelope sender to use if none is specified elsewhere ; default_envelope_sender = my_address@my_host.com
; Force the default envelope sender (if present) ; This is useful if setting up a site-wide noreply address ; The reply-to field will be set with the reply-to or from address. ; force_default_envelope_sender = Off
; Enable attachments in the various "Send Email" pages. ; (Disabling here will not disable attachments on features that ; require them, e.g. attachment-based reviews) enable_attachments = On
I have also tried port 25 for the SMTP server, and ssl rather than tls for authentication method, with no luck.
Any recommendations on what I may need to do to make this connection work?
(As a side note, the reason I am doing this on AWS is so I can demonstrate functionality to a select group of members of my academic society’s board before we invest in a server/colocation costs. I’m not necessarily planning to leave the journal on AWS, but at the same time would like to have that option. I know that to do that we would need to apply to come out of the AWS sandbox, but at the moment it should be working within the sandbox with the addresses I have verified.)
Thanks in advance
Craig.