Re: Problem: Qmail and Eudora 4.0
Dileep Agrawal writes: It does not happen with Eudora 3.0. Does Eudora put in stray newlines? Is Yes. Eudora 4.0 is broken. there a fix? Ask Qualcomm. There's a patch on www.qmail.org that makes Qmail equally broken as Eudora, thus letting it tolerate most of Eudora's nonsense. -- Sam
Re: Problem: Qmail and Eudora 4.0
On Mon, 15 Feb 1999, Dileep Agrawal wrote: SMTP server said: 451 put, E=\r\n at the end of Mether, Mtcp, or Msmtp in sendmail.cf if you are using Solaris 2.5 (fixed in 2.5). I cannot accept messages with stray newlines The mention of sendmail.cf might be a hint that the problem is not with qmail. The server giving this response is obviously running sendmail. (It's not even a sendmail problem for that matter. It's an Eudora bug.) It does not happen with Eudora 3.0. Does Eudora put in stray newlines? Is there a fix? I believe there is a fix on the www.eudora.com site. Cheers, Vern --__ _ ___ _ _ \ \ / / __| _ \ \| | Vern Hart \ V /| _|| / .` | [EMAIL PROTECTED] \_/ |___|_|_\_|\_| 10:28pm up 5 day(s), 22:07, 17 users, load average: 0.07, 0.16, 0.17
Re: Can you limit size of outgoing messages?
Stefan Paletta wrote: Dr. Andreas Wehler wrote/schrieb/scribsit: So, can sned and receive be handled separately? Have tcpserver or tcpd set the DATABYTES environment variable for local clients instead of carrying it in /var/qmail/control/databytes. Ahhh, thanks for this tip! Furthermore, the bounced message will go back the whole length to the sender, couldn't it be cut to the error message and perhaps the first few lines? Hmm. Tis is pushed onto my stack, perhaps I'll go into the qmail sources therefore. Thanks. Andreas Wehler -- CAD/CAM straessle GmbHTel.: (+49) 211 - 52740 - 228 Dr.-Ing. Andreas Wehler Fax.: (+49) 211 - 52740 - 280 http://www.cc-straessle.com
Re: Supervise/Cyclog
- Claudio Neves [EMAIL PROTECTED]: | Hello, | | I know this was discussed here already, but I'm getting trouble when giving | svc -h /var/run/qmail . Here is what I've put on my /etc/rc.d/rc.local: | | csh -cf '/usr/local/bin/supervise /var/run/qmail /var/qmail/rc ' | | And I have the following on /var/qmail/rc : | | exec env - PATH="/var/qmail/bin:$PATH" \ | qmail-start ./Maildir/ /usr/local/bin/accustamp \ | | /usr/local/bin/setuser qmaill /usr/local/bin/cyclog -s 1000 -n 10 \ | /var/log/qmail Well I think this is fundamentally flawed: When sh runs a pipeline, it forks a subprocess for each component. Adding exec does not change this fact, so when sh runs ``exec foo | bar'' then the it forks to shells; first subshell runs exec foo, and the other one runs bar (with an implicit exec). Thus supervise ends up controlling not qmail-send in your case, but the waiting shell. | When I give svc -h /var/run/qmail, I got the famous message "alert: | cannot start: qmail-send is already running" everytime on the logs. You just killed the waiting shell, so supervise started a new one. In order to solve this sort of problem, I created a program I call pipe. You could use it to start qmail as follows: Let /var/qmail/rc contain #!/bin/sh exec pipe qmail-start ./Maildir/ /usr/local/bin/accustamp \ '|1+20' /usr/local/bin/setuser qmaill \ /usr/local/bin/cyclog -s 1000 -n 10 /var/log/qmail That '|1+20' is pipe magic. It pipes file descriptors 1 and 2 of one program into file descriptor 0 of the next one. I put pipe up for grabs at URL:http://www.math.ntnu.no/~hanche/prog/pipe/. - Harald
Fastforward refuses to delivery root email
Hi, I've finally switched works email over to qmail and it all works wonderful even virtuals from /etc/aliases using fastforward. For some reason it refuses to delivery mail to root i have an entry in aliases to go to a non-root account. Printforward shows this correct address, i've also tried removing the aliases entry and creating a ~alias/qmail-root but i qmail-default is taken control (with the following |/var/qmail/bin/fastforward -d /etc/aliases.cdb). Here is the log entries: Feb 16 11:02:52 dipsy qmail: 919162972.617328 starting delivery 1: msg 133349 to local [EMAIL PROTECTED] Feb 16 11:02:52 dipsy qmail: 919162972.618218 status: local 1/10 remote 0/20 Feb 16 11:02:52 dipsy qmail: 919162972.642381 delivery 1: deferral: fastforward:_fatal:_unable_to_exec_qq_(#4.3.0)/ I'm trying to sort this out ASAP as all of roots emails is queued locally but not been delivered! Thanks, Chris.
qmail-pop3d is not working asap
hello, is it the proper behavior of qmail-pop3d not to give out mails as soon as they get the user Maildirs? i noticed this behavior when i moved to the Maildir format and to qmail-pop3d. i see the mail files in ~/Maildir/new/ but when i fire up a POP3 client, it says that i don't have any mails! i did the pop3 conversation myself by telneting the port 110 of my mail server and sure enough, it says that no mails :( however after a period of around 3-5 minutes, i get my mails. so it is no question that the pop3 server is working or not. am using home directories over NFS so is this the problem? Thanks in advance! -marlon
Re: qmail-pop3d is not working asap
What line do you have in inetd.conf? Marlon Anthony Abao wrote: hello, is it the proper behavior of qmail-pop3d not to give out mails as soon as they get the user Maildirs? i noticed this behavior when i moved to the Maildir format and to qmail-pop3d. i see the mail files in ~/Maildir/new/ but when i fire up a POP3 client, it says that i don't have any mails! i did the pop3 conversation myself by telneting the port 110 of my mail server and sure enough, it says that no mails :( however after a period of around 3-5 minutes, i get my mails. so it is no question that the pop3 server is working or not. am using home directories over NFS so is this the problem? Thanks in advance! -marlon
Re: Fastforward refuses to delivery root email
Ok let me explain again the problem, fastforward refuses to send email for the root account using the following: 1. Before we installed fastforward it was working fine with a "~alias/.qmail-root" file with this in: "[EMAIL PROTECTED]" 2. After creating "~alias/.qmail-default" with "|/var/qmail/bin/fastforward -d /etc/aliases.cdb" root mail was refused with the error messages below: Feb 16 13:02:20 dipsy qmail: 919170140.142274 status: local 0/10 remote 0/20 Feb 16 13:02:28 dipsy qmail: 919170148.137147 starting delivery 198: msg 133306 to local [EMAIL PROTECTED] Feb 16 13:02:28 dipsy qmail: 919170148.137335 status: local 1/10 remote 0/20 Feb 16 13:02:28 dipsy qmail: 919170148.308531 delivery 198: deferral: fastforward:_fatal:_unable_to_exec_qq_(#4.3.0)/ 3. I've tried deleting the .qmail-root alias and making an entry in /etc/aliases with "root: gavinlew" in but it still refuses to delivery the mail, giving exactly the same errors above. If I do mailq -s I get the following (mailq script from qmHandle off the qmail web page): Messages in local queue: 76 Messages in remote queue: 0 All off the 76 messages as destinded to the root account but are having trouble being delivered. Any help on how to get it working would be greatly appriated. Regards, Chris. Petr Novotny wrote: On Tue, Feb 16, 1999 at 11:06:08AM +, Chris Bond wrote: qmail-local will refuse to run as root, and hence you can NEVER deliver to root under the qmail system. You must alias root to an ordinary user, usually the administator of the machine. Plus, since there certainly IS a user called root, /etc/aliases (or fastforward, which is run from ~alias/.qmail-default) will not be consulted. Am I right? -- Petr Novotny, ANTEK CS [EMAIL PROTECTED] http://www.antek.cz -- Don't you know there ain't no devil there's just God when he's drunk. [Tom Waits]
Re: Fastforward refuses to delivery root email
On Tue, Feb 16, 1999 at 11:06:08AM +, Chris Bond wrote: qmail-local will refuse to run as root, and hence you can NEVER deliver to root under the qmail system. You must alias root to an ordinary user, usually the administator of the machine. The original poster did say that he set up an alias for root. The problem is that qmail does not seem to notice the alias. Of course, the main problem is that he does not give enough details. What is the alias? How is it set up exactly? Is he using qmail-users? Mate
this user has no $HOME/Maildir (fwd)
Hi i set up qmail and it works fine for those who have shell access but not for my users who login through pop server. When they try to login they get the message: "The mail server responded: this user has no $HOME/Maildir Please enter a new password" I read the man page on "Maildir". My question is how do i set up a maildir if it is not set up when i add a new user? If i have to manually set up a "Maildir" and its subdirectories how do i get the messages in the current $HOME/Mailbox file exported into the "Maildir" ? Also what permissions do i set for the "Maildir" and its subdir's ? I noticed this line in my inetd.conf: #off# pop-3 stream tcp nowait root/usr/sbin/tcpd ipop3d Is this correct ? If so how does qmail-pop3d run? I also installed ucspi-tcp and checkpassword to try it that way. I ran the checkpasswd tests from the command line it worked fine and i have qmail-popup and checkpasswd set to run on startup. # /var/qmail/bin/qmail-popup host /bin/checkpassword pwd +OK ...@host user sam +OK pass baker /home/baker It is not a "case" problem. any help would be appreciated. thanks in advance td
need suggestions (pop/imap or what)
Hi. Sorry if this is slightly O/T. I do have qmail installed, so may be relevant. Currently I've got a mixture of users using various clients for reading email. The most popular method is POP3 using qpopper. However, this leaves some users with the inability to change their pop3 password, since it is tied to their unix account login password and they don't know how to log in to change it. Is there a scheme which would provide the users with the ability to change their own password from the client end, using a standard client such as Netscape Messenger, Eudora, Outlook etc? Would IMAP allow this? Thanks in advance for any suggestions. Brian
Re: Fastforward refuses to delivery root email
Hi, Yes it was users a assign file, stupid deb file i create made one i deleted the assign file put a "." in it, ran qmail-newu and then created my ~alias/qmail-root and it all worked nicely Thankyou for the tip that helped be slove it, and to anyone else that posted something that helped me. Regards, Chris Mate Wierdl wrote: Are you using qmail-users? Mate
Re: Qmail for NT
djcroark writes: are there any plans to port Qmail to windows NT??? None. Windows NT handles forking very badly, and qmail needs forking to be cheap. Why not replace NT with a free operating system? I always recommend that people have a separate machine as their email hub anyway, with no user accounts. -- -russ nelson [EMAIL PROTECTED] http://crynwr.com/~nelson Crynwr supports Open Source(tm) Software| PGPok | There is good evidence 521 Pleasant Valley Rd. | +1 315 268 1925 voice | that freedom is the Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | cause of world peace.
Re: Fastforward refuses to delivery root email
- "Petr Novotny" [EMAIL PROTECTED]: | [...] since there certainly IS a user called root, /etc/aliases (or | fastforward, which is run from ~alias/.qmail-default) will not be | consulted. Am I right? No. As far as qmail-getpw is concerned, a user with UID 0 does not exist. Hence the alias user is used instead. Quick demo: ; /var/qmail/bin/qmail-getpw root | tr '\000' :; echo alias:151:151:/var/qmail/alias:-:root: (The original problem in this thread is resolved, but I just wanted to clear up this point.) - Harald
Re: Qmail for NT
- Stefan Paletta [EMAIL PROTECTED]: | I used cygwin32, which emulates a Unix environment quite well. | Surprisingly, the file I had to tweak most, was the Makefile (but since | cygwin32 includes sed...). The rest compiled quite well without any | changes to the C code, IIRC. This was all I could test. qmail needs inode numbers to generate unique message numbers. Does NT have something equivalent to inode numbers? If not, how do you generate unique message numbers? I am not saying it can't be done, only that it may be nontrivial. (Hmm, have a separate server process hand them out on demand?) - Harald
Re: Script Question
- "Matt D. Landry" [EMAIL PROTECTED]: | I'm trying to set up an auto-reply feature for employees that are | out of the office..can I set up a mailing list type script that | allows employees to set an option that they are out of the office | and my script will auto-reply to any messages sent to the employee, | and has anybody done anything like this? It's been done. It's called the vacation program (try man vacation on your system). Beware of home cooking in this area - it is just too easy to create mail loops. Also note that most (all?) versions of the vacation program must be run as ``|preline vacation ...'' from the .qmail file. - Harald
Can anyone see this ?
Can anyone see this post ? I am having problems with pop logins. I followed the faq and nothing is working. Any tips would be appreciated. regards td.
Re: Can anyone see this ?
On Tue, 16 Feb 1999, Tony D'Andrade wrote: Can anyone see this post ? Nope. I am having problems with pop logins. I followed the faq and nothing is working. Any tips would be appreciated. Can you provide some details? Vince. -- == Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com ==
new-user template directory
Hi, I'm installing Qmail. The document INSTALL.maildir has this sentence, "The system administrator can setup Maildir as the default for everybody by creating a maildir in the new-user template directory and replacing ./Mailbox with ./Maildir/ in /var/qmail/rc" My question: where is this 'new-user template directory'? Does it mean /var/qmail/new-user, /var/qmail/users/new-user or /var/qmail/control/new-user, or something else yet again? cheers, Andrew Richards.
RE: new-user template directory
Andrew Richards wrote/schrieb/scribsit: I'm installing Qmail. The document INSTALL.maildir has this sentence, "The system administrator can setup Maildir as the default for everybody by creating a maildir in the new-user template directory and replacing ./Mailbox with ./Maildir/ in /var/qmail/rc" My question: where is this 'new-user template directory'? What OS are you on? How do you normally create new users? If you use a program, read its manpage and search for "skeleton". Do you have a /etc/skel dir? Stefan
[Fwd: qmail]
Hello. I'm having a problem with pop3 authentication using qmail 1.03 on a FreeBSD 3.0 stable system. Hardware is a pII/300 with 192megs ram, a 2gig uw-scsi primary for the OS and system files, and 2 6.5gig uw-scsi drives using vinum for stripping which has maildirs only. smtp works flawlessly so far. Pop3 fails with "-ERR authorization failed". I have checkpassword 0.81 and ucspi-tcp-0.84 installed and running, however being unfamiliar with the checkpassword package, I dont know how it's doing the check. BSD uses a shadow password scheme, however file names are not consistent with other OS's which use similar. Linux/Solaris use passwd/shadow. BSD uses passwd/master.passwd. I will also be needing to use an alternate db for the passwd file when this machine goes production. My dialip users are authenticated on a Solaris 2.6 server using radius. I was planning to use rsync perhaps and keep a copy of the passwd/shadow file from the solaris box on the mail server..in which case I need a copy of checkpasswd compiled on the bsd machine but configured to run with the solaris shadow file. I'm using following command line for pop3 right now, tcpserver -c300 -uXX -gYY 0 pop3 /var/qmail/bin/qmail-popup mail.myisp.com \ /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir Thanks and regards, -- Stephen C. Comoletti Asst. Systems Administrator DELANET, Inc. http://www.delanet.com TEL: (302) 326-5800, FAX: (302) 326-5802
Re: new-user template directory
It is usually /etc/skel. It is *not* a qmail specific concept. Mate
Re: Sorry About - Re: Can anyone see this ?
On Tue, 16 Feb 1999 13:11:30 -0500 (EST),
Tony D'Andrade [EMAIL PROTECTED] wrote:
"The mail server responded:
this user has no $HOME/Maildir
Please enter a new password."
I know the password is correct. I set up $HOME/Maildir with cur/ tmp/
new/ subdirectories and the proper permissions but i still get the same
message.
Did you setup your Maildir with maildirmake? Try to telnet to your
POP-daemon ("telnet localhost 110"), enter USER name -| PASS passw -| and
see what happens.
Did you set your MAIL-variable to $HOME/Maildir/, the complete path should
be given.
Regards
Mirko
--
mailto:[EMAIL PROTECTED] myhome_aka_~:http://sites.inka.de/picard
RedHat=~/rh52_isdn.htmlteles16.3c=~/teles163c/teles163c_contents.html
XL97-Classes ~/vba-classes/
be aware of culture www.uni-karlsruhe.de/~etcetera
Re: Can you limit size of outgoing messages?
On Tue, 16 Feb 1999, Stefan Paletta wrote: Andrzej Szydlo wrote/schrieb/scribsit: How could I assign a value to the DATABYTES variable using tcpd? tcp-env: 10.0.0: setenv=DATABYTES 100 How could I set both RELAYCLIENT and DATABYTES? man tcprules -- cut here -- Any number of variables may be listed: 127.0.0.1:allow,RELAYCLIENT="",TCPLOCALHOST="movie.edu" -- cut here -- Dunno. Stefan -- "Life is much too important to be taken seriously." Thomas Erskine[EMAIL PROTECTED](613) 998-2836
Re: Can you limit size of outgoing messages?
On Tue, 16 Feb 1999, Stefan Paletta wrote: [EMAIL PROTECTED] wrote/schrieb/scribsit: On Tue, 16 Feb 1999, Stefan Paletta wrote: Andrzej Szydlo wrote/schrieb/scribsit: How could I assign a value to the DATABYTES variable using tcpd? tcp-env: 10.0.0: setenv=DATABYTES 100 How could I set both RELAYCLIENT and DATABYTES? man tcprules Andrzej asked about how to do it with tcpd. You're too right. Mea culpa. Try tcp-env: 10.0.0.: setenv DATABYTES 100:setenv RELAYCLIENT "" Stefan -- "Life is much too important to be taken seriously." Thomas Erskine[EMAIL PROTECTED](613) 998-2836
New Dual Mount Copy Holder by Rubbermaid
Amazing new copy holder can be mounted directly on your computer monitor or it can be used freestanding. Unique design is specifically engineered to increase your efficiency while reducing eye strain, stress, and fatigue. Quality Rubbermaid features include adjustable viewing positions, non-glare surface, spring load paper clamp and detachable line guide. Folds flat for easy out-of-the-way storage. This isn't a cheap clip on, but a full platform copy holder. Special internet savings click here http://www.1vm.com/~rcc and save over $20 from comparable models. Sender: Robert Craig Corp. Phone: 1-800-890-7510 Email: [EMAIL PROTECTED] Details: http://www.1vm.com/~rcc Remove: [EMAIL PROTECTED] To be removed from future service notifications reply to: [EMAIL PROTECTED] Emerge Corporate Email System for Windows 95/98/NT. *** Evaluation version *** Copyright (c) 1994-99 EOL Corporation. http://www.earthonline.com/eval
Re: Qmail for NT
Harald Hanche-Olsen wrote/schrieb/scribsit: Does NT have something equivalent to inode numbers? I don't know for sure (FATfs at least hasn't). The question is rather, does cygwin have inode numbers? I just tried (on 95) and "ls -i" reports something reasonable. Stefan
Building Alternative Back-ends to Qmail.
Hi : I downloaded the 1.03 version of the software. I have untarred and have been reading thru the man pages, INTERNALS file and most of the FAQ. I am trying to build an alternative back-end engine to that used by qmail-send - qmail-lspawn - qmail-local The requirement is that incoming messages via smtp or qmail inject be handled initially by qmail- but forwarded onto another daemon (written in Java). This daemon will process the message, check authorization and do any other processing required. The eventual delivery of the message would then be done using the JavaMail Apis. The current thinking is as follows: Please give your comments/input on it. a.) Keep the qmail-send program intact and have it interact just as it does with qmail-lspawn. b.) I am assuming that qmail-lspawn is created once only(from qmail-start.c) - and it interacts with qmail-send on one end. And takes the message and execs qmail-local which handles the eventual dispatch. c.) Modify qmail-lspawn so that it will initialize the Java VM - ONCE only. and build a handle to the object which will communicate with the Java server. Then instead of execing "qmail-local" each time- we would use the java VM handle to dispatch the message to the java server. The advantage of this approach is that multiple execs are not done- so it could be less expensive than "execing" a local process- especially if the local process is initializing the Java Vm machinery each time. The disadvantage is that error handling- and server unavailable contingencies will be handled in the same thread as that of qmail-lspawn (unless we Multi-thread it). I forgot to mention- I have looked at dot-qmail man page and I completely understand that I could invoke a program using it. This program could handle the connection with the Java Server. The advantage of this is that I dont change qmail sources at all! But the disadvantage seems to be that I would loose performance! Please give your input. If others have developed plugins to qmail and can send me some url's, gottcha's and warnings that would be great! Thanks in advance. -Arjun Khanna
file names = inodes : why?
On Tue, 16 Feb 1999, Harald Hanche-Olsen wrote: qmail needs inode numbers to generate unique message numbers. This has come up a few times here (we are running qmail on a good number of machines.) Is the inode just a handy unique number? Or are there file access speed tricks, e.g. opening files directly using inode. I would like it to be more convenient to manage the queue while mail is being delivered... :-) - Ari -- Ari Rubenstein Unix ISA Digex, West Coast 408-873-4256
Re: file names = inodes : why?
At 18:10 16/02/99 -0800, Ari Rubenstein wrote: On Tue, 16 Feb 1999, Harald Hanche-Olsen wrote: qmail needs inode numbers to generate unique message numbers. This has come up a few times here (we are running qmail on a good number of machines.) Is the inode just a handy unique number? Or are there file access speed tricks, e.g. opening files directly using inode. Handy unique filename. Vastly superior to tmpnam() and all the lame variants that go with it. It's not for speed - excepting speed of creating a unique filename. Regards.
qmail Digest 16 Feb 1999 11:00:01 -0000 Issue 553
qmail Digest 16 Feb 1999 11:00:01 - Issue 553 Topics (messages 21994 through 22032): qmail Co-existence Question 21994 by: Patrick Durusau [EMAIL PROTECTED] 21995 by: Peter van Dijk [EMAIL PROTECTED] Can you limit size of outgoing messages? 21996 by: "Dr. Andreas Wehler" [EMAIL PROTECTED] 21997 by: Anand Buddhdev [EMAIL PROTECTED] 21998 by: "Dr. Andreas Wehler" [EMAIL PROTECTED] 22004 by: "Dr. Andreas Wehler" [EMAIL PROTECTED] 22005 by: Eric Dahnke [EMAIL PROTECTED] 22006 by: Stefan Paletta [EMAIL PROTECTED] 22031 by: "Dr. Andreas Wehler" [EMAIL PROTECTED] Deny Spam Mail 21999 by: "Todd Reese" [EMAIL PROTECTED] 22002 by: Russell Nelson [EMAIL PROTECTED] On demand? 22000 by: Florent Guillaume [EMAIL PROTECTED] 22003 by: Peter van Dijk [EMAIL PROTECTED] Permissions - what does qmail demand? 22001 by: Mate Wierdl [EMAIL PROTECTED] Licensing on "libdjb" 22007 by: "Len Budney" [EMAIL PROTECTED] RELAYCLIENT and inetd 22008 by: Eric Dahnke [EMAIL PROTECTED] 22010 by: Russell Nelson [EMAIL PROTECTED] 22011 by: Harald Hanche-Olsen [EMAIL PROTECTED] 22012 by: Stefan Paletta [EMAIL PROTECTED] Maildir/cur ??? 22009 by: Paul Farber [EMAIL PROTECTED] 22013 by: Gerry Boudreaux [EMAIL PROTECTED] 22014 by: Chris Johnson [EMAIL PROTECTED] 22015 by: Jay Soffian [EMAIL PROTECTED] 22020 by: Eric Dahnke [EMAIL PROTECTED] 22022 by: Peter van Dijk [EMAIL PROTECTED] this user has no $HOME/Maildir 22016 by: "Tony D'Andrade" [EMAIL PROTECTED] 22018 by: Glenn [EMAIL PROTECTED] ADV: ALASKAN TRAVEL 22017 by: [EMAIL PROTECTED] POP-Before-SMTP Solution 22019 by: [EMAIL PROTECTED] 22023 by: Peter van Dijk [EMAIL PROTECTED] The ppiamdn annoyance 22021 by: "D. J. Bernstein" [EMAIL PROTECTED] 22025 by: Tim Pierce [EMAIL PROTECTED] 22026 by: Vince Vielhaber [EMAIL PROTECTED] Supervise/Cyclog 22024 by: Claudio Neves [EMAIL PROTECTED] 22032 by: Harald Hanche-Olsen [EMAIL PROTECTED] Qmail, Majordomo, and virtual domains 22027 by: [EMAIL PROTECTED] (John R. Levine) Problem: Qmail and Eudora 4.0 22028 by: Dileep Agrawal [EMAIL PROTECTED] 22029 by: "Sam" [EMAIL PROTECTED] 22030 by: Vern Hart [EMAIL PROTECTED] Administrivia: To subscribe to the digest, e-mail: [EMAIL PROTECTED] To unsubscribe from the digest, e-mail: [EMAIL PROTECTED] To bug my human owner, e-mail: [EMAIL PROTECTED] To post to the list, e-mail: [EMAIL PROTECTED] -- Greetings, I have installed Qmail (1.03) on a Solaris 2.5.1 Sparc box in anticipation of adding the Lyris mailing list software to the server. The Lyris installation notes that: 3) Append the following line to the /var/qmail/control/smtproutes -- changing "lyris.shelby.com" to be whatever the alias was you defined in your DNS entry above. For example: lyris.shelby.com:[127.0.0.1]:26 (I have obtained the necessary A record in the DNS tables and followed other installation steps.) Unfortunately my installation of qmail does not have an smtproutes file in /var/qmail/control nor do I know the equivalent (if any) under Solaris. I contacted Lyris with this question and they replied that they relied upon the qmail discussion group for the co-existence part of the instructions. (The purpose of all this is to have qmail acting as the mail mail program on my Unix box and allow Lyris to obtain mail for the alias also on port 26. I avoid having to use another IP number and it will be cleaner when I set it up on my production server.) Tips or suggestions? Many thanks! Patrick -- Patrick Durusau Information Technology Services Scholars Press [EMAIL PROTECTED] Interim Manager, ITS On Mon, Feb 15, 1999 at 07:53:06AM -0500, Patrick Durusau wrote: Greetings, I have installed Qmail (1.03) on a Solaris 2.5.1 Sparc box in anticipation of adding the Lyris mailing list software to the server. The Lyris installation notes that: 3) Append the following line to the /var/qmail/control/smtproutes -- changing "lyris.shelby.com" to be whatever the alias was you defined in your DNS entry above. For example: lyris.shelby.com:[127.0.0.1]:26 (I have obtained the necessary A record in the DNS tables and followed other installation steps.) Unfortunately my installation of qmail does not have an smtproutes file in /var/qmail/control nor do I know the equivalent (if any) under Solaris. Just create /var/qmail/control/smtproutes then. A default installation does not have it. Solaris or not doesn't make any difference. Greetz, Peter. -- .| Peter van Dijk | mo|VERWEG stoned worden of coden .| [EMAIL PROTECTED] | mo|VERWEG dat is
