Discuss

discuss@lists.centos.org

1 participants
34753 discussions

Rewriting outgoing email addresses
by Lee W 28 Apr '05

28 Apr '05

Hi Everyone, I have a query which I hope others may find interesting as well. The company that I work for has users that subscribe to many different mailing lists for marketting and informational purposes. What I would like to be able to do is centrally manage this internally so that only one copy of the message is received regardless of the number of people subscribed to each list which we can then either deliver the message internally to anyone interested or via public folders on Cyrus IMAP/MS Exchange. The second thing I would like to be able to do is allow people to send to the appropriate list but for their email address to be rewritten to that of the registered email address of the list therefore everyone in the company who is subscribed to the list gets the replies. I am guessing that the following steps would have to be done:- * Setup an internal email account for each list (e.g. centos-list(a)companya.com) * Configure sendmail to either forward the message onto the exchange server and store in public folders or use filtering rules to deliver it to the appropriate Cyrus mailbox. * Maintain a list of all mailing lists subscribed to and have sendmail rewrite the from headers if anyone tries to send a message to one of the registered list addresses. I'm sure I've forgotten things here but I haven't got a clue how to set this up. Is this possible using the included programs with Centos (Sendmail, Cyrus IMAP, procmail)? As a second query but still related is it possible for sendmail to rewrite incoming email addresses? At the company we have various addresses in the format of firstname.surname.ext(a)company.com (where ext could be support or devel, etc). At present we setup distribution lists on exchange for everyone of these addresses for every user and it is becoming a management nightmare. What I would like to be able to do is for sendmail to notice this double-dot format and based on the ext bit to forward it onto the appropriate user as well as the relevent catch all address (i.e. send to firstname.surname(a)company.com and then also send to ext(a)company.com) Sorry if this is a bit long winded but hopefully I've explained clearly enough for someone to offer some insight Thanks in advance Regards Lee

1 0

Re: [CentOS] Intel motherboard BOXD915GAVL very slow with centos 4
by David Thompson 28 Apr '05

28 Apr '05

Jerry Geis wrote: > >All, > >I am installing a BOXD915GAVL system and centos 4. >The CPU is a 2.8 GIG celeron D with 1GIG memory and 120GIG Seagate drive. > >Is is VERY slow. What gives? > >Any other experience with something like this? > >It is installing but even after install when booting it >is taking VERY long time to even get to the Checking new hardware screen. Two bits of advice: 1) -- get and apply the BIOS update from Intel. That solved our performance problems with 915-based systems for both RHEL 3.4 and 4.0 systems. 2) -- don't send HTML email to mailing lists. Happy Hunting. -- Dave Thompson ( thomas(at)cs(dot)wisc(dot)edu ) Associate Researcher Department of Computer Science University of Wisconsin-Madison http://www.cs.wisc.edu/(twiddle)thomas 1210 West Dayton Street Madison, WI 53706-1685 --

2 1

Re: [CentOS] CentOS 4 Software Raid1 questions
by Lee Parmeter 27 Apr '05

27 Apr '05

--- Les Mikesell <lesmikesell(a)gmail.com> wrote: > On Wed, 2005-04-27 at 10:44, Aleksandar Milivojevic > wrote: > > > You'd need to resize file systems after you import > partitions into MD. > > An e2fsck/resize2fs would take care of that. Do an > "fsck -f /dev/md0" > > (for example). It will complain that information in > superblock is wrong > > (partition size fsck sees is smaller than what it found > in superblock). > > Just answer "no" to abort question. After you did > fsck, you need to > > do "resize2fs /dev/md0". Repeat for all md devices you > created. > > > > For above, the file systems should be either unmounted, > or mounted read > > only. The best thing to do is to boot from CD into > rescue mode, and do > > all job from it. > > > > The reason is that MD uses couple of last blocks for > metadata > > information, and that space is no longer usable for > file system data. > > So your /dev/md* metadisks will be slightly smaller > than partitions you > > created them on. > > What happens if existing files are on these blocks before > you > convert? > > > When you are creating mirrors, make sure you list > devices in right > > order. Data is always copied from first disk you > specify to second > > disk. If you get them the wrong way around, you loose > data. > > Another approach that might be safer is to create a > 'broken' mirror > first by specifying the 2nd device as 'missing'. Then > you can build > a filesystem on the md device and mount it somewhere and > copy the > files over from the existing partition. Then unmount the > old partition, > remount the raid device in its place (adjusting > /etc/fstab to match) > and use mdadm to add the old partition into the new raid, > which will > hot-sync it to match the new setup. Good idea, I will give this a try this evening. Thanks for your input concerning this issue. > > There are some rather good HOWTOs on this question > (with much longer, > > detailed and better descriptions of migration process). > Use the Google > > Luke. > > I looked for this and found lots of info on building > RAIDs but none > about preserving an existing filesystem while converting > to a mirror. > Can you provide a link or a good search term to pick that > up? Also, > I have noticed that after syncing the mirrored drives, > you can split > them and mount a single drive from it into another > machine without > making an md device first. (For example, if one part is > on a > USB/firewire drive, you can plug it into a different > machine and mount > the /dev/sda? partition it becomes.) However, I don't > know if this is > harmful or not. Does anyone know if, after running a > while in this mode > it will still work correctly if detected as an md? device > (with or > without resyncing to a partner)? > > -- > Les Mikesell > les(a)futuresource.com > > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos > -- Lee Parmeter Emperor, linXos - The Flying Penguin http://www.linXos.com Linux Registered User #337161 'It's free. It works. Duh.'" - Eric Harrison The United States is NOT a democracy, it was founded as a Republic! God is not a republican or a democrat nor is His government a democracy! - Lee Parmeter __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Intel motherboard BOXD915GAVL very slow with centos 4
by Jerry Geis 27 Apr '05

27 Apr '05

All, I am installing a BOXD915GAVL system and centos 4. The CPU is a 2.8 GIG celeron D with 1GIG memory and 120GIG Seagate drive. Is is VERY slow. What gives? Any other experience with something like this? It is installing but even after install when booting it is taking VERY long time to even get to the Checking new hardware screen. Thanks, Jerry

3 2

RE: [CentOS] Does CentOS has problems with Norton Ghost 2003 images?
by Marc Powell 27 Apr '05

27 Apr '05

> -----Original Message----- > From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On > Behalf Of Juan Pablo Espino > Sent: Wednesday, April 27, 2005 4:33 PM > To: CentOS mailing list > Subject: Re: [CentOS] Does CentOS has problems with Norton Ghost 2003 > images? > > Hi! > > Thanks for your quick response! > We used GRUB with WhiteBox. Also, White Box used the 2.4 kernel and > CentOS uses the 2.6 kernel... any comments? Nope. Not really. I haven't used Ghost in about 5 years so pretty much all I've said so far I've gleaned from publicly available information on the Internet. It seems to me that if you want to continue to use Ghost then their tech support or Google would be your next step. -- Marc

2 1

RE: [CentOS] Does CentOS has problems with Norton Ghost 2003 images?
by Marc Powell 27 Apr '05

27 Apr '05

> -----Original Message----- > From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On > Behalf Of Juan Pablo Espino > Sent: Wednesday, April 27, 2005 3:45 PM > To: centos(a)centos.org > Subject: [CentOS] Does CentOS has problems with Norton Ghost 2003 images? > > Hello all > > We have two very important workstations dedicated to tasks of > development and investigation. At the moment we have installed a dual > boot platform with CentOS 4.0 and Windows XP Proffessional SP2. In > order to do backups of these machines we need to create an image with > Norton Ghost 2003. > > We have worked with Ghost during several years with different > platforms (Red Hat, White Box Linux, Windows) without problems but now > we are facing problems with our CentOS. When the creation of the image > reaches approximately 50% in BOTH machines the Norton Ghost aborts > with an error. Using the "force cloning" option of Ghost we managed > to complete the creation of the image, nevertheless when recovering it > we got this error: GRUB GRUB (the machine never booted) Chapter E, Boot Configuration section of the Ghost2003 manual at ftp://ftp.symantec.com/public/english_us_canada/products/ghost/manuals/g host2003_guide.pdf states -- "Boot configuration Norton Ghost uses the file /etc/lilo.conf to determine the boot configuration. If this file does not match the boot configuration, Norton Ghost may be unable to patch LILO during cloning. The keyword, default, is not supported in Lilo.conf, so the first target specified should be the default target. If a different boot loader, such as grub, is used, or the preceding conditions are not met, Norton Ghost clones the system but the new disk probably will not boot. The system should be started from a floppy disk or CD, and the boot loader should be reinstalled by running /sbin/lilo or an equivalent." That last paragraph seems applicable. Did White Box use lilo or grub? > Then we tried to boot CentOS from a floppy and linux rescue and it > didn't work. Two days ago we made and we recovered images to those > same discs with White Box and WinXP without problems. > > Given our experience with Norton Ghost, we considered seriously that > the problem is CentOS. We did many tests to have arrived at this > consideration. Here are the details: I believe the opposite is more likely. Ghost needs to support the OS on the disk, not the other way around. That's why you can't use Ghost to clone HFS or ReiserFS partitions. The table below supports that conclusion as well -- http://service1.symantec.com/SUPPORT/ghost.nsf/8f7dc138830563c888256c220 0662ecd/b343f521f647fd1b88256caf00755887?OpenDocument&prod=Norton%20Ghos t&ver=2003%20for%20Windows%202000/NT/Me/98/XP&src=sg&pcode=ghost&svy=&cs m=no My guess is that White Box was identical to or close enough to one of the supported versions to work correctly. RHAS4 and therefore CentOS4 are much newer than Ghost 2003 so it's not too much of a stretch to imagine that it's not supported. -- Marc

2 1

Does CentOS has problems with Norton Ghost 2003 images?
by Juan Pablo Espino 27 Apr '05

27 Apr '05

Hello all We have two very important workstations dedicated to tasks of development and investigation. At the moment we have installed a dual boot platform with CentOS 4.0 and Windows XP Proffessional SP2. In order to do backups of these machines we need to create an image with Norton Ghost 2003. We have worked with Ghost during several years with different platforms (Red Hat, White Box Linux, Windows) without problems but now we are facing problems with our CentOS. When the creation of the image reaches approximately 50% in BOTH machines the Norton Ghost aborts with an error. Using the "force cloning" option of Ghost we managed to complete the creation of the image, nevertheless when recovering it we got this error: GRUB GRUB (the machine never booted) Then we tried to boot CentOS from a floppy and linux rescue and it didn't work. Two days ago we made and we recovered images to those same discs with White Box and WinXP without problems. Given our experience with Norton Ghost, we considered seriously that the problem is CentOS. We did many tests to have arrived at this consideration. Here are the details: Two exactly equal machines (the same hardware and resources), except by the hard disk 1. PC DELL Hard disk: Maxtor 20GB RAM: 512 MB Processor: Pentium 3, 866 MHz 2. PC DELL Hard disk: Seagate 20GB RAM: 512 MB Processor: Pentium 3, 866 MHz The disk partitions are: /hda1 windows xp 10 GB /hda2 /boot 100 MB /hda3 / 8900 MB /hda4 swap 1 GB We would like to know if someone has had the same problem (making an image with Norton Ghost 2003 to a dual boot system using Windows and CentOS.) Any suggestions are VERY important for us. Thanks in advance. Regards, Juan P. Espino

2 3

checkproc
by Cameron Showalter 27 Apr '05

27 Apr '05

greetings, trying to install netapplet (http://primates.ximian.com/~rml/netapplet/) from source on a centos 4 laptop. ./configure, make and make install all work fine, but when I then go to /etc/init.d to start netdaemon, it complains that it cannot find checkproc. I can't seem to even find anything on google for redhat or RHEL and checkproc or killproc. The closest I came was finding that killproc is in /etc/init.d/functions... but I'm not sure how to call it, when starting a daemon. thanks in advance. cameron

1 0

Cups updates - overwriting mime.* files
by Nigel Kendrick 27 Apr '05

27 Apr '05

Every time cups is updated I have to check mime.convs and mime.types to ensure that references to handling raw file types are uncommented otherwise we notice that one of our printers stops working because the files are overwritten by the updates. Should config files not be left untouched? We do have 'print command = lpr -r -oraw -P %p %s' in smb.conf but this on its own didn't make the printer work. Do I just need to keep checking or is there a better way Oh, Centos 3.4, by the way! Thanks Nigel Kendrick

3 2

CentOS-announce Digest, Vol 2, Issue 14
by centos-announce-request＠centos.org 27 Apr '05

27 Apr '05

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2005:387 Moderate CentOS 4 i386 and x86_64 cvs - security update (Johnny Hughes) 2. CESA-2005:387 Moderate CentOS 3 x86_64 cvs: security update (Tru Huynh) 3. CESA-2005:387 Moderate CentOS 3 i386 cvs: security update (Tru Huynh) 4. CESA-2005:387 Moderate CentOS 4 ia64 cvs - security update (Pasi Pirhonen) 5. CESA-2005:387 Moderate CentOS 3 ia64 cvs - security update (Pasi Pirhonen) 6. CESA-2005:387 Moderate CentOS 3 s390(x) cvs - security update (Pasi Pirhonen) 7. CESA-2005:377 Low CentOS 3 ia64 sharutils - security update (Pasi Pirhonen) 8. CESA-2005:377 Low CentOS 3 s390(x) sharutils - security update (Pasi Pirhonen) 9. CESA-2005:377 Low CentOS 4 ia64 sharutils - security update (Pasi Pirhonen) 10. CESA-2005:386 Important CentOS 4 ia64 mozilla - security update (Pasi Pirhonen) 11. CESA-2005:386 Important CentOS 4 i386 and x86_64 mozilla - security update (Johnny Hughes) 12. CESA-2005:377 Low CentOS 4 i386 and x86_64 sharutils - security update (Johnny Hughes) 13. CESA-2005:377 Low CentOS 3 x86_64 sharutils - security update (Tru Huynh) 14. CESA-2005:377 Low CentOS 3 i386 sharutils - security update (Tru Huynh) 15. CESA-2005:375 Important CentOS 4 i386 and x86_64 OpenOffice.org - security update (Johnny Hughes) 16. CESA-2005:377-01: Low CentOS 2 i386 sharutils security update (John Newbigin) 17. CESA-2005:387-06: Moderate CentOS 2 i386 cvs security update (John Newbigin) 18. CESA-2005:375 Important CentOS 3 x86_64 OpenOffice.org - security update (Tru Huynh) 19. CESA-2005:375 Important CentOS 3 i386 OpenOffice.org - security update (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Tue, 26 Apr 2005 08:42:59 -0500 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2005:387 Moderate CentOS 4 i386 and x86_64 cvs - security update To: centos-announce(a)centos.org Message-ID: <1114522979.26429.58.camel(a)myth.home.local> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2005:387 Moderate: cvs security update for CentOS-4 i386 and x86_64 http://rhn.redhat.com/errata/RHSA-2005-387.html refers. The following updated files have been uploaded and are currently syncing to the mirrors: i386: cvs-1.11.17-7.RHEL4.i386.rpm x86_64: cvs-1.11.17-7.RHEL4.i386.rpm src: cvs-1.11.17-7.RHEL4.i386.rpm Get this update with: yum update cvs

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss