qmail Digest 24 Apr 1999 10:00:01 -0000 Issue 620
Topics (messages 24641 through 24681):
Virus scanning with qmail
24641 by: Jeff Hayward <[EMAIL PROTECTED]>
old popdeamons don't do ~user/Mailbox
24642 by: [EMAIL PROTECTED]
24653 by: Peter Haworth <[EMAIL PROTECTED]>
24660 by: Dave Sill <[EMAIL PROTECTED]>
24671 by: [EMAIL PROTECTED]
24675 by: Stefan Paletta <[EMAIL PROTECTED]>
inetd-smtp/tcp problem
24643 by: "Brian D. Kohl" <[EMAIL PROTECTED]>
24644 by: Justin Bell <[EMAIL PROTECTED]>
24646 by: Chris Johnson <[EMAIL PROTECTED]>
24648 by: "Brian D. Kohl" <[EMAIL PROTECTED]>
24658 by: "Reid Sutherland" <[EMAIL PROTECTED]>
[twig] Can\'t Send mail with Webmail-Like Sw
24645 by: <[EMAIL PROTECTED]>
Qmail and trailing spaces
24647 by: "Dave Teske" <[EMAIL PROTECTED]>
24650 by: "Sam" <[EMAIL PROTECTED]>
24654 by: "Fred Lindberg" <[EMAIL PROTECTED]>
Linux qmail lost - help dummy!
24649 by: Dave Sill <[EMAIL PROTECTED]>
24651 by: "Paul J. Schinder" <[EMAIL PROTECTED]>
24655 by: Jeff Hayward <[EMAIL PROTECTED]>
.qmail-
24652 by: [EMAIL PROTECTED]
Restricting Qmail's SMTPd to come form @host.com only.
24656 by: "Duncan, Eric A." <[EMAIL PROTECTED]>
24657 by: Chris Johnson <[EMAIL PROTECTED]>
secondary MX on a Qmail host.
24659 by: Greg Moeller <[EMAIL PROTECTED]>
24661 by: Chris Johnson <[EMAIL PROTECTED]>
Reply from TCPSERVER
24662 by: Holger <[EMAIL PROTECTED]>
24663 by: Chris Johnson <[EMAIL PROTECTED]>
virtualdomains question
24664 by: "Julian L.C. Brown" <[EMAIL PROTECTED]>
24681 by: [EMAIL PROTECTED] (Giulio Orsero)
qmail-popup/checkpassword information
24665 by: Mark Bitting <[EMAIL PROTECTED]>
24666 by: Chris Johnson <[EMAIL PROTECTED]>
24672 by: Russell Nelson <[EMAIL PROTECTED]>
24676 by: Mark Bitting <[EMAIL PROTECTED]>
24678 by: Russell Nelson <[EMAIL PROTECTED]>
newbie's question
24667 by: "Sherrill (Pei-chih) Verbrugge" <[EMAIL PROTECTED]>
MX, IPs and QMail
24668 by: "Bret Van Horn" <[EMAIL PROTECTED]>
24669 by: Chris Johnson <[EMAIL PROTECTED]>
24670 by: "Bret Van Horn" <[EMAIL PROTECTED]>
Qmail + DNS for bogus domain
24673 by: "Subba Rao" <[EMAIL PROTECTED]>
24674 by: "Sam" <[EMAIL PROTECTED]>
Hey - Getting closer, methinks!
24677 by: Roger Merchberger <[EMAIL PROTECTED]>
Err... that was stupid...
24679 by: Roger Merchberger <[EMAIL PROTECTED]>
pine on remote server
24680 by: Brad <[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]
----------------------------------------------------------------------
On Thu, 22 Apr 1999, Tracy R Reed wrote:
No, the virus scanning software is trivial. McAffee has had it for x86 Linux
for ages. Plugging it into qmail is the hard part. Something has to decode the
MIME, decompress the zips, scan, and then do something appropriate with
the email and notify both parties. That's not particularly trivial.
In my somewhat limited use of it I've found the Perl MIME::* modules
to be very useful. It is trivial, for example, to take a file on
stdin, parse the mime structure, examine the content type and
content itself, do encoding transformations, run programs against
individual parts, etc.
-- Jeff Hayward
On Thu, 22 Apr 1999, Pike wrote:
> Don't forget to edit all qmail's config files, startupthingies
> , dotfiles, etc. to change Mailbox into mbox.
>
> I wish I could list exactly what to change where here, but hell,
> qmail has spread itself all across the filesystem randomly.
BTW, I wondered why qmail is not compliant to fsstnd? All the config files
should reside at /etc/qmail, the docs at /usr/doc/qmail or
/usr/local/doc/qmail, the binaries at /usr/bin or /usr/local/bin,
respectively. Only /var/qmail/queue should be placed under /var, perhaps as
/var/qmailq.
The ~/.qmail files I'd suggest to put into ~/etc/qmail, rather than
hiding them among the lots of various other `dotfiles' that you encounter in
users' homes.
Is there good reason to place more or less static files --- not to mention
an application specific hierarchy that could even be put into /opt/qmail
(except for the queue) --- under /var?
GH
[EMAIL PROTECTED] said:
> On Thu, 22 Apr 1999, Pike wrote:
>
> > Don't forget to edit all qmail's config files, startupthingies
> > , dotfiles, etc. to change Mailbox into mbox.
> >
> > I wish I could list exactly what to change where here, but hell,
> > qmail has spread itself all across the filesystem randomly.
Randomly? Surely everything goes in /var/qmail, the exception being users'
.qmail files?
> BTW, I wondered why qmail is not compliant to fsstnd? All the config files
> should reside at /etc/qmail, the docs at /usr/doc/qmail or
> /usr/local/doc/qmail, the binaries at /usr/bin or /usr/local/bin,
> respectively. Only /var/qmail/queue should be placed under /var, perhaps as
> /var/qmailq.
Personally, I prefer having each application in its own directory, with
symlinks from the common locations. This way I can have /opt/app-1.0 and
/opt/app-1.1, with a symlink /opt/app -> app-1.1, then /opt/bin/app ->
/opt/app/bin/app. That qmail prefers to live in /var I can live with. There's
nothing stopping you from installing qmail in /some/other/path, and symlinking
/some/other/path/queue -> /var/qmailq (actually, it would be easier to create
the symlink first, so the queue gets created on the right disk).
> The ~/.qmail files I'd suggest to put into ~/etc/qmail, rather than
> hiding them among the lots of various other `dotfiles' that you encounter
> in users' homes.
The point of putting them in users' home directories is so that the users can
maintain their own aliases without having to bother the sysadmin. This is a
very good thing.
> Is there good reason to place more or less static files --- not to mention
> an application specific hierarchy that could even be put into /opt/qmail
> (except for the queue) --- under /var?
I guess Dan wanted to have everything in one directory, but some of it was
appropriate for /var, so that's where it all went.
--
Peter Haworth [EMAIL PROTECTED]
"Alcohol and calculus don't mix. Don't drink and derive."
[EMAIL PROTECTED] wrote:
>
>BTW, I wondered why qmail is not compliant to fsstnd?
Because qmail runs on many platforms, not just Linux, and because Dan
does things His Way. However, His Way, in this case, is flexible
enough to be made nearly fsstnd compliant.
>All the config files
>should reside at /etc/qmail,
Before installing, do:
# mkdir /var/qmail /etc/qmail
# ln -s /etc/qmail /var/qmail/control
>the docs at /usr/doc/qmail or
>/usr/local/doc/qmail,
# mkdir /usr/doc/qmail
# ln -s /usr/doc/qmail /var/qmail/doc
>the binaries at /usr/bin or /usr/local/bin,
# ln -s /usr/bin /var/qmail
>respectively. Only /var/qmail/queue should be placed under /var, perhaps as
>/var/qmailq.
# mkdir /var/qmailq
# ln -s /var/qmail/queue
>The ~/.qmail files I'd suggest to put into ~/etc/qmail, rather than
>hiding them among the lots of various other `dotfiles' that you encounter in
>users' homes.
I can't agree with you there. They belong in the user's home
directory.
>Is there good reason to place more or less static files --- not to mention
>an application specific hierarchy that could even be put into /opt/qmail
>(except for the queue) --- under /var?
Dan puts everying under /var because it's all potentially
system-specific. Even the binaries, since have UID's/GID's compiled
into them.
-Dave
On Fri, 23 Apr 1999, Peter Haworth wrote:
> [EMAIL PROTECTED] said:
> > On Thu, 22 Apr 1999, Pike wrote:
> >
> > > I wish I could list exactly what to change where here, but hell,
> > > qmail has spread itself all across the filesystem randomly.
>
> Randomly? Surely everything goes in /var/qmail, the exception being users'
> .qmail files?
Pike said `randomly', I'd say, hmm, "sensible, but not compliant to the
standard (and not the way I'd do it)".
> > BTW, I wondered why qmail is not compliant to fsstnd? All the config files
> > should reside at /etc/qmail, the docs at /usr/doc/qmail or
> > /usr/local/doc/qmail, the binaries at /usr/bin or /usr/local/bin,
> > respectively. Only /var/qmail/queue should be placed under /var, perhaps as
> > /var/qmailq.
>
> Personally, I prefer having each application in its own directory, with
> symlinks from the common locations.
I prefer it this, too.
> nothing stopping you from installing qmail in /some/other/path, and symlinking
> /some/other/path/queue -> /var/qmailq (actually, it would be easier to create
> the symlink first, so the queue gets created on the right disk).
Afaik it's not exactly recommended to create numerous symlinks. You'd have
to link really a lot of files to different directories (spreading these
links across the FS `randomly';_). That's what kept me from using links.
And currently I'm not backing up /var since you don't get far with 150MB
tapes these days. Having the binaries and config files installed on a
partition mounted read-only is a much better choice than having them on a
partition that stores files that are often modified. (Of course, qmail
cannot be blamed for missing backups.)
> > The ~/.qmail files I'd suggest to put into ~/etc/qmail, rather than
>
> The point of putting them in users' home directories is so that the users can
> maintain their own aliases without having to bother the sysadmin. This is a
> very good thing.
Hm, what I meant was an `etc' directory in the users home directory, like
`/home/peter/etc', still allowing user to change these files theirselfes
(themselfes?).
> > Is there good reason to place more or less static files --- not to mention
> > an application specific hierarchy that could even be put into /opt/qmail
> > (except for the queue) --- under /var?
>
> I guess Dan wanted to have everything in one directory, but some of it was
> appropriate for /var, so that's where it all went.
Well, I think I'll try to move everything from /var/qmail except for the
queue to /opt then ...
GH
[EMAIL PROTECTED] wrote/schrieb/scribsit:
> Hm, what I meant was an `etc' directory in the users home directory, like
> `/home/peter/etc', still allowing user to change these files theirselfes
> (themselfes?).
See the -/ option to qmail-pw2u.
Stefan
Hey all,
So I have a new qmail install here at my new company. Threw out Exchange
before it was even set up, though after they had paid for it. No worries.
I have Qmail running as it should, been great since last Friday when I set
it up, but yesterday I had 3 seperate events of the following error (as
logged in /var/log/messages):
Apr 22 12:02:43 mailsf inetd[256]: smtp/tcp server failing (looping),
service terminated
This killed everyones ability to connect to our mailserver, and I could not
telnet to port 25 as well. The problem was not with Qmal, but with inetd
itself. A kill -HUP on inetd made the problem go away. It happened 3
times yesterday, but it seemed quite randomly. Hasn't happened again. I
had maybe 10,000 emails go through the server (a PII 400), so load was not
an issue (I have another Qmail setup elsewhere doing 50,000 a day via inetd
- tcpserver is on the plate, but no time yet - not that 50k is alot).
Any ideas what would chop down my port 25 abilities with inetd?
Thanks very much,
Brian
---------------------------------
Brian D. Kohl
Chemconnect, Inc.
415.364.3328
---------------------------------
On Fri, Apr 23, 1999 at 08:26:53AM -0700, Brian D. Kohl wrote:
# Hey all,
#
# So I have a new qmail install here at my new company. Threw out Exchange
# before it was even set up, though after they had paid for it. No worries.
#
# I have Qmail running as it should, been great since last Friday when I set
# it up, but yesterday I had 3 seperate events of the following error (as
# logged in /var/log/messages):
#
# Apr 22 12:02:43 mailsf inetd[256]: smtp/tcp server failing (looping),
# service terminated
this is a common problem, inetd thinks it is being helpful
the best advice is to install tcpserver, its fixed all my problems
--
/- [EMAIL PROTECTED] --------------- [EMAIL PROTECTED] -\
|Justin Bell NIC:JB3084| Time and rules are changing. |
|Pearson | Attention span is quickening. |
|Developer | Welcome to the Information Age. |
\-------- http://www.superlibrary.com/people/justin/ ----------/
On Fri, Apr 23, 1999 at 08:26:53AM -0700, Brian D. Kohl wrote:
> Hey all,
>
> So I have a new qmail install here at my new company. Threw out Exchange
> before it was even set up, though after they had paid for it. No worries.
>
> I have Qmail running as it should, been great since last Friday when I set
> it up, but yesterday I had 3 seperate events of the following error (as
> logged in /var/log/messages):
>
> Apr 22 12:02:43 mailsf inetd[256]: smtp/tcp server failing (looping),
> service terminated
>
> This killed everyones ability to connect to our mailserver, and I could not
> telnet to port 25 as well. The problem was not with Qmal, but with inetd
> itself. A kill -HUP on inetd made the problem go away. It happened 3
> times yesterday, but it seemed quite randomly. Hasn't happened again. I
> had maybe 10,000 emails go through the server (a PII 400), so load was not
> an issue (I have another Qmail setup elsewhere doing 50,000 a day via inetd
> - tcpserver is on the plate, but no time yet - not that 50k is alot).
The standard answer to any question in which "inetd" appears is "Use tcpserver
instead." It would take you just a few minutes to set it up, and if you plan on
using qmail for a while, it's something you're going to do eventually anyway.
Maybe Dan could insert this in the .qmail file that handles this list:
| bouncesaying "Use tcpserver instead." grep -q inetd
Chris
>The standard answer to any question in which "inetd" appears is "Use
tcpserver
>instead." It would take you just a few minutes to set it up, and if you
plan on
>using qmail for a while, it's something you're going to do eventually anyway.
---> Thanks to the 7 responses I just got saying use tcpserver. It shall
be done.
>Maybe Dan could insert this in the .qmail file that handles this list:
>| bouncesaying "Use tcpserver instead." grep -q inetd
---> DOH! You're probably right, though.
Brian
---------------------------------
Brian D. Kohl
Chemconnect, Inc.
415.364.3328
---------------------------------
inetd natively sucks. Get tcpserver from DJB's page.
If you need help setting that up, hit the FAQ, then hit the mailling list
archive, then hit the list if all else fails.
Hope this helps.
Reid Sutherland
Network Administrator
ISYS Technology Inc.
http://www.isys.ca
Fingerprint: 1683 001F A573 B6DF A074 0C96 DBE0 A070 28BE EEA5
-----Original Message-----
From: Brian D. Kohl <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Friday, April 23, 1999 11:32 AM
Subject: inetd-smtp/tcp problem
>Hey all,
>
>So I have a new qmail install here at my new company. Threw out Exchange
>before it was even set up, though after they had paid for it. No worries.
>
>I have Qmail running as it should, been great since last Friday when I set
>it up, but yesterday I had 3 seperate events of the following error (as
>logged in /var/log/messages):
>
>Apr 22 12:02:43 mailsf inetd[256]: smtp/tcp server failing (looping),
>service terminated
>
>This killed everyones ability to connect to our mailserver, and I could not
>telnet to port 25 as well. The problem was not with Qmal, but with inetd
>itself. A kill -HUP on inetd made the problem go away. It happened 3
>times yesterday, but it seemed quite randomly. Hasn't happened again. I
>had maybe 10,000 emails go through the server (a PII 400), so load was not
>an issue (I have another Qmail setup elsewhere doing 50,000 a day via inetd
>- tcpserver is on the plate, but no time yet - not that 50k is alot).
>
>Any ideas what would chop down my port 25 abilities with inetd?
>
>Thanks very much,
>Brian
>
>
>---------------------------------
>Brian D. Kohl
>Chemconnect, Inc.
>415.364.3328
>---------------------------------
>
luca- we use qmail here and twig works just fine.
did you make a link from /usr/bin/sendmail to the apropriate qmail equivalent?
did you remove sendmail from your system?
allan
Luca Pescatore <[EMAIL PROTECTED]> said:
> Hi,
> My name i Luca PEscatore, and \'m newbie in Qmail. At this moment after
> setting up Qmail 1.03 \'m trying to install a Web-mail solution (TWIG), but
> i have a \"big\" problem. When i try to send a Mail i don\'t receive nothing.
>
> What\'s up ? How can i check if mail is delivered ?
>
> Best Regards,
> Luca Pescatore
>
--
test
Here's a wacky little bug/feature?? that cost me some sleep. One of my users
was having trouble sending mail from his M$ Outlook client to certain
addresses. The failure message in the log file looked like
failure:
Sorry,_I_couldn't_find_any_host_named_bm.arthurandersen.com???._(#5.1.2)
So I proceeded to double check the host name, my local DNS and everything I
could think of. Then just for kicks I thought I'd try sending a message to
that host. It worked fine. Now I was confused! Well a bit more testing
revealed that when the user set up their M$ Outlook address book they had
somehow added trailing spaces to the address.
I have a couple of questions. First is there any good reason that Qmail
isn't trimming the trailing (and possibly leading) spaces for the address?
Second is there anything I can do to prevent thin in the future?
Finally I'd suggest that someone look into changing the error message. It
looked to me like Qmail was just adding the ???'s to the end of the message
to indicate that it couldn't find the host.
--Dave
Dave Teske writes:
> I have a couple of questions. First is there any good reason that Qmail
> isn't trimming the trailing (and possibly leading) spaces for the address?
Because it shouldn't.
> Second is there anything I can do to prevent thin in the future?
Actually, what Qmail should do is to reject that address as a recipient
address up front, telling the luser to fix it.
--
Sam
On Fri, 23 Apr 1999 16:40:44 GMT, Sam wrote:
>Actually, what Qmail should do is to reject that address as a recipient
>address up front, telling the luser to fix it.
Outlook express talks SMTP to qmail. It should _send_ correctly. IMHO,
code to check syntax is wasted in qmail, unless required for function.
In this case, all that would result is a [maybe] easier-to-interpret
error message.
-Sincerely, Fred
Fred Lindberg, Inf. Dis., WashU, St. Louis, MO, USA
Any ideas?
The log shows new/info/end entries, but no "delivery" entries, and
the messages aren't sitting in the queue.
-Dave
------- Start of forwarded message -------
From: [EMAIL PROTECTED] (Armand)
Newsgroups: comp.mail.misc,comp.os.linux.networking,comp.os.linux.setup
Subject: Re: Linux qmail lost - help dummy!
Date: 23 Apr 1999 02:34:47 GMT
Organization: XS4ALL Internet BV
Message-ID: <7fom87$9ph$[EMAIL PROTECTED]>
References: <7fnilk$k85$[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
In article <[EMAIL PROTECTED]>,
Dave Sill writes:
> No entries containing the string "delivery"? Sounds
> they're still in the queue. What do qmail-qstat and qmail-qread say?
NOPE
just those three lines, on every attempt
qmail-qstat and qmail-qread only report a few 17 Apr mails, stuck there
from trials during setup. I append the messages at the end. Looks like my
mails did not make it to the queue.
I have ls-checked the whole queue directory, only those old messages.
I've done the same thing over again. fetchmail gets the mails, but they are
nowhere to be found. I ran fetchmail with the verbal option, there was one
error message:
<skip>
fetchmail: POP3< +OK 1049 octets
reading message 1 of 1 (1049 bytes)
fetchmail: about to deliver with: /var/qmail/bin/sendmail
#***********fetchmail: message 1 was not the expected length (1066 != 1049)
flushed
fetchmail: POP3> DELE 1
fetchmail: POP3< +OK Message deleted
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Goodbye
fetchmail: normal termination, status 0
looks like this happens when fetchmail passes the file to qmail. The same
three messages are again logged in /var/log/messages.
Anybody an idea where I can look further?
Thanks for tips!
Armand
PS for my e-mail take the reply-to-one and remove nospam part
reports:
# /var/qmail/bin/qmail-qstat
messages in queue: 6
messages in queue but not yet preprocessed: 0
<etc, skipped>
# qmail-qread
17 Apr 1999 03:23:52 GMT #36964 254 <[EMAIL PROTECTED]>
remote [EMAIL PROTECTED]
<skip>
rc-file:
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start ./Maildir/ splogger qmail
------- End of forwarded message -------
On Fri, Apr 23, 1999 at 12:36:11PM -0400, Dave Sill wrote:
} Any ideas?
}
} The log shows new/info/end entries, but no "delivery" entries, and
} the messages aren't sitting in the queue.
I remember about six months ago that fetchmail changed its behavior
and I lost some mail when I upgraded, because "localhost" wasn't in
the rcpthosts of my linuxppc box. In my case, since I have a fixed
IP, I simply added "smtphost schinder.clark.net" to my .fetchmailrc
and things started working. Fetchmail doesn't seem to be able to deal
with bounces. The logs are long gone, so I don't know what the log
entries looked like.
You also need "forcecr" in the .fetchmailrc, but that's well
documented.
}
} -Dave
}
} ------- Start of forwarded message -------
} From: [EMAIL PROTECTED] (Armand)
} Newsgroups: comp.mail.misc,comp.os.linux.networking,comp.os.linux.setup
} Subject: Re: Linux qmail lost - help dummy!
} Date: 23 Apr 1999 02:34:47 GMT
} Organization: XS4ALL Internet BV
} Message-ID: <7fom87$9ph$[EMAIL PROTECTED]>
} References: <7fnilk$k85$[EMAIL PROTECTED]>
} <[EMAIL PROTECTED]>
} Reply-To: [EMAIL PROTECTED]
} Mime-Version: 1.0
} Content-Type: text/plain; charset=iso-8859-1
}
} In article <[EMAIL PROTECTED]>,
} Dave Sill writes:
} > No entries containing the string "delivery"? Sounds
} > they're still in the queue. What do qmail-qstat and qmail-qread say?
} NOPE
} just those three lines, on every attempt
}
} qmail-qstat and qmail-qread only report a few 17 Apr mails, stuck there
} from trials during setup. I append the messages at the end. Looks like my
} mails did not make it to the queue.
}
} I have ls-checked the whole queue directory, only those old messages.
}
} I've done the same thing over again. fetchmail gets the mails, but they are
} nowhere to be found. I ran fetchmail with the verbal option, there was one
} error message:
}
} <skip>
} fetchmail: POP3< +OK 1049 octets
} reading message 1 of 1 (1049 bytes)
} fetchmail: about to deliver with: /var/qmail/bin/sendmail
} #***********fetchmail: message 1 was not the expected length (1066 != 1049)
} flushed
} fetchmail: POP3> DELE 1
} fetchmail: POP3< +OK Message deleted
} fetchmail: POP3> QUIT
} fetchmail: POP3< +OK Goodbye
} fetchmail: normal termination, status 0
}
} looks like this happens when fetchmail passes the file to qmail. The same
} three messages are again logged in /var/log/messages.
}
} Anybody an idea where I can look further?
}
} Thanks for tips!
}
} Armand
} PS for my e-mail take the reply-to-one and remove nospam part
}
} reports:
} # /var/qmail/bin/qmail-qstat
} messages in queue: 6
} messages in queue but not yet preprocessed: 0
} <etc, skipped>
} # qmail-qread
} 17 Apr 1999 03:23:52 GMT #36964 254 <[EMAIL PROTECTED]>
} remote [EMAIL PROTECTED]
} <skip>
} rc-file:
} exec env - PATH="/var/qmail/bin:$PATH" \
} qmail-start ./Maildir/ splogger qmail
}
} ------- End of forwarded message -------
--
--------
Paul J. Schinder
NASA Goddard Space Flight Center
[EMAIL PROTECTED]
If you send a message with no recipients to qmail-queue you get this
log sequence:
% qmail-inject -n </dev/null
Return-Path: <[EMAIL PROTECTED]>
Date: 23 Apr 1999 17:08:23 -0000
Message-ID: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
Cc: recipient list not shown: ;
% qmail-inject </dev/null; sleep 1; tail -3 log
924887121.550401 new msg 39
924887121.558213 info msg 39: bytes 228 from <[EMAIL PROTECTED]> qp 18130 uid
268
924887121.616803 end msg 39
-- Jeff Hayward
[sorry about the premature copy sent to you, Dave]
On 23 Apr 1999, Dave Sill wrote:
Any ideas?
The log shows new/info/end entries, but no "delivery" entries, and
the messages aren't sitting in the queue.
-Dave
------- Start of forwarded message -------
From: [EMAIL PROTECTED] (Armand)
Newsgroups: comp.mail.misc,comp.os.linux.networking,comp.os.linux.setup
Subject: Re: Linux qmail lost - help dummy!
Date: 23 Apr 1999 02:34:47 GMT
Organization: XS4ALL Internet BV
Message-ID: <7fom87$9ph$[EMAIL PROTECTED]>
References: <7fnilk$k85$[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
In article <[EMAIL PROTECTED]>,
Dave Sill writes:
> No entries containing the string "delivery"? Sounds
> they're still in the queue. What do qmail-qstat and qmail-qread say?
NOPE
just those three lines, on every attempt
qmail-qstat and qmail-qread only report a few 17 Apr mails, stuck there
from trials during setup. I append the messages at the end. Looks like my
mails did not make it to the queue.
I have ls-checked the whole queue directory, only those old messages.
I've done the same thing over again. fetchmail gets the mails, but they are
nowhere to be found. I ran fetchmail with the verbal option, there was one
error message:
<skip>
fetchmail: POP3< +OK 1049 octets
reading message 1 of 1 (1049 bytes)
fetchmail: about to deliver with: /var/qmail/bin/sendmail
#***********fetchmail: message 1 was not the expected length (1066 != 1049)
flushed
fetchmail: POP3> DELE 1
fetchmail: POP3< +OK Message deleted
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Goodbye
fetchmail: normal termination, status 0
looks like this happens when fetchmail passes the file to qmail. The same
three messages are again logged in /var/log/messages.
Anybody an idea where I can look further?
Thanks for tips!
Armand
PS for my e-mail take the reply-to-one and remove nospam part
reports:
# /var/qmail/bin/qmail-qstat
messages in queue: 6
messages in queue but not yet preprocessed: 0
<etc, skipped>
# qmail-qread
17 Apr 1999 03:23:52 GMT #36964 254 <[EMAIL PROTECTED]>
remote [EMAIL PROTECTED]
<skip>
rc-file:
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start ./Maildir/ splogger qmail
------- End of forwarded message -------
On Thu, 22 Apr 1999, Andy Walden wrote:
> > >> What is it about extension addresses that bothers you?
> > >
> > >Its probably not fully understanding what they do yet.
> >
> > I understand, but one shouldn't go around hacking out functionality
> > just because they don't understand it. Do you remove commands from
> > /bin that you don't fully understand?
>
> Yes come to think of it. Its not out of line for me to chmod 0 a command
> unless it can deem itself worthy, I especially pull this on suid stuff.
> Kinda scary eh :)
If you want to disable extension addresses, look at 'man qmail-users'.
If you remove all the + lines in users/assign (except for the initial +
line for alias), then no-one will be able to use extension addresses,
except alias.
> > >I also am
> > >responsible for teaching a tech crew how to get around this once I move it
> > >over and when a call comes in where mail is disappearing, they can't do a
> > >sendmail -v and some of the traditional processes so I would like to keep
> > >some very basic rules like all aliases are in /etc/aliases, users can't
> > >make up variations of their username and have them work as email
> > >addresses, etc....
> >
> > What about those pesky .qmail (or .forward) files? Your tech crew
> > might not be able to follow them. Are you going to outlaw them, too?
>
> sendmail -v follows those around and lays out the whole story.
>
> > That's not a good test for system administration decisions. By
> > reducto ad absurdum you'd end up with no system to administer. Sure,
> > that'd be "easier", but you'd be out of a job.
>
> I'm in no shortage of b.s. to put up with. I could come up with witty
> replies for the rest of it, but I get the idea and this thread is turning
> into something else. Thanks for the help.
>
> -andy
>
>
>
--
"Life is much too important to be taken seriously."
Thomas Erskine <[EMAIL PROTECTED]> (613) 998-2836
I am setting up several domains and hundreds of pop3 boxes
using Qmail and . My question is about the smtp daemon. I
need to be able to allow all users the ability to access the
mail server for the smtp feature (Imagine an employee of a
company that I am hosting for, they need a smtp server to
send mail.
I do not want to allow spammers to spoof their addresses and
to use our machine. But in the same retrospect, I need to
allow any and all IPs to connect.
I've seen in the past some smtp servers that actually
restricted the use of the server for relaying mail if the
From: @host.com did not match what it had set in its
configuration files. Yes even though a spammer can spoof
his From: @host.com address to match what I had and send
mail, I'll deal with this when it arrives. Is Qmail's smtpd
configurable to just allow mail relay if from @host.com as
specified in one of its configuration files?
If so, could someone explain (because I'm a novice at Qmail
and its documentation is very much lacking. But it's
supports group like this that make it such a good product)
the procedure to do so?
- I am not using the mailrelay thing, should I be? (How do
I? Heh)
- I've setup multiple boxes using a single UID per Paul
Gregg's directions.
- I'm using tcpserver for both smtp and pop3.
Any advice would greatly be helpful!
Thanks in advance,
Eric
On Fri, Apr 23, 1999 at 01:22:43PM -0400, Duncan, Eric A. wrote:
> I am setting up several domains and hundreds of pop3 boxes
> using Qmail and . My question is about the smtp daemon. I
> need to be able to allow all users the ability to access the
> mail server for the smtp feature (Imagine an employee of a
> company that I am hosting for, they need a smtp server to
> send mail.
>
> I do not want to allow spammers to spoof their addresses and
> to use our machine. But in the same retrospect, I need to
> allow any and all IPs to connect.
>
> I've seen in the past some smtp servers that actually
> restricted the use of the server for relaying mail if the
> From: @host.com did not match what it had set in its
> configuration files. Yes even though a spammer can spoof
> his From: @host.com address to match what I had and send
> mail, I'll deal with this when it arrives. Is Qmail's smtpd
> configurable to just allow mail relay if from @host.com as
> specified in one of its configuration files?
You'll need a patch to make qmail-smtpd do this. Try
http://www.palomine.net/qmail/relaymailfrom.html
Most people on this list will tell you that controlling relaying based on
envelope sender is a bad thing to do, but you appear to be aware of the risks.
Chris
Ok, I've got a domain that has a total of 3 MX records, one of which is a
high numbered me.
what do I put in the various control files so that my server will accept the
Email then move it off to the higher priority MX hosts?
them.org MX 10 imailrelay.them.org
them.org MX 100 mx.me.net
them.org MX 20 smtpgw.them.org
I'm the 100, and other than be a place that's better connected than them, I
have nothing to do with their Email.
Thanks in advance..
Greg
On Fri, Apr 23, 1999 at 12:35:04PM -0500, Greg Moeller wrote:
>
> Ok, I've got a domain that has a total of 3 MX records, one of which is a
> high numbered me.
> what do I put in the various control files so that my server will accept the
> Email then move it off to the higher priority MX hosts?
> them.org MX 10 imailrelay.them.org
> them.org MX 100 mx.me.net
> them.org MX 20 smtpgw.them.org
>
> I'm the 100, and other than be a place that's better connected than them, I
> have nothing to do with their Email.
them.org should be in control/rcpthosts *only*. That's the only configuration
required.
Chris
Hello all!
I got my qmail running quite well with single user ID POP and relaying
controlled with tcpserver. Is there any possibility to force the
tcpserver to send a special message, when denying a connection??
I thought of something like: Sorry, you're not allowed to relay on this
server.
Regards,
Holger
On Fri, Apr 23, 1999 at 07:28:01PM +0200, Holger wrote:
> Hello all!
>
> I got my qmail running quite well with single user ID POP and relaying
> controlled with tcpserver. Is there any possibility to force the
> tcpserver to send a special message, when denying a connection??
> I thought of something like: Sorry, you're not allowed to relay on this
> server.
qmail-smtpd already sends this message:
553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)
I've always thought that was a lousy message. For one thing, "rcpthosts" isn't
a word, and the only people to whom "rcpthosts" has any significance are qmail
administrators, who are not generally the recipients of the message.
If you want to change the message to something more sensible, edit line 53 of
qmail-smtpd.c and recompile.
By the way, you said you want this sent when tcpserver is "denying a
connection." tcpserver shouldn't be denying any connections--it's qmail-smtpd,
after tcpserver has allowed the connection, that decides it doesn't want to
accept a recipient.
Chris
At 02:48 PM 4/22/99 +0200, Giulio Orsero wrote:
>On Thu, 22 Apr 1999 15:56:24 -0300 (GMT+3), hai scritto:
>
>
>>Well, can I use a domain name as a second part? As example:
>>
>>foo.com:foo1.com
>>
>>Will then qmail send mail to [EMAIL PROTECTED] to [EMAIL PROTECTED] ?
>
>No, try this instead:
>
>virtualdomains:
>foo.com:alias-foo
>
>~alias/.qmail-foo-default
>|forward $[EMAIL PROTECTED]
>
>Ciao.
>
>--
>Giulio
>[EMAIL PROTECTED]
>
Actually, it might just be a whole lot easier to go in to the qmail user's
directory, and edit the .qmail file to say "&[EMAIL PROTECTED]"
Regards,
Julian L.C. Brown
Interware.Net Inc.
mailto:[EMAIL PROTECTED]
http://www.interware.net
On Fri, 23 Apr 1999 14:04:46 -0400, hai scritto:
>>>Well, can I use a domain name as a second part? As example:
>>>foo.com:foo1.com
>>>Will then qmail send mail to [EMAIL PROTECTED] to [EMAIL PROTECTED] ?
>>
>>No, try this instead:
>>
>>virtualdomains:
>>foo.com:alias-foo
>>
>>~alias/.qmail-foo-default
>>|forward $[EMAIL PROTECTED]
>Actually, it might just be a whole lot easier to go in to the qmail user's
>directory, and edit the .qmail file to say "&[EMAIL PROTECTED]"
I thought he wanted to do this for every user at foo.com, and that "bob" was
just an example; so it would be quite time consuming to edit every user's
.qmail file :-)
If he need that only for 1 user than your solution is certainly easier.
Ciao.
--
Giulio
[EMAIL PROTECTED]
Where can I find out exactly what the gazintas/gazoutas are for
checkpassword? I need to use a non-standard user/password file, and
have to modify a login program to work for the pop logins.
On Fri, Apr 23, 1999 at 02:32:13PM -0400, Mark Bitting wrote:
> Where can I find out exactly what the gazintas/gazoutas are for
> checkpassword? I need to use a non-standard user/password file, and
> have to modify a login program to work for the pop logins.
The best thing to do is probably to download
ftp://koobera.math.uic.edu/www/software/checkpassword-0.81.tar.gz and examine
the checkpassword.c source file. It's really very straightforward.
I've written a couple of patches to the above to make checkpassword use a
separate POP user/password file (one a flat text file and the other a cdb
database). It was done with a minumum of fuss.
Chris
Mark Bitting writes:
> Where can I find out exactly what the gazintas/gazoutas are for
> checkpassword? I need to use a non-standard user/password file, and
> have to modify a login program to work for the pop logins.
Look at the second paragraph of http://www.qmail.org/top.html#checkpassword
--
-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.
> Look at the second paragraph of http://www.qmail.org/top.html#checkpassword
I had hoped this was documented somewhere... I'm a microcontroller
assembly language programmer, I have conceptual problems with a language
that has no test-and-branch instructions and seems to consist mainly of
the shifted top row of the keyboard. Oh well, time to dust off the
trusty old K&R book and go reinvent the wheel. Thanks for the pointers,
I'll blunder through.
Mark Bitting
Mark Bitting writes:
> > Look at the second paragraph of http://www.qmail.org/top.html#checkpassword
>
> I had hoped this was documented somewhere...
Sure -- in checkpassword.8.
--
-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.
Hi,
I am new to linux email server. It is ashamed that I have to ask this
stupid question.
I have qmail installed, but I don't know how to setup user accounts for my
users to use my qmail server. Could anyone please guide me? Thank you
very much.
Sincerely,
Sherrill
---------------------------------
Sherrill (Pei-chih) Verbrugge
Right To Life Of Michigan
[EMAIL PROTECTED]
Hello All-
Okay, for starters, I'm relatively new to Unix administration (Solaris
2.6/sparc, more specifically) and Qmail, so please bear with me here. Be
warned, verbose=on.
The Setup:
------------
We have a Solaris box, with www.domain1.com as the primary hostname, set up
with QMail. Tcpserver is not installed, in case that matters. We have a
virtual domain pointed to that same box with its own IP, which we'll call
domain2.com. That domain is listed in the control/virtualhosts and
control/rcpthosts files. And yes, Qmail has been told to reload the
virtualdomains and rcpthosts files. Our Solaris box came setup without a
/etc/named.boot file, if that matters, so we have no MX records on that
machine (we're using /etc/hosts). Our ISP is taking care of setting up our
MX records upstream.
The Problem:
------------
When I send e-mail to domain2.com from our internal company network, it
shows up just fine, with no problems. When I try to send mail to domain2.com
from outside of our network, nothing happens. No errors, nothing in the
domain1.com logs and no bounces--until about a week later when I get a
message from the external network's mail server saying it could not connect
to the host for domain2.com. Mail to domain1.com from outside our network
comes in just dandy.
What I've found:
----------------
After beginning to question whether our ISP had the proper MX records set
up, I discovered the wonderful Dig tool (yes, I am still learning the
wonders of Unix!). A query on the MX records of domain2.com indicated that
they were forwarding all mail for domain2.com to mail.domain2.com, which
they actually pointed (without telling us) to the domain2.com IP address
*not* the domain1.com IP, which QMail was installed under. Still with me? I
tried adding mail.domain2.com to our locals file and rebooting ro no avail.
The Inevitable Newbie Questions:
--------------------------------
1) Do they need to point mail.domain2.com to the IP of domain1.com for qmail
to catch the domain2.com mail? In other words, does QMail only listen to the
primary machine IP address? I have a sneaking suspicion this is the case.
2) If not, even though our ISP has MX records set up to forward the
domain2.com e-mail to our domain1.com machine, do I still need to create MX
records on the domain1.com machine? This wasn't clear to me in the FAQ.
3) Is there anything else I may be overlooking that could be causing this?
I would really appreciate any help or suggestions you all might be able to
provide.
Thanks,
Bret Van Horn
--------------------------------
Communi(k), Inc.
On Fri, Apr 23, 1999 at 01:08:01PM +0100, Bret Van Horn wrote:
> Hello All-
>
> Okay, for starters, I'm relatively new to Unix administration (Solaris
> 2.6/sparc, more specifically) and Qmail, so please bear with me here. Be
> warned, verbose=on.
>
> The Setup:
> ------------
> We have a Solaris box, with www.domain1.com as the primary hostname, set up
> with QMail. Tcpserver is not installed, in case that matters. We have a
> virtual domain pointed to that same box with its own IP, which we'll call
> domain2.com.
Why call it domain2.com? Why not call it what it is?
> That domain is listed in the control/virtualhosts and control/rcpthosts
> files. And yes, Qmail has been told to reload the virtualdomains and
> rcpthosts files. Our Solaris box came setup without a /etc/named.boot file,
> if that matters, so we have no MX records on that machine (we're using
> /etc/hosts). Our ISP is taking care of setting up our MX records upstream.
>
> The Problem:
> ------------
> When I send e-mail to domain2.com from our internal company network, it
> shows up just fine, with no problems. When I try to send mail to domain2.com
> from outside of our network, nothing happens. No errors, nothing in the
> domain1.com logs and no bounces--until about a week later when I get a
> message from the external network's mail server saying it could not connect
> to the host for domain2.com. Mail to domain1.com from outside our network
> comes in just dandy.
*Please* don't sanitize your DNS information by using fictitious domain names.
If a DNS problem is the source of your troubles, there's no way anyone on the
list can discover that.
> What I've found:
> ----------------
> After beginning to question whether our ISP had the proper MX records set
> up, I discovered the wonderful Dig tool (yes, I am still learning the
> wonders of Unix!). A query on the MX records of domain2.com indicated that
> they were forwarding all mail for domain2.com to mail.domain2.com, which
> they actually pointed (without telling us) to the domain2.com IP address
> *not* the domain1.com IP, which QMail was installed under. Still with me? I
> tried adding mail.domain2.com to our locals file and rebooting ro no avail.
When you say "forwarding all mail for domain2.com to mail.domain2.com," do you
mean that they have the MX record for domain2.com pointing to the machine
mail.domain2.com? And what does "which they actually pointed (without telling
us) to the domain2.com IP address" mean? This is where having real domain names
would help. I suspect you've got a problem with CNAME records here, but without
the real names I can't check.
> The Inevitable Newbie Questions:
> --------------------------------
> 1) Do they need to point mail.domain2.com to the IP of domain1.com for qmail
> to catch the domain2.com mail? In other words, does QMail only listen to the
> primary machine IP address? I have a sneaking suspicion this is the case.
That's definitely not the case--qmail doesn't listen to anything at all. You
said you're not using tcpserver, so I assume you're using inetd, so it's inetd
that's doing the listening. I don't know much about inetd, but I'd suspect that
unless you told it to do otherwise it'll listen on all your interfaces.
> 2) If not, even though our ISP has MX records set up to forward the
> domain2.com e-mail to our domain1.com machine, do I still need to create MX
> records on the domain1.com machine? This wasn't clear to me in the FAQ.
>
> 3) Is there anything else I may be overlooking that could be causing this?
>
> I would really appreciate any help or suggestions you all might be able to
> provide.
Provide the real names of your domains, and someone will be able to tell you
within seconds whether things are correct or need fixing.
Chris
Okay, sorry about sanitizing the names: domain1.com = www.communik.com
(207.170.212.4), domain2.com = cknewsletters.com (207.170.212.2)
mail.cknewsletters.com uses the .2 IP.
As for the MX records, here they are:
; <<>> DiG 2.0 <<>> mx cknewsletters.com
;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 7
;; flags: qr rd ra ; Ques: 1, Ans: 1, Auth: 2, Addit: 3
;; QUESTIONS:
;; cknewsletters.com, type = MX, class = IN
;; ANSWERS:
cknewsletters.com. 78612 MX 0 mail.cknewsletters.com.
;; AUTHORITY RECORDS:
cknewsletters.com. 78612 NS svr2.gstis.net.
cknewsletters.com. 78612 NS svr1.gstis.net.
;; ADDITIONAL RECORDS:
mail.cknewsletters.com. 78612 A 207.170.212.2
svr2.gstis.net. 10800 A 207.170.196.62
svr1.gstis.net. 10800 A 207.170.196.61
;; Sent 2 pkts, answer found in time: 9 msec
;; FROM: cobalt to SERVER: default -- 127.0.0.1
;; WHEN: Fri Apr 23 13:28:02 1999
;; MSG SIZE sent: 35 rcvd: 151
I hope this helps. :)
-Bret
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, April 24, 1999 3:21 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: MX, IPs and QMail
>
>
> On Fri, Apr 23, 1999 at 01:08:01PM +0100, Bret Van Horn wrote:
> >> Hello All-
> >>
> >> Okay, for starters, I'm relatively new to Unix administration (Solaris
> >> 2.6/sparc, more specifically) and Qmail, so please bear with
> me here. Be
> >> warned, verbose=on.
> >>
> >> The Setup:
> >> ------------
> >> We have a Solaris box, with www.domain1.com as the primary hostname,
> >set up
> >> with QMail. Tcpserver is not installed, in case that matters. We have a
> >> virtual domain pointed to that same box with its own IP, which we'll
> >call
> >> domain2.com.
>
> Why call it domain2.com? Why not call it what it is?
>
> >> That domain is listed in the control/virtualhosts and control/rcpthosts
> >> files. And yes, Qmail has been told to reload the virtualdomains and
> >> rcpthosts files. Our Solaris box came setup without a /etc/named.boot
> >file,
> >> if that matters, so we have no MX records on that machine (we're using
> >> /etc/hosts). Our ISP is taking care of setting up our MX records
> >upstream.
> >>
> >> The Problem:
> >> ------------
> >> When I send e-mail to domain2.com from our internal company network, it
> >> shows up just fine, with no problems. When I try to send mail to
> >domain2.com
> >> from outside of our network, nothing happens. No errors, nothing in the
> >> domain1.com logs and no bounces--until about a week later when I get a
> >> message from the external network's mail server saying it could not
> >connect
> >> to the host for domain2.com. Mail to domain1.com from outside our
> >network
> >> comes in just dandy.
>
> *Please* don't sanitize your DNS information by using fictitious domain
> names.
> If a DNS problem is the source of your troubles, there's no way anyone on
> the
> list can discover that.
>
> >> What I've found:
> >> ----------------
> >> After beginning to question whether our ISP had the proper MX records
> >set
> >> up, I discovered the wonderful Dig tool (yes, I am still learning the
> >> wonders of Unix!). A query on the MX records of domain2.com indicated
> >that
> >> they were forwarding all mail for domain2.com to
> mail.domain2.com, which
> >> they actually pointed (without telling us) to the domain2.com
> IP address
> >> *not* the domain1.com IP, which QMail was installed under. Still with
> >me? I
> >> tried adding mail.domain2.com to our locals file and rebooting ro no
> >avail.
>
> When you say "forwarding all mail for domain2.com to mail.domain2.com," do
> you
> mean that they have the MX record for domain2.com pointing to the machine
> mail.domain2.com? And what does "which they actually pointed (without
> telling
> us) to the domain2.com IP address" mean? This is where having real domain
> names
> would help. I suspect you've got a problem with CNAME records here, but
> without
> the real names I can't check.
>
> >> The Inevitable Newbie Questions:
> >> --------------------------------
> >> 1) Do they need to point mail.domain2.com to the IP of domain1.com for
> >qmail
> >> to catch the domain2.com mail? In other words, does QMail only listen
> >to the
> >> primary machine IP address? I have a sneaking suspicion this is the
> >case.
>
> That's definitely not the case--qmail doesn't listen to anything at all.
> You
> said you're not using tcpserver, so I assume you're using inetd, so it's
> inetd
> that's doing the listening. I don't know much about inetd, but I'd suspect
> that
> unless you told it to do otherwise it'll listen on all your interfaces.
>
> >> 2) If not, even though our ISP has MX records set up to forward the
> >> domain2.com e-mail to our domain1.com machine, do I still need to
> >create MX
> >> records on the domain1.com machine? This wasn't clear to me in the FAQ.
> >>
> >> 3) Is there anything else I may be overlooking that could be causing
> >this?
> >>
> >> I would really appreciate any help or suggestions you all might be able
> >to
> >> provide.
>
> Provide the real names of your domains, and someone will be able to tell
> you
> within seconds whether things are correct or need fixing.
>
> Chris
>
>
> --- Internet Message Header Follows ---
> Received: from muncher.math.uic.edu (131.193.178.181)
> by communik.com (FirstClass Mail Server v5.11)
> transient id 116; 1:22:39 PM -0700
> Received: (qmail 8576 invoked by uid 1002); 23 Apr 1999 20:21:15 -0000
> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
> Precedence: bulk
> Delivered-To: mailing list [EMAIL PROTECTED]
> Received: (qmail 21362 invoked from network); 23 Apr 1999 20:21:15 -0000
> Received: from shemp.palomine.net ([EMAIL PROTECTED])
> by muncher.math.uic.edu with SMTP; 23 Apr 1999 20:21:15 -0000
> Received: (qmail 25764 invoked by uid 1000); 23 Apr 1999 20:21:29 -0000
> Date: Fri, 23 Apr 1999 16:21:29 -0400
> From: Chris Johnson <[EMAIL PROTECTED]>
> To: Bret Van Horn <[EMAIL PROTECTED]>
> Cc: Qmail List <[EMAIL PROTECTED]>
> Subject: Re: MX, IPs and QMail
> Message-ID: <[EMAIL PROTECTED]>
> References: <000701be8d81$eefa9610$0e06a8c0@bret>
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> X-Mailer: Mutt 0.95.4i
> In-Reply-To: <000701be8d81$eefa9610$0e06a8c0@bret>; from Bret Van Horn on
> Fri, Apr 23, 1999 at 01:08:01PM +0100
>
Hello all
I know this list is using Qmail with EZMLM. I am trying to install Qmail
on my system. The prerequite for this is to have a working DNS.
My home LAN has a bogus domainname. It uses the private (10.x.x.x )
addressing scheme. Would Qmail work with a bogus domainname?
Will it translate the bogus domainname to my ISP's name?
Any experiences and advice appreciated.
Thank you in advance.
Subba Rao
[EMAIL PROTECTED]
==============================================================
Disclaimer - I question and speak for myself.
On Fri, 23 Apr 1999, Subba Rao wrote:
> Hello all
>
> I know this list is using Qmail with EZMLM. I am trying to install Qmail
> on my system. The prerequite for this is to have a working DNS.
>
> My home LAN has a bogus domainname. It uses the private (10.x.x.x )
> addressing scheme. Would Qmail work with a bogus domainname?
Yes, provided you set it up correctly.
> Will it translate the bogus domainname to my ISP's name?
You will need to enter the IP addresses of all your machines into
control/smtproutes, and arrange to have reverse-DNS lookups appropriately
handled by tcpserver (whether by patching tcpserver to use gethostby...,
or by disabling reverse DNS lookups entirely).
Yes, I'm replying to my own stuff... but it's for update purposes only!
[snip on qmail configuration...]
Everything I had listed was correct and working (thanks, all!!! ;-)
...but...
>And finally, this is what I have in /var/qmail/alias/envtest.pl:
>
>#!/usr/local/bin/perl
[proggie snip]
>foreach $quack (@ENV) {
> print Q "\$ENV - $quack = $ENV{$quack}\n";
>}
This little code fragment is supposed to print all of the environment
variables that are passed to perl from the .qmail file. Unforch, there are
none. I even modified the proggie in several ways trying to output explicit
environment variables hardcoded in the program... nothing flows.
I've changed the .qmail-frazzlespork-default file to read this:
|echo $SENDER>>/var/qmail/alias/zztest.txt
|/var/qmail/alias/envtest.pl
and $SENDER is accurately echoed & appended to the file.
What am I forgetting to get the environment variables passed to perl?
Thanks for your continuing help,
Roger "Merch" Merchberger
--
Roger "Merch" Merchberger --- sysadmin, Iceberg Computers
Recycling is good, right??? Ok, so I'll recycle an old .sig.
If at first you don't succeed, nuclear warhead
disarmament should *not* be your first career choice.
Re: my Perl code...
I found the problem -- funny what errors you see when you step away from
the problem for a 1/2 hour!!!
Thanks again, and if anyone's interested in what I did, just let me know.
Roger "Merch" Merchberger
--
Roger "Merch" Merchberger --- sysadmin, Iceberg Computers
Recycling is good, right??? Ok, so I'll recycle an old .sig.
If at first you don't succeed, nuclear warhead
disarmament should *not* be your first career choice.
We have a dedicated shell/users server so people can log in
and grab mail, etc.
We also have a dedicated pop3 and smtp server running qmail.
I would like to be able to configure pine on the shell
server to use the pop3 and smtp servers running qmail.. but
am having a problem with the "from" line...
Example:
Running pine 4.10 on Slackware 3.6.
log on shell as username: bigbob
run pine
prompts for username on pop3 server (defaults to bigbob)
press enter, all is good.. BUT!
If I enter a _different_ pop3 username _while_ logged onto
the shell server as bigbob, the return/from line is always
bigbob and not what the user entered for the pop3 username.
Any ideas?
Thanks,
Brad
Americanisp, LLC.
