qmail Digest 28 Dec 2000 11:00:01 -0000 Issue 1227
Topics (messages 54420 through 54447):
Re: Limited SMTP Relay
54420 by: Chris Johnson
54439 by: asantos
qmail news && RDF
54421 by: Russell Nelson
"warning: unable to unlink local/9/3601004; will try again later" mystery solved
54422 by: Bradley C. Kuszmaul
Re: Logging Messages - qmail newbie
54423 by: Markus Stumpf
Re: concurrency always > 0
54424 by: Markus Stumpf
Re: help me
54425 by: Markus Stumpf
Re: qmail-pop3d and users groups
54426 by: Markus Stumpf
Re: checkpassword question
54427 by: Markus Stumpf
54440 by: Rick Lu
Looking for a detailed qmail log analyzer .. preferably something pretty for the CEO.
54428 by: Steve Fulton
Xinetd & Qmail & New Problem!
54429 by: Jeff Lacy
Re: Other Outlook features and qmail
54430 by: Boz Crowther
54431 by: Luca Pescatore
RBLSMTPD
54432 by: drew.ricshaw.com.au
54447 by: Piotr Kasztelowicz
"Backup" Qmail Server
54433 by: Michael Hornby
54434 by: Mike Jackson
54435 by: Henning Brauer
54436 by: Dennis
54437 by: Henning Brauer
54442 by: richard.illuin.org
rblsmtpd - notification
54438 by: drew.ricshaw.com.au
Re: Attachment-based relaying
54441 by: David L. Nicol
not sure what the subject should be
54443 by: Timothy Falardeau
54445 by: Andrew Hill
alias system
54444 by: drew.ricshaw.com.au
54446 by: Mark Delany
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]
----------------------------------------------------------------------
On Tue, Dec 26, 2000 at 10:10:31PM -0500, Aaron Carr wrote:
> This file contains 192.168.1.0:allow,RELAYCLIENT=" "
That should be RELAYCLIENT="", not RELAYCLIENT=" " (you shouldn't have a space
between the quotation marks). Also, as someone else pointed out, the IP address
should be a pattern, not a netmask (i.e. 192.168.1. instead of 192.168.1.0).
Chris
From: Chris Johnson <[EMAIL PROTECTED]>
>That should be RELAYCLIENT="", not RELAYCLIENT=" " (you shouldn't have a
space
>between the quotation marks). Also, as someone else pointed out, the IP
address
>should be a pattern, not a netmask (i.e. 192.168.1. instead of
192.168.1.0).
I think that the contents of RELAYCLIENT will simply be appended to the
incoming recipient address. Possibly harmless, therefore.
Armando
If you have the ability to do so, please test my qmail news RDF Site
Summary (RSS) file. The URL is http://qmail.org/news.rdf . I haven't
announced it anywhere except this message right now, so for example
it's not available at Slashdot as a news box. Once I get some
feedback I'll start submitting it (that should be taken as a broad
hint. Very broad.)
More information on RSS is at http://my.netscape.com/publish/help/quickstart.html
More information on RDF is at http://www.w3.org/TR/REC-rdf-syntax/
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com | A steak, bacon
Crynwr sells support for free software | PGPok | and cheese sandwich is
521 Pleasant Valley Rd. | +1 315 268 1925 voice | offensive to every major
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | religion.
There is a lot of email in the archives of this list complaining about
things such as
warning: unable to unlink local/9/3601004; will try again later
I saw this too, (running with the rpms made by Bruce Guenter E<[EMAIL PROTECTED]>)
I investigated what was going on. The key is to look at errno when
the unlink fails. (By the way, I suggest that the when printing the
warning about the unlink failing, the error code ought to be printed
out too.)
The unlink returned error code 5 (I/O error) sometimes, but not
always.
By taking out the syncdir patch, the problem goes away.
I mounted the ext2fs filesystem "sync" (it turns out the only thing on
that disk is my qmail queue and my alias maildirs, so it is an
excellent candidate for being mounted "sync".)
Now the system works much better, with none of those "unable to
unlink" messages in the logs.
A related problem: The "try again later" is 123 seconds later:
pe.dt = now() + SLEEP_SYSFAIL;
This can cause problem if more than a few hundred messages get into
this state (especially when using syslogd). The problem is that qmail
spends all its time looking at these messages. Much better would be
if the retry were scheduled with a quadratic backoff strategy to avoid
swamping qmail with these bad messages.
-Bradley
On Sat, Dec 23, 2000 at 09:27:52PM +0000, Anonymous user wrote:
> Has anybody got a more elegant way of doing this?
What would you consider "elegant" ?
> Thinking this I tried to construct a Maildir for my messages by putting
> ./MaildirLog/ in .qmail-log and creating a maildir in the alias directory -
> it didn't work (I got can chdir to directory messages in the log). I am now
> wondering though if I should have created the Maildir owned by a particular
> user - any info?
The whole direcvtory and any subdir has to be owned by user "alias".
(That's the user under who's permissions the mail gets delivered).
> One more thing. Can I put the |script type construct in the .qmail-log file
> to process the messages myself? If so, I am not sure how it works. Does
> this mean that the routine you specify will get the whole message on STDIN?
> Does the system expect any output or can you do anything you like with the
> message in the script?
Yes, the script gets the whole message on stdin.
It doesn't have to outout anything, you can however control further
delivery by exit codes.
See the qmail-command man page for more information.
\Maex
--
SpaceNet AG | http://www.Space.Net/ | Stress is when you wake
Research & Development | mailto:[EMAIL PROTECTED] | up screaming and you
Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | realize you haven't
D-80807 Muenchen | Fax: +49 (89) 32356-299 | fallen asleep yet.
On Sun, Dec 24, 2000 at 05:37:33PM +0100, J.M. Roth wrote:
> I have those mrtg scripts which visualize qmail status
> A few weeks ago remote concurrency became 1 and that is its minimum value
> ever since, I wonder why. Before that it was always 0, unless sth.
> happenend...
Take a look at the output of
qmail-qread
How many outgoing messages are there? How old are those?
Do a
ps auxw | grep qmail-remote
Do you see any "hanging" deliveries (running a few days or sth like
that)
I don't use mrtg, just guessing.
\Maex
--
SpaceNet AG | http://www.Space.Net/ | Stress is when you wake
Research & Development | mailto:[EMAIL PROTECTED] | up screaming and you
Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | realize you haven't
D-80807 Muenchen | Fax: +49 (89) 32356-299 | fallen asleep yet.
On Tue, Dec 26, 2000 at 04:27:08PM +0800, wheatly wrote:
> out mail system is based on Freebsd+mysql+qmail and now local to remote ro remote to
>local is ok,but
> local to local doesn't work. what is the reason ,who can help me?
What do the logs say?
How are those local to local messages injected?
Do you get any errors? What do they say?
\Maex
--
SpaceNet AG | http://www.Space.Net/ | Stress is when you wake
Research & Development | mailto:[EMAIL PROTECTED] | up screaming and you
Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | realize you haven't
D-80807 Muenchen | Fax: +49 (89) 32356-299 | fallen asleep yet.
On Tue, Dec 26, 2000 at 10:19:18PM -0300, Roberto Samarone Araujo (RSA) wrote:
> I have a qmail server running in a FreeBSD 4.2 and using
> qmail-pop3d. I would like to know if I could set up qmail-pop3d to work only
> for users in some groups in /etc/group file. Is it possible to do this? How
This can be accomplished by using a modified checkpassword program.
It would take user and password and could check the user against /etc/group
and if the user isn't in one of the groups deny the access.
You can either modify the checkpassword by DJB or pick one at
http://www.qmail.org/ and modify one of those (there are some perl
version also).
\Maex
--
SpaceNet AG | http://www.Space.Net/ | Stress is when you wake
Research & Development | mailto:[EMAIL PROTECTED] | up screaming and you
Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | realize you haven't
D-80807 Muenchen | Fax: +49 (89) 32356-299 | fallen asleep yet.
On Wed, Dec 27, 2000 at 10:24:55AM +0800, Rick Lu wrote:
> I am a newbie to this list. Now, I want to authenticate SMTP and POP3
> and SMTPD and POP3D do well in the "qmaild" user which I set its uid to root id (0).
> But do I have to let "qmaild" become super-user? Have any other way to do this ,
>because
> "qmaild" super-user is not good enough to me.
1) it's a really bad idea to set the uid of qmaild to zero.
this will have no effect, until you completely recompile the qmail
package.
2) what exactly is your problem?
\Maex
--
SpaceNet AG | http://www.Space.Net/ | Stress is when you wake
Research & Development | mailto:[EMAIL PROTECTED] | up screaming and you
Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | realize you haven't
D-80807 Muenchen | Fax: +49 (89) 32356-299 | fallen asleep yet.
Hello,
Thanks Maex.
as we all know, there are two super-user functions in checkpassword package: setuid &
setgid.
because qmaild is only a normal user in nofiles group, so he has no privilege to call
these codes. it will show "-ERR authorization failed".
My question is that how qmaild user can use checkpassword and I do not have to set
the uid of this user to zero.
>1) it's a really bad idea to set the uid of qmaild to zero.
> this will have no effect, until you completely recompile the qmail
> package.
>2) what exactly is your problem?
>
> \Maex
>
Xin Lu
[EMAIL PROTECTED]
I've been looking at some of the log file analzyers available, and I haven't
yet found one that meets our needs without some additional programming - and
I am lousy @ programming - so I've decided to throw the dice & ask you all,
the venerable members of the qmail list.
Basically, I am looking for an analyzer that can give me general statistics
(daily, weekly, monthly), domain specific stats (d/w/m etc, how much mail
sent out, sent in etc) and *user* specific stats - so I can catch spammers
and other such wankers. I've looked at qlogtools, isoQlog etc, but they do
not seem to go far enough. On top of that, I need something that would look
pretty when I show the CEO of the company -- we all know how CEO's like
pretty graphs. Something like the isoQlog program, with a touch of mrtg
thrown in (yes, I know about the qmail-mrtg scripts - but they don't go far
enough either).
So, can anyone suggest anything?
Steve.
Okay. Thanks everyone who helped me. Qmail accepts mail and things seem to
be mostly better. Now I only have problem and I would very very grateful if
anyone could help me with it.
After qmail accepts a message from me, I assume it does it thing. Then I go
to my mail program (outlook express) and say for check new mail. It asks
for new mail, via pop3, and it comes back with nothing at all. I don't know
how to find the all the messages I send. Qmail is hiding/destroying my
mail! Could someone please tell me where to look and/or how to fix the
problem?
.qmail-root and .qmail-postmaster both are:
jeff
[EMAIL PROTECTED]
~jeff/.qmail is:
./Maildir/
~jeff/Maildir/ is owned by jeff and is a mail dir so it should work.
Doing an 'echo to:jeff | /var/qmail/bin/qmail-inject' doesn't show up
anywhere. Email to root get lost too.
Could someone please help me? Thanks everyone :-D
Jeff
----- Original Message -----
From: "Paco Gracia" <[EMAIL PROTECTED]>
To: "Jeff Lacy" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, December 27, 2000 2:31 AM
Subject: RE: Xinetd & Qmail
> Hello,
>
> This set up used to work with qmail and RH7.0. It uses vpopmail so if
> you have a standard qmail instalation you'll have to change vchkpw to use
> checkpassword.
>
> Each service is in one file inside /etc/xinet.d. Read xinet man pages
to
> allow and deny connections, set a maximun number of concurrent
connections,
> bind and external ip to an internal ip, configure your logs, etc...
>
> tcpserver was the only solution before xinet and it is still the best
> solution for advanced qmail instalations. For nothing too complicated
xinet
> can do the job perfectly... and it is most straightforward than tcpserver.
> So the choice depends on your needs.
>
> Bye.
>
> /etc/xinet.d/smtp
>
> # default: on
> service smtp
> {
> disable = no
> socket_type = stream
> protocol = tcp
> wait = no
> user = qmaild
> server = /var/qmail/bin/tcp-env
> server_args = /var/qmail/bin/qmail-smtpd
> log_on_success += USERID
> log_on_failure += USERID
> }
>
>
> /etc/xinet.d/pop
>
> # default: on
> service pop3
> {
> disable = no
> socket_type = stream
> wait = no
> user = root
> server = /var/qmail/bin/qmail-popup
> server_args = your.mail.server
/home/vpopmail/bin/vchkpw
> /var/qmail/bin/qmail-pop3d Maildir
> log_on_success += USERID
> log_on_failure += USERID
> }
>
>
> ----- Original Message -----
> From: Jeff Lacy <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, December 27, 2000 2:56 AM
> Subject: Xinetd & Qmail
>
>
> > Hello Everyone,
> >
> > I'm new to this list, so please forgive me if this has been asked
> before
> > or is really dumb.
> >
> > I'm running RH7.0 and I would like to run qmail. I thought I had it
> > working once, but I was just calling tcpd from xinetd and that seemed a
> > little foolish. I have been messing around with xinetd all day and my
> > progress has been -42. Qmail accepts messages, but then they just sort
of
> > disappear. I think it all stems from a problem with my xinetd
> > configuration. I have searched the internet and everything I find is
> > different from everything else. I am looking for the 'definitive' thing
> to
> > use with xinetd. Hopefully, it should have logging and not use anything
> > toooo complex (and allow relaying from my lan).
> >
> > I would also really appreciate it if someone would tell me why so
many
> > people use tcpserver instead of xinetd. I understand that tcpserver can
> be
> > run continually, but xinetd only starts smtpd (or whatever) when someone
> > connects to port 25. I am going to be running a very very (did I
mention
> > very) low-volume mail server.
> >
> > PLEASE someone, just tell me what to do. Thanks very much in
advance.
> > Maybe now I can put down my virtual water gun. Thanks.
> >
> > Despairing Jeff
> >
> >
>
Have you looked at OpenMail? www.openmail.com
----- Original Message -----
From: "Dennis" <[EMAIL PROTECTED]>
To: "Qmail@List. Cr. Yp. To" <[EMAIL PROTECTED]>
Sent: Tuesday, December 26, 2000 8:19 PM
Subject: Other Outlook features and qmail
> Hi all...
>
> I'm looking to implement the calendar, tasks, notes etc features available
> in Outlook with qmail and courier-imap
>
> Does anyone know of any product that allows for the complete integration
of
> Outlook and qmail/courier-imap without having to use MS Exchange
> *shudder*...
>
> Cheers
> Dennis
>
>
Did you tried TWIG or IMP ?
Best Regards,
Luca
At 13.50 27/12/00 -0800, Boz Crowther wrote:
>Have you looked at OpenMail? www.openmail.com
>
>
>----- Original Message -----
>From: "Dennis" <[EMAIL PROTECTED]>
>To: "Qmail@List. Cr. Yp. To" <[EMAIL PROTECTED]>
>Sent: Tuesday, December 26, 2000 8:19 PM
>Subject: Other Outlook features and qmail
>
>
> > Hi all...
> >
> > I'm looking to implement the calendar, tasks, notes etc features available
> > in Outlook with qmail and courier-imap
> >
> > Does anyone know of any product that allows for the complete integration
>of
> > Outlook and qmail/courier-imap without having to use MS Exchange
> > *shudder*...
> >
> > Cheers
> > Dennis
> >
> >
Hi,
Can anyone please advise me if there is anyway of telling
an attacker if you like that they have been blocked via an email or
something similiar. I am having the problem that people are getting
blocked however it appears the mail goes through but is then not
returned. Please Help.
Drew
Hello
> Hi,
> Can anyone please advise me if there is anyway of telling
> an attacker if you like that they have been blocked via an email or
> something similiar. I am having the problem that people are getting
> blocked however it appears the mail goes through but is then not
> returned. Please Help.
The rblsmtpd based for instance on ORBS - this is not good idea.
I think - each admin should generate its own "black" list of
spam hosts rather than take it from ORBS. This server from I'm
writing now (administrated by me) does not support open relay
now, since time, when I have begun administrate it, I have installed
the newest software - qmail and configure it with tcpserver. The
relayclients are carefuly established. Nothing more are not able
to relay post by server of mine but I'm existing further time
till today on ORBS list as insecure. Why? How about ask Alan Brown?
I suppose, that in like my case are more peoples!
If any host might support open relay if not, would bee seen without
complicated tests. Each can see that my host does not support
open relay but my host sitll exists on ORBS list!
ORBS and like ORBS lists
there are stupid idea, which makes more evil than good. First of all
from such as ORBS 'insecure hosts' list" are using all presented on Net
hacers, who have directly listing of host, which potentialy can
be used to attack. I'm of opinion, that giving such list public
is illegal and harmful. I have met such case, that after each test
made from ORBS was reported hackers proof to destroy my host, therefore
the access for ORBS on my host has been by my on tcpserver blocked:
....
=nl:deny
=nz:deny
Best Wishes
Piotr
---
Piotr Kasztelowicz <[EMAIL PROTECTED]>
[http://www.am.torun.pl/~pekasz]
I am running qmail on a server which will be going down shortly for
upgrades. I have a unix machine running at my house (static IP address) that
I would like to use as a "backup" server. I plan on changing the MX record
for my domain to point to my home machine, and to have all the mail
delivered there while the main server is down. Instead of having mail being
sent to me bounce, it will go through via the backup server.
My ultimate goal is to have my home server accept any mail that is being
sent to any e-mail address being hosted on the main server, and to
indefinitely try to forward it to the main server. This way, when the main
server returns, it will receive all the mail it missed while it was down.
All the e-mail will then continue to be stored on the main server, and users
can login there to retrieve it.
Does anyone have any ideas as to how I might implement this? Any help is
greatly appreciated. Thanks in advance.
Michael Hornby wrote:
>
> I am running qmail on a server which will be going down shortly for
> upgrades. I have a unix machine running at my house (static IP address) that
> I would like to use as a "backup" server. I plan on changing the MX record
> for my domain to point to my home machine, and to have all the mail
> delivered there while the main server is down. Instead of having mail being
> sent to me bounce, it will go through via the backup server.
>
> My ultimate goal is to have my home server accept any mail that is being
> sent to any e-mail address being hosted on the main server, and to
> indefinitely try to forward it to the main server. This way, when the main
> server returns, it will receive all the mail it missed while it was down.
> All the e-mail will then continue to be stored on the main server, and users
> can login there to retrieve it.
>
> Does anyone have any ideas as to how I might implement this? Any help is
> greatly appreciated. Thanks in advance.
The best way to upgrade your mail server is to install a forwarding
sendmail on your firewall, then queue mail at the firewall until your
new server is complete. Set the bounce timeout on the firewall to
something like 5 days. I did this a week ago, and it took me about 30
hours for a large migration plus many mailing lists and domains... When
you are happy, open the floodgates... I had about 4000 messages queued.
Mike
Am Donnerstag, 28. Dezember 2000 00:28 schrieb Mike Jackson:
> Michael Hornby wrote:
> > I am running qmail on a server which will be going down shortly for
> > upgrades. I have a unix machine running at my house (static IP address)
> > that I would like to use as a "backup" server. I plan on changing the MX
> > record for my domain to point to my home machine, and to have all the
> > mail delivered there while the main server is down. Instead of having
> > mail being sent to me bounce, it will go through via the backup server.
> >
> > My ultimate goal is to have my home server accept any mail that is being
> > sent to any e-mail address being hosted on the main server, and to
> > indefinitely try to forward it to the main server. This way, when the
> > main server returns, it will receive all the mail it missed while it was
> > down. All the e-mail will then continue to be stored on the main server,
> > and users can login there to retrieve it.
> >
> > Does anyone have any ideas as to how I might implement this? Any help is
> > greatly appreciated. Thanks in advance.
>
> The best way to upgrade your mail server is to install a forwarding
> sendmail on your firewall,
????
The easiest way is to add another mx record with higher precedence to your
domain pointing to your home machine and install qmail there, set
~/control/me and just copy over ~/control/rcpthosts from your original
server. Thats all. You don't need to change this setup when you're finished,
your home qmail will get all mail as loang as your primary server is down and
send it to your primary when it becomes availabel again.
The important thing here is that your domains are NOT in locals or
virtualdomains.
> then queue mail at the firewall until your
> new server is complete. Set the bounce timeout on the firewall to
> something like 5 days. I did this a week ago, and it took me about 30
> hours for a large migration plus many mailing lists and domains... When
> you are happy, open the floodgates... I had about 4000 messages queued.
>
> Mike
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
www.bsws.de | Germany
thats a good idea for pop servers but not for imap.
> -----Original Message-----
> From: Henning Brauer [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 28 December 2000 10:44 AM
> To: Mike Jackson; Michael Hornby
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: "Backup" Qmail Server
>
>
> Am Donnerstag, 28. Dezember 2000 00:28 schrieb Mike Jackson:
> > Michael Hornby wrote:
> > > I am running qmail on a server which will be going down shortly for
> > > upgrades. I have a unix machine running at my house (static
> IP address)
> > > that I would like to use as a "backup" server. I plan on
> changing the MX
> > > record for my domain to point to my home machine, and to have all the
> > > mail delivered there while the main server is down. Instead of having
> > > mail being sent to me bounce, it will go through via the
> backup server.
> > >
> > > My ultimate goal is to have my home server accept any mail
> that is being
> > > sent to any e-mail address being hosted on the main server, and to
> > > indefinitely try to forward it to the main server. This way, when the
> > > main server returns, it will receive all the mail it missed
> while it was
> > > down. All the e-mail will then continue to be stored on the
> main server,
> > > and users can login there to retrieve it.
> > >
> > > Does anyone have any ideas as to how I might implement this?
> Any help is
> > > greatly appreciated. Thanks in advance.
> >
> > The best way to upgrade your mail server is to install a forwarding
> > sendmail on your firewall,
>
> ????
>
> The easiest way is to add another mx record with higher
> precedence to your
> domain pointing to your home machine and install qmail there, set
> ~/control/me and just copy over ~/control/rcpthosts from your original
> server. Thats all. You don't need to change this setup when
> you're finished,
> your home qmail will get all mail as loang as your primary server
> is down and
> send it to your primary when it becomes availabel again.
> The important thing here is that your domains are NOT in locals or
> virtualdomains.
>
> > then queue mail at the firewall until your
> > new server is complete. Set the bounce timeout on the firewall to
> > something like 5 days. I did this a week ago, and it took me about 30
> > hours for a large migration plus many mailing lists and domains... When
> > you are happy, open the floodgates... I had about 4000 messages queued.
> >
> > Mike
>
> --
>
> Henning Brauer | BS Web Services
> Hostmaster BSWS | Roedingsmarkt 14
> [EMAIL PROTECTED] | 20459 Hamburg
> www.bsws.de | Germany
Am Donnerstag, 28. Dezember 2000 00:40 schrieb Dennis:
[qmail + courier-imap]
> thats a good idea for pop servers but not for imap.
can't see you problem.
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
www.bsws.de | Germany
On Wed, 27 Dec 2000, Michael Hornby wrote:
> My ultimate goal is to have my home server accept any mail that is being
> sent to any e-mail address being hosted on the main server, and to
> indefinitely try to forward it to the main server. This way, when the main
> server returns, it will receive all the mail it missed while it was down.
> All the e-mail will then continue to be stored on the main server, and users
> can login there to retrieve it.
>
> Does anyone have any ideas as to how I might implement this? Any help is
> greatly appreciated. Thanks in advance.
example.com IN MX 10 main.example.com. ; main machine
IN MX 20 backup.example.net. ; home machine
if main.example.com is unreachable for any reason then anyone sending mail
to @example.com will send it to backup.example.net instead.
backup.example.net won't try to forward mail to itself, it'll just kep
trying main.example.com until it suceeds, or the timeouts expire (see
qmail-control for details of the files which control this)
the only extra thing you have to do is make sure example.com is in
rcpthosts on backup.example.net and also does not appear in locals or
virtualdomains on that machine. (if it does then you have to do htings
slightly differently)
RjL
==================================================================
You know that. I know that. But when || Austin, Texas
you talk to a monkey you have to || Email: [EMAIL PROTECTED]
grunt and wave your arms -ck ||
Hi,
Just read my last message and it is not really clear. I have
rblsmtpd set up and it is working fine. However when I send an
email to myself through an open relay it appears to send the mail
but does not. The mail is obviously being blocked by rblsmtpd. My
question is: Is there anyway of notifying the person who sent the
mail to you through the open relay, with a generic message that
they were blocked. Say "Your message could not be processed by
our server." If anyone could help with this it would be much
appreciated.
Drew
Brett Randall wrote:
>
> how to intercept mail that our users send through our mail server,
> check the size of the mail, and if it exceeds a certain size (say,
> 5mb), then it relays the mail to another qmail relay, otherwise the
> current relay treats it as normal outgoing e-mail.
>
> Does anyone have ideas as to how I would implement this? TIA
you could alter your qmail-remote, to connect to your peer that uses
the alternate interface instead of the proper destination, when the
size is too big. Sort of like the hack to defer when a message is
too big but instead of deferring the peer-address is changed.
For a starting point here is how to find the file size of the message
within qmail-remote.c
#include <sys/stat.h>
int instat;
fstat( ssin.fd, &instat);
--
David Nicol 816.235.1187 [EMAIL PROTECTED]
Today in art class, draw your sword
I have qmail running on Linux.cima.org. and all my
mail mail must be sent to [EMAIL PROTECTED] What
I want to know and have yet to find documented is how
to have the mail sent to [EMAIL PROTECTED] anyone
shed some light here?
Timothy Falardeau wrote:
> I have qmail running on Linux.cima.org. and all my
> mail mail must be sent to [EMAIL PROTECTED] What
> I want to know and have yet to find documented is how
> to have the mail sent to [EMAIL PROTECTED] anyone
> shed some light here?
See question/answer 3.1 in the FAQ.
Cheers,
--
Andrew Hill
"Right now, I'd happily snort gunk from the sink if it would take
my brain somewhere away from here...." - JB
Hi,
I have a .qmail file in my home directory that is .qmail-user and
it contains the line:
/usr/home/drew/Maildir2/ where Maildir2 is a seperate Mail
directory setup than the one we use on the system. Is there
anyway I can pop mail from this directory or is that an
impossibility. Anyones input would be much appreciated.
Drew
Andrew Toussaint
Richardson-Shaw Pty Ltd
[EMAIL PROTECTED]
Anything's possible, but the standard qmail-pop setup, with the
standard checkpassword does not support this.
Essentially, checkpassword and friends require a separate user in
/etc/passwd per Maildir.
Alternative checkpassword programs allow greater flexibility and may
possibly support what you want. Details on www.qmail.org (at 11).
A simple solution is to create a separate user who effective has a
$HOME/Maildir that points to (and has permissions to access)
/usr/home/drew/Maildir2. This of course doesn't scale nicely.
Regards.
On Thu, Dec 28, 2000 at 04:28:52PM +1100, [EMAIL PROTECTED] wrote:
> Hi,
> I have a .qmail file in my home directory that is .qmail-user and
> it contains the line:
> /usr/home/drew/Maildir2/ where Maildir2 is a seperate Mail
> directory setup than the one we use on the system. Is there
> anyway I can pop mail from this directory or is that an
> impossibility. Anyones input would be much appreciated.
>
> Drew
>
> Andrew Toussaint
> Richardson-Shaw Pty Ltd
> [EMAIL PROTECTED]
>
