I would like to setup a mail server. Can anybody help?

This is not lazy way out. I have been trying for years, and I have probably read most of the “HowTo’s” in the SuSE/Linux corner of the Internet.
But I still have not had any success.

Firstly, am I in the correct area of the forum? Secondly, let me explain some of the background to my difficulties.

For a “very long” time, I had been using a brilliant (for my purposes) custom setup script from iRedMail. However, support for openSuSE has terminated.
For one reason or another, alternatives have been hard to find. The two that have almost got me were I wish to go are: 1. Run the iRedMail on Ubuntu or use an OS independent mail software. Namely Apache JAMES.

I am now hoping that I can find someone who can talk me through setting up Postfix (and all the attendant auxiliary applications) from within the SuSE environment. What I think I need, is to be able to describe my required scenario, and from that, someone to advise on the work-flow I need to accomplish.

Sorry that this is not a quick “my 'puters broke - how do I fix it” type posting…

Best regards, Martin

What you’re asking is pretty broad because the uses of Postfix range from frontend to backend server with or without an administrative interface and whether you want openSUSE to modify and create the configuration files or write them from scratch yourself.

So in essence what would help is defining your requirements and needs;

  • Will this be a frontend server
  • If so, how many clients?
  • WebUI?
  • Will you require MySQL based user authentication?
  • Will you require LDAP authentication?
  • Spamassassin?
  • Amavis + ClamAV?

Hi
Maybe a free one like Axigen, standalone 100 users 5 calendar users?

I use/recommend Axigen 8.1.0 myself (on openSUSE 13, 13.1), easy setup, ajax web-interface and its working with common e-mail clients like k-mail and evolution.

regards

Hi Miuku,

Yes! I know, that is why it taking me years to fail at it!

So in essence what would help is defining your requirements and needs;

  • Will this be a frontend server
  • If so, how many clients?
  • WebUI?
  • Will you require MySQL based user authentication?
  • Will you require LDAP authentication?
  • Spamassassin?
  • Amavis + ClamAV?

In the order listed above:

  • “frontend server” There we go. First problem: definitions. If this means a server that can be seen by other Internet Mail Servers, then yes. My router will have a Port Forwarding Rule, that will expose port 25 SMTP to anyone that requests it. It must also be seen (ports 25, 587, 110 et al) by local clients.
  • <10
  • Server management only. a’la WebMin / iRedAdmin
  • To be decided, after I understand what the issues/ merits are. I currently do use mySQL (but only because that is provided by iRedMail)
  • As above. I don’t currently use LDAP
  • Some form of spam protection. I currently use graylisting which works a treat.
  • Yes.

I guess that maybe, one way it to start with trying to answer the setup questions in the Yast2 Mail Server setup?

Regards, Martin

I asked those because all of them can be configured via the YAST2 Mail Server plugin and/or editing /etc/sysconfig/mail and /etc/sysconfig/postfix :slight_smile:

With additional tools like postfixadmin you can setup MySQL authentication and virtual users.

Hi Malcolm,

Is Axigen free? I can only see a “Free Trial”?

Regards, Martin

Hi Miuku,

Yes.*** IF you understand*** the context in which the setup questions are being asked. For example, one of the first questions that is asked is “Outgoing mail server”.
Seems simple enough!

But is it the name of the machine on which postfix is running (ie hostname -f)?
Or is it the mail relay agent that my ISP provides ( and I need to use to insure that I don’t get blacklisted because my domain IP keeps changing)?
Or is the name that my mx record resolves to?

And so, on…

Well we can talk about masquerading later?

Regards, Martin

Hi
Don’t really like posting links… :wink:
https://www.axigen.com/mail-server/download/#license=free

You do have to apply for the free license from memory…

On 2014-12-01 20:06, martinprowe wrote:

> In the order listed above:
> - “frontend server” There we go. First problem: definitions. If this
> means a server that can be seen by other Internet Mail Servers, then
> yes. My router will have a Port Forwarding Rule, that will expose port
> 25 SMTP to anyone that requests it. It must also be seen (ports 25, 587,
> 110 et al) by local clients.

By “local clients” I understand that all clients are intranet. It
simplifies things.

> - <10

For only 10 clients you do not need databases. It is a small thing.

> - Server management only. a’la WebMin / iRedAdmin

About that, I dunno.

> - Some form of spam protection. I currently use graylisting which works
> a treat.
> - Yes.

Then amavis, which integrates antispam and antivirus (the antivirus can
be free or proprietary, but it is external; and it can be several of
them). For a finer antispam control, you need spamassassin with bayes
settings.

> I guess that maybe, one way it to start with trying to answer the setup
> questions in the Yast2 Mail Server setup?

Yes, the basic settings do.

I don’t remember if yast configures dovecot or not, and you did not say
if you need pop/imap services for your clients.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Hi to Jontel & Malcolm,

Just a quick update and to say a big thank-you for the AXIGEN tip.

I have downloaded, tested, got the licence key and committed to it! WooHooo… It’s just what I was looking forlol!

Having a bit of “fun” with antivirus - Having solved the Axigen/ClamAV access problems, ClamAV is reporting that it is detecting the EICAR test files but not quarantining them. But I guess that that’s a CalmAV issue? I’ll move on to solving that next (I hope!).

Once again. Thank you…

Regards, Martin