Simply Fedora if you prefer. I'm using the latest version - 8. I think 9 is in beta right now.HGFB wrote:Fedora Core? It hasn't been called Fedora Core for a while. Which version are you using?
The Official *nix Thread
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
- Dungeon-Dave
- Baaaaaa!

- Posts: 3925
- Joined: Thu Aug 04, 2005 12:01 pm 0
- Location: UK
- Contact:
Re: The Official *nix Thread
No, but they need some authentication mechanism (else everyone else can read other mailboxen).RageMatrix wrote:Does each user need to be a Linux user on the mail server?
I use postfix as my mail server under FC4 (it's dead simple to set up, once you know the basics of mail servers). Mail gets dropped into each user's mailbox in maildir format (was a one-line change to postfix).
This mail is then accessed using IMAP in Thunderbird, rather than POP3, meaning it stays on the mail server rather than gets copied to the mail clients. I used dovecot for this originally, but switched to courier after getting shafted by two updates (an dI couldn't get cyrus to work)
Since my mail is held on the server I can also use squirrelmail (browser-based) to access it remotely, which I couldn't do if it was downloaded locally to one of my other wankstations.
If you want a hand in getting it all worky, give a yell and I can give you some pointers. But you need to tackle several different tasks here, not just the one: get email going out/in of the mail server to tha big world, then get it delivered locally to some mailboxen.
Depending upon your authentication mechanism, you may want to consider what happens when users change their passwords too.
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
Hi Dave,
Perhaps you could just give me a quick overview of what exactly all the bits do? I've got Exim running on port 25 and I've got Courier compiled and installed, although what I'm supposed to do with it now is anyone's guess. I've searched high and low for some sort of "Idiots Guide" on what a mail server is comprised of and how each bit is supposed to work, but the "documentation" - and I use that term laughingly - assumes so much implied knowledge of what I'm supposed ot be doing that I'm a little lost.
Who would have thought something that sounds as simple as a mail server is turning into the hardest thing I've tried to do under Linux?
Perhaps you could just give me a quick overview of what exactly all the bits do? I've got Exim running on port 25 and I've got Courier compiled and installed, although what I'm supposed to do with it now is anyone's guess. I've searched high and low for some sort of "Idiots Guide" on what a mail server is comprised of and how each bit is supposed to work, but the "documentation" - and I use that term laughingly - assumes so much implied knowledge of what I'm supposed ot be doing that I'm a little lost.
Who would have thought something that sounds as simple as a mail server is turning into the hardest thing I've tried to do under Linux?
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
- disciple
- Sheepie Whore

- Posts: 13941
- Joined: Mon Oct 27, 2003 11:33 pm 0
- XBL Gamertag: LiberMentis
- PSN: Prime_Heretic
- Location: Greenfield
- Contact:
Re: The Official *nix Thread
Well from memory, basically you configure Exim so that it stores mboxes in a specified location, then set Courier so it looks for and serves mboxes to clients from that same location. Basically the two just communication which each other via a common shared directory and a common file format.RageMatrix wrote:Hi Dave,
Perhaps you could just give me a quick overview of what exactly all the bits do? I've got Exim running on port 25 and I've got Courier compiled and installed, although what I'm supposed to do with it now is anyone's guess. I've searched high and low for some sort of "Idiots Guide" on what a mail server is comprised of and how each bit is supposed to work, but the "documentation" - and I use that term laughingly - assumes so much implied knowledge of what I'm supposed ot be doing that I'm a little lost.
Who would have thought something that sounds as simple as a mail server is turning into the hardest thing I've tried to do under Linux?
That's the jist of it and yes I remember it being an absolute bugger to figure out and set up, this was like 4 years ago though, it's a bit disappointing to see things haven't got any easier.
PS4 : Prime_Heretic
Steam: bitstorm
Elite Dangerous: Cmdr Britain
Steam: bitstorm
Elite Dangerous: Cmdr Britain
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
So - Exim is the SMTP daemon running on port 25 that receives the mails and Courier (as IMAP or POP3) hands out the mails to a specific mail client (like Outlook) from a specific shared directory that both point to (correct so far)?disciple wrote:Well from memory, basically you configure Exim so that it stores mboxes in a specified location, then set Courier so it looks for and serves mboxes to clients from that same location. Basically the two just communication which each other via a common shared directory and a common file format.RageMatrix wrote:Hi Dave,
Perhaps you could just give me a quick overview of what exactly all the bits do? I've got Exim running on port 25 and I've got Courier compiled and installed, although what I'm supposed to do with it now is anyone's guess. I've searched high and low for some sort of "Idiots Guide" on what a mail server is comprised of and how each bit is supposed to work, but the "documentation" - and I use that term laughingly - assumes so much implied knowledge of what I'm supposed ot be doing that I'm a little lost.
Who would have thought something that sounds as simple as a mail server is turning into the hardest thing I've tried to do under Linux?
That's the jist of it and yes I remember it being an absolute bugger to figure out and set up, this was like 4 years ago though, it's a bit disappointing to see things haven't got any easier.
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Re: The Official *nix Thread
Does anyone use Xubuntu? I have an old PII system @233. It had 256MB RAM and a good Graphics card (GForce2 64MB) and I am thinking to install Xubuntu and use it for light thingies like office apps (Open Office) and internet...
- Dungeon-Dave
- Baaaaaa!

- Posts: 3925
- Joined: Thu Aug 04, 2005 12:01 pm 0
- Location: UK
- Contact:
Re: The Official *nix Thread
Sorry, dude - been away for a bit and missed this post.
Essentially, you're not solving one problem. Setting up the mail server part is simple; it's configuring it to work with several users is the issue, which brings in the other components.
A mail server is responsible for delivery and acceptance of email, what they call a MTA (message transfer agent) over SMTP. Most companies run SMTP software that throws emails back and forth. That's what postfix does for me, and exim for you; essentially emails hitting it either are held for local delivery or forward out to the wibbly wobbly web, depending on the rulesets it has. It helps to think of it as a postman sitting in your office lobby, looking at any letters coming into it and deciding if it needs to be thrown into someone's pigeon-hole or dropped into a sack waiting to be chucked at the post office.
The other bit to content with is how people access their mailboxen. For instance, your ISP will be throwing emails back and forth but any emails intended for their customers drop into a pigeon-hole located at that company. Then you need to access it in some way, for which you have one of two options:
1. POP3 collection - the email is downloaded from your ISP and held locally, what most people do at home.
2. LDAP (IMAP) access - the email is held centrally and someone access it remotely. Think of ISP's webmail systems, gmail, hotmail, etc. No emails are stored locally (on your machine).
The normal Exchange/Outpuke route is to have Outcrock talk to sExchange using their proprietary LDAP protocols, meaning that the mails are stored within Derranged and Doubtlook just provides some view into the mailboxen, amongst other things.
Since you're looking at Exim, the mails intended for local delivery will be dropped into some mailboxes of some format (either mbox spool or Maildir format - I'd recommend the latter) then something will enable LookOut to access these. For this you'll need some POP3/IMAP connector, but you want to decide if the end-users want to POP3-download and store all their emails locally in .PST files (meaning THEY are responsible for backup etc) or they access it remotely over IMAP, meaning mails are held on the server. The latter is a better option for resilience (provided you do data backups on the server), AV scanning, spam-filtering etc but presents headaches in the sense of quota-checking and maintanence - depending on how idiotic can self-centred your end users are. At least with IMAP you have the choice of several other mail clients (Thunderbird, Evolution, Eudora, etc).
When I set up my mail server, I originally set up two accounts (tom and jerry) and tested the following:
1. local delivery: tom can mail jerry (stays local)
2. local delivery: jerry can reply to tom (still stays local)
3. outgoing delivery: tom can email my work account (forwarded out to the interweb)
4. incoming delivery: a mail addressed to jerry from those internets found its way into the right mailbox.
5. alias/virtual/spam rulesets: mail for thomas@ still found its way into tom@, but administrator@ was blocked. Mail originating from a specific domain/bearing a specific subject/containing specific attachment was blocked, etc.
Once I had THAT framework established, I then worked out how to access tom and jerry's boxes remotely, which I used with dovecot originally then progressed to courier-imap. I also set up squirrelmail so that I could access it web-based.
As mentioned earlier, you *really* need to sit down and work out who will be mailing whom, and how, then decide for EVERY action taken how you can present some system to implement the requirements of the system. I think you're trying to start from a technical viewpoint, rather than from a service-provider view.
Footnote: implementing and running a mail server is NOT a simple task. Some people foolishly believe that a few mouse clicks in some sexchange wizard bestows Postmaster Almighty power unto them, and it isn't until several months later their ISP blocks them for appearing on many RBLs for running an open relay do they wise up and understand there's a HELL of a lot more to it. I read up for a good month before I felt ready to let my server go live, and even then I was shitting planets when watching mail logs carefully until I was convinced I'd done it right.
Essentially, you're not solving one problem. Setting up the mail server part is simple; it's configuring it to work with several users is the issue, which brings in the other components.
A mail server is responsible for delivery and acceptance of email, what they call a MTA (message transfer agent) over SMTP. Most companies run SMTP software that throws emails back and forth. That's what postfix does for me, and exim for you; essentially emails hitting it either are held for local delivery or forward out to the wibbly wobbly web, depending on the rulesets it has. It helps to think of it as a postman sitting in your office lobby, looking at any letters coming into it and deciding if it needs to be thrown into someone's pigeon-hole or dropped into a sack waiting to be chucked at the post office.
The other bit to content with is how people access their mailboxen. For instance, your ISP will be throwing emails back and forth but any emails intended for their customers drop into a pigeon-hole located at that company. Then you need to access it in some way, for which you have one of two options:
1. POP3 collection - the email is downloaded from your ISP and held locally, what most people do at home.
2. LDAP (IMAP) access - the email is held centrally and someone access it remotely. Think of ISP's webmail systems, gmail, hotmail, etc. No emails are stored locally (on your machine).
The normal Exchange/Outpuke route is to have Outcrock talk to sExchange using their proprietary LDAP protocols, meaning that the mails are stored within Derranged and Doubtlook just provides some view into the mailboxen, amongst other things.
Since you're looking at Exim, the mails intended for local delivery will be dropped into some mailboxes of some format (either mbox spool or Maildir format - I'd recommend the latter) then something will enable LookOut to access these. For this you'll need some POP3/IMAP connector, but you want to decide if the end-users want to POP3-download and store all their emails locally in .PST files (meaning THEY are responsible for backup etc) or they access it remotely over IMAP, meaning mails are held on the server. The latter is a better option for resilience (provided you do data backups on the server), AV scanning, spam-filtering etc but presents headaches in the sense of quota-checking and maintanence - depending on how idiotic can self-centred your end users are. At least with IMAP you have the choice of several other mail clients (Thunderbird, Evolution, Eudora, etc).
When I set up my mail server, I originally set up two accounts (tom and jerry) and tested the following:
1. local delivery: tom can mail jerry (stays local)
2. local delivery: jerry can reply to tom (still stays local)
3. outgoing delivery: tom can email my work account (forwarded out to the interweb)
4. incoming delivery: a mail addressed to jerry from those internets found its way into the right mailbox.
5. alias/virtual/spam rulesets: mail for thomas@ still found its way into tom@, but administrator@ was blocked. Mail originating from a specific domain/bearing a specific subject/containing specific attachment was blocked, etc.
Once I had THAT framework established, I then worked out how to access tom and jerry's boxes remotely, which I used with dovecot originally then progressed to courier-imap. I also set up squirrelmail so that I could access it web-based.
As mentioned earlier, you *really* need to sit down and work out who will be mailing whom, and how, then decide for EVERY action taken how you can present some system to implement the requirements of the system. I think you're trying to start from a technical viewpoint, rather than from a service-provider view.
Footnote: implementing and running a mail server is NOT a simple task. Some people foolishly believe that a few mouse clicks in some sexchange wizard bestows Postmaster Almighty power unto them, and it isn't until several months later their ISP blocks them for appearing on many RBLs for running an open relay do they wise up and understand there's a HELL of a lot more to it. I read up for a good month before I felt ready to let my server go live, and even then I was shitting planets when watching mail logs carefully until I was convinced I'd done it right.
Re: The Official *nix Thread
What he said.DungeonDave wrote:Implementing and running a mail server is NOT a simple task.
In your case, it's even harder, as you don't want the recipients to have local accounts on the machine. In this case, you need to think about how they are going to authenticate against the mail server to retrieve their mails, and how the mail server is going to know who should receive mail, and who shouldn't.
The first step, as Dave said, is to set up a mail server that accepts and delivers mail for local users, sending outbound mail correctly, accepting inbound mail correctly, and not relaying spam from any tom, dick and harry off the intermanets. That's non-trivial, but do-able. Don't worry about mail pickup or remote access for sending just yet; test, as Dave suggests, using a couple of local users and command line mail clients on the mail server.
Then you need to think about how to handle non-local users. If you have a directory access server (LDAP or what have you) that's already used for authorising and so on for network mounts and the like, then that's the way to go. If not, you can probably get away with something less heavyweight, but it might be worth considering setting up LDAP anyway. Whichever way you go, this is going to be hard to set up.
Once you've got past this hurdle, you have a mail server that's accepting and delivering mail for non-local users, and hopefully still not relaying spam. Now you need to set up remote access for sending mail; this should be done over SSL links, not plain port 25 traffic (this is where having an LDAP server is handy, you can do all the authorisation and so on using PAM, *passwords for network access will be the same as for mail access*, and the setups for all the remote stuff will look remarkably similar)
And finally, you'll want one or both of IMAP and POP3 daemons running, again over secured connections, for those remote users.
Like Dave said, it's really not easy. 'cause now you have to handle security updates for at least 2, and possibly 3 or 4, additional daemons, without breaking mail access for all those users.
Simon
"massive retard™", "full of shit™", "tiny bitch™", "retarted™", "a bit of a one trick pony™", "petty™", "simple minded idealistic twat™", "miserable humourless fucker™"
- Kemper_Boyd
- Sheepie Whore

- Posts: 11967
- Joined: Wed Jul 31, 2002 9:15 pm 0
Re: The Official *nix Thread
I have not used Zimbra but I have read good things about it.
It is an open source, and supported commercial, alternative to
Exchange. It uses all the usual open source components but is
packaged as a single system. You can get a VM image to kick
the tires. I have read people say that they found it a pleasant
alternative to learning the ropes of half a dozen packages when
'solving the email problem' has been dumped into their lap.
http://www.zimbra.com/
It is an open source, and supported commercial, alternative to
Exchange. It uses all the usual open source components but is
packaged as a single system. You can get a VM image to kick
the tires. I have read people say that they found it a pleasant
alternative to learning the ropes of half a dozen packages when
'solving the email problem' has been dumped into their lap.
http://www.zimbra.com/
- stealthbanana
- Baaaaaa!

- Posts: 2805
- Joined: Wed Nov 09, 2005 11:59 pm 0
- Location: Over Here.
Re: The Official *nix Thread
Xubuntu should run happily on that system.manicx wrote:Does anyone use Xubuntu? I have an old PII system @233. It had 256MB RAM and a good Graphics card (GForce2 64MB) and I am thinking to install Xubuntu and use it for light thingies like office apps (Open Office) and internet...
Not long now before lollipop men are called Darren
- WiteWulf
- Sheepie Whore

- Posts: 10125
- Joined: Mon Aug 23, 2004 11:20 am 0
- PSN: WiteWulf
- Location: Loughborough(ish)
Re: The Official *nix Thread
Here's a crontab teaser for you: a colleague of mine wants a script to run at 03:05 on the first Monday of every month but is having great difficulty achieving this.
The closest he's managed to get so far is:
Now I thought this would cause the script to run at 5 minutes past 3 on a Monday (the 1) that falls in the first 7 days (1-7) of any (*) month.
But oh, no...the fields in the crontab are all logically AND'ed except the day of the month and the day of the week which are logically OR'ed for some annoying reason. Consequently the above entry runs every Monday in any month and every day of the first week in every month.
Any bright ideas how I can sort this out?
The closest he's managed to get so far is:
Code: Select all
5 3 1-7 * 1 <script_name>But oh, no...the fields in the crontab are all logically AND'ed except the day of the month and the day of the week which are logically OR'ed for some annoying reason. Consequently the above entry runs every Monday in any month and every day of the first week in every month.
Any bright ideas how I can sort this out?
:::G:::
PSN: WiteWulf
Switch: SW-3941-2878-7584
Steam: WITEWULF66
PSN: WiteWulf
Switch: SW-3941-2878-7584
Steam: WITEWULF66
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
Linux (of any favour) should run happily on that setup. I'm running Fedora 8 on a laptop with barely more power than that and its fine.manicx wrote:Does anyone use Xubuntu? I have an old PII system @233. It had 256MB RAM and a good Graphics card (GForce2 64MB) and I am thinking to install Xubuntu and use it for light thingies like office apps (Open Office) and internet...
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
Ngggh - slowly getting everything sorted out I think. Exim refuses to access the mbox directories and I think I've got Courier-IMAP sorted out. I'm now using Postfix instead for the SMTP. My problems are complicated somewhat by the fact that I've got to use MySQL too to use virtual domains. I've already got local users set up correctly, but now I have to thread all these different parts together (like about five daemons, plus the database) and tie everything together. Tomorrow will be the decider, but I've now got my boss (who knows a hell of a lot more Linux than me) in on the task, documenting what works as we go along. Apparently, when the "big" boss assigned me this, my immediate boss knew I wouldn't be able to do it alone and left me to it for three days just to see if I'd crack, the bastardtufty wrote:What he said.DungeonDave wrote:Implementing and running a mail server is NOT a simple task.
In your case, it's even harder, as you don't want the recipients to have local accounts on the machine. In this case, you need to think about how they are going to authenticate against the mail server to retrieve their mails, and how the mail server is going to know who should receive mail, and who shouldn't.
The first step, as Dave said, is to set up a mail server that accepts and delivers mail for local users, sending outbound mail correctly, accepting inbound mail correctly, and not relaying spam from any tom, dick and harry off the intermanets. That's non-trivial, but do-able. Don't worry about mail pickup or remote access for sending just yet; test, as Dave suggests, using a couple of local users and command line mail clients on the mail server.
Then you need to think about how to handle non-local users. If you have a directory access server (LDAP or what have you) that's already used for authorising and so on for network mounts and the like, then that's the way to go. If not, you can probably get away with something less heavyweight, but it might be worth considering setting up LDAP anyway. Whichever way you go, this is going to be hard to set up.
Once you've got past this hurdle, you have a mail server that's accepting and delivering mail for non-local users, and hopefully still not relaying spam. Now you need to set up remote access for sending mail; this should be done over SSL links, not plain port 25 traffic (this is where having an LDAP server is handy, you can do all the authorisation and so on using PAM, *passwords for network access will be the same as for mail access*, and the setups for all the remote stuff will look remarkably similar)
And finally, you'll want one or both of IMAP and POP3 daemons running, again over secured connections, for those remote users.
Like Dave said, it's really not easy. 'cause now you have to handle security updates for at least 2, and possibly 3 or 4, additional daemons, without breaking mail access for all those users.
Simon
Still think this is just about the hardest thing I've done and I'm leaving work each day at the moment knackered, but I'm expecting to be a better Linux guy after this through trial by fire. Not - I hasten to add - that I'd wish the same situation on anyone else, mind - its a total nightmare!
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
- Dungeon-Dave
- Baaaaaa!

- Posts: 3925
- Joined: Thu Aug 04, 2005 12:01 pm 0
- Location: UK
- Contact:
Re: The Official *nix Thread
Yup.WiteWulf wrote:Any bright ideas how I can sort this out?
Code: Select all
5 3 * * 1 <script_name>The script will run 4 times in the month, but on 3 of them it won't do anything. It's the old "logic OR" problem (one I use on my training courses frequently)
- Wibble
- Baaaaaa!

- Posts: 3317
- Joined: Fri May 02, 2003 10:13 pm 0
- XBL Gamertag: misterwibble
- Location: The Hague - The Netherlands
- Contact:
Re: The Official *nix Thread
Haven't touched Exchange (in a while), have you?Dungeon-Dave wrote:Some people foolishly believe that a few mouse clicks in some sexchange wizard bestows Postmaster Almighty power unto them, and it isn't until several months later their ISP blocks them for appearing on many RBLs for running an open relay do they wise up and understand there's a HELL of a lot more to it. I read up for a good month before I felt ready to let my server go live, and even then I was shitting planets when watching mail logs carefully until I was convinced I'd done it right.
To be honest, anyone with ubuntu or debian can setup a working mail system with only a few commands, with no significant extra security, using exim and courier. It's no more effort than setting up Exchange. It only gets exciting when you want to configure reliable spam filtering.
Wise words from D-D though - You'd think it's common sense to read up on anything and understanding it before installing and configuring
