Another question
The user exists and it's a valid shell account, but gives this error: [EMAIL PROTECTED]: Sorry, no mailbox here by that name. (#5.1.1) To learn is a natural pleasure - Aristotle --- Kennie J. Cruz Gutierrez, Student Department of Mathematics, U of Puerto Rico [Mayaguez Campus] Work Phone: (787) 832-4040 x 3798 Email: [EMAIL PROTECTED] Web: http://ece.uprm.edu/~kennie
Re: Another question
At 10:19 17.05.01 +0400, Kennie J. Cruz-Gutierrez wrote: The user exists and it's a valid shell account, but gives this error: [EMAIL PROTECTED]: Are you sure? The user in words r null null t. I know a user root - supervisor in unix. Is it correct defined in the userfile of qmail.? Exits for him a mailbox/maildir? Sorry, no mailbox here by that name. (#5.1.1) Regards, Ruprecht
Re: Another question
Kennie J. Cruz-Gutierrez [EMAIL PROTECTED] wrote: The user exists and it's a valid shell account, but gives this error: [EMAIL PROTECTED]: Sorry, no mailbox here by that name. (#5.1.1) From the manpage of qmail-getpw: qmail-getpw considers an account in /etc/passwd to be a user if (1) the account has a nonzero uid, (2) the account's home directory exists (and is visible to qmail- getpw), and (3) the account owns its home directory. qmail-getpw ignores account names containing uppercase letters. qmail-getpw also assumes that all account names are shorter than 32 characters. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: Another question
Kennie J. Cruz-Gutierrez [EMAIL PROTECTED] wrote: The user exists and it's a valid shell account, but gives this error: [EMAIL PROTECTED]: Sorry, no mailbox here by that name. (#5.1.1) From man qmail-getpw: qmail-getpw considers an account in /etc/passwd to be a user if (1) the account has a nonzero uid, (2) the account's home directory exists (and is visible to qmail- getpw), and (3) the account owns its home directory. qmail-getpw ignores account names containing uppercase letters. qmail-getpw also assumes that all account names are shorter than 32 characters. -Dave
OK, another question...
No one helped me with my original problems, but I think that's because they thought I was a moron... BUT I still have faith... Here's what happens now when I send a message to myself (attached with one of the banned extensions) failure: 192.168.2.26_failed_after_I_sent_the_message./Remote_host_said:_554_mail_ser ver_permanently_rejected_message_(#5.3.0)/ Here's what I have as my 'qmail-queue' in /var/qmail/bin #!/bin/sh exec /var/qmail/bin/qmail-qfilter /var/qmail/bin/deny-filetypes If there's no 'banned' attachment, it goes through okay... and I receive a bounce saying 192.168.2.26 failed after I sent the message. Remote host said: 554 mail server permanently rejected message (#5.3.0) How do I get qmail-filter to add something about having a banned extension... ??? Again, I am using the qmail-qfilter program without using QMAILQUEUE ... Thanks!!!
Re: Another question on mailboxes
"Isaiah Chua" [EMAIL PROTECTED] wrote: I keep getting this error message when trying to send mails to my new qmail server at the office: Hi. This is the qmail-send program at mail.twc-sg.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. [EMAIL PROTECTED]: Sorry, no mailbox here by that name. (#5.1.1) I've already created the Maildir dir in the $HOME for myself. What can be wrong? Your username is isaiah.chua? Do you own Maildir? What Do The Logs Say(tm)? -Dave
Another question on mailboxes
hi folks, I keep getting this error message when trying to send mails to my new qmail server at the office: Hi. This is the qmail-send program at mail.twc-sg.com.I'm afraid I wasn't able to deliver your message to the following addresses.This is a permanent error; I've given up. Sorry it didn't work out.[EMAIL PROTECTED]:Sorry, no mailbox here by that name. (#5.1.1) I've already created the Maildir dir in the $HOME for myself. What can be wrong? Best regards, Isaiah ChuaOfficial Email: [EMAIL PROTECTED]AIM Nick : radar00
yet another question about Virtual domains
I know this is a tense subject on the mailing list, but please bear with me. ;o) I haven't even INSTALLED qmail yet, but would much rather use it on my RedHat 6.1 box than the stock sendmail that's full of holes. However, my dilemma is that I'm going to be running multiple virtual domains on one server, web, mail, ftp, etc. and am curious to know what steps exactly I should follow to get the setup completed with qmail. Before you start ranting about "RTFM", I have read through the FAQ's and found them a little confusing. I also searched through the mailing list archives and am even more confused. What I'm looking for here is a way to set up my server to accept mail for domain1.com, domain2.com and domain3.com ... etc, to domainn.com. Each domain should have its own unique users. That is, [EMAIL PROTECTED] is NOT [EMAIL PROTECTED] Is this going to be a problem? This is the issue that I fail to see (easily) addressed from what I've read so far. I plan to have a directory structure in place such as: /home/domain1/mail/user1 /home/domain1/mail/user2 etc for each of the domains so that each user can login using POP/IMAP to retrieve their mail. I'd also like an way to handle Email aliasing so that [EMAIL PROTECTED] can be sent to [EMAIL PROTECTED] or wherever else I need it to go. I'm not new to Linux, but I'm new to the idea of setting up multiple domains on a single host, so any hand-holding would be appreciated. Thanks much, --- Ian Douglas, System Administration [EMAIL PROTECTED]
Re: yet another question about Virtual domains
For a little more information, I'm getting into virtual web hosting which I can set up and maintain quite well ... but everyone's looking for Email to go with it. So each domain I host is going to have their own webmaster@, sales@, info@ address, etc. I would like all root@, sysadmin@, and postmaster@ Email to be filtered into one POP box for myself. Again, I appreciate any helpful responses. --- Ian Douglas, System Administration [EMAIL PROTECTED]
Re: yet another question about Virtual domains
Ian Douglas [EMAIL PROTECTED] wrote: However, my dilemma is that I'm going to be running multiple virtual domains on one server, web, mail, ftp, etc. and am curious to know what steps exactly I should follow to get the setup completed with qmail. As far as qmail is concerned, this is not a problem, although you probably want to use a virtual user manager of some sort -- there's several to pick from. What I'm looking for here is a way to set up my server to accept mail for domain1.com, domain2.com and domain3.com ... etc, to domainn.com. Virtual domain support is simple and documented in Life with qmail, etc. Essentially you create one user account for each virtual domain, although this varies between manager systems. Each domain should have its own unique users. That is, [EMAIL PROTECTED] is NOT [EMAIL PROTECTED] Is this going to be a problem? This is the issue that I fail to see (easily) addressed from what I've read so far. It's not a problem for virtual mail users, _but_ ... I plan to have a directory structure in place such as: /home/domain1/mail/user1 /home/domain1/mail/user2 etc This looks like you're planning on setting up home directories for virtual mail users -- why? Do they need shell/ftp/other access? If so, they're not really virtual mail users. A virtual mail user doesn't need an account of their own -- they just need a POP mailbox (or IMAP, etc). for each of the domains so that each user can login using POP/IMAP to retrieve their mail. I'd also like an way to handle Email aliasing so that [EMAIL PROTECTED] can be sent to [EMAIL PROTECTED] or wherever else I need it to go. Yet here you say you only need POP/IMAP access for them. Forget about giving virtual users individual home directories. I'm not new to Linux, but I'm new to the idea of setting up multiple domains on a single host, so any hand-holding would be appreciated. More details will get you more detailed responses, providing you go read "Life with qmail", mentioned almost every day in this list. Also read everything on www.qmail.org, especially concerning virtual mail user management systems. Charles -- Charles Cazabon [EMAIL PROTECTED] Any opinions expressed are just that -- my opinions.
Re: yet another question about Virtual domains
I plan to have a directory structure in place such as: /home/domain1/mail/user1 /home/domain1/mail/user2 etc This looks like you're planning on setting up home directories for virtual mail users -- why? Do they need shell/ftp/other access? If so, they're not really virtual mail users. A virtual mail user doesn't need an account of their own -- they just need a POP mailbox (or IMAP, etc). The directory structure will be used for web/ftp hosting as well... for example: /home/domain1/public_html/ /home/domain1/anon_ftp/ /home/domain1/mail/ Shell access is still up in the air with regards to security issues. But that's not for this list to discuss... Thanks for any other ideas. Ken sent me a link for Inter7 which seems to be what I need for the virtual mail hosting. Many thanks. Ian
Yet another question :)
I think this is a good one. Because we'll be generating the messages on different machines than those that we send from, we have to find the most efficient way to get them into the queue. That presents us with a variety of options. Here are the few that we've come up with (some of these are good options, some are down right horrible... this is just a list): 1. Have the generator write directly to the qmail SMTP server via sockets 2. Open a telnet/rsh/rexec to the machine and use qmail-inject 3. Modify the source to qmail-inject to work on NT and remotely (very little work) and inject to the queue over a samba/nfs share 4. Send mail to the server via relay, using the Microsoft SMTP servers as relay and writing to them as we are now (this seems kludgey because the servers can only send 30 messages per second on the lan). 5. Telepathy? If anyone has any other options, or just their recommendations on which is fastest, that'd be great. The qmail queue is still a bit of a mystery to me, so I'm not quite sure what the fastest way to get something queue'd is. Cris Daniluk MicroStrategy
Re: Yet another question :)
At 02:01 PM 8/9/99 -0400, Cris Daniluk wrote: I think this is a good one. Because we'll be generating the messages on different machines than those that we send from, we have to find the most efficient way to get them into the queue. That presents us with a variety of options. Here are the few that we've come up with (some of these are good options, some are down right horrible... this is just a list): 1. Have the generator write directly to the qmail SMTP server via sockets 2. Open a telnet/rsh/rexec to the machine and use qmail-inject 3. Modify the source to qmail-inject to work on NT and remotely (very little work) and inject to the queue over a samba/nfs share 4. Send mail to the server via relay, using the Microsoft SMTP servers as relay and writing to them as we are now (this seems kludgey because the servers can only send 30 messages per second on the lan). 5. Telepathy? Check out qmail-qmqpc and qmail-qmqpd. David. __ David Villeger (212) 972 2030 x34 http://www.CheetahMail.com The Internet Email Publishing Solution
Re: Yet another question :)
[snip] Check out qmail-qmqpc and qmail-qmqpd. This looks like it would do what we need, BUT, there's no documentation at best :) Where would you find more detailed documentation? The man pages don't even discuss how to implement it. In fact, they say that qmqpd needs several environment variables which must be passed by tcp-env, but never says what! I would imagine this should be a pretty decent priority, as it doesn't seem to be worth even having a man page if it's going to be that helpless :) Cris Daniluk MicroStrategy
Re: Yet another question :)
On Mon, 9 Aug 1999, Cris Daniluk wrote: [snip] Check out qmail-qmqpc and qmail-qmqpd. This looks like it would do what we need, BUT, there's no documentation at best :) Where would you find more detailed documentation? The man pages don't even discuss how to implement it. In fact, they say that qmqpd needs several environment variables which must be passed by tcp-env, but never says what! I would imagine this should be a pretty decent priority, as it doesn't seem to be worth even having a man page if it's going to be that helpless :) man 5 tcp-environ gives you the environment variables so, I'd guess at starting it like you do qmail-smtpd under tcpserver (which sets the environment variables, and can enforce access control so only your MS servers can submit using it). obviously, use a different port than #25 Richard
Re: Yet another question :)
On Mon, 9 Aug 1999, Cris Daniluk wrote: [snip] Check out qmail-qmqpc and qmail-qmqpd. This looks like it would do what we need, BUT, there's no documentation at best :) Where would you find more detailed documentation? The man pages don't even discuss how to implement it. In fact, they say that qmqpd needs several environment variables which must be passed by tcp-env, but never says what! I would imagine this should be a pretty decent priority, as it doesn't seem to be worth even having a man page if it's going to be that helpless :) On the client side: mv /var/qmail/bin/qmail-queue /var/qmail/bin/qmail-queue.orig ln -s /var/qmail/bin/qmail-qmqpc /var/qmail/bin/qmail-queue cat /var/qmail/control/qmqpservers EOF # List of QMQP servers. This file is used by qmail-qmqpc. To enable # QMQP, remove qmail-queue and make a symbolic link as follows: # # qmail-queue - qmail-qmqpc # # Instead of queueing mail locally, qmail will now make a QMQP # connection to the first available QMQP server from the list below. # The QMQP servers must be listed by IP address. If no servers can be # contacted, mail delivery will fail. Hopefully, one of the QMQP # servers will be running qmail-qmqpd. # # ! WARNING ! WARNING ! WARNING ! WARNING ! WARNING ! WARNING ! WARNING ! # Do NOT put the current host in this list - this will cause an endless # loop of qmail-qmqpc/qmail-qmqpd connections because qmail-qmqpd wants # to call qmail-queue to place the incoming message in the queue. # ! WARNING ! WARNING ! WARNING ! WARNING ! WARNING ! WARNING ! WARNING ! # qmqpservers - listed by IP address ONLY 1.2.3.4 1.2.3.5 EOF On the server side: - edit /etc/services and add the line qmqp 628/tcp mail - run qmail-qmqpd from inetd (not recommended). Edit /etc/inetd.conf (all on one line) qmqp stream tcp nowait qmaild /pkgs/bin/tcpd /var/qmail/bin/tcp-env /var/qmail/bin/qmail-qmqpd /pkgs/bin/tcpd is wherever you have tcp_wrappers installed. Access control is handled by /etc/hosts.allow and /etc/hosts.deny. tcp-env provides the necessary environment variables to qmail-qmqpd. - run qmail-qmqpd from tcpsever (highly recommended). In a startup script run the following tcpserver -u 7791 -g 2108 -c 40 -v -R -x \ /etc/qmqpdrules.cdb 0 qmqp /var/qmail/bin/qmail-qmqpd 21 \ | accustamp | cyclog -s 100 /var/log/qmqp 7791 and 2108 are the uid and gid of the qmaild user and nofiles group. tcpserver provides the necessary environment variables to qmail-qmqpd. The -R option stops tcpserver doing identd lookups. Access control is handled by the cdb file /etc/qmqpdrules.cdb. This file is generated from /etc/qmqpdrules by running the command tcprules /etc/qmqpdrules.cdb /etc/qmqpdrules.tmp /etc/qmqpdrules You should also look at wrapping the tcpserver invocation in supervise (part of Dan's daemontools package) eval "env - PATH=$PATH supervise -r /etc/qmqpd \ tcpserver -u 7791 -g 2108 -c 40 -v -R -x \ /etc/qmqpdrules.cdb 0 qmqp /var/qmail/bin/qmail-qmqpd 21 \ | accustamp | cyclog -s 100 /var/log/qmqp " This is how I run it at tansu. Regards Peter -- Peter Samuel[EMAIL PROTECTED] Technical Consultantor at present: eServ. Pty Ltd [EMAIL PROTECTED] Phone: +61 2 9206 3410 Fax: +61 2 9281 1301 "If you kill all your unhappy customers, you'll only have happy ones left"
Another question about reply messages...
Giles Lean wrote: On Tue, 15 Jun 1999 20:20:35 +0200 Ana =?iso-8859-1?Q?Bel=E9n?= Santos wrote: Hi, I would like that when a mail comes to some user another mail could be replied to the sender answering something I have in one archive . You could look at http://www.nemeton.com.au/sw/autoreply/ This is a very simple autoresponder, designed to be safe for unsophisticated users to use. It may or may not be suitable for what you want to do. Regards, Giles I have several e-mail alias, and I want to send diferents autoreply-message depending the alias. But all mails come to the same acount anasan, who is the real user. Can I do that?? thanks
Re: Another question about reply messages...
+ Ana Belén Santos [EMAIL PROTECTED]: | I have several e-mail alias, and I want to send diferents | autoreply-message depending the alias. But all mails come to the | same acount anasan, who is the real user. Can I do that?? The easiest way is to have each alias forward to anasan-something and then create different ~anasan/.qmail-something files. - Harald
another question
I'm using Paul Gregg's setup for POP3 accounts for virtual domains, with one UID perdomain, and it works like a charm. Here's the question : I just found out that with the checkpoppaswd that Paul G. suggests using, it still relies on a single passwd-style file, which means that if you're hosting 50 domains, you can only have one POP3 account named "webmaster". Do you guys know of any other solution? I know that web servers deal out virtual domains by reading which domain name was asked to deliver material. For example, I have a site, foo.org, that hosts bar.com and blah.com. If I telnet to blah.com, port 80, and do a GET? I'll get blah's html, and if I do the same for foo.com, I'll get foo's html. Does POP3 have something like such, so that there can be a seperate passwd-style file for each domain? Thanks for listing to my drool, -Josh Murrah, who's getting fed up with virtuals hehe :)
Re: another question
On Wed, Jan 06, 1999 at 12:52:15AM -0600, Josh Murrah wrote: I'm using Paul Gregg's setup for POP3 accounts for virtual domains, with one UID perdomain, and it works like a charm. Here's the question : I just found out that with the checkpoppaswd that Paul G. suggests using, it still relies on a single passwd-style file, which means that if you're hosting 50 domains, you can only have one POP3 account named "webmaster". Do you guys know of any other solution? I know that web servers deal out virtual domains by reading which domain name was asked to deliver material. For example, I have a site, foo.org, that hosts bar.com and blah.com. If I telnet to blah.com, port 80, and do a GET? I'll get blah's html, and if I do the same for foo.com, I'll get foo's html. Does POP3 have something like such, so that there can be a seperate passwd-style file for each domain? If you have the following in control/virtualdomains: foo.org:foo bar.com:bar you can have entries like the following in your poppasswd file: foo-joeblow:$1$M14AAVdd$L9PxbFmKINwEtIabcdefg.:popuser:/var/qmail/popboxes/foo-org/joeblow/ bar-joeblow:$1$M14AAVdd$L9PxbFmKINwEtIhijklmn.:popuser:/var/qmail/popboxes/bar-com/joeblow/ User [EMAIL PROTECTED] would use foo-joeblow for his POP user name, and user [EMAIL PROTECTED] would use bar-joeblow for his POP user name. This allows you to have any number of accounts with the same name, so long as they're in different domains. Chris
