qmail Digest 11 May 1999 10:00:00 -0000 Issue 637

Topics (messages 25395 through 25435):

configuration questions
        25395 by: Achim Gosse <[EMAIL PROTECTED]>
        25396 by: Anand Buddhdev <[EMAIL PROTECTED]>

qmail-smtpd start error!
        25397 by: Achim Gosse <[EMAIL PROTECTED]>

qmail doesn't accept any connections on port 25
        25398 by: Achim Gosse <[EMAIL PROTECTED]>
        25399 by: "Soffen, Matthew" <[EMAIL PROTECTED]>
        25400 by: Chris Johnson <[EMAIL PROTECTED]>
        25402 by: Achim Gosse <[EMAIL PROTECTED]>
        25403 by: Achim Gosse <[EMAIL PROTECTED]>

how do I purge the queue ?
        25401 by: "Claudiu Balciza" <[EMAIL PROTECTED]>

Setting up Qmail for the first time
        25404 by: Doug Lumpkin <[EMAIL PROTECTED]>

strange problems with qmail on OpenBSD-current
        25405 by: Pavel Korovin <[EMAIL PROTECTED]>

qmail doesn't accept any messages
        25406 by: Achim Gosse <[EMAIL PROTECTED]>
        25411 by: Achim Gosse <[EMAIL PROTECTED]>

secondary MX
        25407 by: "Matt Buford" <[EMAIL PROTECTED]>

Qmail as an IMail replacement
        25408 by: Jonathan W Herbert <[EMAIL PROTECTED]>
        25410 by: Peter Gradwell <[EMAIL PROTECTED]>

pine and maildir
        25409 by: "Adam D. McKenna" <[EMAIL PROTECTED]>

Mail receiving problems
        25412 by: "Damir Cosic" <[EMAIL PROTECTED]>

piping mail to news server
        25413 by: Samuel Dries-Daffner <[EMAIL PROTECTED]>

Qmail to procmail and back again?
        25414 by: Ralf Nagel <[EMAIL PROTECTED]>

procmail issues
        25415 by: xs <[EMAIL PROTECTED]>
        25416 by: Peter van Dijk <[EMAIL PROTECTED]>
        25417 by: Andy Walden <[EMAIL PROTECTED]>
        25418 by: xs <[EMAIL PROTECTED]>
        25426 by: xs <[EMAIL PROTECTED]>

setting relay clients
        25419 by: Jari Tenhunen <[EMAIL PROTECTED]>
        25427 by: Wilson Fletcher <[EMAIL PROTECTED]>
        25435 by: Jari Tenhunen <[EMAIL PROTECTED]>

Host unknown
        25420 by: "x" <[EMAIL PROTECTED]>
        25429 by: "x" <[EMAIL PROTECTED]>

smtproutes failover
        25421 by: Jason <[EMAIL PROTECTED]>
        25422 by: Chris Johnson <[EMAIL PROTECTED]>

root mail
        25423 by: David McCall <[EMAIL PROTECTED]>
        25424 by: Peter van Dijk <[EMAIL PROTECTED]>
        25430 by: "Robin Bowes" <[EMAIL PROTECTED]>

Fundamental flaws in List-Unsubscribe
        25425 by: "D. J. Bernstein" <[EMAIL PROTECTED]>

Is there a similar feature to sendmail's 'access_db' macro ?
        25428 by: "Yusuf Goolamabbas" <[EMAIL PROTECTED]>

How can I purge the queue
        25431 by: "Claudiu Balciza" <[EMAIL PROTECTED]>
        25433 by: Anand Buddhdev <[EMAIL PROTECTED]>

Qmail changing From: field
        25432 by: [EMAIL PROTECTED]
        25434 by: Anand Buddhdev <[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]


----------------------------------------------------------------------


Title: configuration questions

hello,

i'm new to qmail and i have some questions about it.
i heard, that qmail is an espacially safe mta. so i want to install it as an email gateway for my firewall.
my configuration looks like this:
-internet---firewall (ipchains)/qmail---exchange-

i want qmail to get all our mail from our internet service provider an to forward them to the exchange server behind the firewall and vice versa.

how can i configure qmail to do that?
i'm using maquerading behind the firewall, is that a problem?


thanks in advance

achim





On Mon, May 10, 1999 at 12:26:54PM +0200, Achim Gosse wrote:

>    i'm new to qmail and i have some questions about it.
>    i heard, that qmail is an espacially safe mta. so i want to install it
>    as an email gateway for my firewall.
>    my configuration looks like this:
>    -internet---firewall (ipchains)/qmail---exchange-
>    
>    i want qmail to get all our mail from our internet service provider an
>    to forward them to the exchange server behind the firewall and vice
>    versa.

Setup qmail on the firewall as per the instructions. Then put in your
domain name in control/rcpthosts. Now qmail will accept mail for your
domain. Then setup control/smtproutes like this:

your.domain.com:[IP.address.of.exchange.server]

This takes care of incoming mail. For outgoing mail, setup Exchange to use
the qmail as a smarthost. On the firewall, arrange to run qmail-smtpd so
accept relayed messages from the Exchange server. See:

http://qmail-docs.surfdirect.com.au/docs/qmail-antirelay.html

for instructions on how to setup qmail-smtpd safely.

-- 
System Administrator
See complete headers for address, homepage and phone numbers




Title: qmail-smtpd start error!

--- [EMAIL PROTECTED] ---
926346923.348859 supervise: fatal: unable to acquire lock: temporary failure
------

what's wrong???

achim





Title: qmail doesn't accept any connections on port 25

hello,

i've installed qmail like it is described in the qmail faq.
internal mail deliviery is running fine, but qmail doesn't get any emails from outside and doesn't accept any connections per telnet on port 25 (telnet localhost 25).

any hints?

thanks in advance
achim





can you give some more data ?

What does the mail log say ?

How do you start qmail.  what is the command line you use to start qmail
?  What is in your inetd.conf file for SMTP ?



> -----Original Message-----
> From: Achim Gosse [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, May 10, 1999 11:00 AM
> To:   '[EMAIL PROTECTED]'
> Subject:      qmail doesn't accept any connections on port 25
> 
> hello, 
> i've installed qmail like it is described in the qmail faq. 
> internal mail deliviery is running fine, but qmail doesn't get any
> emails from outside and doesn't accept any connections per telnet on
> port 25 (telnet localhost 25).
> any hints? 
> thanks in advance 
> achim 




On Mon, May 10, 1999 at 05:00:21PM +0200, Achim Gosse wrote:
> hello,
> 
> i've installed qmail like it is described in the qmail faq.
> internal mail deliviery is running fine, but qmail doesn't get any emails
> from outside and doesn't accept any connections per telnet on port 25
> (telnet localhost 25).

How do you start qmail-smtpd? From tcpserver or inetd? If from inetd, did you
remember to SIGHUP inetd after changing your inetd.conf file?

Chris




Title: AW: qmail doesn't accept any connections on port 25

i start qmail by tcpserver.

i got the rc script by the qmail faq website and i made my changes.

the log says, that rblsmtpd is missing.

i've installed ucspi-tcp-0.84 and daemontools-0.53, like described in the howtos.

what went wrong? where can i get that file?


achim





Title: AW: AW: AW: qmail doesn't accept any connections on port 25

> > PATH=$PATH:/usr/local/bin:/var/qmail/bin
> > USERID=1001    # CHANGE THIS TO YOUR QMAILD UID!!!
> > GROUPID=101  # CHANGE THIS TO YOUR NOFILES GID!!!
> >
> > case "$1" in
> >     start)
> >         echo -n "Starting mail-transfer agent: qmail"
> >         ulimit -v 2048
> >
> >         csh -cf '/var/qmail/rc &'
> >
> >         supervise /var/lock/qmail-smtpd tcpserver -v
> -x/etc/tcp.smtp.cdb
> > -u$USER
> > ID -g$GROUPID 0 25 \
> >         rblsmtpd qmail-smtpd 2>&1 | setuser qmaill accustamp | \
>
> I'm not familiar with this script, but I think it should work
> if you just
> remove "rblsmtpd" from the line above.
>
> Chris
>


tanks! it works fine now!

achim





(qmail 1.03/RedHat5.2/kernel 2.2.5)

Hi,

Whenever I tweak with my firewall rules, qmail fails to deliver messages
(that's ok).
I can see them on the queue.
But when it retries to send those certain deffered messages it fails again.
I tried sending a new message with the exact to/from/subject/content and it
left in no time while the old one still stays in the queue.
I even forced the delivery by hand (to no avail)

How can I purge the queue ?

Claudiu






Also make sure you have a /var/qmail/control/me file that reads:
your.hostname.com
If this isn't in there, qmail just seems to disappear...
--
Doug Lumpkin
PacInfo Internet
[EMAIL PROTECTED]



Charles Zealey wrote:

> Everybody tells me how easy it is to set up but frankly I'm struggling.  I
> think I've followed all the instructions (several times) but when I come to
> run Qmail-start it just disappears without trace.  Please, how can I find
> out where it has gone and why?
>
> Charles








Solved.
Brain damage. The core of the problem was not-working qbiff
and misconfigured vmailmgr - i used these programs to 
execute from .qmail.
Just 8 hours of sleep - and the problem was solved :)
What a shame!!!
Sorry. 
---
Pavel Korovin
 SMTP: [EMAIL PROTECTED]
 PSTN: +7 (095) 721-26-00




Title: qmail doesn't accept any messages

--- [EMAIL PROTECTED] ---
926351484.770763 tcpserver: status: 1/40
926351484.771106 tcpserver: pid 10118 from 62.132.88.21
926351484.773343 tcpserver: ok 10118 firewall.nasa20.com:62.132.88.11:25 :62.132
.88.21::3051
926351487.004716 tcpserver: end 10118 status 0
926351487.004776 tcpserver: status: 0/40
--- end ---

hmm... instead qmail accepts telnet on port 25, it still doesn't accept any messages.
heres what the logfile says.

the smtp client reports an 503 error (smtp server not ready for data)


any ideas?


btw: the mx records are fine.


thanks in advance.
achim


achim Gosse  mailto:[EMAIL PROTECTED]
n.a.s.a.2.0 gmbh     http://www.nasa20.com
borselhof   borselstr. 16c   22765 hamburg
speak.+49.40.39888288  fax.+49.40.39888299
icq.#3139144          cell.+49.177.3180433
registered linux user #122734





Title: qmail doesn't accept any messages

sorry, that was a firewall problem.

 

achim

 

 --- [EMAIL PROTECTED] ---
926351484.770763 tcpserver: status: 1/40
926351484.771106 tcpserver: pid 10118 from 62.132.88.21
926351484.773343 tcpserver: ok 10118 firewall.nasa20.com:62.132.88.11:25 :62.132
.88.21::3051
926351487.004716 tcpserver: end 10118 status 0
926351487.004776 tcpserver: status: 0/40
--- end ---

hmm... instead qmail accepts telnet on port 25, it still doesn't accept any messages.
heres what the logfile says.

the smtp client reports an 503 error (smtp server not ready for data)


any ideas?


btw: the mx records are fine.


thanks in advance.
achim





Well the main thing I can say is don't share secondary MX with other
services.  I've seen it happen many times where an ISP does secondary MX for
a downstream (perhaps on ISDN) mail server.  That mail server gets
mailbombed, and becomes unreachable.  Now the attack moves over to take out
your server too.  If you put secondary MX on a box by itself thats fine, but
often people share it with a web server or something, and the box is
hammered by the attack moving over to the secondary...

----- Original Message -----
From: Efgé <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, May 08, 1999 10:44 AM
Subject: Re: secondary MX


> Thanks for all your answers.
>
>
> > I didn't see your explanation of the problem that you expect to solve
> > with a secondary MX record, though.
>
> Oh right, now I remember that a number of you people are against the use
> of secondary MX. Could you restate your reasons ? Have you had by
> experience with them ?
>
> Would you also hold the same position against an _intelligent_ secondary
> MX that could do mail distribution exactly like the primary (but this
> was not the point of my original question).
>
> Basically, I think I'd rather have a secondary MX because I'd rather
> have mail queued at my end than at sender's end, where I don't control
> delay before bounce, queue reliability, and so on.
>
> Also, if I remember well, you stated that secondary MX was even
> unnecessary in the case of service outage on the primary due to
> maintenance, given that mail will wait at the other end. Again, I'd
> rather have mail wait at my end. Maybe this is a misguided attempt at
> controling too much ?
>





Hello,

I'm working on migrating the email for some 160+
domains over to qmail from IMail (NT). I've used qmail
in the past, but never for something this large in scale.

I imagine at some point, you could even do maildir delivery
with load-balanced mail servers to something like a netapp,
but i digress.

My problem is that the majority of these users are `real' users,
in that they need to pop for their mail, as well as be able to
send mail through this new host.

I'm having trouble understanding if this is possible, although i imagine

it is. If i'm correct, every user that wants to pop for his mail must
have an account on the machine? If thats true, how will i distinguish
between [EMAIL PROTECTED], and [EMAIL PROTECTED] ? If I'm incorrect in this
assumption, how do i tell qmail where the pop users mail resides?

I'm having a hard time with this, any light you could shed on this
would be great.

Thanks,

Jonathan

--
Jonathan W. Herbert
Senior Systems Engineer
--------------------------------------------
Tortus Tek, Inc.
1789 Northampton Street  Phone:(413)535-5080
Holyoke, Ma.  01040      URL: tortus-tek.com
--------------------------------------------
Tortus Tek: A-head of Art, A-head of Science




At 9:29 am -0700 10/5/99,the wonderful Jonathan W Herbert wrote:

>My problem is that the majority of these users are `real' users,
>in that they need to pop for their mail, as well as be able to
>send mail through this new host.
>
>I'm having trouble understanding if this is possible, although i imagine

check out 'single uid' pop3 -

http://www.tibus.net/pgregg/projects/qmail/single-uid-howto.txt.

peter.

--
peter at gradwell dot com; http://www.gradwell.com/
gradwell dot com Ltd. Enabling the internet you don't see.

** Cheap and easy ecommerce: http://www.gradwell.net/ **




I have been distributing the c-client library patch from my website
(http://www.flounder.net/qmail/) for quite a while now.  My question is, has
anyone updated this patch so that it works with the newest version of pine?
Is anyone willing to?  The current patch works on pine 3.96, which is a
rather old version.

As a secondary note, is UW planning on adding Maildir support to pine at any
time?  It would seem that this would be a worthwhile feature.

--Adam






I am running Red Hat 5.2 and tried to replace sendmail with qmail but
experienced some problems. Installation went pretty smoothly, but when it 
came to test, it failed.

Well, maybe failure is not correct word, since I didn't get an error 
message, but I didn't get what I expected either. I tried to send mail 
locally, as described in TEST.receive, by telnet to port 25, but I never got 
anything in the Mailbox. Now, as I said, no error messages in maillog, but 
delivery - success field is incomplete. Here are messages from maillog:

May  8 11:51:03 localhost qmail: 926185863.365457 new msg 471059
May  8 11:51:03 localhost qmail: 926185863.365600 info msg 471059: bytes 208 
from <> qp 680 uid 7791
May  8 11:51:03 localhost qmail: 926185863.456627 starting delivery 2: msg 
471059 to local @hal.utah-inter.net
May  8 11:51:03 localhost qmail: 926185863.456721 status: local 1/10 remote 
0/20
May  8 11:51:03 localhost qmail: 926185863.457687 delivery 2: success:
May  8 11:51:03 localhost qmail: 926185863.457768 status: local 0/10 remote 
0/20
May  8 11:51:03 localhost qmail: 926185863.457829 end msg 471059

Then I tried remote-to-local test, it failed too, but this time with an 
error message:


May  8 12:38:25 localhost qmail: 926188705.179383 new msg 471059
May  8 12:38:25 localhost qmail: 926188705.179510 info msg 471059: bytes 
1106 from <[EMAIL PROTECTED]> qp 1961 uid 7791
May  8 12:38:25 localhost qmail: 926188705.270538 starting delivery 4: msg 
471059 to remote dcosic@localhost
May  8 12:38:25 localhost qmail: 926188705.270639 status: local 0/10 remote 
1/20
May  8 12:38:25 localhost qmail: 926188705.926201 delivery 4: failure: 
Sorry._Although_I'm_listed_as_a_best-preference_MX_or_A_for_that_host,/it_isn't_in_my_control/locals_file,_so_I_don't_treat_it_as_local._(#5.4.6)/
May  8 12:38:25 localhost qmail: 926188705.926338 status: local 0/10 remote 
0/20
May  8 12:38:26 localhost qmail: 926188706.041654 bounce msg 471059 qp 1963
May  8 12:38:26 localhost qmail: 926188706.041985 end msg 471059

After this followed message about bounce mail, which was sent successfully.

Well I don't what else to say or what else information could help solving 
this problem. During installation I followed instructions from INSTALL.* 
files. I didn't try any 'fancy' stuff, except masquerading host name. Host 
name is hal.utah-inter.net and utah-inter.net is my ISP's domain. One more 
thing. I don't know if qmail-local is supposed to be running all the time, 
but when I run ps, I get this:

  367  ?  S    0:00 qmail-lspawn ./Mailbox
  366  ?  S    0:00 splogger qmail
  369  ?  S    0:00 qmail-clean
  368  ?  S    0:00 qmail-rspawn
  355  ?  S    0:00 qmail-send

Well that's all. On the end of the file I included output from qmail-showctl 
if you need to know more about qmail configuration. I hope somebody can help 
me solve this problem. I don't feel like using
hotmail any more!
Thanks.

Damir

qmail home directory: /var/qmail.
user-ext delimiter: -.
paternalism (in decimal): 2.
silent concurrency limit: 120.
subdirectory split: 23.
user ids: 7790, 7791, 7792, 0, 7793, 7794, 7795, 7796.
group ids: 2108, 2107.

badmailfrom: (Default.) Any MAIL FROM is allowed.
bouncefrom: (Default.) Bounce user name is MAILER-DAEMON.
bouncehost: (Default.) Bounce host name is hal.utah-inter.net.
concurrencylocal: (Default.) Local concurrency is 10.
concurrencyremote: (Default.) Remote concurrency is 20.
databytes: (Default.) SMTP DATA limit is 0 bytes.
defaultdomain: (Default.) Default domain name is hal.utah-inter.net.
defaulthost: (Default.) Default host name is hal.utah-inter.net.
doublebouncehost: (Default.) 2B recipient host: hal.utah-inter.net.
doublebounceto: (Default.) 2B recipient user: postmaster.
envnoathost: (Default.) Presumed domain name is hal.utah-inter.net.
helohost: (Default.) SMTP client HELO host name is hal.utah-inter.net.
idhost: (Default.) Message-ID host name is hal.utah-inter.net.
localiphost: (Default.) Local IP address becomes hal.utah-inter.net.
locals: (Default.) Messages for me are delivered locally.
me: My name is hal.utah-inter.net.
percenthack: (Default.) The percent hack is not allowed.
plusdomain: (Default.) Plus domain name is hal.utah-inter.net.
qmqpservers: (Default.) No QMQP servers.
queuelifetime: (Default.) Message lifetime in the queue is 604800 seconds.
rcpthosts: (Default.) SMTP clients may send messages to any recipient.
morercpthosts: (Default.) No rcpthosts; morercpthosts is irrelevant.
morercpthosts.cdb: (Default.) No effect.
smtpgreeting: (Default.) SMTP greeting: 220 hal.utah-inter.net.
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: [EMAIL PROTECTED]:[EMAIL PROTECTED]



_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com





Here is a simple program I wrote that pipes email messages to a news
server. We are testing out the idea of concurrent qmail aliases and
local news groups and this program has been very useful. I have added the
following to a .qmail alias file:

| /usr/local/bin/q2news.pl NEWS.SERVER.HERE NEWS.GROUP.HERE

It calls the q2news.pl program whose code follows. The program requires
two perl modules which are easily found at your favorite CPAN site.

Please send me any ideas or comments, and I can add features and a README
for more formal distribution etc.

Enjoy,

Samuel Daffner
Mills College ITS
Oakland, CA


#!/usr/local/bin/perl -w
#
# q2news.pl -- Pipes mail messages to news groups
# 
# by Samuel Daffner, [EMAIL PROTECTED]
# updated 5.7.99
#
########################

$news_server = @ARGV[0];
$news_group  = @ARGV[1];

@body=<STDIN>;

########################

use Mail::Internet;
  $mail    = Mail::Internet->new(\@body);
  $subject = $mail->get('Subject');
  $from    = $mail->get('From');

@header=("Newsgroups: $news_group");
@header=(@header,"From: $from","Subject: $subject");

########################

use News::NNTPClient;
  $c = new News::NNTPClient("$news_server");
  $c->post(@header, "", @body)|| print "Error posting:$!\n";

  __END__





Hi,

is it possible to handle incoming mail to procmail for
further processing (for example corrections of redundant
Reply-to lines or bad subject lines: the german AW: unstead
of Re: etc) and then give it back to qmail for delivery
in a maildir?

Thanks,

Ralf





hey all, i recently tried going back to some procmail scripts i had before
and am getting the follow error:

May 10 14:33:36 rhino qmail: 926360703.993456 new msg 253997
May 10 14:33:36 rhino qmail: 926360704.000787 info msg 253997: bytes 228
from <[EMAIL PROTECTED]> qp 1299 uid 500
May 10 14:33:36 rhino qmail: 926360704.008772 starting delivery 54: msg
253997 to local [EMAIL PROTECTED]
May 10 14:33:36 rhino qmail: 926360704.008901 status: local 1/10 remote
0/20
May 10 14:33:36 rhino qmail: 926360704.206914 delivery 54: success:
procmail:_Couldn't_create_"/var/spool/mail/xs"/did_0+0+1/
May 10 14:33:36 rhino qmail: 926360704.207090 status: local 0/10 remote
0/20
May 10 14:33:36 rhino qmail: 926360704.207155 end msg 253997 


thats cuz there is no /var/spool/mail
$MAIL is set to $HOME/Mailbox
none the less, if i mkdir /var/spool/mail, and ln -s $HOME/Maildir
/var/spool/mail/$USER, it says it's a bogus file and renames it. 
so i went back and set some vars in $HOME/.procmailrc:
PATH=/bin:/usr/bin:/usr/bin:$PATH
ORGMAIL=$HOME/Mailbox
MAILDIR=$HOME/mail
DEFAULT=$HOME/Mailbox   #completely optional
LOGFILE=$MAILDIR/procmail.log

:0 Wh: msgid.lock
| formail -D 8192 msgid.cache

:0:
* ^From.*xs*
/home/xs/xs666


nothing much wrong there. heres $HOME/mail/procmail.log:
>From [EMAIL PROTECTED] Mon May 10 18:25:27 1999
  Folder: /home/xs/xs666
348

(14:29:12)(xs@rhino)(~/mail)$ echo $MAIL
/home/xs/Mailbox

(14:29:58)(xs@rhino)(~)$ cat ~/.qmail-test1
|preline procmail

? any ideas?


end
+-------------------------------------+
|Greg Albrecht   KF4MKT   [EMAIL PROTECTED]|
|Safari Internet        www.safari.net|
|Fort Lauderdale, FL    1-888-537-9550|
+-------------------------------------+





On Mon, May 10, 1999 at 02:30:57PM -0400, xs wrote:
> 
> hey all, i recently tried going back to some procmail scripts i had before
> and am getting the follow error:
> 
> none the less, if i mkdir /var/spool/mail, and ln -s $HOME/Maildir
> /var/spool/mail/$USER, it says it's a bogus file and renames it. 

Ofcourse it is. procmail doesn't do Maildir.

Greetz, Peter
-- 
| 'He broke my heart,    |                              Peter van Dijk |
     I broke his neck'   |                     [EMAIL PROTECTED] |
   nognikz - As the sun  |        Hardbeat@ircnet - #cistron/#linux.nl |
                         | Hardbeat@undernet - #groningen/#kinkfm/#vdh |




On Mon, 10 May 1999, Peter van Dijk wrote:

> On Mon, May 10, 1999 at 02:30:57PM -0400, xs wrote:
> > 
> > hey all, i recently tried going back to some procmail scripts i had before
> > and am getting the follow error:
> > 
> > none the less, if i mkdir /var/spool/mail, and ln -s $HOME/Maildir
> > /var/spool/mail/$USER, it says it's a bogus file and renames it. 
> 
> Ofcourse it is. procmail doesn't do Maildir.

Though there is a version on the qmail page that does and works well.

andy






ecuse me
that should be $HOME/Mailbox


end
+-------------------------------------+
|Greg Albrecht   KF4MKT   [EMAIL PROTECTED]|
|Safari Internet        www.safari.net|
|Fort Lauderdale, FL    1-888-537-9550|
+-------------------------------------+

On Mon, 10 May 1999, Peter van Dijk wrote:

>On Mon, May 10, 1999 at 02:30:57PM -0400, xs wrote:
>> 
>> hey all, i recently tried going back to some procmail scripts i had before
>> and am getting the follow error:
>> 
>> none the less, if i mkdir /var/spool/mail, and ln -s $HOME/Maildir
>> /var/spool/mail/$USER, it says it's a bogus file and renames it. 
>
>Ofcourse it is. procmail doesn't do Maildir.
>
>Greetz, Peter
>-- 
>| 'He broke my heart,    |                              Peter van Dijk |
>     I broke his neck'   |                     [EMAIL PROTECTED] |
>   nognikz - As the sun  |        Hardbeat@ircnet - #cistron/#linux.nl |
>                         | Hardbeat@undernet - #groningen/#kinkfm/#vdh |
>






i figured out a solution, in $HOME/.qmail-test1 
i put:
|preline procmail -m /home/xs/.procmailrc

and it seems to work.

-xs


end
+-------------------------------------+
|Greg Albrecht   KF4MKT   [EMAIL PROTECTED]|
|Safari Internet        www.safari.net|
|Fort Lauderdale, FL    1-888-537-9550|
+-------------------------------------+

On Mon, 10 May 1999, xs wrote:

>
>hey all, i recently tried going back to some procmail scripts i had before
>and am getting the follow error:
>
>May 10 14:33:36 rhino qmail: 926360703.993456 new msg 253997
>May 10 14:33:36 rhino qmail: 926360704.000787 info msg 253997: bytes 228
>from <[EMAIL PROTECTED]> qp 1299 uid 500
>May 10 14:33:36 rhino qmail: 926360704.008772 starting delivery 54: msg
>253997 to local [EMAIL PROTECTED]
>May 10 14:33:36 rhino qmail: 926360704.008901 status: local 1/10 remote
>0/20
>May 10 14:33:36 rhino qmail: 926360704.206914 delivery 54: success:
>procmail:_Couldn't_create_"/var/spool/mail/xs"/did_0+0+1/
>May 10 14:33:36 rhino qmail: 926360704.207090 status: local 0/10 remote
>0/20
>May 10 14:33:36 rhino qmail: 926360704.207155 end msg 253997 
>
>
>thats cuz there is no /var/spool/mail
>$MAIL is set to $HOME/Mailbox
>none the less, if i mkdir /var/spool/mail, and ln -s $HOME/Maildir
>/var/spool/mail/$USER, it says it's a bogus file and renames it. 
>so i went back and set some vars in $HOME/.procmailrc:
>PATH=/bin:/usr/bin:/usr/bin:$PATH
>ORGMAIL=$HOME/Mailbox
>MAILDIR=$HOME/mail
>DEFAULT=$HOME/Mailbox   #completely optional
>LOGFILE=$MAILDIR/procmail.log
>
>:0 Wh: msgid.lock
>| formail -D 8192 msgid.cache
>
>:0:
>* ^From.*xs*
>/home/xs/xs666
>
>
>nothing much wrong there. heres $HOME/mail/procmail.log:
>>From [EMAIL PROTECTED] Mon May 10 18:25:27 1999
>  Folder: /home/xs/xs666
>348
>
>(14:29:12)(xs@rhino)(~/mail)$ echo $MAIL
>/home/xs/Mailbox
>
>(14:29:58)(xs@rhino)(~)$ cat ~/.qmail-test1
>|preline procmail
>
>? any ideas?
>
>
>end
>+-------------------------------------+
>|Greg Albrecht   KF4MKT   [EMAIL PROTECTED]|
>|Safari Internet        www.safari.net|
>|Fort Lauderdale, FL    1-888-537-9550|
>+-------------------------------------+
>
>





Hope I didn't post this twice...

The problem is that I can't make qmail accept relayclients.
I did everything like they say in Qmail FAQ #5.4 but qmail-smtpd still 
rejects any relay attempts. I get messages saing the domain is not listed
in rcpthosts. And I thought setting RELAYCLIENT would cause
qmail-smtpd to relay without reading rcpthosts... Do I have to recompile
tcp_wrappers or something ??
        However, there seems to be something odd in the way qmail-smtpd
behaves: After putting "all: all:deny" into /etc/hosts.deny
(/etc/hosts.allow still contained the line "tcp-env: etc...") port 25
refused to answer at all. It didn't answer even if put "tcp-env: all:
allow" in /etc/hosts.allow. Weird.

some conf files:
--->8---

/etc/hosts.allow:
ALL: 127.0.0.1, 192.168.0.0/255.255.255.0 : allow

tcp-env: 127.0.0.1, 192.168.0.1, 192.168.0.2: setenv RELAYCLIENT

# tried also:
# tcp-env: 127.0.0.1, 192.168.0.1, 192.168.0.2: setenv = RELAYCLIENT
# tcp-env: 127.0.0.1, 192.168.0.1, 192.168.0.2: setenv = RELAYCLIENT ""
# tcp-env: 127.0.0.1, 192.168.0.1, 192.168.0.2: setenv RELAYCLIENT ""

--->8---

/etc/hosts.deny:
#ALL: ALL: deny

--->8---
/etc/inetd.conf:
smtp    stream  tcp     nowait  qmaild  /usr/sbin/tcpd /var/qmail/bin/tcp-env 
/var/qmail/bin/qmail-smtpd

--->8---

my system:
AMD K6@233 / Linux 2.2.7 / RedHat 6.0
qmail-1.03 (compiled from sources)
tcp_wrappers-7.6-7 (i386 rpm binary)



A very desperate admin,
-- 
Jari Tenhunen - [EMAIL PROTECTED]
                                        
                                                        Stardate [-30]2959.10





1) Make sure tcp-wrappers are installed. Mine were I'm using RedHat 5.1 
with kernel 2.034

2) You must modify your inetd.conf as specified in the FAQ. I used inetd I 
did not use TCP wrappers

3) You must edit your hosts.allow as indicated in your email. Try putting 
the IP of your computer only just to test it.

4) Correct me if I'm wrong but if you put "all: all: deny" into 
/etc/hosts/deny aren't you denying all services ? My hosts.deny is empty.

5) I still had problems and so I restarted the Linux box (call me a 
philistine). After that all was OK. (ie. I didn't have success in getting 
it to register the changes to hosts.allow without restarting.)

Probably doesn't help but hope it does.

Wilson Fletcher

On Monday, May 10, 1999 8:06 PM, Jari Tenhunen 
[SMTP:[EMAIL PROTECTED]] wrote:
> Hope I didn't post this twice...
>
> The problem is that I can't make qmail accept relayclients.
> I did everything like they say in Qmail FAQ #5.4 but qmail-smtpd still
> rejects any relay attempts. I get messages saing the domain is not listed
> in rcpthosts. And I thought setting RELAYCLIENT would cause
> qmail-smtpd to relay without reading rcpthosts... Do I have to recompile
> tcp_wrappers or something ??
>         However, there seems to be something odd in the way qmail-smtpd
> behaves: After putting "all: all:deny" into /etc/hosts.deny
> (/etc/hosts.allow still contained the line "tcp-env: etc...") port 25
> refused to answer at all. It didn't answer even if put "tcp-env: all:
> allow" in /etc/hosts.allow. Weird.
>
> some conf files:
> --->8---
>
> /etc/hosts.allow:
> ALL: 127.0.0.1, 192.168.0.0/255.255.255.0 : allow
>
> tcp-env: 127.0.0.1, 192.168.0.1, 192.168.0.2: setenv RELAYCLIENT
>
> # tried also:
> # tcp-env: 127.0.0.1, 192.168.0.1, 192.168.0.2: setenv = RELAYCLIENT
> # tcp-env: 127.0.0.1, 192.168.0.1, 192.168.0.2: setenv = RELAYCLIENT ""
> # tcp-env: 127.0.0.1, 192.168.0.1, 192.168.0.2: setenv RELAYCLIENT ""
>
> --->8---
>
> /etc/hosts.deny:
> #ALL: ALL: deny
>
> --->8---
> /etc/inetd.conf:
> smtp    stream  tcp     nowait  qmaild  /usr/sbin/tcpd 
/var/qmail/bin/tcp-env /var/qmail/bin/qmail-smtpd
>
> --->8---
>
> my system:
> AMD K6@233 / Linux 2.2.7 / RedHat 6.0
> qmail-1.03 (compiled from sources)
> tcp_wrappers-7.6-7 (i386 rpm binary)
>
>
>
> A very desperate admin,
> --
> Jari Tenhunen - [EMAIL PROTECTED]
>
>                                                               Stardate [-30]2959.10




On Tue, 11 May 1999, Wilson Fletcher wrote:

> 1) Make sure tcp-wrappers are installed. Mine were I'm using RedHat 5.1 
> with kernel 2.034

they are. 
 
> 2) You must modify your inetd.conf as specified in the FAQ. I used inetd I 
> did not use TCP wrappers

I made all the changes necessary as you could see in my previous message.

> 3) You must edit your hosts.allow as indicated in your email. Try putting 
> the IP of your computer only just to test it.

I'll try that but it should work with multiple hosts, too.
 
> 4) Correct me if I'm wrong but if you put "all: all: deny" into 
> /etc/hosts/deny aren't you denying all services ? My hosts.deny is empty.

Nope, access is granted when hosts.deny contains "all: all: deny" AND
hosts.allow contains "all: 127.0.0.1: allow". That's the way it works with
other daemons. I tried also with and empty hosts.deny file, no success.

> 5) I still had problems and so I restarted the Linux box (call me a 
> philistine). After that all was OK. (ie. I didn't have success in getting 
> it to register the changes to hosts.allow without restarting.)

Booting was unnecessary. hosts.{allow, deny} are read every time tcpd is
executed ie. when a daemon is started by inetd. So the changes take place
right away.
 
Anyway, back to my problem.
Has anyone succesfully configured selective relay with tcp_wrappers ??
Or do I have to install tcpserver ??

> > The problem is that I can't make qmail accept relayclients.
> > I did everything like they say in Qmail FAQ #5.4 but qmail-smtpd still
> > rejects any relay attempts. I get messages saing the domain is not listed
> > in rcpthosts. And I thought setting RELAYCLIENT would cause
> > qmail-smtpd to relay without reading rcpthosts... Do I have to recompile
> > tcp_wrappers or something ??
> >         However, there seems to be something odd in the way qmail-smtpd
> > behaves: After putting "all: all:deny" into /etc/hosts.deny
> > (/etc/hosts.allow still contained the line "tcp-env: etc...") port 25
> > refused to answer at all. It didn't answer even if put "tcp-env: all:
> > allow" in /etc/hosts.allow. Weird.
> >
> > some conf files:
> > --->8---
> >
> > /etc/hosts.allow:
> > ALL: 127.0.0.1, 192.168.0.0/255.255.255.0 : allow
> >
> > tcp-env: 127.0.0.1, 192.168.0.1, 192.168.0.2: setenv RELAYCLIENT
> >
> > # tried also:
> > # tcp-env: 127.0.0.1, 192.168.0.1, 192.168.0.2: setenv = RELAYCLIENT
> > # tcp-env: 127.0.0.1, 192.168.0.1, 192.168.0.2: setenv = RELAYCLIENT ""
> > # tcp-env: 127.0.0.1, 192.168.0.1, 192.168.0.2: setenv RELAYCLIENT ""
> >
> > --->8---
> >
> > /etc/hosts.deny:
> > #ALL: ALL: deny
> >
> > --->8---
> > /etc/inetd.conf:
> > smtp    stream  tcp     nowait  qmaild  /usr/sbin/tcpd 
> /var/qmail/bin/tcp-env /var/qmail/bin/qmail-smtpd
> >
> > --->8---
> >
> > my system:
> > AMD K6@233 / Linux 2.2.7 / RedHat 6.0
> > qmail-1.03 (compiled from sources)
> > tcp_wrappers-7.6-7 (i386 rpm binary)
> >



-- 
Jari Tenhunen - [EMAIL PROTECTED]
                                        
                                                        Stardate [-30]2961.86





/*
 i installed Memphis package, played around,
 tried sending to my IP and i got back:
 ... Host unknown (Name server: xx.yy.zz.nn: host not found)
 */
 rpm -e [...]; rm -fR /var/queue; rm -fR /etc/tcp*; reinstall ?
would that solve it ? 
any shorter solution ?





 > /*
 >  i installed Memphis package, played around,
 >  tried sending to my IP and i got back:
 >  ... Host unknown (Name server: IP: host not found)
 >  */
 >  rpm -e [...]; rm -fR /var/queue; rm -fR /etc/tcp*; reinstall ?
 > would that solve it ? 
 
  no it didn't.
can anyone provide a solution in next 6hours if i pay ?
trying sendmail, else.






is it possible to something like this in smtproutes?
so that it if it fails trying to send to the first host (10.1.1.1),
qmail
will try sending it to the second host (10.1.1.2).. ive tried this and 
it seems to be just taking whatever entry is last, which isnt the
desired
effect.. :)


domain.com:10.1.1.1
domain.com:10.1.1.2



-- 
=======================================================================
|  Jason Welsh   [EMAIL PROTECTED]   |   If you think there's     |
|                                        |   good in everybody, you   |
|      http://welsh.dynip.com/           |   haven't met everybody.   |
=======================================================================




On Mon, May 10, 1999 at 05:09:25PM -0400, Jason wrote:
> is it possible to something like this in smtproutes?
> so that it if it fails trying to send to the first host (10.1.1.1),
> qmail
> will try sending it to the second host (10.1.1.2).. ive tried this and 
> it seems to be just taking whatever entry is last, which isnt the
> desired
> effect.. :)
> 
> 
> domain.com:10.1.1.1
> domain.com:10.1.1.2

No.

Chris




suppose I want to get mail as root.....
is there a safe way other than routing it to another user?

thankx
dmc





On Mon, May 10, 1999 at 02:35:10PM -0700, David McCall wrote:
> suppose I want to get mail as root.....
> is there a safe way other than routing it to another user?

There is no other way, be it safe or unsafe.

Apart from forwarding to another host ofcourse, or having procmail/binmail
deliver.

Greetz, Peter
-- 
| 'He broke my heart,    |                              Peter van Dijk |
     I broke his neck'   |                     [EMAIL PROTECTED] |
   nognikz - As the sun  |        Hardbeat@ircnet - #cistron/#linux.nl |
                         | Hardbeat@undernet - #groningen/#kinkfm/#vdh |




David McCall wrote:
> 
> suppose I want to get mail as root.....
> is there a safe way other than routing it to another user?

mail to root goes to the alias user (as you obviously know...!)

I use mutt and have the following in my root user's .muttrc:

spoolfile='/var/qmail/alias/Maildir/'

So when I read mail as root I am actually reading the alias maildir.

R.
-- 
Two rules to success in life: 
  1. Don't tell people everything you know.
     -- Sassan Tat




Fred Lindberg writes:
> rfc2369 is the way to do it.

No.

Let's say a user clicks the ``unsubscribe'' button while he's looking at
an old message from the SOS mailing list. What should the MUA do?

RFC 2369 suggests that the MUA follow the List-Unsubscribe instructions
in that message. But what happens when the instructions are out of date?

What the MUA should do is find the most recent subscription confirmation
from the SOS list, and follow the instructions in _that_ message. This
is why I proposed putting a List-ID field into every message; it lets
the MUA reliably keep track of the latest information for each list.

The RFC 2369 List-Unsubscribe syntax might be tolerable for confirmation
messages. But there's no excuse for MUAs to assume that List-Unsubscribe
appears in _every_ message. The MUA support envisioned in RFC 2369 is
not the right thing to do.

---Dan




Hi, I want to setup a front-end which does spam-management to a set of 
qmail boxes and I was wondering if there was a way to get a similar feature 
as sendmail's FEATURE('access_db') which allows one to reject both senders/recipients 
at the SMTP level

Thanks, Yusuf

Yusuf Goolamabbas
[EMAIL PROTECTED]






(qmail 1.03/RedHat5.2/kernel 2.2.5)

Hi,

Whenever I tweak with my firewall rules, qmail fails to deliver messages
(that's ok).
I can see them on the queue.
But when it retries to send those certain deffered messages it fails again.
I tried sending a new message with the exact to/from/subject/content and it
left in no time while the old one still stays in the queue.
I even forced the delivery by hand (to no avail)

How can I purge the queue ?

Claudiu






On Tue, May 11, 1999 at 08:34:54AM +0300, Claudiu Balciza wrote:

Send an ALRM signal to qmail-send. Since you're using Redhat, do this:

# killall -ALRM qmail-send

> (qmail 1.03/RedHat5.2/kernel 2.2.5)
> 
> Hi,
> 
> Whenever I tweak with my firewall rules, qmail fails to deliver messages
> (that's ok).
> I can see them on the queue.
> But when it retries to send those certain deffered messages it fails again.
> I tried sending a new message with the exact to/from/subject/content and it
> left in no time while the old one still stays in the queue.
> I even forced the delivery by hand (to no avail)

-- 
System Administrator
See complete headers for address, homepage and phone numbers




Qmail is changing the "From: " field in the header on all messages sent
out.  The way I read the documentation, it is not supposed to do this.
Can anyone suggest what might be wrong?

Thanks,
Dick Kreutzer
AmeriCom Inc.




On Tue, May 11, 1999 at 02:33:10AM -0600, [EMAIL PROTECTED] wrote:

qmail-smtpd does *not* change the From: header. Your From: header is
probably being altered by qmail-inject. Read the man page to find out more
about header manipulation with qmail-inject.

> Qmail is changing the "From: " field in the header on all messages sent
> out.  The way I read the documentation, it is not supposed to do this.
> Can anyone suggest what might be wrong?
> 
> Thanks,
> Dick Kreutzer
> AmeriCom Inc.

-- 
System Administrator
See complete headers for address, homepage and phone numbers


Reply via email to