New to mailstation and a lot of questions

[mowgli]

Hello guys and girls

I am what others would call a n00b when it comes to NAS and linux, but I have worked as a computer tech, for the last 20 years - on the windows platform.

I am currently running af mail server on a Windows box and using Mdeamon as mail server software.
It's easy to use, and you have full control via a nice gui.

A couple of weeks ago I bought a DS410J and I am pretty happy with it so far.
The only thing I am not using right now is the mailstation package, but I would really like to, but hesitate because I don't feel that I have enough control...
That was a little background info, and now for the questions....

1) How do I set it up to send mails directly to another mail server, with fail over using my ISP's mailserver ? (Doing this in mdaemon)
Kinda fixed see here viewtopic.php?f=132&t=22826#p93285

2) Is there a log file where I can check the mail flow in order to debug problems ?

3) How do I update spamassasin ?

4) What about antivirus ? do I have to rely on the antivirus that is installed on the local computer ?
Well the 410J is too slow to do it, so I have to let the client handle the antivirus part

5) Is it normal that the web mail is loading slow ? I have a 12/2 mbit connection, seems to load pretty slow on the inside too....

6) How do I redirect mail from one of the accounts on the DS to another (My son and Daughter's mail accounts)

7) How can I set the mailstation to use spamhaus and others like it ?

More to come, but the questions above are very important as they are problems that would prevent me from changing to mailstation

Answer would be highly appreciated
/Highboy

[mowgli]

Anybody ?

[mowgli]

Well seems like nobody knows the answers to my questions, so I will keep using my Mail server that runs on a plain windows box.

Bye bye

[yngve0]

Patient. . .
1) viewtopic.php?f=132&t=13848&p=91506&hilit=spamhaus#p91506
2) Search in this forum, i guess you will find something
6) Look in /usr/syno/mailstation/etc/aliases

[mowgli]

Patient. . .
1) viewtopic.php?f=132&t=13848&p=91506&hilit=spamhaus#p91506
2) Search in this forum, i guess you will find something
6) Look in /usr/syno/mailstation/etc/aliases

Sorry for being impatient, but just want to get this up and running - going from windows to Linux, is very frustrating, since there is no gui (wonder why)
1) I have tried that, but my ISP requires authentication, and I have tried to follow instructions found here and other places, without getting it to work (maybe my fault, but can't understand why they don't add this to the existing gui in the mail setup screen. (It seems like I am not alone about this problem)
Have tested the the username and password to the outgoing smtp server with outlook, and it works just fine..
2) Have tried to search for log and debug in the mailstation forum - nothing came out......
6) I will have a look into that....

Thanks for the help so far m8

[yngve0]

but can't understand why they don't add this to the existing gui in the mail setup screen. (It seems like I am not alone about this problem)
Have tested the the username and password to the outgoing smtp server with outlook, and it works just fine..

I agree that the mailstation-GUI is very limited, and I presume that it ment to user less skilled into IMAP/SMTP than you and me. Some "advanced"-section would be pretty welcome. Since there are SMTP-entries (with authentication) under "Warning", I miss a function to use this entries as smarthost for the mailstation aswell. Seems like it is not ment to use the mailstation as relay for outbound mail.

As far as understand, with some basic postfix knowledge, almost everything is possible through CLI. Unfortunately, due to slow access at home I havent tested the mailstation very much. . .

[mowgli]

Okay after a lot of fiddling with the system I got the smart host relay with authentication to work.

I added this to the main.cf located /usr/syno/mailstation/etc

smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/usr/syno/mailstation/etc/sasl_passwd
smtp_sasl_security_options =

Then I created a password file here /usr/syno/mailstation/etc/

cat > sasl_passwd
asmtp.mail.dk username@yousee.dk:mypassword

Pressed Ctrl+D to save the file.

Then I created a DB file by entering the following command (I was in this directory /usr/syno/mailstation/etc/)
../sbin/postmap sasl_passwd

Then I reloaded the postfix settings by entering the following command

../sbin/postfix reload

And that did the trick, my mail server is now relaying outbound mail to mys ISP's mailserver with authentication

That somehow took care of my first question

[Townie]

Most of the info you need is about in the forum in one form or another but hopefully this can point you in the right direction a little bit.
1. You got sorted which is great.

2. You will need to either enable logging in the roundcube config file or install something like syslog-ng through ipkg.
if it's basic logging then enabling the rouncube logging should suffice. Read this thread.
viewtopic.php?f=132&t=20364

3. Whilst the new version of Mailstation does have spamassasin, personally I haven't turned this on. The majority of spam can be blocked with a little tinkering within postfix. Read this post here
viewtopic.php?f=132&t=13721

momo does use a lot of checking, and while there is nothing wrong with that I tend to prefer to use only what is needed. If it ever does become a problem then I would review it and adjust as required. Currently this is all I have within my postfix main.cf;

smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
smtpd_sender_restrictions = reject_unknown_sender_domain
smtpd_sasl_authenticated_header = yes
smtpd_sasl_auth_enable = yes

smtp_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous

Ultimately, spamassassin works no differently than setting these manually, the only difference is that spamassassin can be adjusted to 'learn' what is spam and what is not. Having said that with these settings I can say I haven't received a spam mail in months. They keep coming for sure but get rejected, as the logs testify.

4. ClamAV is available from ipkg.

5. Roundcube can be tweaked a little to improve things, read this thread here.
http://trac.roundcube.net/wiki/Howto_Performance

6. By using the aliases file you can redirect mail to whoever you use. For example, within roundcube you can add many different identities and whichever id you used it will always be relayed back to the main inbox of that user. For example, you have;
admin@mail.domain.tld abuse@mail.domain.tld info@mail.domain.tld . These are set as identities under admin. Within the aliases file you need to relay these aliases to admin like;

abuse:admin
info:admin
another:admin
and.another:admin
and.yet.another:admin


using vi (or nano if you installed it through ipkg) look in;
/usr/syno/mailstation/etc/aliases

Read the information within the config file, it does explain the process quite well.

important note, as stated within the config file itself, always alias 'root' to a real mail account. You should never receive mail as root.
root:admin

You can do this for all users. Once you are finished then run the command
'/usr/syno/mailstation/bin/newaliases'

This will create a database file that postfix can read, and all the mail will now be delivered to the accout as you set up within the aliases file.


7. Refer back to no.3. If you blocking the dodgy hostnames then chances are you will block out the dodgy mails.


Major important point. BACKUP BEFORE EDITING. A simple command like

'cp /path/to/filename /path/to/filename.original'

will create a copy of the file before you do any editing. At worst if you make a complete hash of editing the config files, you can at least copy back from the .original file and start again.

Hope this helps a little.

[mowgli]

Hello

Thanks for the help guys, but this is too much trouble to get at mailserver up and running, so i have decided to continue to user my mdeamon mail server running on a windows box....

We are in the year 2010 but for some reason the linux world sticks to configuration files and not a GUI that everyone can handle..... 0