This is one of those things I hate about email... tone is not accounted for... I do not mean to say that SuSE Email Server III is a bad product. I just do not want to hear that it is the answer to all of our current problems. If it is the answer to life the universe and everything, should it not be free? But seriously, Many of the people here are trying to help from a more personal level and are not interested in commercial products that cost $1000+ I saw a post looking for a lower cost version of the firewall on a cd software that SuSE sells. I would also be interested in this. I was able to afford Email Server II (for personal use, $300), but I can not afford Email Server III ($1000). Not all of us are businesses. Just users. Help us Help You (didn't I see this in a movie?) Also, along the same lines, pushing SuSE Linus Enterprise Server does not help me either. Just because I have hardware that might fall in that category (Proliant 1850s) does not mean that I am an entrerprise. I very much prefer SuSE Linux over all other OS choices for most of my hardware. Let's just work with what we have rather than paying for all of the latest versions that SuSE would like us to use. Greg S. Johnson gjohnson@frozen.com P.S. Incedently, I do own every version of SuSE professional since 7.0, and I will continue to buy them. Quoting Greg Johnson :

Quoting Michael Hasenstein :

...

Bartydeux wrote: ...

...

I don't understand because Cyrus-Imap should not interfere with POP3

cyrus also provides pop3 access to the main folder of the user (INBOX)

...

...

Does anybody have an answer for that problem?

SuSE EMail Server III:

http://www.suse.com/us/press/press_releases/archive01/emailserver3_test.html

...

Test it online: http://emailserver3.SuSE.de/perl/login.pl?doit=login&lang=EN

Please stop pushing Email Server III. I paid good money for Email Server II and now I am screwed. You do not have a reasonable upgrade path. There is not a reasonable support mechanism for email server II (upgrades and patches). and the software is still full of bugs.

Now, Email Server III costs 3x what I paid for Email server II. With the

upgrade price being the difference (2 more X what I paid). Email server II was already outdated versions of free software, the only thing of value was SuSE Linux Enterprise Server (7.0). The rest was crap. I am still running it, why? It takes a lot of effort to change a mail system that more than you use. As for my investment in Email server II? Shame on me...

Greg gjohnson@frozen.com

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com

Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com

[Don't worry, I'll wrap your long lines for you] * Greg Johnson (gjohnson@frozen.com) [011121 22:27]:

I saw a post looking for a lower cost version of the firewall on a cd software that SuSE sells. I would also be interested in this.

You already have it--Marc's firewall script is available for free. Oh wait, you also want it to run from a CD and have a nice GUI tool to configure it? Well, there are development costs involved. Contray to popular belief, we don't receive tens of millions of dollar in funding from the NSA for building the next-generation unmarked black heliocopters with shady Philipino characters.

I was able to afford Email Server II (for personal use, $300), but I can not afford Email Server III ($1000).

Why on earth would you buy a $300 dollar product for personal email? Apparantly you're upset that we sold it to you; I'm very sorry about that. Please feel free to ask advice....Surely you aren't considering buying the FWCD for your home DSL line?

Not all of us are businesses. Just users. Help us Help You (didn't I see this in a movie?) Also, along the same lines, pushing SuSE Linus Enterprise Server does not help me either. Just because I have hardware that might fall in that category (Proliant 1850s) does not mean that I am an entrerprise.

Who's pushing that on home users? Home users don't normally run things like Oracle or SAP so they probably don't need something that was certified for them. Did I mention that the certification process costs a lot of money?

I very much prefer SuSE Linux over all other OS choices for most of my hardware. Let's just work with what we have rather than paying for all of the latest versions that SuSE would like us to use.

I would like everyone on this list to buy 10 copies of SLES each so that I get a Christmas bonus this year. The guy who posted the original POP/postfix question apparantly doesn't know much about mail servers and didn't include any information in his post that would allow someone to help him (logs, postconf, inetd.conf or xinetd.conf...does he know which one he is running?). There's nothing wrong with that--he could be a Nobel laureate in physics for all I know--but that's who products like the email server III are aimed at.

P.S. Incedently, I do own every version of SuSE professional since 7.0, and I will continue to buy them.

Thank you. -- -ckm

Hello,

I would like everyone on this list to buy 10 copies of SLES each so that I get a Christmas bonus this year. The guy who posted the original POP/postfix question apparantly doesn't know much about mail servers and didn't include any information in his post that would allow someone to help him (logs, postconf, inetd.conf or xinetd.conf...does he know which one he is running?).

Yes I know something about mail server because Postfix is now running but it is not my speciality. There are people yhat know more about e-mail server than I and that's why I send my question to the list, not to launch a debate about "should I buy Email server III or not": it looks too muck like MS policy. If you want me to send you all my logs and config files, OK, just tell me which ones. I am running inetd.conf if you want to know. I did not have time yet to learn xinetd (too much time spent trying to find a manual about cyrus-imap). I solved my problem with mu inability to read my Mailbox. I just changed START_CYRUS="yes" to START_CYRUS="no" in /etc/rc.config because it was the Cyrus implementation that causes problems of password reading (which problem I don't know) even if I typed rccyrus stop. I found where the problem was after making a telnet 110. Thanks again for any good manual (I am not a Nobel laureate bur I read Perl/ipchains/Mysql/Tk/ + the rest ....) Sorry I don't have enough pocket money to buy Email server III. Not easy to convince a majority of MS or Apple users to try Linux when you are the only person to know something (even little) about servers configuration. Alain There's

nothing wrong with that--he could be a Nobel laureate in physics for all I know--but that's who products like the email server III are aimed at.

...

P.S. Incedently, I do own every version of SuSE professional since 7.0, and I will continue to buy them.

Thank you.

Thanks for answering and sorry to disturb you again. I thought that to install an imap server should as easy (I mean not impossible) than installing a pop/smtp server.

Because we read through the docs you can't find, create a full ldap/imap/pop mailserver and ask for money for it we're MS now?

imap/pop is enough and pop is already running with Postfix

My point was that you didn't include any of the information in the first place...what an I supposed to guess?

My problem at the beginning was which info or doc

I saw that...it suggests that maybe you were starting the daemon twice (once from inetd and once from the cyrus init script) but I don't know since I couldn't see the logs or inetd.conf.

Thus there is a cyrus init script. I suppose it is /etc/cyrus.config. I already send it nth times and I supposed nobody could read it (I have personaly trouble interpreting it). # standard standalone server implementation START { # do not delete these entries! mboxlist cmd="ctl_mboxlist -r" deliver cmd="ctl_deliver -r" # this is only necessary if using idled for IMAP IDLE # idled cmd="idled" } # UNIX sockets start with a slash and are put into /var/imap/socket SERVICES { # add or remove based on preferences imap cmd="imapd" listen="imap" prefork=0 # imaps cmd="imapd -s" listen="imaps" prefork=0 pop3 cmd="pop3d" listen="pop3" prefork=0 # pop3s cmd="pop3d -s" listen="pop3s" prefork=0 # sieve cmd="timsieved" listen="sieve" prefork=0 ----- ### Comment: I uncommented imaps, pop3s because it is too early to play with ###SSL. ### Sieve too: for later ----- # at least one LMTP is required for delivery lmtp cmd="lmtpd" listen="lmtp" prefork=0 # lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0 ----- ###Comment: difference between lmtp and lmtpunix? ###I tried to find a manual who could explain me clerly the meaning of prefork. ----- ============================== Here is inetd.conf: I still need to uncomment a few lines (rlogin ...) imap line I uncommented it then recommented it but nothing changed. # See "man 8 inetd" for more information. # # If you make changes to this file, either reboot your machine or send the # inetd a HUP signal with "/sbin/init.d/inetd reload" or by hand: # Do a "ps x" as root and look up the pid of inetd. Then do a # "kill -HUP <pid of inetd>". # The inetd will re-read this file whenever it gets that signal. # # <proto> <flags> <user> <args> # # echo stream tcp nowait root internal # echo dgram udp wait root internal # discard stream tcp nowait root internal # discard dgram udp wait root internal # daytime stream tcp nowait root internal # daytime dgram udp wait root internal # chargen stream tcp nowait root internal # chargen dgram udp wait root internal time stream tcp nowait root internal time dgram udp wait root internal # # These are standard services. # # ftp stream tcp nowait root /usr/sbin/tcpd wu.ftpd -a # ftp stream tcp nowait root /usr/sbin/tcpd proftpd ftp stream tcp nowait root /usr/sbin/tcpd in.ftpd # # If you want telnetd not to "keep-alives" (e.g. if it runs over a ISDN # uplink), add "-n". See 'man telnetd' for more details. telnet stream tcp nowait root /usr/sbin/tcpd in.telnetd # nntp stream tcp nowait news /usr/sbin/tcpd /usr/sbin/leafnode # smtp stream tcp nowait root /usr/sbin/sendmail sendmail -bs # printer stream tcp nowait root /usr/sbin/tcpd /usr/bin/lpd -i # # Shell, login, exec and talk are BSD protocols. # The option "-h" permits ``.rhosts'' files for the superuser. Please look at # man-page of rlogind and rshd to see more configuration possibilities about # .rhosts files. shell stream tcp nowait root /usr/sbin/tcpd in.rshd -L # shell stream tcp nowait root /usr/sbin/tcpd in.rshd -aL # # If you want rlogind not to "keep-alives" (e.g. if it runs over a ISDN # uplink), add "-n". See 'man rlogind' for more details. login stream tcp nowait root /usr/sbin/tcpd in.rlogind # login stream tcp nowait root /usr/sbin/tcpd in.rlogind -a # exec stream tcp nowait root /usr/sbin/tcpd in.rexecd talk dgram udp wait root /usr/sbin/tcpd in.talkd ntalk dgram udp wait root /usr/sbin/tcpd in.talkd # # # Pop et al # # pop2 stream tcp nowait root /usr/sbin/tcpd in.pop2d pop3 stream tcp nowait root /usr/sbin/tcpd /usr/sbin/popper -s # # Imapd - Interactive Mail Access Protocol server # Attention: This service is very insecure # imap stream tcp nowait root /usr/sbin/tcpd imapd # # Comsat - has to do with mail. # # comsat dgram udp wait root /usr/sbin/tcpd in.comsat # # The Internet UUCP service. # # uucp stream tcp nowait uucp /usr/sbin/tcpd /usr/lib/uucp/uucico -l # # Tftp service is provided primarily for booting. Most sites # run this only on machines acting as "boot servers." # # tftp dgram udp wait root /usr/sbin/tcpd in.tftpd -s /tftpboot # bootps dgram udp wait root /usr/sbin/bootpd bootpd -c /tftpboot # # Finger, systat and netstat give out user information which may be # valuable to potential "system crackers." Many sites choose to disable # some or all of these services to improve security. # Try "telnet localhost systat" and "telnet localhost netstat" to see that # information yourself! # # finger stream tcp nowait nobody /usr/sbin/tcpd in.fingerd -w # systat stream tcp nowait nobody /usr/sbin/tcpd /bin/ps -auwwx # netstat stream tcp nowait root /usr/sbin/tcpd /bin/netstat -a # # For man on the fly and ht://dig (full text search) # http-rman stream tcp nowait.10000 nobody /usr/sbin/tcpd /usr/sbin/http-rman # # For XCept4 # # btx stream tcp nowait root /usr/sbin/tcpd /usr/lib/xcept4/bin/ceptd -i/usr/lib/xcept4/etc/init.ceptd -u/usr/lib/xcept4/etc/users.ceptd -l/var/log/log.ceptd # # For rplay daemon # # Old versions of rplay: # rplay dgram udp wait root /usr/sbin/tcpd rplayd -b 8192 -c 60 -s 8192 # New Versions of rplay (>=3.3.0) # rplay dgram udp wait root /usr/sbin/tcpd rplayd -t 30 -c 60 -s 16384 -F0 --inetd # # vbox (Voice Box) # vboxd stream tcp nowait root /usr/sbin/tcpd /usr/sbin/vboxd # # For midinetd # midinet stream tcp nowait root /usr/sbin/tcpd in.midinetd # # swat is the Samba Web Administration Tool # swat stream tcp nowait.400 root /usr/sbin/swat swat # # # amanda backup server with indexing capabilities # amandaidx stream tcp nowait root /usr/lib/amanda/amindexd amindexd # amidxtape stream tcp nowait root /usr/lib/amanda/amidxtaped amidxtaped # # amanda backup client # amanda dgram udp wait amanda /usr/lib/amanda/amandad amandad # # the rsync daemon # rsync stream tcp nowait root /usr/sbin/tcpd /usr/sbin/rsyncd --daemon # # # Mimer database # mimer stream tcp nowait root /opt/mimer/bin/mimtcp mimtcp -l # # CVS pserver (remote acces to your CVS repositories) # Please read the section on security and passwords in the CVS manual, # before you enable this. # cvspserver stream tcp nowait root /usr/sbin/tcpd /usr/bin/cvs --allow-root=/home/cvsroot pserver # # procstatd deamon (cluster software) # procstatd stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/procstatd -i 7885 # # End. ========================================= Here is imapd.conf: Problem: which password check to choose. It is not clear. In /etc/pam.d there is well an imap file. configdirectory: /var/imap partition-default: /var/spool/imap admins: cyrus allowanonymouslogin: no autocreatequota: 10000 reject8bit: no quotawarn: 90 timeout: 30 sasl_pwcheck_method: pam ===========================

...

Sorry I don't have enough pocket money to buy Email server III.

I don't either, but whether your boss spends the money on a "canned" solution (Sendmail has a very nice one, ours, or whatever) or pays you for 20 hours to build one yourself he's still spending the money.

Of course ...

...

Not easy to convince a majority of MS or Apple users to try Linux when you are the only person to know something (even little) about servers configuration.

I don't know about MS, but I don't see how setting up something like this on OSX will be any easier.

I know that it will not be obvious with MacOSX, that's why I prefer SuSE/Linux

Quoting Michael Hasenstein :

Greg Johnson wrote:

...

[a bunch of stupid banter purged (my own)] Linux Enterprise Server (7.0). The rest was crap.

No. The value was that you got a pre-configured, running Cyrus IMAP, OpenLDAP, postfix system. When you do that yourself it will take you between 1-3 days the first time you do it, depending on how much you already know. For $299 we took care of that. If the time you would have to spend to setup a similar configuration be less valuable than that, you would have been better off to assemble everything yourself, that's true. The value is in the package, not in the software, which is indeed all open-source. We did include some web stuff like the vacation or procmail settings, but this is not often needed if one uses an imap mailclient.

You are correct, and that was the value I wanted ang I did get. I was having a bad day and went off on the wrong thing. Sorry. I had just run into several of the annoying items in EM II and I guess I let it out. I guess my gripe is that EM II is not real easy to keep up to date. YOU works well for me, but is not in this version of SLES.

EM III is so much more expensive because it bundles a commercial component that provides most of the UI and all the calendar functionality.

I was not aware of that. That might make it more valuable.

As for the bugs, we use EM II ourselves. Never had any issues. I even used the webinterface from a TV with internet access from a hotel room (resolution 640x480, terrible keyboard). The webinterface does hacve it's issues, agreed. I (personally) consider the most value in EM II and III the combination of user-less system (all are in LDAP) and postfix and Cyrus IMAPD, and those three work together very well right from the start. Try to configure that stuff yourself (I did once as a consulting job. Not too difficult if you're a reasonably good admin, but it takes lots of time).

The userless system is wonderful. I only use the web interface right now. It has many bothersome quirks, but I am getting used to it. EM II does have value for me. I just want to be able to stay up-to-date. If nothing else, it has shown what packages to hook together and how. I will probably overtime recreate much of this on whatever current version of SuSE pro I have running at the time. Thanks, Greg gjohnson@frozen.com