How to duplicate a copy of all incoming and outgoing mail

2005-10-04 Thread Patrick Dung

It is system wide, not specific user (~/.forward)
Is it possble with Sendmail?
How about Postfix and Qmail?
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: How to duplicate a copy of all incoming and outgoing mail

2005-10-04 Thread Edwin Groothuis
On Tue, Oct 04, 2005 at 05:00:12PM +0800, Patrick Dung wrote:
> It is system wide, not specific user (~/.forward)
> Is it possble with Sendmail?
> How about Postfix and Qmail?

Grep for bcc in the output of postconf for postfix:

[~] [EMAIL PROTECTED]>postconf | grep bcc
always_bcc = 
recipient_bcc_maps = 
sender_bcc_maps = 

Edwin
-- 
Edwin Groothuis  |Personal website: http://www.mavetju.org
[EMAIL PROTECTED]|  Weblog: http://weblog.barnet.com.au/edwin/
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: How to duplicate a copy of all incoming and outgoing mail

2005-10-04 Thread Patrick Dung

Thanks for reply.
Wow, postifx got their power. Very simple.

But I really want to know about Sendmail, because it's default in many Unix.
Checking out http://www.technoids.org/procmailfilter.html but it seems 
quite complex.


Edwin Groothuis wrote:


On Tue, Oct 04, 2005 at 05:00:12PM +0800, Patrick Dung wrote:
 


It is system wide, not specific user (~/.forward)
Is it possble with Sendmail?
How about Postfix and Qmail?
   



Grep for bcc in the output of postconf for postfix:

   [~] [EMAIL PROTECTED]>postconf | grep bcc
   always_bcc = 
   recipient_bcc_maps = 
   sender_bcc_maps = 


Edwin
 



___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: How to duplicate a copy of all incoming and outgoing mail

2005-10-04 Thread Eric Anderson

Patrick Dung wrote:

Thanks for reply.
Wow, postifx got their power. Very simple.

But I really want to know about Sendmail, because it's default in many 
Unix.
Checking out http://www.technoids.org/procmailfilter.html but it seems 
quite complex.


I think you want sendmail's -X option:

-X logfile
Log all traffic in and out of mailers in the indicated log file. This 
should  only be used as a last resort for debugging mailer bugs.  It 
will log a lot of data very quickly.


Eric





Edwin Groothuis wrote:


On Tue, Oct 04, 2005 at 05:00:12PM +0800, Patrick Dung wrote:
 


It is system wide, not specific user (~/.forward)
Is it possble with Sendmail?
How about Postfix and Qmail?
  



Grep for bcc in the output of postconf for postfix:

   [~] [EMAIL PROTECTED]>postconf | grep bcc
   always_bcc =recipient_bcc_maps =sender_bcc_maps =
Edwin
 



___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"



--

Eric AndersonSr. Systems AdministratorCentaur Technology
Anything that works is better than anything that doesn't.

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


re: freebsd-5.4-stable panics

2005-10-04 Thread Rob Watt
> It turns out that the sysctl buffer is already wired in one of the two
> cases
> that this function is called, so I moved the wiring up to the upper
layer
> in
> the other case and cut out a bunch of the locking gymnastics as a
result.
> Can you try this patch?
>
> Index: kern_proc.c
> ===
> RCS file: /usr/cvs/src/sys/kern/kern_proc.c,v
> retrieving revision 1.231
> diff -u -r1.231 kern_proc.c
> --- kern_proc.c 27 Sep 2005 18:03:15 - 1.231
> +++ kern_proc.c 30 Sep 2005 17:04:57 -
> @@ -875,22 +875,16 @@
>
> if (flags & KERN_PROC_NOTHREADS) {
> fill_kinfo_proc(p, &kinfo_proc);
> - PROC_UNLOCK(p);
> error = SYSCTL_OUT(req, (caddr_t)&kinfo_proc,
> sizeof(kinfo_proc));
> - PROC_LOCK(p);
> } else {
> - _PHOLD(p);
> FOREACH_THREAD_IN_PROC(p, td) {
> fill_kinfo_thread(td, &kinfo_proc);
> - PROC_UNLOCK(p);
> error = SYSCTL_OUT(req, (caddr_t)&kinfo_proc,
> sizeof(kinfo_proc));
> - PROC_LOCK(p);
> if (error)
> break;
> }
> - _PRELE(p);
> }
> PROC_UNLOCK(p);
> if (error)
> @@ -932,6 +926,9 @@
> if (oid_number == KERN_PROC_PID) {
> if (namelen != 1)
> return (EINVAL);
> + error = sysctl_wire_old_buffer(req, 0);
> + if (error)
> + return (error);
> p = pfind((pid_t)name[0]);
> if (!p)
> return (ESRCH);

John,

We tried this patch and were able to run our simulations (and top) for 3
days straight without crashing. Since we were panicking every 3-6 hours
before when running top, this seems to have fixed the problem.

We noticed the patches from Don Lewis, but have not tested them yet. We
weren't sure if we could just apply those patches against 6.0-BETA5, or
whether we should wait for them to be MFC'd.

-
Rob Watt
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Moving Files

2005-10-04 Thread John Baldwin
On Monday 03 October 2005 03:24 pm, Maslan wrote:
> hello,
> i was wondering what/where changes should i do to make files when
> moving a file from directory to another in the kernel source.
> for example if want to move all /usr/src/sys/i386 , /usr/src/sys/ia64
> in /usr/src/sys/intel/i386 and /usr/src/sys/intel/ia64.
> so can any one point me to any document or webpage that discuss this stuff
> ? thanks you very much

The location of files that config(8) uses to generate the Makefile for a 
kernel build are stored in sys/conf/files*

-- 
John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: freebsd-5.4-stable panics

2005-10-04 Thread Don Lewis
On  3 Oct, Rob Watt wrote:
>> It turns out that the sysctl buffer is already wired in one of the two
>> cases
>> that this function is called, so I moved the wiring up to the upper
> layer
>> in
>> the other case and cut out a bunch of the locking gymnastics as a
> result.
>> Can you try this patch?
>>
>> Index: kern_proc.c
>> ===
>> RCS file: /usr/cvs/src/sys/kern/kern_proc.c,v
>> retrieving revision 1.231
>> diff -u -r1.231 kern_proc.c
>> --- kern_proc.c 27 Sep 2005 18:03:15 - 1.231
>> +++ kern_proc.c 30 Sep 2005 17:04:57 -
>> @@ -875,22 +875,16 @@
>>
>> if (flags & KERN_PROC_NOTHREADS) {
>> fill_kinfo_proc(p, &kinfo_proc);
>> - PROC_UNLOCK(p);
>> error = SYSCTL_OUT(req, (caddr_t)&kinfo_proc,
>> sizeof(kinfo_proc));
>> - PROC_LOCK(p);
>> } else {
>> - _PHOLD(p);
>> FOREACH_THREAD_IN_PROC(p, td) {
>> fill_kinfo_thread(td, &kinfo_proc);
>> - PROC_UNLOCK(p);
>> error = SYSCTL_OUT(req, (caddr_t)&kinfo_proc,
>> sizeof(kinfo_proc));
>> - PROC_LOCK(p);
>> if (error)
>> break;
>> }
>> - _PRELE(p);
>> }
>> PROC_UNLOCK(p);
>> if (error)
>> @@ -932,6 +926,9 @@
>> if (oid_number == KERN_PROC_PID) {
>> if (namelen != 1)
>> return (EINVAL);
>> + error = sysctl_wire_old_buffer(req, 0);
>> + if (error)
>> + return (error);
>> p = pfind((pid_t)name[0]);
>> if (!p)
>> return (ESRCH);
> 
> John,
> 
> We tried this patch and were able to run our simulations (and top) for 3
> days straight without crashing. Since we were panicking every 3-6 hours
> before when running top, this seems to have fixed the problem.
> 
> We noticed the patches from Don Lewis, but have not tested them yet. We
> weren't sure if we could just apply those patches against 6.0-BETA5, or
> whether we should wait for them to be MFC'd.

I haven't tried applying my patch to RELENG_5 yet, but hope to do so in
the next few days in preparation for doing a MFC.  If any changes are
required, I can send you a copy of the patch.


___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: How to duplicate a copy of all incoming and outgoing mail

2005-10-04 Thread Fernando Gleiser

On Tue, 4 Oct 2005, Patrick Dung wrote:


Thanks for reply.
Wow, postifx got their power. Very simple.

But I really want to know about Sendmail, because it's default in many Unix.
Checking out http://www.technoids.org/procmailfilter.html but it seems quite 
complex.


You can use mailsnarf (part of dsniff port) tosniff all the mails
from the net and drop into an mbox file.

For sendmail, you can try mimedefang. it was functions to add/remove
recipients from any message.



Fer
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Moving Files

2005-10-04 Thread Maslan
On 10/4/05, John Baldwin <[EMAIL PROTECTED]> wrote:
> On Monday 03 October 2005 03:24 pm, Maslan wrote:
> > hello,
> > i was wondering what/where changes should i do to make files when
> > moving a file from directory to another in the kernel source.
> > for example if want to move all /usr/src/sys/i386 , /usr/src/sys/ia64
> > in /usr/src/sys/intel/i386 and /usr/src/sys/intel/ia64.
> > so can any one point me to any document or webpage that discuss this stuff
> > ? thanks you very much
>
> The location of files that config(8) uses to generate the Makefile for a
> kernel build are stored in sys/conf/files*
>
> --
> John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
> "Power Users Use the Power to Serve"  =  http://www.FreeBSD.org
>

thanks
that's what i was searchinf for ;-)

--
I'm Searching For Perfection,
So Even If U Need Portability U've To Use Assembly ;-)
http://www.maslanlab.org
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: LOR #55 fix proposal (kern_descrip.c patch)

2005-10-04 Thread Roman Kurakin

Commited.

Roman Kurakin:


Hi,

   It seems that the LOR #55 
(http://sources.zabbadoz.net/freebsd/lor.html#055)
could be fixed by following patch. I need testers and reviewers of it 
since I want

to commit it.

   I do not see a reason why not to extend action of FILEDESC_LOCK.

(http://www.cronyx.ru/~rik/freebsd/lor055/lor55.pch)

Index: kern_descrip.c
===
RCS file: /home/ncvs/src/sys/kern/kern_descrip.c,v
retrieving revision 1.280
diff -u -r1.280 kern_descrip.c
--- kern_descrip.c  26 Aug 2005 11:16:39 -  1.280
+++ kern_descrip.c  27 Sep 2005 17:31:57 -
@@ -2275,7 +2275,6 @@
   fdused(fdp, indx);
   if (fp != NULL)
   FILE_LOCK(fp);
-   FILEDESC_UNLOCK(fdp);

   /*
* We now own the reference to fp that the ofiles[] array
@@ -2283,6 +2282,9 @@
*/
   if (fp != NULL)
   fdrop_locked(fp, td);
+
+   FILEDESC_UNLOCK(fdp);
+
   return (0);

   default:

Best regards,
rik

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to 
"[EMAIL PROTECTED]"




___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"