How to manage email accounts in centos 6 and roundcube - centos

I have setup roundcube on my centos 6 server. Now want to create a admin panel so I can manage users. I could not found a way to install admin like iredadmin on already running server.
I have courier mail server.
Can any one give a better suggestion.

PostfixAdmin. Perfect solution. :)

Related

Sending out email from Linux VM instances

Old linux user here; but only recently started using Google Cloud solutions to create a few VM instances running CentOS. Works great and have been using them for a few years successfully.
I am adding some new functions and I would like to be able to get emails that normally go to root to be sent to me.
In the past, I simply added a line in /etc/aliases at the end of
root: myemail#gsuitedomain.com
This worked well as most of the boxes that I managed were inside a network where I also controlled the local mail server and could just send through it.
It appears that I need to setup some sort of relay using G-Suite?
Is that the right path?
Also, I really don't want to relay the email. I just want to send it to one of the G-Suite accounts. So, no real relaying needed.
Can someone direct me in the right direction for the easiest path to accomplish this?
Thank you for your help,
Tamer
GCP by default blocks all outbound traffic on port 25 so you have to use different one. You can read about it in more detail in the GCE documentation.
In my opinion you will have to run sendmail, postfix or anything else to send emails out but you have to configure them to some other port than 25.

Need advice for a SMTP server on Windows

I would like to ask for advice about SMTP Servers.
I'd like to setup a small and simple server for a school project for which I need to send (or mock send) emails to a small amount of recipients.
So I need a simple, lightweight and Windows 10 compatible SMTP server.
I've already tried hMailServer but it didn't work, though I don't know why.
It had also messed with my OpenVPN configuration and I needed to reinstall it to have VPN tunelling working again.
Thank you in advance for any piece of advice.

Why iRedMail only works for few hours on my machine on EC2?

I have installed the latest version of iRedMail on my VM on EC2 (ubuntu 14.04) and it works perfectly fine for the first few hours. After that, I can not send and receive any emails from/to my VM. I have already submitted the form to Amazon to remove the the Email limitations.
Any hints/helps is highly appreciated.
I found a filtering rule in the main.cf causes that. I remove the filters and it perfectly worked.

Solution for Multidomain Email?

I'm using a custom root server to handle multiple domains on one IP. The basic OS is Debian and the WWW is done with: Nginx+MariaDB.
Now I'm trying to install any working non MySQL based Email service on it. I've watched several tutorials and googled the whole web for a solution.
My last attempt was to work with Postfix and Dovecot. The emails was kind of identified but getting the error:
<domain.org/info#mail.domain.com> (expanded from <info#domain.org>):
mail for mail.domain.com loops back to myself
Is there a step by step explanation for multidomain mail alias setting that is not running on any MySQL?
Do I need to run my virtual emails on MySQL?
Any Cpanel or Plesk like interface that could handle virtual Email aliases on non MySQL basis?
postfix can use mysql as a backend, but it's not required. Usually you can find tutorials on the net just using the db files.
no, you don't have to.
No idea. I usually do that stuff directly in the files or with a database backend.
This question might be better suited for serverfault, but it's pretty generic as it stands.

Is it possible to use an Amazon EC2 instance as an email server?

I want to be able to run an EC2 instance (CentOS LAMP based) as a mail server and create email addresses for users when they sign up so that they can upload files via email. The emails would be parsed and attached files processed and added to S3 for storage.
Is this feasible?
What mail package would I need for this?
I would like to be able to create email address such as username#uploads.domainname.com
my domainname points to a webserver not on amazon web services so I realise this may not be possible.
where do I start with this, are there any good resources for setting up a mail server on EC2
many thanks
To answer the question, yes it is possible. As paul says, if you require 24x7 and long term then EC2 may be more expensive than some other providers. But it can make sense if you're a startup or if you're doing this to learn more about these topics.
Basic steps would be:
Create a linux EC2 Instance http://docs.amazonwebservices.com/AWSEC2/2008-02-01/GettingStartedGuide/?ref=get-started
Install a mail package http://flurdy.com/docs/postfix/
Change your DNS MX record http://en.wikipedia.org/wiki/MX_record
Amazon has had trouble in the past with blacklisting.. but they're trying to address that. Read here: http://developer.amazonwebservices.com/connect/thread.jspa?threadID=37650
Edit: You could also use a pre-configured CentOS image (combining step 1+2), this one has postfix already installed: http://developer.amazonwebservices.com/connect/entry.jspa?externalID=821
Using EC2 as a mail server does not seem like a good fit to me. You're not using either the "Elastic" or the "Cloud" part of the "Elastic Compute Cloud". You need something that has to be up 24x7, has the same IP all the time, and doesn't need to expand or contract on demand, so a VPS would be a better solution.
It can probably be done with the use of an elastic IP along with the correct configuration of the mail server on the ec2 instance to receive mails.
However, it might be easier to use Google AppEngine. You can forward the messages from username#uploads.domainname.com from your existing mail server to your appspot email address, then process the messages and store the files on S3 with a some appengine code in python. See the appengine documentation on receiving email for more information: http://code.google.com/appengine/docs/python/mail/overview.html