SuSE 10 When setting up e-mail handling in YaST > Network Services, the dialog includes a setting for handing off mail to Cyrus IMAP. Actually, on my system, Cyrus was in a scrollable pick-list... with one member... implying that the mail could potentially be handed to other types of server or app. My question is why is Cyrus the only choice? I've got nothing against Cyrus, I just wonder why a pick-list would not have a few other choices (especially since I basically took the "install almost everything" option when installing SuSE 10). The question is further reinforced by the fact that I didn't have Cyrus-IMAP installed. Furthermore, when Cyrus-IMAP was left as the choice and the dialog confirmed, YaST did not bother to point out that Cyrus was not installed. Furthermore, furthermore, when I later used YaST to install Cyrus, the first thing that it did was indicate a collision with existing imap and require me to un-install regular old imap in order to cleanly install Cyrus-IMAP. So, if regular old imap was already installed, why wasn't it given as one of the options when YaST was configuring the mail flow? What would make a mail server/handler eligible to be included in the selection when fetchmail and sendmail or whatever are being configured? Or is that an example of "product placement"? :-) Kevin (curious about how/why this stuff works) The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it.
mlist@safenet-inc.com wrote:
SuSE 10 When setting up e-mail handling in YaST > Network Services, the dialog includes a setting for handing off mail to Cyrus IMAP. Actually, on my system, Cyrus was in a scrollable pick-list... with one member... implying that the mail could potentially be handed to other types of server or app.
My question is why is Cyrus the only choice? I've got nothing against Cyrus, I just wonder why a pick-list would not have a few other choices (especially since I basically took the "install almost everything" option when installing SuSE 10).
The question is further reinforced by the fact that I didn't have Cyrus-IMAP installed.
Furthermore, when Cyrus-IMAP was left as the choice and the dialog confirmed, YaST did not bother to point out that Cyrus was not installed.
Furthermore, furthermore, when I later used YaST to install Cyrus, the first thing that it did was indicate a collision with existing imap and require me to un-install regular old imap in order to cleanly install Cyrus-IMAP. So, if regular old imap was already installed, why wasn't it given as one of the options when YaST was configuring the mail flow? What would make a mail server/handler eligible to be included in the selection when fetchmail and sendmail or whatever are being configured? Or is that an example of "product placement"? :-)
Kevin (curious about how/why this stuff works)
The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it.
I'm not the expert on this, but those options allow you to change the normal output of postfix. The default is to /var/spool/mail. That is where uw-imap (the regular imap) and others work from. The options in yast allow you to change the output from that to other places, Cyrus uses, at least in Suse /var/spool/imap. I haven't look in there in a while, but other options are for procmail for example. This is a funcitonality option, definately not "product placement". Jim
Several Cyrus-imap HowTos, as well as HowTos for other apps make reference to "fully qualified hostname" and "fully qualified domain". How do you manage that if your home network does not include a DNS server? I've got a few machines behind a LinkSys router, which is taking care of NAT. The ISP does DNS of course, but it doesn't see inside my little network. So, does this imply that I shouldn't try to run Cyrus-imap if I don't have my own DNS server, or that I need to trick the program in some way? If so, how? While I was going through the MTA dialog in YaST, I don't remember seeing a setting for that. In the DNS and Hostname dialog, there was a field for "Domain", and I just made up a name to fill in. Is that "legal"? Or am I going to encounter grief later, when the bogus domain conflicts with something, or fails to be resolved (because there's no DNS server...)? Kevin (who just doesn't know how much of this stuff can be lies and impromptu bullshit and still work....)
elefino wrote:
Several Cyrus-imap HowTos, as well as HowTos for other apps make reference to "fully qualified hostname" and "fully qualified domain".
How do you manage that if your home network does not include a DNS server? I've got a few machines behind a LinkSys router, which is taking care of NAT. The ISP does DNS of course, but it doesn't see inside my little network.
So, does this imply that I shouldn't try to run Cyrus-imap if I don't have my own DNS server, or that I need to trick the program in some way? If so, how?
Why don't you describe why you want to set up an imap server and what you wish to achieve? Within your own network you can set up whatever you like. Hostname resolution is also possible via /etc/hosts, though you have to copy that file to each hosts in your network.
While I was going through the MTA dialog in YaST, I don't remember seeing a setting for that. In the DNS and Hostname dialog, there was a field for "Domain", and I just made up a name to fill in. Is that "legal"? Or am I going to encounter grief later, when the bogus domain conflicts with something, or fails to be resolved (because there's no DNS server...)?
There are problems, that might arise, though most of them will not plague you if you do not communicate with regular servers on the internet. For example if you want to send mail to a server outside your network and you use an account with a fantasy domain that only exists inside your private network, you have to rewrite that address to one that is routable for external servers. If you want to set up your own mail/imap server please be prepared to learn a LOT about networking, this will not be done in a month or two! Sandy PS: Just to be sure, you do plan to make backups, right?!? Just my pet peeve... -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
On Thursday 19 January 2006 14:32, mlist@safenet-inc.com wrote:
SuSE 10 When setting up e-mail handling in YaST > Network Services, the dialog includes a setting for handing off mail to Cyrus IMAP. Actually, on my system, Cyrus was in a scrollable pick-list... with one member... implying that the mail could potentially be handed to other types of server or app.
My question is why is Cyrus the only choice? I've got nothing against Cyrus, I just wonder why a pick-list would not have a few other choices (especially since I basically took the "install almost everything" option when installing SuSE 10).
[snip] This list is not meant to give you a choice of servers to use, but a choice of ways to deliver mail to mail boxes or directories. As Jim F. says also in reply, Cyrus works differently from other imap servers, using its own file system (placed under /var/spool/imap here). So it has to have its own entry in the list. The other two entries on the list cover everything else - whether uw-imap or courier-imap (or maybe dovecote) or whatever. Any of them should work fine with procmail, for example. A procmail entry in this little list also can mean "everything else except for Cyrus". Cyrus won't work with procmail, I believe. In fact it has its own procmail-like filtering system called sieve. :) Fish
Mark Crean wrote:
On Thursday 19 January 2006 14:32, mlist@safenet-inc.com wrote:
SuSE 10 When setting up e-mail handling in YaST > Network Services, the dialog includes a setting for handing off mail to Cyrus IMAP. Actually, on my system, Cyrus was in a scrollable pick-list... with one member... implying that the mail could potentially be handed to other types of server or app.
My question is why is Cyrus the only choice? I've got nothing against Cyrus, I just wonder why a pick-list would not have a few other choices (especially since I basically took the "install almost everything" option when installing SuSE 10).
[snip]
This list is not meant to give you a choice of servers to use, but a choice of ways to deliver mail to mail boxes or directories.
As Jim F. says also in reply, Cyrus works differently from other imap servers, using its own file system (placed under /var/spool/imap here). So it has to have its own entry in the list. The other two entries on the list cover everything else - whether uw-imap or courier-imap (or maybe dovecote) or whatever. Any of them should work fine with procmail, for example. A procmail entry in this little list also can mean "everything else except for Cyrus". Cyrus won't work with procmail, I believe. In fact it has its own procmail-like filtering system called sieve.
Not entirely correct. Procmail can be configured as the standard mailbox transport, and within procmail the local delivery agent "deliver" from the cyrus packages can be executed for final delivery to Cyrus. Though I have to agree that sieve is a bit easier to configure but also not as generic and powerful as procmail. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
participants (5)
-
elefino -
Jim Flanagan -
Mark Crean -
mlist＠safenet-inc.com -
Sandy Drobic