qmail Digest 19 Dec 2000 11:00:00 -0000 Issue 1218
Topics (messages 54168 through 54195):
unsubsribe
54168 by: �����
Re: Newbie to qmail
54169 by: Charles Cazabon
Re: Qmail to forward remote mail
54170 by: Charles Cazabon
Re: how to ignore $HOME/.qmail ?
54171 by: Dave Sill
Re: Qmail support in Australia ?
54172 by: Peter Samuel
cyclog...
54173 by: Seby
Re: More on relay problem, something to do with tcpserver
54174 by: Boz Crowther
email list working with ldap ?
54175 by: Marcio Sa
Disable envnoathost?
54176 by: Kris Kelley
54178 by: Charles Cazabon
54179 by: Mark Delany
54180 by: Mike Jackson
54184 by: Kris Kelley
54185 by: Charles Cazabon
501 Badly structured mime attachment
54177 by: John Logiudice
54188 by: David Dyer-Bennet
smtp-auth problem
54181 by: Clemens Hermann
54193 by: Clemens Hermann
Re: qmail scanner
54182 by: Rainer Link
Potentially stupid question about bounces...
54183 by: Kris Kelley
54186 by: Charles Cazabon
relay-ctrl problem
54187 by: Adam Stiles
Trailing Spaces?
54189 by: Adam
odd problem...
54190 by: Jeremy Anthony
A problem with pipes
54191 by: Jim Breton
Life With qmail -- INCOMPLETE ???
54192 by: RAGHVENDRA SHUKLA
How Using IMAP4/POP3
54194 by: Ould
Changing the Received line in header
54195 by: Denis Gasparin
Administrivia:
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
Jeff Jensen <[EMAIL PROTECTED]> wrote:
>
> I have just install qmail + vmailmgr and courier-imap. I have followed the
> how-to document, and haven't had any problems here, but when I reboot my
> machine all qmail service report the error: "svscan is not running".
>
> How can I fix this. I use RH 6.2
Depends how you installed the various packages. The normal methods of
starting qmail services use svscan to monitor them; but as the error message
above says, you're not running svscan.
If you're using /etc/rc.d/init.d type scripts, make sure svscan is started
before any of the other services; this will allow it to be used to start
qmail, qmail-smtpd, etc.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
-----------------------------------------------------------------------
Luiz de Almeida <[EMAIL PROTECTED]> wrote:
> I have an issue in that I have Remote users that need to use my E-Smith Mail
> server and I have toyed with the idea of opening up the box for RELAY but
> have been firmly told not to even consider this.
Your remote users should use their ISP's SMTP server for their outgoing mail.
This is what ISP smarthosts are for. If for some reason this isn't feasible,
you could use controlled relaying (as opposed to being an open relay).
The best solution, in my opinion, is to use an SMTP-after-POP scheme like
Bruce Guenter's relay-ctrl (http://em.ca/~bruceg/relay-ctrl/).
> My next option has been Webmail which I now have working but the last hurdle
> is getting the remote users to login and be able to send.
[...]
> Then I can send a message to any user that has been created on that server
> and is therefore a local user on the LAN. BUT if I try to send a mail to a
> user that is not a user that has been created on the local server i.e. to the
> 'your' being you the readers mail address it does not go. Kind of like it is
> not allowing RELAY although I am under the impression that RELAY is not an
> issue here.
Relaying is most definitely the issue here if your webmail program sends mail
by SMTP, rather than by calling qmail-inject directly. What you probably
need to do is set the RELAYCLIENT environment variable for connections from
127... addresses in your tcpserver tcprules file. See the qmail FAQ for
more information.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
-----------------------------------------------------------------------
Matt Harrington <[EMAIL PROTECTED]> wrote:
>i put this line in /var/qmail/users/assign:
>
>=joe:alias:81:81:/var/qmail/alias:-:joe:
>
>
>but qmail-newu complains:
>
>msg# /var/qmail/bin/qmail-newu
>qmail-newu: fatal: bad format in users/assign
>
>
>what am i doing wrong?
Did you forget to terminate "assign" with a '.' line?
http://www.lifewithqmail.org/lwq.html#qmail-users
[Thanks to Henning Brauer for donating lifewithqmail.org]
-Dave
On Mon, 18 Dec 2000, listmon wrote:
> try [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>
> peter samuels is the person to speak to.
Missed us by 4 months. Both Gordon Rowell (gormand) and myself have
moved to Canada to work for e-smith. Let us put word out on the
grapevine at home in Oz to see if we can find anyone available.
>
> Else for hands off mail server, look to e-smith ( uses qmail as mail
> server )
> we have a number of clients running 4.0 now
> www.e-smith.com
So do we :) Thanks for the plug.
>
> Regards
> Stewart Evans
> Macclinic
> Adelaide
>
>
> ----- Original Message -----
> From: Dennis <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, December 16, 2000 10:20 AM
> Subject: Qmail support in Australia ?
>
>
> > Hi all...
> >
> > I'm in the process of proposing a shift off our current (almost working
> :))
> > email system to qmail and have stumbled upon a small but significant
> > problem.
> >
> > Our IT manager is a non-techi and as such is always looking for the, MS
> > solution... I'm the only *nix guy in the department and have successfully
> > convinced him to move DNS/WEB/Cache/DHCP over to *nix, phew !!! (email is
> > next)
> >
> > The IT manager likes throwing "What happens if you get hit by a bus" at
> > me... well, I get hit by a bus and not a single soul in our IT department
> > can do any Qmail admin.
> >
> > I'd be happy to train them up but I need to also know that commercial
> > support is available in Australia... This is the clincher !!!
> >
> >
> > Cheers
> > Dennis
> >
>
>
--
Regards
Peter
----------
Peter Samuel [EMAIL PROTECTED]
http://www.e-smith.org (development) http://www.e-smith.com (corporate)
Phone: +1 613 368 4398 Fax: +1 613 564 7739
e-smith, inc. 1500-150 Metcalfe St, Ottawa, ON K2P 1P1 Canada
"If you kill all your unhappy customers, you'll only have happy ones left"
From were do i get cyclog.. i instaled daemontools...
But there is no cyclog... should i use multilog insted.. and if so.. how
do i uset it...
Thakyou...
Seby...
---------------
-=Ionita Sebastian=-
http://lapd.cj.edu.ro/~seby
E-mail: [EMAIL PROTECTED]
---------------
The Shuttle is now going five times the sound of speed.
-- Dan Rather, first landing of Columbia
Interesting.
I couldn't check the return from my mailer, since it didn't provide one
(VERY basic utility). Upgrading to a new version of the mailer corrects the
problem, however.
Now, is there any way to resolve the stray-LF problem, short of upgrading
all the workstations on my network?
Thanks.
----- Original Message -----
From: "Charles Cazabon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, December 16, 2000 11:31 AM
Subject: Re: More on relay problem, something to do with tcpserver
> Boz Crowther <[EMAIL PROTECTED]> wrote:
> > Ok, by checking the logs I've determined that from certain clients
(namely a
> > command-line DOS smtp mailer we use) the smtp connection ends before
getting
> > any data, with the following message in
/var/log/qmail/qmail-smtpd/current:
> >
> > tcpserver: end xxx status 256
> [...]
> > Simple question: where can I find out what the end statuses provided by
> > tcpserver mean?
>
> The status is that provided by the program tcpserver runs -- in this case,
> qmail-smtpd.
>
> Did you check what error message your DOS mailer was returning? It should
> point you to http://cr.yp.to/docs/smtplf.html, which explains the problem.
>
> Also, please fix your mailer; your message gets a little difficult to read
with
> 200+ character lines. On mailing lists, try to limit your line length to
> 72-78 characters.
>
> Charles
> --
> -----------------------------------------------------------------------
> Charles Cazabon <[EMAIL PROTECTED]>
> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
> Any opinions expressed are just that -- my opinions.
> -----------------------------------------------------------------------
>
Hello,
when i have used Netscape, there are a functionality that allow me to create a
user in LDAP that
is a search filter to send email for a list of users. So, a user like email_list_1
can be a search
of uid=m* and then i could send a email to email_list_1 that dinamically will be
send to all
of users of my database that satisfy a filter (uid=m*). Its a dinamic list.
There are any implementation that looks like these in qmail-ldap or i need to run
a script to
atualize my alias list when i create a new user in LDAP (a static list) ?
Do i need fastforward or can i use a dummy user with .qmail-sos and a cat
/dev/null to this Mailbox
in my script_after_creation_of_new_user_ldap ( for static solution) ?
Thanks,
Marcio Sa
Is there a way to disable qmail-send's use of the envnoathost control file,
so that any message bound for an address without an @ sign is simply
refused?
I know I could put something like nonexistenttrashdomain.com in envnoathost
so that all such messages would get bounced back to the sender, but I'm
hoping for a cleaner solution, and hopefully one that doesn't involve code
hacking.
Thanks!
---Kris Kelley
Kris Kelley <[EMAIL PROTECTED]> wrote:
> Is there a way to disable qmail-send's use of the envnoathost control file,
> so that any message bound for an address without an @ sign is simply
> refused?
Write a wrapper script around qmail-queue, perhaps, which checks that
a domain was specified for addresses. Exit with 100 or 111 if your
preconditions aren't met properly. Then rename qmail-inject to
real-qmail-inject and have your wrapper call it after its satisfied with
its input.
To save some work, you could use Bruce Guenter's QMAILQUEUE patch, and
insert your filter inbetween qmail-inject and qmail-queue instead. The
filter would be easier, as well, because you wouldn't have to parse the
message for recipient addresses. There's pointers to Bruce's work at
www.qmail.org, or have a look at http://em.ca/~bruceg/ .
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
-----------------------------------------------------------------------
On Mon, Dec 18, 2000 at 03:27:01PM -0600, Kris Kelley wrote:
> Is there a way to disable qmail-send's use of the envnoathost control file,
> so that any message bound for an address without an @ sign is simply
> refused?
>
> I know I could put something like nonexistenttrashdomain.com in envnoathost
> so that all such messages would get bounced back to the sender, but I'm
> hoping for a cleaner solution, and hopefully one that doesn't involve code
> hacking.
Put nonexistenttrashdomain.com in ennvnoathost *and* virtualdomains
with a catch-all .qmail-default that has something like:
| bouncesaying "No recipient domain = No delivery"
Regards.
On Mon, 18 Dec 2000, Kris Kelley wrote:
> Is there a way to disable qmail-send's use of the envnoathost control file,
> so that any message bound for an address without an @ sign is simply
> refused?
>
> I know I could put something like nonexistenttrashdomain.com in envnoathost
> so that all such messages would get bounced back to the sender, but I'm
> hoping for a cleaner solution, and hopefully one that doesn't involve code
> hacking.
>
> Thanks!
>
> ---Kris Kelley
>
>
Its really simple. Just delete the envnoathost file and it doesnt get
used.
Mike
Charles Cazabon wrote:
> Write a wrapper script around qmail-queue, perhaps, which checks that
> a domain was specified for addresses...
>
> To save some work, you could use Bruce Guenter's QMAILQUEUE patch, and
> insert your filter inbetween qmail-inject and qmail-queue instead...
Actually, there are no local users on these boxes, per se, so the filter
would have to be between qmail-smtpd and qmail-queue. Otherwise, this makes
sense. I'll keep it in mind.
Mark Delaney wrote:
> Put nonexistenttrashdomain.com in envnoathost *and* virtualdomains
> with a catch-all .qmail-default that has something like:
>
> | bouncesaying "No recipient domain = No delivery"
Think I'll try this one first. :)
Thanks for the help!
---Kris Kelley
Kris Kelley <[EMAIL PROTECTED]> wrote:
> >
> > To save some work, you could use Bruce Guenter's QMAILQUEUE patch, and
> > insert your filter inbetween qmail-inject and qmail-queue instead...
>
> Actually, there are no local users on these boxes, per se, so the filter
> would have to be between qmail-smtpd and qmail-queue. Otherwise, this makes
> sense. I'll keep it in mind.
If I'm not mistaken, qmail-smtpd calls qmail-inject, which calls qmail-queue.
I belive Bruce's patch changes _all_ qmail programs which call qmail-queue
to look at the contents of QMAILQUEUE (or similar) environment variable, and
if set, to call that instead of qmail-queue directly. Therefore it would
work in this case. Just have tcpserver set QMAILQUEUE to
"/path/to/my/filter", and filter calls qmail-queue.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
-----------------------------------------------------------------------
Hello,
I've recently set up a server on Linux using qmail
1.03. Several = different users here received bounces like this one
when sending mail:
> Hi. This is the qmail-send program at
opalgroup.net. > I'm afraid I wasn't able to deliver your message to
the following = addresses. > This is a permanent error; I've
given up. Sorry it didn't work out. > > <[EMAIL PROTECTED]>: > 209.116.174.162 failed after I sent the
message. > Remote host said: 501 Badly structured mime
attachment.
Most attachments are going through fine, and the same
users were able to = send attachments to other recipients. The
attachments that had this = trouble ranged in size from a 128kb .DOC file, to
a 4mb .EPS file. =20
Although not a major problem -- yet -- I'd like to
know if there is some = configuration issue on my end that will prevent
this. All the users who = had this trouble are using Outlook Express
5.
Please let me know if there is any more info I should
supply.
Thanks, John
|
John Logiudice <[EMAIL PROTECTED]> writes on 18 December 2000 at 16:34:53 -0500
> Hello,
>
> I've recently set up a server on Linux using qmail 1.03. Several =
> different users here received bounces like this one when sending mail:
>
> > Hi. This is the qmail-send program at opalgroup.net.
> > I'm afraid I wasn't able to deliver your message to the following =
> addresses.
> > This is a permanent error; I've given up. Sorry it didn't work out.
> >
> > <[EMAIL PROTECTED]>:
> > 209.116.174.162 failed after I sent the message.
> > Remote host said: 501 Badly structured mime attachment.
Qmail is just reporting the result of the SMTP transaction with the
destination.
One of two things is happening:
1. Qmail is suddenly exhibiting a new bug where it corrupts mime
attachments. I consider this extremely unlikely, given that
there's never been such a bug before, and qmail is very careful
not to perturb the bytes as they go by.
2. Some users are sending messages which are being built by the MUA
they use in a format that whatver the MTA at 209.116.174.162 is
detects as badly structured. This is what I'd bet on, so I'd
focus on determing which users and which MUAs had this problem.
> Most attachments are going through fine, and the same users were able to =
> send attachments to other recipients. The attachments that had this =
> trouble ranged in size from a 128kb .DOC file, to a 4mb .EPS file. =20
>
> Although not a major problem -- yet -- I'd like to know if there is some =
> configuration issue on my end that will prevent this. All the users who =
> had this trouble are using Outlook Express 5.
Bingo. What a surprise. There's a common factor.
--
David Dyer-Bennet / Welcome to the future! / [EMAIL PROTECTED]
SF: http://www.dd-b.net/dd-b/ Minicon: http://www.mnstf.org/minicon/
Photos: http://dd-b.lighthunters.net/
Hi,
I am having some trouble setting up Krzysztof Dabrowski's SMTP-AUTH
patch with qmail.
I applied the smtp-auth patch and it run through without errors.
I compiled qmail out of the ports collection af FreeBSD 4.2 and
according to LWQ.
qmail itsself seems to run o.k. (I tested it with telnet from local and
remote).
I also installed cmd5checkpw.
the mailserver (mail.mydomain.com) is correctly resolved on the server
and on the client.
My /etc/poppasswd looks like this:
------------------
user1:password
------------------
my /var/qmail/supervise/qmail-smtpd/run looks like this:
------------------
#!/bin/sh
QMAILDUID=`id -u qmaild`
NOFILESGID=`id -g qmaild`
exec /usr/local/bin/softlimit -m 2000000 \
/usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \
-u $QMAILDUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd \
/bin/checkpassword /bin/true /bin/cmd5checkpw /bin/true
------------------
I configured Netscape Communicater (4.75) on my remote machine like
this:
------------------
outgoing Mailserver: mail.mydomain.com
outgoing username: user1
Use SSL: never
------------------
If I try to send a Mail this way via my mailserver I am presented wit an
Netscape-auth-window in both cases, for recipients in the local domain
and for those in a foreign domain.
If I enter "password" when I am asked for the password for
[EMAIL PROTECTED] the password is not accepted and I am asked
again and again.
any ideas?
is there any information on qmail & smtp-auth available besides the
short description on the HP of the above patch?
thanks in advance for any hints
/Clemens
Am 18.12.2000 um 18:13:49 schrieb Kris Kelley:
Hi Kris,
thanks for your help!
> It may be a matter of permissions. When invoked from patched
qmail-smtpd,
> both checkpassword and cmd5checkpw do not have root access.
Therefore, they
> must be given permission to look at /etc/poppasswd. One way to grant
this
> permission is to set /etc/poppasswd world writable, but obviously that
is
> NOT a good idea.
I did it as described in the INSTALL-file of cmd5checkpw
> The latest version of cmd5checkpw (0.22) handles both clear-text and
> CRAM-MD5 authentication schemes, so I would recommend using it
exclusively,
It is the version I use.
> for simplicity's sake. Assuming you have 0.22, change your
> /var/qmail/supervise/qmail-smtpd/run file to look like this:
>
> #!/bin/sh
> QMAILDUID=`id -u qmaild`
> NOFILESGID=`id -g qmaild`
> exec /usr/local/bin/softlimit -m 2000000 \
> /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \
> -u $QMAILDUID -g $NOFILESGID 0 smtp
/var/qmail/bin/qmail-smtpd
> \
> /bin/cmd5checkpw /bin/true /bin/cmd5checkpw /bin/true
I changed it according to this example.
> Next, follow these instructions, taken from the cmd5checkpw INSTALL
file:
>
> Now select a free user id in your system. Create that user in
> /etc/passwd
> do "chown thatuser /etc/poppasswd" , "chmod 400 /etc/poppasswd",
> "chown thatuser /bin/cmd5checkpw" and "chmod a+s
/etc/cmd5checkpw".
> Of course replace "thatuser" with username of the user you have
> created.
I have done this when I installed cmd5checkpw. (I thing it should be
"chmod a+s /bin/cmd5ckeckpw" instead of "chmod a+s /etc/....". If
Krzysztof is not reading the List I will drop him a note)
> This makes cmd5checkpw set itself to be owned by the same UID that
owns
> /etc/poppasswd, thus allowing it to read the file.
it should always have been able to read it, I double-checked te
permissions, they look like this:
-r-------- 1 smtpauth smtpauth 10 Dec 19 09:51 /ec/poppasswd
-rwsr-sr-x 1 smtpauth smtpauth 22701 Dec 18 21:36 /bin/cmd5checkpw
it still does not work, still the same problem. I tried it with a system
user (included in /etc/passwd) and with a trest-user (not in /etc/passwd
but only in /etc/poppasswd) it worked in no case.
Thanks for your help
/Clemens
Alan Chung wrote:
Hi!
Hehe, I'm sure Jason "triggers" on this $subject :)
> I have just installed the following packages for qmail virus scanning.
>
> * maildrop (MIME Handlers)
> * tnef
> * amavis
>
> I had the following ten processes running before I installed it.
[cut]
> I even tried to reinstalled from source again but it is not coming back. I
> can send/receive mail without any problem but does anyone see this problem
> before?
Hum, can you give me some more details? Which version of AMaViS do you
use? Btw, in general I would recommend to use AMaViS-Perl instead. And,
well, please post AMaViS-releaded questions to our amavis-user mailing
list, thanks.
best regards,
Rainer Link
--
Rainer Link | Member of Virus Help Munich (www.vhm.haitec.de)
[EMAIL PROTECTED] | Member of AMaViS Development Team (amavis.org)
rainer.w3.to | OpenAntiVirus Project (www.openantivirus.org)
I'm trying to get an idea of exactly how qmail does bounce messages, since I
will probably have to write various delivery programs to deal with special
quotas and such in the near future.
Simply put, are all bounce messages generated by qmail-send? If so, that
means a delivery program only has to exit with the right error code for a
bounce to be generated, correct?
Sorry if I seem to be overlooking the obvious, but the qmail docs don't give
a clear picture about this, and I can tell from the list archives that there
has been plenty of confusion about bouncing!
---Kris Kelley
Kris Kelley <[EMAIL PROTECTED]> wrote:
> I'm trying to get an idea of exactly how qmail does bounce messages, since I
> will probably have to write various delivery programs to deal with special
> quotas and such in the near future.
You're not clear on what you're trying to accomplish here. Just thought I'd
mention that if it's virtual domain quotas, vmailmgr has this covered
already. Users in a virtual domain was on Bruce's todo list, although I'm not
sure if he's finished it yet.
> Simply put, are all bounce messages generated by qmail-send? If so, that
> means a delivery program only has to exit with the right error code for a
> bounce to be generated, correct?
qmail-local signals delivery status to qmail-lspawn with its exit codes.
You can do things in a .qmail file and exit with the appropriate codes to
get the behaviour you want; man qmail-command and man dot-qmail for more
details.
qmail-remote does things a little differently; it signals its status by
printing letter codes.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
-----------------------------------------------------------------------
Hi,
I've been running qmail for a while and had relaying controlled using
tcprules to allow my cable modem IP address to relay (via /etc/tcp.smtp -->
tcp.smtp.cdb). I'm going to be travelling and will be dialing thru an ISP so
I need to use relay-ctrl so I can send mail.
My qmail installation was done using "Life with qmail"
<http://web.infoave.net/~dsill/lwq.html> and my startup script is exactly
what is listed there in section 2.8.2.1. I added to that script to start
qmail-popup, qmail-pop3d like this:
tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup FQDN \
/bin/checkpassword /usr/sbin/relay-ctrl-allow
/var/qmail/bin/qmail-pop3d Maildir 2>&1 | \
/var/qmail/bin/splogger pop3d &
I installed relay-ctrl 2.5 per the instructions.
My IP address gets logged to /var/spool/relay-ctrl as expected.
relay-ctrl-age gets run by cron every minute and updates /etc/tcp.smtp.cdb.
A dump (using cdbdump) of this file shows that my IP address is included in
the cdb file.
qmail-smtpd gets started by tcpserver and passes (among other things)
/etc/tcp.smtp.cdb in its script by supervise.
I get the standard '553 sorry' message about not relaying.
Any ideas?
Adam
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
Hi,
I've read some of the archives and people have posted before about the
trailing spaces. I have a lot of mail that is getting rejected because if
it, I realize that it's not qmail's fault by any means but is there a way (a
patch perhaps?) that I can have it strip the trailing spaces.
Thanks!!!
Adam
ookay...mail being sent from users works just fine, however when a cgi
script or other server program tries to send mail, this happens:
> ----- Transcript of session follows -----
> 553 5.3.5 mail.mydarkness.com. config error: mail loops back to me (MX
problem?)
> 554 5.3.5 [EMAIL PROTECTED] Local configuration
errorReporting-MTA: dns; darkestweb.com
Arrival-Date: Mon, 18 Dec 2000 03:42:15 -0700
the mail goes to root with this error...
what's wrong?!?!
thanks,
jeremy
This is in reference to:
http://www.ornl.gov/its/archives/mailing-lists/qmail/1998/12/msg01046.html
and
http://www.ornl.gov/its/archives/mailing-lists/qmail/2000/07/msg01597.html
I am finally going to stop using syslog and instead pipe to multilog to
keep my mail logs. However I'm having a problem with I/O re-direction
and I'm not certain whether this is a shell issue, or a tcpserver or
recordio issue.
Fwiw I am running into the same problem on both Debian 2.2 and OpenBSD
2.8 systems. My shell is bash on both of them, but if I use /bin/sh
(aka pdksh) on OBSD I get the same result. I have the feeling this
amounts to something I am missing regarding I/O redirection and I am
looking for advice. :)
I have a script 'qmail-smtpd' which looks like this:
exec /usr/local/bin/tcpserver -x /usr/local/etc/tcp.smtp.cdb -R -u 1002 -g \
1001 0 25 /var/qmail/bin/qmail-smtpd > /dev/null &
I would like to pipe tcpserver's output through some text processor
(such as grep or awk) using recordio, like this:
exec /usr/local/bin/tcpserver -x /usr/local/etc/tcp.smtp.cdb -R -u 1002 -g \
1001 0 25 recordio /var/qmail/bin/qmail-smtpd | awk '{if ($2 != "<") print}' \
| multilog /var/log/smtpd
as described in DJB's example on the above-referenced list message.
However, when I do so, I get NO output into the logs at all. Well, after
lots of playing around with re-direction characters and wasting lots of
time, I think I can simplify my question this way:
Why does this work (i.e., produce output in /var/log/smtpd/current):
exec /usr/local/bin/tcpserver -x /usr/local/etc/tcp.smtp.cdb -R -u 1002
-g 1001 0 25 recordio /var/qmail/bin/qmail-smtpd 2>&1 | cat | multilog
/var/log/smtpd
but not this (i.e., this produces no output in /var/log/smtpd/current):
exec /usr/local/bin/tcpserver -x /usr/local/etc/tcp.smtp.cdb -R -u 1002
-g 1001 0 25 recordio /var/qmail/bin/qmail-smtpd 2>&1 | cat -n | multilog
/var/log/smtpd
Of course I'm not planning on using 'cat' in reality but something
strange is occurring here where if I specify arguments to cat (or any
other program), I end up with no output. Anyone know the reason for this,
and what I am doing wrong? I think once I figure that out I'll be able
to get awk or grep or whatever to work as well.
Thanks.
Helo ,
i have followed the life with qmail for installing
the qmail . But after that i run the qmail by
qmail start --> following the script.
But it didn't started sending/receiving mail with this.
Then i have gone to the /var/qmail/boot and explicitly
and then runned the ./home script in which the
the qmail-start ... was there.
Why i have to start it explicitly the qmail.
after starting the above script only the
3 daemons started --> lspawn , clean , rspawn.
Please Read The next 4 lines after the 2.8.2.1. (The qmail Script).
waiting for your reply .
Regards
rshukla
Hello,
I use actually POP3 with tcpserver.
I Want to use IMAP4 in order to dump users message's.
I'm based on LWQ. But I don't know how to include togheter
POP3/IMAP4?
Thanks
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
The qmail server displays in the Received line of the header field the HELO
command given by the remote client.
I would like to change qmail behaviour so that it displays the HELO command
only for hosts coming from the internet and not for hosts coming from the
internal local network.
Here is an example:
Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 1982 invoked from network); 19 Dec 2000 09:29:59 -0000
-->Here is the incriminated line
Received: from proxy.edinet.it (HELO edspctec12.edinet.it) (127.0.0.1)
by proxy.edinet.it with SMTP; 19 Dec 2000 09:29:59 -0000
Message-Id: <[EMAIL PROTECTED]>
Date: Tue, 19 Dec 2000 10:32:19 +0100
To: [EMAIL PROTECTED]
From: Denis Gasparin <[EMAIL PROTECTED]>
Subject: Example
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Status:
Sending example
Thanks to all
Denis