John R. Levine writes:
> I see that if the first line of a .qmail file is blank, qmail-local
> dies with a temporary failure code. Other blank lines are ignored,
> but there's a specific test and a failure message "Uh-oh: first line of
> .qmail file is blank. (#4.2.1)"
>
> Anyone know why? It's
I've been reading through the source code of qmail-local to be sure
I'm telling the truth about what it does in the qmail book.
I see that if the first line of a .qmail file is blank, qmail-local
dies with a temporary failure code. Other blank lines are ignored,
but there's a specific test and a
I'm having a problem getting an ezmlm list setup. I know that it has a
seperate list, but I think this is a qmail configuration problem.
Here is users/assign (yes, I ran qmail-newu):
+:jjn:500:500:/home/jjn:::
+soccer:soccer:514:514:/home/soccer:::
=jjn:jjn:500:500:/home/jjn:::
[snip - standard
ECTED]
>Subject: Re: Editing .qmail Files Creates
>qmail-spawn_unable_to_open_messageError.
>
>On Tue, 6 Mar 2001 [EMAIL PROTECTED] wrote:
>
>> What I want to do is add the X-Envelope-To: to every email sent to my
>> virtual domain. Then I can have pullmail just look at the
On Tue, 6 Mar 2001 [EMAIL PROTECTED] wrote:
> What I want to do is add the X-Envelope-To: to every email sent to my
> virtual domain. Then I can have pullmail just look at the X-Envelope-To:
> field and fix receiving mail sent to
> mailing lists.
>
> This is what I've
What I want to do is add the X-Envelope-To: to every email sent to my
virtual domain. Then I can have pullmail just look at the X-Envelope-To:
field and fix receiving mail sent to
mailing lists.
This is what I've done to my .qmail files:
In .qmail-default
|(echo "X-Envelope-To: $DEF
e: Problem with qmail-inject and .qmail files
>
>
> Scotte Zinn <[EMAIL PROTECTED]> wrote:
> > If I have a .qmail-test file in my home directory with the lines
> >
> > |groups >>MYGROUP ; exit 0
> >
> > I can send email to me-test and everything works
Scotte Zinn <[EMAIL PROTECTED]> wrote:
> If I have a .qmail-test file in my home directory with the lines
>
> |groups >>MYGROUP ; exit 0
>
> I can send email to me-test and everything works out fine.
>
> However, if .qmail-test contains
>
> |groups | mail $SENDER -s "Groups" ; exit 0
>
> then
If I have a
.qmail-test file in my home directory with the lines
|groups
>>MYGROUP ; exit 0
I can send email to
me-test and everything works out fine.
However, if
.qmail-test contains
|groups | mail
$SENDER -s "Groups" ; exit 0
then I don't get the
message back and the log file c
Wolfgang Zeikat <[EMAIL PROTECTED]> wrote on Sun, 25 Feb 2001:
> the program delivery lines in my dot-qmail files are beginning to get
> lengthy -
> for example with if ... elif statements and such ...
>
> is there a way to continue a line on the next line in order to keep a
the program delivery lines in my dot-qmail files are beginning to get
lengthy -
for example with if ... elif statements and such ...
is there a way to continue a line on the next line in order to keep an
overwiew and make editing easier?
thanks
wolfgang
On Fri, 23 Feb 2001, Alex Pennace wrote:
> On Fri, Feb 23, 2001 at 07:01:48PM -0700, Ben Schumacher wrote:
> > I was wondering if anybody had a patch to make qmail-local look in an
> > alternate directory for .qmail files before going to $HOME. I know I saw
> > somewhere t
On Fri, Feb 23, 2001 at 07:01:48PM -0700, Ben Schumacher wrote:
> I was wondering if anybody had a patch to make qmail-local look in an
> alternate directory for .qmail files before going to $HOME. I know I saw
> somewhere that somebody had done something like this, but I've be
Hello-
I was wondering if anybody had a patch to make qmail-local look in an
alternate directory for .qmail files before going to $HOME. I know I saw
somewhere that somebody had done something like this, but I've been unable
to find it again.
If all else fails, I will just go ahead and
Dan Poynor <[EMAIL PROTECTED]> wrote:
> So, how would you make all .filename files invisible to ftp users?
Check the documentation for your ftpd -- probably something in its configuration
file. It's certainly not got anything to do with qmail.
Charles
--
---
Previously I made .filename files invisible to users logging in via ftp as a security
precaution. Now I need to make the files
available to ftp users but can't remember how I made them invisible. The
problem/feature occurs using various GUI ftp clients on
different platforms from different ip ad
"Kelly Prophet" <[EMAIL PROTECTED]> wrote:
>So, basically what I am asking is if anyone is aware of a way to pipe
>incoming email for a specified user to a location on the server. In
>this case, a CGI-script.
How about, in the appropriate .qmail file:
|/path/to/cgi-script
-Dave
Greetings,
I've just started the process of transferring servers. Not
really using the old data persay, but rather just moving from a sendmail system
to a qmail system.
One thing I have to have is the ability to pipe incoming email
for a specified user to a CGI script. I originally did th
mains/metta.lk/name-of-account/.qmail
Try putting the directions in
/home/vpopmail/domains/metta.lk/.qmail-name-of-account instead, since...
> -
> # copy of mail in Maildir
> ./Maildir/
> # copy of mail to Mr abc
> &[EMAIL PROTECTED]
...vpopmail .qmail files
Hi all
I have installed
qmail / vpopmail / vqsignup / sqwebmail
I have and account in the dir
/home/vpopmail/domains/metta.lk/"name-of-account"
I want to keep a copy in the Maildir of "name-of-account"
and want to forward a copy of the mail to another account
In qmail I would generate a fi
Cyril Bitterich <[EMAIL PROTECTED]> wrote:
>IMHO /var/qmail/users/assign only works for mailadresses that are nor
>equal to the username.
Whether or not qmail-users overrides users is a matter of fact, not a
matter of opinion. In fact, qmail-users (users/assign) *does* override
normal delivery
similar on you system as well.
> To be more specific, I want some users not to be able to receive mail at all
> (they all bellong to the same group)
echo "#" > .qmail
> and others not be able to change
> delivery instruction by creating their own dot-qmail files via ftp
the same group) and others not be able to change
> > delivery instruction by creating their own dot-qmail files via ftp
> > (they all belong to another group).
> >
> > I suppose that this is controled by QMAILHOME/users/assign,
> > but the man page is not very helpful.
> >
> > Can anyone help?
> >
> > John
> >
> >
>
>
> I would like to prevent users with ftp access to change the
> delivery instructions for qmail.
>
> To be more specific, I want some users not to be able to receive mail at all
> (they all bellong to the same group) and others not be able to change
> delivery instruction by
il-list
Subject: How to ignore .qmail-* files for given users?
Hello,
I would like to prevent users with ftp access to change the
delivery instructions for qmail.
To be more specific, I want some users not to be able to receive mail at all
(they all bellong to the same group) and others not be
-qmail files via ftp
(they all belong to another group).
I suppose that this is controled by QMAILHOME/users/assign,
but the man page is not very helpful.
Can anyone help?
John
OTECTED]]
> Sent: Saturday, October 21, 2000 9:43 PM
> To: qmail liste
> Subject: understand .qmail files
>
>
> Hi,
>
> I got some questions concerning .qmail files.
> I'm installing qmail for the very first time
> and now trying to get things done. So first
> I r
Hi,
I got some questions concerning .qmail files.
I'm installing qmail for the very first time
and now trying to get things done. So first
I run "maildirmake /home/sebastian/Maildir" to
create the maildirectory for the local user sebastian.
Now I must create the .qmail file fo
hey..
I was wondering y my info@ e-mail address were not being used much latly..
geez o peats... I get this..
966362592.970325 new msg 672345
966362592.970351 info msg 672345: bytes 783 from <[EMAIL PROTECTED]> qp
4205 uid 100
966362592.974618 starting delivery 15: msg 672345 to local
[EMAIL
On Sat, Aug 05, 2000 at 04:08:08PM -0500, Chris Hardie wrote:
...
> -Has anyone else already done this?
Chris, we've done something similar to this at ENoor. We allow users to
authenticate themselves, and go to a web page from which they can create
.qmail files to redirect mail to
On Sat, Aug 05, 2000 at 04:08:08PM -0500, Chris Hardie wrote:
> Hi folks. I'm interested in creating a web interface to manage user
> dot-qmail files. I'm ready to start coding :) but thought I'd would
> solicit the sagacious and smooth advice of this list about so
r an alias).
The main problem I see about a program which should work with
.qmail-* files, is that it must then be run with the same
userid as the directory owner -> one cgi-script per domain,
or one suid script, which is never really good on any system..
Hi folks. I'm interested in creating a web interface to manage user
dot-qmail files. I'm ready to start coding :) but thought I'd would
solicit the sagacious and smooth advice of this list about some of the
architecture/design issues.
My proposal is here:
http://www.summer
hi all,
We have two locally delivered domains: cia.com.au and ezeelynx.com.au
We have a user willows who wants to receive mail at [EMAIL PROTECTED] and
wants [EMAIL PROTECTED] to be forwarded somewhere else. I've tried
creating:
/var/qmail/alias/.qmail-ezeelynx:com:au-willows
with a line:
&[E
I am using vpopmail and I am wondering were my .qmail files go if I want
to forward to another e-mail address... Any Ideas?
t for user (rather than administrator)
> acceptance of qmail is that all the .qmail-* files a user creates go
> in $HOME.
>
> Personally I've "just got used to it", but wonder if anyone has worked
> out if there is a good reason for this that would not be addressed by
>
On Tomorrow, Giles Lean wrote:
>
> One regular sticking point for user (rather than administrator)
> acceptance of qmail is that all the .qmail-* files a user creates go
> in $HOME.
I like a clean home dir as well. Which is why, for myself, I have
added to users/assign:
=vern:
[I'm sure this has been discussed before. If someone is better than I
am at nagivating the archives and can find a discussion, please point
me at it. Thanks.]
One regular sticking point for user (rather than administrator)
acceptance of qmail is that all the .qmail-* files a user creat
.qmail-unsubscribe should be owned by user alias and should contain one line:
&clifmail
and in the clifmail home directory, there should be a .qmail file with
./Mailbox
as its contents.
and Mailbox should not be readable by anyone but user clifmail (600)
>
> file and my ~cliffmail/Mailbox are set to 644 and are owned by me(bothe UID
> and GID)
Giving $HOME/Mailbox a perm of 644 is typically a bad thing(TM), and is
not conducive to proper operation of qmail...
> Can someone help me out with this? I would really appreciate any help.
> Thanks in adva
clifford thurber <[EMAIL PROTECTED]> wrote:
>Under /var/qmail/alias I have a file a file called .qmail-unsubscribe.
>The file contains one line of text wich says: /home/clifmail/Mailbox
Deliveries to .qmail files under ~alias are done as user "alias". User
alias can
Hello,
I am new to qmail and yes I have read the docs extensively. Here is my
question:
Under /var/qmail/alias I have a file a file called .qmail-unsubscribe.
The file contains one line of text wich says: /home/clifmail/Mailbox
Now if I send a mail message to [EMAIL PROTECTED]
I never see that mes
ty) Note the line that
says "qmaildotmaode=ldapwithprog". That statement says to
execute the deliverprogrampath field if it's defined, otherwise
deliver to whatever the LDAP default is. :)
If you set that to "both", it will execute the .qmail file.
If you only want
Here's my suggestion, try renameing your .qmail file to .qmail-default and see
if that works.
There appears to be depending on how qmail is configured it looks for .qmail or
.qmail-default.
Can anybody exaplain to me what dubs what file qmail looks for? I'm still
trying to figure this out.
.qmail
I've finally got qmail-ldap to deliver to one place (I've given up trying to
avoid a storage location completely, and now everyone's mail will go to the
same Maildir before being removed by .qmail).
But now qmail is not paying attention to the .qmail file in that
directory... it still delivers t
At 09:54 16.11.99 -0500, you wrote:
>Geoff Roberts <[EMAIL PROTECTED]> wrote:
>Give us an example of what you'd like to do, and we'll show you how to
>do it. Depending upon what you're trying to do, something like:
>
>|command ... exit 99 ...
>./Maildir
>
>or
>
>|command ... | safecat
Geoff Roberts <[EMAIL PROTECTED]> wrote:
>>The "commands" in the dot-qmail are delivery instructions.
>>qmail-local follows each instruction in turn.
>>
>>The lines are not chained together in some sort of pipe, so each line gets
>>THE SAME MESSAGE.
>>
>>If you want to do piping, then do everythi
>The "commands" in the dot-qmail are delivery instructions.
>qmail-local follows each instruction in turn.
>
>The lines are not chained together in some sort of pipe, so each line gets
>THE SAME MESSAGE.
>
>If you want to do piping, then do everything on one single line with pipes.
So that mea
From:.*mailaddress/From: newmailaddress/1'
> ./pppdir/
>
>Files are written to the pppdir OK, but the from field is the same as
> before. If I redirect the output of the sed command to a file, it is
> rewriting the from field properly.
>
>Are the commands in dot-qmail files
the sed command to a file, it is
rewriting the from field properly.
Are the commands in dot-qmail files able to do what I would like?
Thanks
Geoff
On Fri, Oct 29, 1999 at 10:07:50AM -, Yusuf Goolamabbas wrote:
>
> Hi, I just tried the following experiement in a .qmail-ext file
> which contains the following line
> /dev/null
>
> Anything I might have missed
Just put a comment in the .qmail-file!
#this comment means that the mail goes
Platform RH 6.0 with kernel 2.2.13
Hi, I just tried the following experiement in a .qmail-ext file
which contains the following line
/dev/null
Sending email to user-ext@machine results in the following message in
the log file
deferral: Unable_to_write_/dev/null:_invalid_argument._(#4.3.0)/
How
Problem solved!!
Thanks to those who mailed me some suggestions..
Basically, if you have a wildcard domain:
+domain.com-:user:UID:GID:/var/spool/dir:-::
You use a .qmail-default in the /var/spool/dir/
If you have
=domain.com-user:user:UID:GID:/var/spool/dir:::
You use a .qmail in the /var/s
On Wed, 21 Jul 1999, Stephen Casey wrote:
> Being very specific:
>
> defaultdelivery/rc
> ./Maildir/
>
> control/rcpthosts
> jobmagic.net
>
> control/virtualdomains
> jobmagic.net:jobmagic.net
>
> users/assign
> +jobmagic.net-:qmailpop:87:81:/var/qmail/users/spool/jobmagic.net:::
>
> /var/qm
Being very specific:
defaultdelivery/rc
./Maildir/
control/rcpthosts
jobmagic.net
control/virtualdomains
jobmagic.net:jobmagic.net
users/assign
+jobmagic.net-:qmailpop:87:81:/var/qmail/users/spool/jobmagic.net:::
/var/qmail/users/spool/jobmagic.net/.qmail-default
&[EMAIL PROTECTED]
/var/qmai
"Stephen Casey" <[EMAIL PROTECTED]> wrote:
>
> I am having terrible trouble getting qmail to
>work for virtual domains. I have followed the advice
>from one of the links on qmail.org, and used the
>users/assign file to break up my site into domains.
What exactly did you put in users/assign?
it gets there, I can't seem
to use a .qmail file to cause forwarding, or Maildir
formats..
Any idea what I could be doing wrong? Some
notes:
* the entire directory tree for delivery is owned
by the correct user/group. It is chmod 700,
except for the .qmail files
On a, May 10, 1999 at 11:44:17AM +1000, Peter Samuel wrote:
>On Mon, 10 May 1999, Pavel Korovin wrote:
>
>> Hi!
>> I feel big troubles with execution programs from .qmail* files.
>> Any stuff after '|' I put in .qmail* files seems to be missed by qmail-local.
On Mon, 10 May 1999, Pavel Korovin wrote:
> Hi!
> I feel big troubles with execution programs from .qmail* files.
> Any stuff after '|' I put in .qmail* files seems to be missed by qmail-local.
It could be either a permission problem or a path problem. Either way,
qmail wi
Hi!
I feel big troubles with execution programs from .qmail* files.
Any stuff after '|' I put in .qmail* files seems to be missed by qmail-local.
I use qmail on OpenBSD-current, i686.
Here is my SYSDEPS:
--- cat SYSDEPS ---
VERSION
systype
hasshsgr.h
hasnpbg1.h
select.h
hasflock.h
On 19 Mar 1999, Scott Schwartz wrote:
> Joel Eriksson <[EMAIL PROTECTED]> writes:
> | [root@hades ~]# /bin/sh -c '{ echo foo; echo bar }'
> | foo
> | bar
> |
> | No trailing ; needed..?
>
> That's a nonstandard feature of whatever shell you've got installed as
> /bin/sh.
Doh!
[root@hades ~]#
On Fri 1999-03-19 (17:04), Scott Schwartz wrote:
> Joel Eriksson <[EMAIL PROTECTED]> writes:
> | > You need a ";" before the "}".
> |
> | Huh?
>
> Yes. That's how the Bourne shell works.
>
> | [root@hades ~]# /bin/sh -c '{ echo foo; echo bar }'
> | foo
> | bar
> |
> | No trailing ; needed..?
Joel Eriksson <[EMAIL PROTECTED]> writes:
| > You need a ";" before the "}".
|
| Huh?
Yes. That's how the Bourne shell works.
| [root@hades ~]# /bin/sh -c '{ echo foo; echo bar }'
| foo
| bar
|
| No trailing ; needed..?
That's a nonstandard feature of whatever shell you've got installed as
/
- Joel Eriksson <[EMAIL PROTECTED]>:
| > You need a ";" before the "}".
|
| Huh?
|
| [root@hades ~]# /bin/sh -c '{ echo foo; echo bar }'
| foo
| bar
|
| No trailing ; needed..?
Lesson one in portable computing: That something works in one
environment does not prove it works in another. The
On 19 Mar 1999, Scott Schwartz wrote:
> Robin Bowes <[EMAIL PROTECTED]> writes:
> | How is the shell used by .qmail files determined?
>
> Hardcoded as /bin/sh.
>
> % grep /bin/sh *.c
> qmail-local.c: args[0] = "/bin/sh"; args[1] = "-c"
On Fri, 19 Mar 1999, Robin Bowes wrote:
> How is the shell used by .qmail files determined?
Use the source, Luke. ;-)
--- extract from qmail-local.c - START
switch(child = fork())
{
case -1:
temp_fork();
case 0:
args[0] = "/bin/sh"; args[1] = "-c";
Robin Bowes <[EMAIL PROTECTED]> writes:
| How is the shell used by .qmail files determined?
Hardcoded as /bin/sh.
% grep /bin/sh *.c
qmail-local.c: args[0] = "/bin/sh"; args[1] = "-c"; args[2] = prog; args[3] = 0;
qmail-local.c: strerr_die3x(111,"Unable to
How is the shell used by .qmail files determined?
The reason I ask is that I was using { } brackets to group commands, eg:
| { echo "To: [EMAIL PROTECTED]"; cat - } | qmail-inject
[EMAIL PROTECTED] [EMAIL PROTECTED]
However, this didn't work; I got the following error:
1
On Tue, Feb 23, 1999 at 04:37:02PM +0100, Victor Regner wrote:
> |bouncesaying "You cannot post to this list" [ "$SENDER"="[EMAIL PROTECTED]"
> ]
> &user1
> &user2
> etc...
>
> my .qmail-users
>
The problem is that qmail checks the envelope sender, and that is $SENDER.
In your case, the envelope
|bouncesaying "You cannot post to this list" [ "$SENDER"="[EMAIL PROTECTED]"
]
&user1
&user2
etc...
my .qmail-users
looks like this but I cant mail to the list i just says You cannot post to this
list which is prob what it's supposed to say when you're not allowed to send to
the list.
Any cl
On Tue, Feb 23, 1999 at 01:22:27PM +0100, Victor Regner wrote:
> I wanna make a one way mailing list. Do I have to install majordomo or
> exmlm or can I just put a line in the .qmail file so that I am the only
> one that can send mail to it?
Put
|bouncesaying "You cannot post to this lis" [ "$SE
I wanna make a one way mailing list. Do I have to install majordomo or
exmlm or can I just put a line in the .qmail file so that I am the only
one that can send mail to it?
Victor
begin:vcard
n:Regner;Victor
tel;pager:0740-132878
tel;cell:070-4920505
tel;fax:08-6948119
tel;work:08-7023158
x-
>I suppose he tries to do the same things as me : renaming user e mail address
>from internal name to external
>I have tried
>|preline sed "s/local\.intranet\.net/my_company\.com/" |
>/usr/local/bin/safecat
>/var/qmail/alias/pppdir/tmp /var/qmail/alias/pppdir/new
>It is creating files but maild
rom [EMAIL PROTECTED]).
So here's my problem. I can currently use dot-qmail files to handle mail
at a domain level with no problem. I'd like to be able to handle it at a
virtual *user* level, however, because the cnmnetwork.com domain
currently has over 7000 users and at the current rat
74 matches
Mail list logo
