1

How to serve MailCatcher behind HTTPS and authentication?

view story
linux-howto

http://serverfault.com – I am developing a Ruby on Rails app, and have a staging server. But this staging server isn't sending any emails -- instead, it is discarding them. In order to test our emails being sent, and how those emails looks like (so we can use the staging server for QA), I found MailCatcher. But currently it is focused on development environment, so there isn't support for neither HTTPS or authentication -- and I don't want to expose all MailCatcher emails for everyone. Is there any ways to provide HTTPS and basic authentication through Apache or Nginx? Maybe a reverse proxy? (HowTos)

grtyyu's picture
Submitted by grtyyu on 09/10/2011

Stories similar to How to serve MailCatcher behind HTTPS and authentication?

I'm developing a Rails app which when I run it locally, it's able to send emails through a gmail account via smtp.

When I moved it to my sever (running Nginx), it comes up with the following error for example when I try to create a new user.

Net::SMTPAuthenticationError in UsersController#create

535-5.7.1 Username and Password not accepted.

The nginx.conf file remains the same from when I set

Problem sending newsletter 43 weeks 6 days ago

Hi,

I have a dedicated server for sending emails. When I shot for 100 000 emails, it takes more than a day to send, but sends.

I have a cPanel account whose emails I migrated from another server. The account can receive emails in SquirrelMail but cannot receive emails in Mail.app on OSX. I can test the account with Outlook's test button successfully, though I've not tried to download any emails. The chances are, a brand new account would work correctly.

I've configured Amazon SES and obtained the first level of increased sending rate. So my limits are now 10,000 emails/day, 5 emails/second. My question is: do I need to enforce those rates within my own application (i.e.

Basic HTTP Authentication With Nginx

This tutorial shows how you can use basic HTTP authentication with Nginx to password-protect directories on your server or even a whole website. This is the Nginx equivalent to basic HTTP authentication on Apache with .htaccess/.htpasswd.

I am developing an application against a remote https web service. While developing I need to proxy requests from my local development server (running nginx on ubuntu) to the remote https web server.

I've set up Nginx to handle all my static files else proxy_pass to a Node.js server. It's working fine but I'm having difficulty rewriting the url so that it remove the .html file extension.

Hello everyone,

I'm having a major issue with a new WMH/Plesk instalation on a CentOS server regarding emails.

The problem is as follows:

I have a particular account under of the domains which can send emails just fine. However, when viewing arriving emails with webmail/squirrelmail you can see that there are new emails on the inbox folder.

Is it possible to have the reverse proxy (Apache HTTP 2.2) handle authentication (HTTP Basic) and then still use the container managed security of the Java application server (GlassFish 3.1 or JBoss 7.0.2) for authorization?

I've got GlassFish doing container managed security (both authentication and authorization together) just fine using both declarative and programmatic container security with