qmail Digest 28 Aug 2001 10:00:00 -0000 Issue 1470
Topics (messages 68565 through 68600):
Re: more "unable to start supervise"
68565 by: Dave Sill
68573 by: dermini.nevada.edu
Re: qmail on dial-up gateway
68566 by: Dave Sill
[OT] Sendmail On IBM Mainframes Running GNU/Linux
68567 by: Adriano Nagelschmidt Rodrigues
68587 by: MarkD
Qmail Relaying and startup script
68568 by: Subba Rao
68570 by: Charles Cazabon
68571 by: Chris Johnson
68595 by: Subba Rao
Update to UW IMAP Maildir
68569 by: Herbie
Logging only undeliverable messages?
68572 by: Joshua Pollak
68574 by: Dave Sill
68575 by: Charles Cazabon
68576 by: Joshua Pollak
68577 by: Charles Cazabon
68578 by: Dave Sill
68579 by: Joshua Pollak
68580 by: Charles Cazabon
68581 by: Dave Sill
68582 by: Chris Johnson
68583 by: Dave Sill
68584 by: Scott Gifford
68585 by: Joshua Pollak
68586 by: Joshua Pollak
68589 by: Dave Sill
68599 by: dssyenon
Re: qmail not delivering mail to local users
68588 by: Alexander Jernejcic
Re: detecting the original envelope recipient under a virtualdomain?
68590 by: Markus Stumpf
68596 by: Pavel Kankovsky
Virtual Domains (I've read FAQs, docs, PIC, INSTALLS, and this board)
68591 by: Mike Reavey
68592 by: Charles Cazabon
68593 by: Mike Reavey
68594 by: Charles Cazabon
about bounce
68597 by: mugund.intercept-india.com
retriving email from another server
68598 by: hauser
ESMTP question
68600 by: Alexey Korchagin
Administrivia:
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
[EMAIL PROTECTED] wrote:
>svscan: warning: unable to start supervise qmail-send: file does not exist
svscan can't find supervise. Which version of daemontools did you
install? Do you see supervise?
-Dave
Indeed, supervise was missing. I installed the latest daemontools and it
works. Thank you for pointing that out.
Duncan
On Mon, 27 Aug 2001, Dave Sill wrote:
> [EMAIL PROTECTED] wrote:
>
> >svscan: warning: unable to start supervise qmail-send: file does not exist
>
> svscan can't find supervise. Which version of daemontools did you
> install? Do you see supervise?
>
> -Dave
>
"Martin Dvorak" <[EMAIL PROTECTED]> wrote:
>3. Messages which are addressed to mailboxes which are later
> downloaded to local POP3/IMAP server should never be sent
> to Internet but instead immediately sent to corresponding
> local mailboxes (no matter what is the status of the dial-up
> link).
Are you saying you want messages from local to local users that
specify their non-local mailboxes to be delivered locally?
In other words, say you're retrieving [EMAIL PROTECTED]'s mail
using getmail and delivering it locally to joe. Some local user sends
joe a message using his AOL address. You want to deliver that
directly, rather than sending it to AOL and POPing it back?
If so, this is easy. Put the following in control/virtualdomains:
[EMAIL PROTECTED]:joe-aol
And "touch ~joe/.qmail-aol-default".
-Dave
Sendmail has released a version of its e-mail server software that can
run on Linux-powered IBM mainframe computers, the company will
announce Monday.
http://news.cnet.com/news/0-1003-200-6964729.html?tag=lh
In one benchmark test , IBM found that it was possible to house 2
million e-mail accounts on a single server, with 10 percent of the
users accessing their mail at any given moment, Hodges said.
--------------------------------------------
Just a provocation from an old timer (v. 0.96) returning to the
list...
Dan, have you abandoned us? Where is qmail 2.0? I'm sure you can do
better! ;-)
Regards,
--
Adriano
On Mon, Aug 27, 2001 at 12:00:18PM -0300, Adriano Nagelschmidt Rodrigues allegedly
wrote:
> Sendmail has released a version of its e-mail server software that can
> run on Linux-powered IBM mainframe computers, the company will
> announce Monday.
>
> In one benchmark test , IBM found that it was possible to house 2
> million e-mail accounts on a single server, with 10 percent of the
> users accessing their mail at any given moment, Hodges said.
>
> --------------------------------------------
>
> Just a provocation from an old timer (v. 0.96) returning to the
> list...
>
> Dan, have you abandoned us? Where is qmail 2.0? I'm sure you can do
> better! ;-)
You will note of course that sendmail itself has nothing to do with
"accesses". They are either referring to something like qpopper or
possibly the MessagingDirect product that they rebadge. Very effective
marketing spin if people incorrectly assume it refers to MTA
performance.
It'd be interesting to know whether they actually built the machine
that supports 200,000 concurrent accesses. That's a lot of concurrent
sockets for any single system to handle - even top-end IBM fridges.
But as I said, that press announcement has nought to do with the MTA
itself.
Regards.
Hello,
Over the weekend, I have upgraded my HW and did a clean install of Linux.
Before upgrading I did save most of the configuration files with the exception
of Qmail...:-(
I am trying to get this running to the way it was. Qmail is compiled and
running fine. I can send email from the local host only. When I telnet to
port 25 on any interface, I get connection "Connection refused". By default
relaying is turned off. So, I have created /etc/tcprules.smtp and the CDB file.
All the local nets are in that DB. Now, I NOT running Qmail via tcpserver.
I would like to run it via svscan/supervise services (/var/qmail/rc = run).
Is there anyway to control relay when Qmail is not run by tcpserver? What
files should I configure to allow my other machines to relay mail through
this server?
TIA.
--
Subba Rao
[EMAIL PROTECTED]
http://members.home.net/subba9/
GPG public key ID CCB7344E
Key fingerprint = A8DD 4CBA 1E9B D962 A55B 2B55 BAFE 92C5 CCB7 344E
Subba Rao <[EMAIL PROTECTED]> wrote:
>
> Over the weekend, I have upgraded my HW and did a clean install of Linux.
> Before upgrading I did save most of the configuration files with the exception
> of Qmail...:-(
All the critical files are in /var/qmail/control -- simply recover that
directory from your backups.
> I am trying to get this running to the way it was. Qmail is compiled and
> running fine. I can send email from the local host only. When I telnet to
> port 25 on any interface, I get connection "Connection refused".
Either you can't connect to port 25 for firewall reasons, or nothing is
listening on 25.
> By default relaying is turned off. So, I have created
> /etc/tcprules.smtp and the CDB file. All the local nets are in that
> DB.
This doesn't help us in the least. Show us /etc/tcprules.smtp, and
we'll tell you if anything is wrong with it.
> Now, I NOT running Qmail via tcpserver.
tcpserver is only used for qmail-smtpd, not qmail proper (qmail-start,
which leads to qmail-send).
> I would like to run it via svscan/supervise services (/var/qmail/rc =
> run).
tcpserver and svscan/supervise are not mutually exclusive. A standard
installation nowadays uses svscan/supervise for all processes, and
a supervised tcpserver for qmail-smtpd.
> Is there anyway to control relay when Qmail is not run by tcpserver?
> What files should I configure to allow my other machines to relay mail
> through this server?
Use of anything but tcpserver to run qmail-smtpd is deprecated. Use
tcpserver. Really -- it takes three minutes to install & configure.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------
On Mon, Aug 27, 2001 at 11:10:28AM -0400, Subba Rao wrote:
> Now, I NOT running Qmail via tcpserver. I would like to run it via
> svscan/supervise services (/var/qmail/rc = run). Is there anyway to control
> relay when Qmail is not run by tcpserver?
You don't ever run qmail-send from tcpserver. tcpserver is used only for
daemons that listen to the network, like qmail-smtpd and qmail-pop3d, and for
these you *must* use tcpserver (or inetd or xinetd, but those wouldn't be
compatible with svscan/supervise).
It sounds like you're not running qmail-smtpd at all. You need to set up and
run qmail-smtpd via tcpserver, and then you can worry about relaying. See
http://www.lifewithqmail.org.
Chris
PGP signature
On 0, Chris Johnson <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 27, 2001 at 11:10:28AM -0400, Subba Rao wrote:
> > Now, I NOT running Qmail via tcpserver. I would like to run it via
> > svscan/supervise services (/var/qmail/rc = run). Is there anyway to control
> > relay when Qmail is not run by tcpserver?
>
> You don't ever run qmail-send from tcpserver. tcpserver is used only for
> daemons that listen to the network, like qmail-smtpd and qmail-pop3d, and for
> these you *must* use tcpserver (or inetd or xinetd, but those wouldn't be
> compatible with svscan/supervise).
>
> It sounds like you're not running qmail-smtpd at all. You need to set up and
> run qmail-smtpd via tcpserver, and then you can worry about relaying. See
> http://www.lifewithqmail.org.
>
Thanks Chris and Charles. I did use the tcpserver for smtpd and pop3d. Now,
my local systems can relay email. I did follow the LWQ from David Sill. This
document has improved so much for the better. The instructions are so much more
clearer now, especially QMAILCTL script. (Thanks David).
Now on to the VPN issue.....
Upgrades are so much fun. Aren't they? :-)
--
Subba Rao
[EMAIL PROTECTED]
http://members.home.net/subba9/
GPG public key ID CCB7344E
Key fingerprint = A8DD 4CBA 1E9B D962 A55B 2B55 BAFE 92C5 CCB7 344E
Actually it's more of a very ugly kludge.
I had been having problems with the Maildir patched UW IMAP server, where
other mailbox drivers were being called, most noticeably for some reason
the dummy driver as the maildir wasn't responding well to the mailstream.
Long story short, I hacked out all the other drivers leaving a maildir
only daemon, useful to me, maybe to some other folks, probably not
wide-spread usefulness.
For the record, this patch is in desperate need of a full time maintainer,
and it was ugly to start with, now it's uglier, anyone wants to take a
stab at rewriting the whole thing, be my guest, it needs done badly.
The README outlining my kludge and the patch itself are available
(still) at http://www.greboguru.org/qmail/
herbie
Hello,
I've made the modification to qmail to log all messages, however, I was
wondering if there is a way to modify that system so that only locally
undeliverable messages get stored? I don't really want every message
logged, but if a message comes in for a user that qmail can't find, I'd
like to log that message.
Is that possible?
Joshua Pollak <[EMAIL PROTECTED]> wrote:
>I've made the modification to qmail to log all messages, however, I was
>wondering if there is a way to modify that system so that only locally
>undeliverable messages get stored? I don't really want every message
>logged, but if a message comes in for a user that qmail can't find, I'd
>like to log that message.
>
>Is that possible?
Sure. Think about ~alias/.qmail-default.
-Dave
Joshua Pollak <[EMAIL PROTECTED]> wrote:
>
> I've made the modification to qmail to log all messages, however, I was
> wondering if there is a way to modify that system so that only locally
> undeliverable messages get stored? I don't really want every message
> logged, but if a message comes in for a user that qmail can't find, I'd
> like to log that message.
>
> Is that possible?
Yes -- disable QUEUE_EXTRA and use ~alias/.qmail-default .
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------
> > I've made the modification to qmail to log all messages, however, I was
> > wondering if there is a way to modify that system so that only locally
> > undeliverable messages get stored? I don't really want every message
>
>Yes -- disable QUEUE_EXTRA and use ~alias/.qmail-default .
Ok, simple enough, but I have fastforwad installed in .qmail-default: How
do I only log the messages fastforward can't handle?
Don't cc: me on list messages, please. That's why I set
Mail-Followup-To: appropriately in my first reply to your message.
Joshua Pollak <[EMAIL PROTECTED]> wrote:
>
> > > I've made the modification to qmail to log all messages, however, I was
> > > wondering if there is a way to modify that system so that only locally
> > > undeliverable messages get stored? I don't really want every message
> >
> >Yes -- disable QUEUE_EXTRA and use ~alias/.qmail-default .
>
> Ok, simple enough, but I have fastforwad installed in .qmail-default: How
> do I only log the messages fastforward can't handle?
Not easily; fastforward bounces messages which aren't handled by it.
Do you really need fastforward?
I've never used it. ~alias/.qmail-* has always been sufficient for me.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]> wrote:
>Not easily; fastforward bounces messages which aren't handled by it.
>Do you really need fastforward?
The "-p" (passthrough) option causes fastforward not to generate
bounces and to exit 0 on unmatched addresses.
-Dave
At 11:31 AM 8/27/2001 -0600, Charles Cazabon wrote:
>Don't cc: me on list messages, please. That's why I set
>Mail-Followup-To: appropriately in my first reply to your message.
Sorry, I didn't mean to, Reply-To: doesn't seem to be set to the mailing
list and I wasn't paying attention, usually I am.
I found the answer: Invoking fastforward like this:
fastforward -p ...
will make it pass through if it cannot find a match, or forward if it does
find one. I guess this means people will never get bounces for
undeliverable mail though.
> > Ok, simple enough, but I have fastforward installed in .qmail-default: How
> > do I only log the messages fastforward can't handle?
>
>Not easily; fastforward bounces messages which aren't handled by it.
>Do you really need fastforward?
>
>I've never used it. ~alias/.qmail-* has always been sufficient for me.
Dave Sill <[EMAIL PROTECTED]> wrote:
> Charles Cazabon <[EMAIL PROTECTED]> wrote:
>
> >Not easily; fastforward bounces messages which aren't handled by it.
> >Do you really need fastforward?
>
> The "-p" (passthrough) option causes fastforward not to generate
> bounces and to exit 0 on unmatched addresses.
Thanks for the correction; I'd forgotten that. I did say I've never
used it :).
Is fastforward in common use? Or is it primarily a crutch while
sendmail administrators adjust to the qmail way of doing things?
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------
Joshua Pollak <[EMAIL PROTECTED]> wrote:
>fastforward -p ...
>
>will make it pass through if it cannot find a match, or forward if it does
>find one. I guess this means people will never get bounces for
>undeliverable mail though.
You can make it bounce if you want to. For example, put the following
in .qmail-default:
|fastforward -p alias.cdb
&unknown-log
&unknown-bounce
Then create .qmail-unknown-log:
./Unknown/
and .qmail-unknown-bounce:
|bouncesaying "unknown user"
-Dave
On Mon, Aug 27, 2001 at 11:50:58AM -0600, Charles Cazabon wrote:
> Is fastforward in common use? Or is it primarily a crutch while
> sendmail administrators adjust to the qmail way of doing things?
You're probably thinking of dot-forward, which is sendmail-ish. fastforward
fits right in with the qmail way of doing things.
Chris
PGP signature
Charles Cazabon <[EMAIL PROTECTED]> wrote:
>Thanks for the correction; I'd forgotten that. I did say I've never
>used it :).
We'll give you the benefit of the doubt...this time. :-)
>Is fastforward in common use? Or is it primarily a crutch while
>sendmail administrators adjust to the qmail way of doing things?
I don't use it myself, and I have no idea how widely used it is. Of
course it was designed to be crutch for sendmail migration, but it
does look like a pretty efficient way to handle lots of aliases.
-Dave
Joshua Pollak <[EMAIL PROTECTED]> writes:
> I've made the modification to qmail to log all messages, however, I
> was wondering if there is a way to modify that system so that only
> locally undeliverable messages get stored? I don't really want every
> message logged, but if a message comes in for a user that qmail can't
> find, I'd like to log that message.
If the undeliverable messages have some special string in them, and
you are using multilog, you could try using its pattern-matching
capabilities to only log the lines you want to see.
Good luck,
---ScottG.
These instructions work perfectly, thank you, I didn't know there was a
bouncesaying program. :)
>You can make it bounce if you want to. For example, put the following
>in .qmail-default:
>
> |fastforward -p alias.cdb
> &unknown-log
> &unknown-bounce
>
>Then create .qmail-unknown-log:
>
> ./Unknown/
>
>and .qmail-unknown-bounce:
>
> |bouncesaying "unknown user"
>
>-Dave
>Is fastforward in common use? Or is it primarily a crutch while
>sendmail administrators adjust to the qmail way of doing things?
It certainly makes mailing list administration (non-ezlm of course) easy.
Just put all the relevant addresses in /etc/aliases and run newaliases...
-Josh
Joshua Pollak <[EMAIL PROTECTED]> wrote:
>These instructions work perfectly, thank you, I didn't know there was a
>bouncesaying program. :)
Glad to help.
Of course, you don't need bouncesaying to this. You could use:
|echo "unknown user"; exit 100
-Dave
On Mon, 27 Aug 2001, Dave Sill wrote:
> You can make it bounce if you want to. For example, put the following
> in .qmail-default:
>
> |fastforward -p alias.cdb
> &unknown-log
> &unknown-bounce
>
> Then create .qmail-unknown-log:
>
> ./Unknown/
>
> and .qmail-unknown-bounce:
>
> |bouncesaying "unknown user"
I don't use fastforward so my .qmail-default has just the 2 lines.
"[EMAIL PROTECTED]" doesn't exist so I'd expect it to bounce. It does,
and gets logged, but the bounce message has:
<[EMAIL PROTECTED]>:
unknown user
instead of
<[EMAIL PROTECTED]>:
unknown user
The full headers in the included original message do mention user123, but
how do I get user123 instead of unknown-bounce in the bounce message?
Also, why involve 3 files (.qmail-default, .qmail-unknown-log,
.qmail-unknown-bounce)? The dot-qmail man page says each line is a
delivery instruction followed in turn. If I just put this in
.qmail-default:
./Unknown/
|bounecsaying "unknown user"
it does bounce with the actual failed address in the message (user123) but
it doesn't get saved to Unknown. If each line is executed in turn,
./Unknown/ must have executed before |bouncesaying. Instead, it appears we
just skip to |bouncesaying.
hi,
somethings wrong with the default delivery. recheck your qmail-start - some
typo
in the rc i assume. it should EXACTLY read like LWQ...
hope that helps
alexander
hauser [mailto:[EMAIL PROTECTED]] wrote:
mucha snip
> @400000003b8989ad114a6a1c starting delivery 2: msg 216052 to local
> 'cat_/var/qmail/control/defaultdelivery'@email.nyandashs.qld.edu.au
lot a snip
On Thu, Aug 23, 2001 at 06:04:45PM -0400, John R. Levine wrote:
> > Is there any way to determine what the *original* envelope recipient
> > ([EMAIL PROTECTED]) was under a virtualdomain before qmail changed
> > it to the local representation?
>
> Of course. When qmail rewrites the local part of a virtual domain
> address, it does NOT change the domain. So all you have to do is to
> look up $DOMAIN in virtualdomains, and if you find it strip off the
> prepend string. It should take about three lines of perl. It doesn't
> even need for the prepends to be unique.
May I note, that virtualdomains accepts lines of the format
user@domain:prepend
Despite its name it can also be used as a "virtualusers" file, so
- it may not be enough to only scan for domains and sorting out
the user@domain:prepend may take a bit more work as you can have
[EMAIL PROTECTED]:prepend-1
[EMAIL PROTECTED]:prepend-2
example.com:prepend-3
.example.com:prepend-4
- in case of .domain:prepend this scanning may be a bit more work
to match subdomains
\Maex
--
SpaceNet AG | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development | D-80807 Muenchen | Fax: +49 (89) 32356-299
Stress is when you wake up screaming and you realize you haven't fallen
asleep yet.
On 23 Aug 2001, John R. Levine wrote:
> Finally, if you look at the source code for qmail, you will see that
> even if you wanted to pass along the unprefixed version of the
> address, it would take a great deal of hackery to do so.
Surpise...if you look at the source code, you will see qmail-send already
does a "great deal of hackery" to de-virtualize rcpt addresses when it
generates bounces (stripvdomprepend()). And of course, 1. it fails to do
this when it generates VERPs, ergo it generates wrong VERPs sometimes,
2. the de-virtualization is unreliable anyway because it fails when a
corresponding entry of virtualdomains is removed or changed while a
message with a munged rcpt waits in the queue.
--Pavel Kankovsky aka Peak [ Boycott Microsoft--http://www.vcnet.com/bms ]
"Resistance is futile. Open your source code and prepare for assimilation."
I've read FAQs, msg boards, INSTALL files, and I still can't
get this to work. Any help will be greately appreciated.
I compiled and installed qmail this weekend. Using tcpserver
and supervise scripts
It works great for any local accounts
I can't get virtual domains to work. My goal is to
have "[EMAIL PROTECTED]" go to "[EMAIL PROTECTED]".
Everything I send to "[EMAIL PROTECTED]"
including "[EMAIL PROTECTED]", bounces back with "Sorry,
no mailbox here by that name."
Here are my config files:
cat control/locals
pimppilot.com
mail.pimppilot.com
-----
cat control/rcpthosts
pimppilot.com
mail.pimppilot.com
aristophanes.net
------
cat control/virtualdomains
aristophanes.net:bradc
-------
cat /home/bradc/.qmail
&[EMAIL PROTECTED]
---------
Some notes:
Any mail to [EMAIL PROTECTED] works wonderfully
I had no control/virtualdomains file in my /var/qmail/control
directory, I had to create it. All the files in
my /var/qmail/control directory are owned by root in
group root, included virtualdomains that I created.
Here's the output of my qmail-showctl, I appologize for not
including it in
the first messages
qmail home directory: /var/qmail.
user-ext delimiter: -.
paternalism (in decimal): 2.
silent concurrency limit: 120.
subdirectory split: 23.
user ids: 502, 503, 504, 0, 505, 506, 507, 508.
group ids: 502, 503.
badmailfrom: (Default.) Any MAIL FROM is allowed.
bouncefrom: (Default.) Bounce user name is MAILER-DAEMON.
bouncehost: (Default.) Bounce host name is mail.pimppilot.com.
concurrencylocal: (Default.) Local concurrency is 10.
concurrencyremote: (Default.) Remote concurrency is 20.
databytes: (Default.) SMTP DATA limit is 0 bytes.
defaultdomain: Default domain name is pimppilot.com.
defaulthost: (Default.) Default host name is mail.pimppilot.com.
doublebouncehost: (Default.) 2B recipient host:
mail.pimppilot.com.
doublebounceto: (Default.) 2B recipient user: postmaster.
envnoathost: (Default.) Presumed domain name is
mail.pimppilot.com.
helohost: (Default.) SMTP client HELO host name is
mail.pimppilot.com.
idhost: (Default.) Message-ID host name is mail.pimppilot.com.
localiphost: (Default.) Local IP address becomes
mail.pimppilot.com.
locals:
Messages for pimppilot.com are delivered locally.
Messages for mail.pimppilot.com are delivered locally.
me: My name is mail.pimppilot.com.
percenthack: (Default.) The percent hack is not allowed.
plusdomain: Plus domain name is pimppilot.com.
qmqpservers: (Default.) No QMQP servers.
queuelifetime: (Default.) Message lifetime in the queue is
604800
seconds.
rcpthosts:
SMTP clients may send messages to recipients at
mail.pimppilot.com.
SMTP clients may send messages to recipients at pimppilot.com.
SMTP clients may send messages to recipients at
aristophanes.net.
morercpthosts: (Default.) No effect.
morercpthosts.cdb: (Default.) No effect.
smtpgreeting: (Default.) SMTP greeting: 220 mail.pimppilot.com.
smtproutes: (Default.) No artificial SMTP routes.
timeoutconnect: (Default.) SMTP client connection timeout is 60
seconds.
timeoutremote: (Default.) SMTP client data timeout is 1200
seconds.
timeoutsmtpd: (Default.) SMTP server data timeout is 1200
seconds.
virtualdomains:
Virtual domain: aristophanes.net:bradc
defaultdelivery: I have no idea what this file does.
concurrencyincoming: I have no idea what this file does.
Please let me know if anyone has any ideas....I've done
everything according to the FAQ, Posts, doc files (including
PICs), restarted qmail, rebooted, went to confession, and am at
a complete loss.
Thanks!
Mike
[EMAIL PROTECTED]
Mike Reavey
Voice mail: 877.204.4797
E-mail: [EMAIL PROTECTED]
www.mikereavey.org
(Please send all replies to [EMAIL PROTECTED])
________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
Mike Reavey <[EMAIL PROTECTED]> wrote:
> I've read FAQs, msg boards, INSTALL files, and I still can't
> get this to work. Any help will be greately appreciated.
I'd recommend you re-read the qmail man pages. You've made some fairly
basic errors in the use of .qmail files, etc.
> I compiled and installed qmail this weekend. Using tcpserver
> and supervise scripts
"supervise scripts"? Do you mean the package by Bruce Guenter? Did you
install qmail from his qmail+patches source RPM as well? This is
relevant information.
> I can't get virtual domains to work. My goal is to
> have "[EMAIL PROTECTED]" go to "[EMAIL PROTECTED]".
[...]
> Here are my config files:
In future, just give us the unedited output of qmail-showctl. It's
easier for you, and it's in a standard format which we expect. Oh, I
see you did later. Good for you.
> cat control/virtualdomains
> aristophanes.net:bradc
Do you understand that this will cause mail to <[EMAIL PROTECTED]>
to be delivered as if it was to a local account handling
<[EMAIL PROTECTED]>?
> cat /home/bradc/.qmail
> &[EMAIL PROTECTED]
And that this .qmail file doesn't handle mail for the above?
Read the man page for dot-qmail several times. The answer is there.
> I had no control/virtualdomains file in my /var/qmail/control
> directory, I had to create it.
That's fine; a normal fresh install of qmail doesn't have any
virtualdomains.
> All the files in my /var/qmail/control directory are owned by root in
> group root, included virtualdomains that I created.
This is atypical, but if they're world-readable, it shouldn't cause any
harm. Typically files are owned by group "qmail" or some such.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------
I've changed the information a bit. Thank you for the help,
with the information below, I'm still unable to get mail to the
virtual domain.
Once again, thank you for the help.
Charles Cazabon wrote:
>
> > I'd recommend you re-read the qmail man pages. You've made
> some fairly
> > basic errors in the use of .qmail files, etc.
> >
> > > I compiled and installed qmail this weekend. Using
> tcpserver
> > > and supervise scripts
> >
> > "supervise scripts"? Do you mean the package by Bruce
> Guenter? Did you
> > install qmail from his qmail+patches source RPM as well?
> This is
> > relevant information.
>
No, I installed from qmail-1.03.tar.gz.
> >
> > > I can't get virtual domains to work. My goal is to
> > > have "[EMAIL PROTECTED]" go
> to "[EMAIL PROTECTED]".
> > [...]
>
My goal is to have "[EMAIL PROTECTED] go
to "[EMAIL PROTECTED]" (sorry for the mistake)
>
>
> > > Here are my config files:
> >
> > In future, just give us the unedited output of qmail-
> showctl. It's
> > easier for you, and it's in a standard format which we
> expect. Oh, I
> > see you did later. Good for you.
> >
> > > cat control/virtualdomains
> > > aristophanes.net:bradc
> >
> > Do you understand that this will cause mail to
> <[EMAIL PROTECTED]>
> > to be delivered as if it was to a local account handling
> > <[EMAIL PROTECTED]>?
> >
> > > cat /home/bradc/.qmail
> > > &[EMAIL PROTECTED]
> >
> > And that this .qmail file doesn't handle mail for the above?
> >
> > Read the man page for dot-qmail several times. The answer
is
> there.
> >
> > > I had no control/virtualdomains file in
> my /var/qmail/control
> > > directory, I had to create it.
> >
> > That's fine; a normal fresh install of qmail doesn't have
any
> > virtualdomains.
> >
> > > All the files in my /var/qmail/control directory are
owned
> by root in
> > > group root, included virtualdomains that I created.
> >
> > This is atypical, but if they're world-readable, it
shouldn't
> cause any
> > harm. Typically files are owned by group "qmail" or some
> such.
> >
> > Charles
> > --
> > ------------------------------------------------------------
--
> ---------
> > Charles Cazabon
> <[EMAIL PROTECTED]>
> > GPL'ed software available at:
> http://www.qcc.sk.ca/~charlesc/software/
> > ------------------------------------------------------------
--
> ---------
> >
> >
>
>
> ________________________________________________
> Get your own "800" number
> Voicemail, fax, email, and a lot more
> http://www.ureach.com/reg/tag
>
>
________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
Mike Reavey <[EMAIL PROTECTED]> wrote:
>
> I've changed the information a bit. Thank you for the help,
> with the information below, I'm still unable to get mail to the
> virtual domain.
Summing up my previous message: ~bradc/.qmail does not control delivery
to bradc-anything@anydomain. See the manpage for "dot-qmail", where this
issue is covered fully. In addition, re-read "Life with qmail", which
also covers this issue.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------
hi all,
iam using qmail 1.03 on a linux redhat 6.2
i notice that the bounce messages are received with the original message (which i
intended to send) being embedded in it. is there any way to make the bounce message
contain only the mailid from which the mail had been bounced back and not to contain
the original message.
thanking you,
awaiting your reply very very soon.
Rgeards,
Mugundhan
hi,
I am wondering if any one knows what i can do to get mail from 600+ pop
accounts from a server to my local users mailboxs every 20+ mins.
regards,
eric.
Greeting you, people!
Can I ask about patches or solve next problem:
If we make telnet connection to qmail-ESMTP, we can see next:
>telnet 192.168.2.1 25
220 domain.com ESMTP
MAIL FROM: [EMAIL PROTECTED]
250 Ok
RCPT TO: somebody
250 Ok
DATA
354 go ahead
bla-bla-bla
.
250 ok 998993970 qp 28932
quit
221 domain.com
> Connection closed by foreign host.
And nothing mean if user "somebody" don't exist
If we look at this on sendmail we can see:
>telnet 192.168.2.1 25
220 domain.com ESMTP Sendmail x.x.x/x.x.x Tue, 28 Aug 2001 16:19:59 +
0600 (YEKST)
MAIL FROM: [EMAIL PROTECTED]
250 [EMAIL PROTECTED] Sender ok
RCPT TO: somebody
550 somebody... User unknew
quit
221 domain.com closing connection.
> Connection closed by foreign host.
In other words I want ask: did exist any solution in qmail not recive
letters for non-exists users?
Thank you.
--
Best regards,
Alexey mailto:[EMAIL PROTECTED]
