Hi,
I want to setup a mail server on my LAN. I want to send e-mails from 1 system to another systems.
Please guide me through this process.
Thanks.
Hi,
I want to setup a mail server on my LAN. I want to send e-mails from 1 system to another systems.
Please guide me through this process.
Thanks.
My guess is the reason you have not received any assistance yet is because you have apparently done absolutely nothing to figure it out yourself. A quick google search will provide you with all the information you need. You might want to try that before expecting someone to do your work for you.
here you go!
http://lmgtfy.com/?q=how+to+configure+sendmail+
:-)
Hi all!
I saw the same thingy at linuxquestion's site. This is really not nice guys.
I don't want to let down anybody but the sendmail configuration 1000 pages so it is not just google it and it will work fine at all.
If you google the sendmail configuration it takes 1-2 week to get to 3/4 of the configurations if you don't know anything about it.
I set up a sendmail mail server for my new friend(we didn't know each other before) at Kuala Lumpur because ha asked me to do that and I didn't say any bad thing I just helped him.
Yeah evidently to setup something and to learn something you have to try it first by yourself.
But I think this behavior scaring people to hell does not it?
Anyway krantionline l will do a small sendmail thingy for you as I wanted to.
I just don't have much time right now because I'm moving to an another house.
It is really not a small thing to set it up. Billion different things have to do for the proper configuration.
Laz.
Registered Linux user #405129#
MCP 70-210, 70-290
Intel core 2 quad 2.4Ghz, 4 Gb RAM, ASUS P5K Workstation MB
2 * Seagate Cheetah 15K 147Gb U320_SCSI
DELL PERC 320/DC RAID controller
#########################
# http://opensourcetechnology.co.uk #
#########################
################################
# http://en.wikipedia.org/wiki/Rubik%27s_Cube #
################################
Like this guide yeah: http://tradepricehosting.com/tutorials/sendmail.html
This must be a joke
Registered Linux user #405129#
MCP 70-210, 70-290
Intel core 2 quad 2.4Ghz, 4 Gb RAM, ASUS P5K Workstation MB
2 * Seagate Cheetah 15K 147Gb U320_SCSI
DELL PERC 320/DC RAID controller
#########################
# http://opensourcetechnology.co.uk #
#########################
################################
# http://en.wikipedia.org/wiki/Rubik%27s_Cube #
################################
So: this site is contain everything you need to setup a sendmail. (basic configurations)
https://osuny.co.uk/~azure/txt/sendmail_strategies.txt
Try it first and if you need help let me know.
This is not contain the pop3/imap setup.
Laz.
Registered Linux user #405129#
MCP 70-210, 70-290
Intel core 2 quad 2.4Ghz, 4 Gb RAM, ASUS P5K Workstation MB
2 * Seagate Cheetah 15K 147Gb U320_SCSI
DELL PERC 320/DC RAID controller
#########################
# http://opensourcetechnology.co.uk #
#########################
################################
# http://en.wikipedia.org/wiki/Rubik%27s_Cube #
################################
I know I'm late to this thread - but setting up sendmail is a monster. Sendmail is an ancient mail server that can handle a huge number of users. I'd strongly suggest you switch to postfix which will still handle a few hundred or a thousand account and is much more modern -- 100 times easier to configure.
Am I too late to answer?
http://www.feep.net/sendmail/tutorial/
Hello,
I realize I am 6 years late getting to this dance but this post is a very fine example as to why Linux will never be a major force in the OS game.
Let me set a few parameters.
I am a small business owner looking for economic solutions tor few of my customers needs.
I have no programming skills.
A programmer friend suggested I explore Linux as it and it's applications are vast free and ....wait for it...easy...yes he said easy.
Well I love Linux and yes the most major applications are free and very simple.
But, I need a mail server that will work on a LAN/Intranet with no access to the outside world.
I spent 3 days trying to get Postfix to work but could not find any instructions....YES I Googled.
I finally found a link to this question and upon reading the first response I almost closed the screen but the optimist in me continued reading. Fortunately their are a few educated and understanding experts who are willing to assist novices and others.
So I am now trying to use Citadel instead of Postfix... but once again the instructions are scarce.
I know it is very complicated for us MS zombies to get the feel for Linux and that aggravation tends to lead to surrender.
I wonder if there is a market for a website devoted to MS users who are interested in Linux to get clear and layman terms instructions on how to use Linux and it's complicated applications?
The default sendmail configuration will handle just about everything you want.
And it will handle several thousand users at a time (the largest I ever did was a bit over 1900).
Most small servers do not pass mail to other hosts - that requires a mail server for each host the mail gets forwarded to.
Normally, mail is retrieved from a single server using POP/IMAP programs which are NOT part of sendmail.
The apparent complexity of sendmail is due to the overabundance of people thinking everybody should admire the details of how Email rules and standards are implemented.
None of that is required for a simple mail server.
The basic thing to remember is that sendmail is a MTA (mail transfer agent)- which means it accepts mail on port 25 and routes it to a destination. For a standalone server isolated from the internet, this means only local user accounts will receive mail.
The default configuration makes that destination local user accounts (the files show up in /var/mail or /var/spool/mail, and /var/mail points to /var/spoolmail).
Mail may be read on the server using remote login, or by configuring mail clients (such as thunderbird) to use a pop/imap connection. If pop/imap is to be supported by the server, then the package uw-imap needs to be installed to have the service daemons available (they also need to enabled and started so that systemd will activate them...)
Let me reset a few parameters. You've been mislead by a 'friend' or your own optimism - therefore Linux is at fault; kookie logic that.
Setting up an MTA is never trivial. It involves a lot of decisions about address rewriting and forwarding and network access and authentication and security and virtual accounts that a 'non programmer' (meaning non-technical person) really isn't equipped to address. H*ll - I write kernel code and do Linux ports and work on system security models for a living and I would NEVER suggest that I am genuinely competent to make these sort of sysadmin decisions. I can however muddle through it pretty well.
Not sure WHY you are having so much trouble finding example configs - there are some on this forum. Your google-fu must be inferior.
??? WTF ??? No it's due to the nauseating, ancient and crufty load of M4 macros used for sendmail config. There was a time (in the 1980s) when I though M4 was pretty neat. Then I grew up.The apparent complexity of sendmail is due to the overabundance of people thinking everybody should admire the details of how Email rules and standards are implemented.
There are a lot of MTAs around and for my money postfix is the needs, reasonably modern and decent security out of the box.
My SOHO configs (as patches, editted for security) are ....
My LAN domain is setup as '.localdomain'.Code:--- main.cf.orig 2012-04-20 15:11:41.014795763 -0400 +++ main.cf 2012-04-20 15:59:36.124737447 -0400 @@ -1,3 +1,26 @@ +###+ +mydomain = localdomain +myorigin = $myhostname +inet_interfaces = $myhostname, localhost +###+ (if this is the destination - deliver locally) +mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain, $myhostname.$mydomain +###+ use the virtual address maps +virtual_alias_maps = hash:/etc/postfix/virtual +###+ mynetworks - restrict IPs which can use SMTP +mynetworks = 192.168.1.0/24 127.0.0.0/8 [::1]/128 +###+ (for outbound email) +relayhost = [my.ispmail.com] +###+ (is default) +#alias_maps = hash:/etc/aliases +#alias_database = hash:/etc/aliases +home_mailbox = .Maildir/ +###+ extras +bounce_size_limit = 50000 +header_size_limit = 102400 +mailbox_size_limit = 512000000 +message_size_limit = 40960000 + # Global Postfix configuration file. This file lists only a subset # of all parameters. For the syntax, and for a complete parameter # list, see the postconf(5) manual page (command: "man 5 postconf"). @@ -113,7 +136,7 @@ #inet_interfaces = all #inet_interfaces = $myhostname #inet_interfaces = $myhostname, localhost -inet_interfaces = localhost +#inet_interfaces = localhost # Enable IPv4, and IPv6 if supported inet_protocols = all @@ -161,7 +184,7 @@ # # See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS". # -mydestination = $myhostname, localhost.$mydomain, localhost +#mydestination = $myhostname, localhost.$mydomain, localhost #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain, # mail.$mydomain, www.$mydomain, ftp.$mydomain
Outbound mail goes to my.ispmail.com via smtp.
Note this sets up maildir directories in ~/.Maildir (dovecot or other server needs to know this).
then I add my accounts and email aliases to the end of /etc/postfix/virtual and run
postmap /etc/postfix/virtual #one time.
====
For the dovecot config you need to install the package and then create a self-signed cert.
Code:cd /etc/pki/dovecot openssl genrsa -out ./private/dovecot.pem 1024 openssl req -new -x509 -key ./private/dovecot.pem -out ./certs/dovecot.pem -days 1500 <answer questions> Country Name (2 letter code) [XX]:US State or Province Name (full name) []:Montana Locality Name (eg, city) [Default City]:Soon Organization Name (eg, company) [Default Company Ltd]:Dental Floss Tycoon, LLC Organizational Unit Name (eg, section) []:SOHO Common Name (eg, your name or your servers hostname) []:mail.localdomain Email Address []:stevea@myisp.com
Then you need to create a dovecot config file to direct it to the maildirs ...
Then start the services (postfix & dovecot) and open port 993 for IMAP (with SSL) and port 25 for SMTP.$ cat /etc/dovecot/conf.d/11-local-mail.conf
mail_location=maildir:/home/%u/.Maildir
Last edited by stevea; 3rd May 2012 at 03:51 PM.
stevea - addressing not relevent for offsite. A LAN doesn't need offsite.
And your complaint abount M4 is reasonable, if you had to write the macros yourself.
They are already written.
Unless there is something really confusing, you only need to define the smart host that relays your outgoing mail, you know, the one that has "SMART_HOST". But it usually isn't necessary.
Then you can set your domain header as "MASQUERADE_AS" for outgoing messages...
But then you don't really have to do that either.
raw sendmail configuration files can be a mess, but then mail rules itself are a mess requiring many different rule handling capability, or someone will not be able to receive their mail.
sendmail itself is the most flexible MTA out there. Most others give up when it is something that should be recognized, but is not handled.
It would be nice to have a different preprocessor... Which one would you like? m4 is on nearly everywhere, and doesn't depend on anything else.
Expert systems are always a bit difficult to interpret, and that is all sendmail is.
Right - and it's trivial to change - right ? Or leave it in and use it for outgoing.
So the M4 macros are perfect for all applications and require no changes and no analysis to tell what is going wrong ? Not in my experience and I've setup sendmail a few times, tho' not for years.And your complaint abount M4 is reasonable, if you had to write the macros yourself.
They are already written.
It is flexible, but so is source code. That flexibility means complexity and gory detail and the probability of errors. So it's only accessible to a guru, but you exaggerate the limitations of other MTAs..sendmail itself is the most flexible MTA out there. Most others give up when it is something that should be recognized, but is not handled.
FTFY.It would benicenecessary to have a different preprocessor...
None of the above. The preprocessor concept for a "configuration language" is highly lame. In a modern code package If they included a bail of C source and told you had to tweak it for your config you'd laugh in their faces. But sendmail is doing exactly the same with M4 instead of C. Sheesh - at least C is widely known. No - the correct approach is to create a simple config file with simple syntax and put all the likely-to-be-localized parameters there. If thats not sufficient make a GUI tool generate the config. If I really had to create a language to configure an MTA (highly dubious) then I'd use a functional language like haskell - where the set of declarations are independent and can be tested or even proven consistent. Much clearer than the bucket of nested macros.Which one would you like? m4 is on nearly everywhere, and doesn't depend on anything else.
Fair enough it requires an expert - but the point is ALL that complexity was a design error (legacy) and the sendmail configuration is about as pleasant and modern as toggling a bootstrap in octal through the front panel of a computer. It smells of the 1980s. Like Disco - belongs on the ash-heap of history.Expert systems are always a bit difficult to interpret, and that is all sendmail is.
Last edited by stevea; 4th May 2012 at 07:34 AM.
You evidently have not done much application generation
autoconf does exactly that - it is a preprocessor that generates C header files (frequently, not always) for compilation. No difference. Oh, and it uses m4 as well.
But if you want complexity... try modifying a medium sized autoconf file... the macros expanded can be a real mess.
Haskell may be clearer, but it is much less portable, and less available. You would do better to use python.
But note - your configuration tool is now treating python as a macro preprocessor.... And it doesn't matter if that configuration tool is GUI based or not. And it gets more complicated on each round, because now you also have to maintain your application configuration tool in addition to maintaining the application.
The only advantage m4 really has is that it is nonspecific. It is a small program that doesn't require the application developer to maintain.
The sendmail m4 macros encapsulate the rules for features. Most of them are of the "uncomment if you want the feature" variety, with a few "set the value if you want". One of the reasons for the macros is that optional features can affect other features so that they can be implemented properly.
Yes, the macros can be a pain.
BTW, there was (briefly) a project that could generate the sendmail rules from simplified "if... then" rules. It disappeared within a year. And the rules themselves are nothing more than Markov algorithms, but expressed in a minimal language to reduce the effort at loading the rules - hence a simple preprocessor to generate the configuration file.