Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Installation and Upgrades / Re: freshclam is outdated
« on: July 09, 2008, 08:12:52 pm »
you could always do what I did, go to /var/run/clamav and see if the .pid file is there, not very high tech, but if you update clamav, you will have to check the pid file manually until the GUI gets fixed.
2
Installation and Upgrades / Re: freshclam is outdated
« on: July 09, 2008, 03:40:38 pm »
Tricky one this, it is not just freshclam thats out of date, all of clamav is. You can update it, but if you are using squid and dansguardian these will be removed 
and the summary page will show antivirus as not running when plainly it is.
If after reading this, you still want to upgrade, do an internet search for the clamav website, all the info is on there.
and the summary page will show antivirus as not running when plainly it is.If after reading this, you still want to upgrade, do an internet search for the clamav website, all the info is on there.
3
Installation and Upgrades / Re: Allowing email server outside LAN
« on: July 09, 2008, 03:34:22 pm »
As I said, we use Mdaemon at the moment running on windoze. We run an internal workgroup and two virtual domains, neither of which has any connection with the workgroup. The mail is collected from two multidrop boxes at our isp and Mdaemon sorts it into user mailboxes ready for collection.
The way users are added (and on just about every other mailserver I have looked at) is this:
You first create the mail domain and then add the users to this.
a@foo.org and a@bar.org could be the same person, but the emails never get mixed.
The user downloads the mail with a client (outlook, thunderbird, whatever) and the mail would then end up in separate folders, if you get my drift.
The virtual users would not have any other contact with the server other than for downloading mail, unless they were also setup (completely separately) as fileusers.
As I said, this is virtually standard practise, your way of doing things, seems to be:
1) create maildomains
2) create user
3) add user to foo.org, i.e. a@foo.org
4) create alias a@bar.org to a@foo.org
This to me, would mix all the mail into a@foo.org, and would not work for us.
The way users are added (and on just about every other mailserver I have looked at) is this:
You first create the mail domain and then add the users to this.
a@foo.org and a@bar.org could be the same person, but the emails never get mixed.
The user downloads the mail with a client (outlook, thunderbird, whatever) and the mail would then end up in separate folders, if you get my drift.
The virtual users would not have any other contact with the server other than for downloading mail, unless they were also setup (completely separately) as fileusers.
As I said, this is virtually standard practise, your way of doing things, seems to be:
1) create maildomains
2) create user
3) add user to foo.org, i.e. a@foo.org
4) create alias a@bar.org to a@foo.org
This to me, would mix all the mail into a@foo.org, and would not work for us.
4
Installation and Upgrades / Re: Allowing email server outside LAN
« on: July 07, 2008, 01:58:18 pm »
Yes, I will hold my hand up, I got it wrong 
an ebox user cannot log into the server, but the email user still needs to be an ebox user first. A better way would be to create email domains first, then add users to this. The reason I am investigating email servers is because we run Mdaemon at present with two domains and have maxed out on users. Several users have email addresses in both domains and want to use the same username in both domains and when one of them is the boss, I am not going to argue with him. We also need to add another domain, with the present ebox setup it would seem you can have one email address and aliases for this but not as I need, separate domains with the same users, unless I am missing something.
an ebox user cannot log into the server, but the email user still needs to be an ebox user first. A better way would be to create email domains first, then add users to this. The reason I am investigating email servers is because we run Mdaemon at present with two domains and have maxed out on users. Several users have email addresses in both domains and want to use the same username in both domains and when one of them is the boss, I am not going to argue with him. We also need to add another domain, with the present ebox setup it would seem you can have one email address and aliases for this but not as I need, separate domains with the same users, unless I am missing something.
5
Installation and Upgrades / Re: Allowing email server outside LAN
« on: July 07, 2008, 12:22:59 pm »Quote
I'm not following you here. You would like to have a user with a mail account in a virtual domain and you want this user to only use the mail system and nothing else?
What is a 'virtual user'? by the very name this is a user that does not actually exist on the server, but is a mail user. By the way ebox is setup, every mail user will have to be an ebox user as well and will take up space on the server. If you are not sure what I am getting at, think about an isp, they give their users email addresses but not access to any other part of the server because they are all 'Virtual Users', they cannot login to the server because they are not Unix users.
As for the 'wisp' guy, you probably would be better off using Smoothwall with 3 network cards, one to connect to the network, one as a 'DMZ' connected to your wireless and the other to connect to your network. Set Smoothwall up to allow only the ports open you require, this will also do DHCP and VPN and allow you to set up a webserver and/or mailserver on your network.
6
Installation and Upgrades / Re: Allowing email server outside LAN
« on: July 06, 2008, 01:14:44 am »
Ah right, you just want to collect your mail from your isp, thats easy, turn off your ebox and connect through your router, once you are sure that everything works, reconnect your ebox, restart and then turn off dns, the mailserver etc open the required ports on the firewall and you should be good to go. But if all you want is a fileserver, dhcp and a firewall, use dhcp from router and just install samba and some form of iptables gui, but it sounds to me you do not need anything like ebox, you just need an old computer running smoothwall ( believe me for a firewall, it is better than ebox) and a fileserver running samba, you will find these a lot more configurable from the CLI .
I repeat these are my opinions and I have removed ebox from my test server as I think it is trying to do too much and non of it brilliantly, for instance, virtual domains, anybody care to tell me how you set up a virtual user without making him/her an actual ebox user?
I repeat these are my opinions and I have removed ebox from my test server as I think it is trying to do too much and non of it brilliantly, for instance, virtual domains, anybody care to tell me how you set up a virtual user without making him/her an actual ebox user?
7
Installation and Upgrades / Re: Allowing email server outside LAN
« on: July 04, 2008, 07:11:50 pm »
Hi, I was testing ebox and think that I did, what you are trying to do, relay mail through your isp that is.
Firstly, do you have
a) a fixed ip
b) an MX record pointing at that fixed ip
If not you will have to relay through your isp. If you have both you do not need to relay anything.
If you have to relay through your isp, you will manually have to edit /etc/postfix/main.conf, add three lines and then create a password file in /etc/postfix/sasl/. The three lines you add, have to be re added every time you update or if you turn on the mailfilter.
You will also have to install Fetchmail and set this up.
I have, as I said, been testing ebox, and due to the fact that I spent as much time altering things from the command line as from the ebox webpage, I personally at this time cannot recommend ebox for serious use. I will probably get flamed for saying this, but that is my opinion. This opinion may change in the future, if the developers stop trying to get ebox to be the jack-of-all-trades and also stop trying to re-invent the wheel, I repeat, this is my opinion for what it is worth.
Firstly, do you have
a) a fixed ip
b) an MX record pointing at that fixed ip
If not you will have to relay through your isp. If you have both you do not need to relay anything.
If you have to relay through your isp, you will manually have to edit /etc/postfix/main.conf, add three lines and then create a password file in /etc/postfix/sasl/. The three lines you add, have to be re added every time you update or if you turn on the mailfilter.
You will also have to install Fetchmail and set this up.
I have, as I said, been testing ebox, and due to the fact that I spent as much time altering things from the command line as from the ebox webpage, I personally at this time cannot recommend ebox for serious use. I will probably get flamed for saying this, but that is my opinion. This opinion may change in the future, if the developers stop trying to get ebox to be the jack-of-all-trades and also stop trying to re-invent the wheel, I repeat, this is my opinion for what it is worth.
8
Installation and Upgrades / Re: ebox and clamav
« on: July 03, 2008, 04:56:18 pm »
As far as the sasl password is concerned, I think you are getting smtp and smtpd mixed up, now I am no expert, but my understanding is:
smtp is used to send mail, and if you are relaying through another mailserver you need a username and password for there.
smtpd is the receiving part of postfix on your own mailserver and users need a password to connect and receive mail
I cannot be the only person that needs to relay mail through my isp, in fact now I think of it, why does the ebox mailserver (in the way it is set up at present) not rely on the dns module. As far as I can see, without an MX record, most of the mail that a standard ebox server sends out, would either get bounced back or disappear into oblivion due to receiving mailservers not being able to look up the ebox server. To send mail, you either need an MX record pointing to your mailserver or you have to, as I am doing, relay through your isp or similar.
I do not think that you can be serious about ebox overwriting all managed configuration files at start, for if this was to happen, the server would have to be reset every time you rebooted.
smtp is used to send mail, and if you are relaying through another mailserver you need a username and password for there.
smtpd is the receiving part of postfix on your own mailserver and users need a password to connect and receive mail
I cannot be the only person that needs to relay mail through my isp, in fact now I think of it, why does the ebox mailserver (in the way it is set up at present) not rely on the dns module. As far as I can see, without an MX record, most of the mail that a standard ebox server sends out, would either get bounced back or disappear into oblivion due to receiving mailservers not being able to look up the ebox server. To send mail, you either need an MX record pointing to your mailserver or you have to, as I am doing, relay through your isp or similar.
I do not think that you can be serious about ebox overwriting all managed configuration files at start, for if this was to happen, the server would have to be reset every time you rebooted.
9
Installation and Upgrades / Re: ebox and clamav
« on: June 30, 2008, 03:49:15 pm »
So, what you are saying is that there is one postfix main.cf template without a mailfilter and another template with? and if/when the server reboots I will loose the relay host password lines?
If my understanding of this is correct, then this is stupid, all you need to do to add a line, is use the postconf command. This does not remove anything, just adds lines one by one. By all means start with a basic template, use sed to enter the relevant details and then postconf any further lines to it. Want to relay mail through your isp, no problem just use postconf to enter the relevant lines, write a small script to create the passwd files and away you go.
I will now reboot my ebox server and see what happens to the main.cf file.
Well it's not that bad, the alterations survive a reboot, but it still does not help with the original problem, why does ebox wipe out any alterations made to the main.cf file?
If my understanding of this is correct, then this is stupid, all you need to do to add a line, is use the postconf command. This does not remove anything, just adds lines one by one. By all means start with a basic template, use sed to enter the relevant details and then postconf any further lines to it. Want to relay mail through your isp, no problem just use postconf to enter the relevant lines, write a small script to create the passwd files and away you go.
I will now reboot my ebox server and see what happens to the main.cf file.
Well it's not that bad, the alterations survive a reboot, but it still does not help with the original problem, why does ebox wipe out any alterations made to the main.cf file?
10
Installation and Upgrades / ebox and clamav
« on: June 27, 2008, 03:01:05 pm »
I have installed ebox on top of Ubuntu 8.04 server and am trying it out, but have a few problems:
firstly whilst ebox lets you enter a relay host, there does not seem to be a way to set up the user details. You have to manualy edit /etc/postfix/main.cf adding:
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options =
and then creating sasl_passwd, but it gets better, when you then start the mailfilter, the above three lines get removed and you have to enter them again, perhaps just using 'postconf' to insert the required line for the mailfilter would be better?
After setting up Fetchmail and was sure that I could send/receive mail, I found (from the relevant ebox page) that Clamav engine 0.92.1 was out of date and was asked to update it. Now as I sure you know, Ubuntu does not seem to take seriously ( MY OPINION) antivirus software and has no way of keeping up todate with Clamav (unless you know differently, and if so please share), so after a quick Google (they can't touch you for it!) I added the Debian volatile address to sources.list and upgraded to 0.93.1.
This brought its own share of problems, the Clamav database format has changed, sorted this and got Clamav-daemon to start,
but in the process of upgrading Clamav I lost the following three files: dansguardian ebox-squid libclamav3, so it would seem even if I wanted to, I now cannot use squid.
Now we come to final problem that I found (so far), on the summary page I get this:
Mail filter
Status enabled
Filter ebox internal mail filter
Antivirus Stopped
Antispam running
This shows that ebox thinks the antivirus software has stopped, but 'ps -e | grep clamd' gets me this '17448 ? 00:00:02 clamd' this would seem to show that it is running. Can anyone tell my how ebox checks to see if a program is running?
Apart from these small and I am sure easily fixable problems ebox looks great.
firstly whilst ebox lets you enter a relay host, there does not seem to be a way to set up the user details. You have to manualy edit /etc/postfix/main.cf adding:
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options =
and then creating sasl_passwd, but it gets better, when you then start the mailfilter, the above three lines get removed and you have to enter them again, perhaps just using 'postconf' to insert the required line for the mailfilter would be better?
After setting up Fetchmail and was sure that I could send/receive mail, I found (from the relevant ebox page) that Clamav engine 0.92.1 was out of date and was asked to update it. Now as I sure you know, Ubuntu does not seem to take seriously ( MY OPINION) antivirus software and has no way of keeping up todate with Clamav (unless you know differently, and if so please share), so after a quick Google (they can't touch you for it!) I added the Debian volatile address to sources.list and upgraded to 0.93.1.
This brought its own share of problems, the Clamav database format has changed, sorted this and got Clamav-daemon to start,
but in the process of upgrading Clamav I lost the following three files: dansguardian ebox-squid libclamav3, so it would seem even if I wanted to, I now cannot use squid.
Now we come to final problem that I found (so far), on the summary page I get this:
Mail filter
Status enabled
Filter ebox internal mail filter
Antivirus Stopped
Antispam running
This shows that ebox thinks the antivirus software has stopped, but 'ps -e | grep clamd' gets me this '17448 ? 00:00:02 clamd' this would seem to show that it is running. Can anyone tell my how ebox checks to see if a program is running?
Apart from these small and I am sure easily fixable problems ebox looks great.
Pages: [1]