Re: Intel SRCU42X SCSI RAID contoller
Sebastiaan wrote: Hi, On Wed, 28 Jan 2004, Marcin Owsiany wrote: Hi! Forgive me the cross-post, but this is rather urgent for me :-/ Does anyone know if the Debian kernel in woody-proposed-updates (2.4.22) supports Intel SRCU42X SCSI RAID contoller? Intel's web page says that it is supported by Suse and RH, but they make a binary driver available for download (megaraid.o). The source is included, so probablu it the same as in stock kernel, but could anyone confirm this? Not sure. I can't find it in the official kernel 2.4.23 (www.kernel.org), or I am looking over it. What I can find is a driver with the same module name: CONFIG_SCSI_MEGARAID: This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490, 467, 471 and 493 SCSI host adapters. This is the old and very heavily tested driver but lacks features like clustering. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called megaraid.o. - Either this module is compatible with your mega raid, or suse and rh gave a very poor name. I have looked to the kernel patches, but I could not find information about CONFIG_SCSI_MEGARAID, so I assume it is disabled by default. If you don't need to boot from your controller, you can compile the module afterwards, otherwise a module isn't good enough and you should compile your custom kernel before installation. FYI This card is HEAVILY based or the LSI reference card that Megaraid uses so there is a good chance the standard megaraid driver will work
Re: I/O performance issues on 2.4.23 SMP system
Mark Ferlatte wrote: Benjamin Sherman said on Wed, Jan 28, 2004 at 03:16:56PM -0600: I've got some machines in nearly the same configuration. What I ended up doing was to put an `append="mem=1G"' in the lilo.conf boot stanza for the kernel I was using, and rebooted the machine in question. This does reduce the available memory in the machine to 1GB, but solves the IO problem. In my case, it was much faster, even though MySQL couldn't buffer nearly as much as with 4GB. Thanks, Mark. I will probably try this with 3GB instead of 1GB. Did you try that? Yes; it didn't work. The problem (bug) is that block device IO has to go through buffers that are below 1GB. The memory manager doesn't know this, so what happens is that the IO layer requests a block of memory below 1GB, and the swapout daemon (kswapd) then runs around like a madman trying to free pages, instead of shuffling pages that don't need to be below 1GB to higher memory addresses. Since many of the pages below 1GB can't be freed (they belong to active programs), the IO starves. With 1GB of memory, both the IO layer and the swapout daemon are working with the same view of memory, so the bug is concealed, and performance is good. I have heard of people trying 2GB, and having it work, but it didn't for me. M Is this problem specific to the 3ware cards? does anyone know of any issues with the Highpoint 1640 SATA RAID cards? Any experience or recomendations with these? Which is the best SATA raid card for linux at the moment? Thanks José PS. please reply to the list.
Re: Intel SRCU42X SCSI RAID contoller
Sebastiaan wrote: Hi, On Wed, 28 Jan 2004, Marcin Owsiany wrote: Hi! Forgive me the cross-post, but this is rather urgent for me :-/ Does anyone know if the Debian kernel in woody-proposed-updates (2.4.22) supports Intel SRCU42X SCSI RAID contoller? Intel's web page says that it is supported by Suse and RH, but they make a binary driver available for download (megaraid.o). The source is included, so probablu it the same as in stock kernel, but could anyone confirm this? Not sure. I can't find it in the official kernel 2.4.23 (www.kernel.org), or I am looking over it. What I can find is a driver with the same module name: CONFIG_SCSI_MEGARAID: This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490, 467, 471 and 493 SCSI host adapters. This is the old and very heavily tested driver but lacks features like clustering. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called megaraid.o. - Either this module is compatible with your mega raid, or suse and rh gave a very poor name. I have looked to the kernel patches, but I could not find information about CONFIG_SCSI_MEGARAID, so I assume it is disabled by default. If you don't need to boot from your controller, you can compile the module afterwards, otherwise a module isn't good enough and you should compile your custom kernel before installation. FYI This card is HEAVILY based or the LSI reference card that Megaraid uses so there is a good chance the standard megaraid driver will work -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Postfix doesn't reject empty senders --good ;-)
I am happy that the protocol is so simple.
If it was not for the RFC's, which do not work that well in modern times
where would we work ?
SMTP has been around for a very long time:
"The SMTP specification originally started with the Mail Transfer
Protocol in 1980, evolved into Simple Mail Transfer Protocol (SMTP) in
1981, and since has been enhanced into the protocol we know today."
Source: http://freebooks.by.ru/view/RedHatLinux6Unleashed/rhl6u065.htm
'Eric Allman' did us all a favor and created a great amount of industry by
drafting and distributing a simple protocol that was so trusting. ;-)
On a more serious note, I met Eric at a LISA conference in Philadelphia
and a young Debian developer told him
he should modify the protocol, but Eric said he could not for there
are too many applications dependent on it staying the same. He would
probably get sued if he modified now. Email is big business.
Look at all the money/jobs the trusting protocol created:
1. SPAM
2. Anti-SPAM Software
3. Email Viruses
4. Anti-virus software
5. Many more people employed in the email business than would be otherwise.
On 28/01/04 18:48 +0100, Tom?s N??ez Lirola wrote:
> Hi
> My smtp server (postfix) was receiving a lot of mails with empty senders
> ("mail from:<>"), and it sends them as they was from
> "[EMAIL PROTECTED]". I want to change this behaviour, so I added to
> main.cf the line
>
> 'smtpd_sender_restrictions = reject_non_fqdn_sender'
>
> thinking that "<>" is not a fqdn. But after that, postfix still sends them.
> So
> I added
>
> 'smtpd_sender_restrictions = reject_non_fqdn_sender,
> reject_unknown_sender_domain'
>
> but this way I get the same response:
>
> helo k
> 250 mydomain.com
> mail from:<>
> 250 Ok
> rcpt to:[EMAIL PROTECTED]
> 250 Ok
> data
> 354 End data with .
> fds
> fdsfsf
> fdsfs
> .
> 250 Ok: queued as B4F7C3EFF
> quit
> 221 Bye
>
>
> RTFM'ing, I don't find any more option to reject this kind of senders, so I
> don't know what to do...
> Am I doing anything wrong? Can anyone please help me?
>
> Thank you very much
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
--
--
Ted Knab
Chester, MD 21619
--
35570707f6274702478656021626f6c6964796f6e602f66602478656
02e6164796f6e60237471647560216e6460276c6f62616c60257e696
4797e2a0
Exim: Different mail retry times depending upon response from remote host...
You don't have to be a rocket scientist to realize that the following remote mailer messages give varying degrees of optimism regarding future delivery: 550 Requested action not taken: mailbox unavailable 452 Mailbox full 452 Insufficient disk space; try again later 421 Too many concurrent SMTP connections; please try again later. With the first, you're pretty sure that the problem is *not* going to be corrected in the next few days. Meanwhile, the others give you some hope in waiting. Unfortunately, I haven't seen anything in Exim that lets you customize it's retry behavior based upon this. It does offer an "error" field in the retry section, but it's only for some silly hard-coded failure types. So, I wrote a little script that goes through all of the msglog files and finds good candidates to toss (ie, "No such user", "Account Terminated", etc.). With just a day's worth of tweaking the script, I've managed to get the pending queue down to about 1/3 of what it was. But I figured I'd ask... does anybody already have a script for doing this (or maybe a better way altogether, since this script has to be explicitly run periodically)? - Joe
Re: I/O performance issues on 2.4.23 SMP system
Mark Ferlatte wrote: Benjamin Sherman said on Wed, Jan 28, 2004 at 03:16:56PM -0600: I've got some machines in nearly the same configuration. What I ended up doing was to put an `append="mem=1G"' in the lilo.conf boot stanza for the kernel I was using, and rebooted the machine in question. This does reduce the available memory in the machine to 1GB, but solves the IO problem. In my case, it was much faster, even though MySQL couldn't buffer nearly as much as with 4GB. Thanks, Mark. I will probably try this with 3GB instead of 1GB. Did you try that? Yes; it didn't work. The problem (bug) is that block device IO has to go through buffers that are below 1GB. The memory manager doesn't know this, so what happens is that the IO layer requests a block of memory below 1GB, and the swapout daemon (kswapd) then runs around like a madman trying to free pages, instead of shuffling pages that don't need to be below 1GB to higher memory addresses. Since many of the pages below 1GB can't be freed (they belong to active programs), the IO starves. With 1GB of memory, both the IO layer and the swapout daemon are working with the same view of memory, so the bug is concealed, and performance is good. I have heard of people trying 2GB, and having it work, but it didn't for me. M Is this problem specific to the 3ware cards? does anyone know of any issues with the Highpoint 1640 SATA RAID cards? Any experience or recomendations with these? Which is the best SATA raid card for linux at the moment? Thanks José PS. please reply to the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Postfix doesn't reject empty senders --good ;-)
I am happy that the protocol is so simple.
If it was not for the RFC's, which do not work that well in modern times
where would we work ?
SMTP has been around for a very long time:
"The SMTP specification originally started with the Mail Transfer
Protocol in 1980, evolved into Simple Mail Transfer Protocol (SMTP) in
1981, and since has been enhanced into the protocol we know today."
Source: http://freebooks.by.ru/view/RedHatLinux6Unleashed/rhl6u065.htm
'Eric Allman' did us all a favor and created a great amount of industry by
drafting and distributing a simple protocol that was so trusting. ;-)
On a more serious note, I met Eric at a LISA conference in Philadelphia
and a young Debian developer told him
he should modify the protocol, but Eric said he could not for there
are too many applications dependent on it staying the same. He would
probably get sued if he modified now. Email is big business.
Look at all the money/jobs the trusting protocol created:
1. SPAM
2. Anti-SPAM Software
3. Email Viruses
4. Anti-virus software
5. Many more people employed in the email business than would be otherwise.
On 28/01/04 18:48 +0100, Tom?s N??ez Lirola wrote:
> Hi
> My smtp server (postfix) was receiving a lot of mails with empty senders
> ("mail from:<>"), and it sends them as they was from
> "[EMAIL PROTECTED]". I want to change this behaviour, so I added to
> main.cf the line
>
> 'smtpd_sender_restrictions = reject_non_fqdn_sender'
>
> thinking that "<>" is not a fqdn. But after that, postfix still sends them. So
> I added
>
> 'smtpd_sender_restrictions = reject_non_fqdn_sender,
> reject_unknown_sender_domain'
>
> but this way I get the same response:
>
> helo k
> 250 mydomain.com
> mail from:<>
> 250 Ok
> rcpt to:[EMAIL PROTECTED]
> 250 Ok
> data
> 354 End data with .
> fds
> fdsfsf
> fdsfs
> .
> 250 Ok: queued as B4F7C3EFF
> quit
> 221 Bye
>
>
> RTFM'ing, I don't find any more option to reject this kind of senders, so I
> don't know what to do...
> Am I doing anything wrong? Can anyone please help me?
>
> Thank you very much
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
--
--
Ted Knab
Chester, MD 21619
--
35570707f6274702478656021626f6c6964796f6e602f66602478656
02e6164796f6e60237471647560216e6460276c6f62616c60257e696
4797e2a0
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Postfix doesn't reject empty senders
On January 28, 2004 12:48 pm, Tomàs Núñez Lirola wrote:
> My smtp server (postfix) was receiving a lot of mails with empty senders
> ("mail from:<>"), and it sends them as they was from
> "[EMAIL PROTECTED]". I want to change this behaviour, so I added to
> main.cf the line
Bounces are sent from the null sender, blocking such messages is usually a bad
idea.
--
Fraser Campbell <[EMAIL PROTECTED]> http://www.wehave.net/
Georgetown, Ontario, Canada Debian GNU/Linux
Exim: Different mail retry times depending upon response from remote host...
You don't have to be a rocket scientist to realize that the following remote mailer messages give varying degrees of optimism regarding future delivery: 550 Requested action not taken: mailbox unavailable 452 Mailbox full 452 Insufficient disk space; try again later 421 Too many concurrent SMTP connections; please try again later. With the first, you're pretty sure that the problem is *not* going to be corrected in the next few days. Meanwhile, the others give you some hope in waiting. Unfortunately, I haven't seen anything in Exim that lets you customize it's retry behavior based upon this. It does offer an "error" field in the retry section, but it's only for some silly hard-coded failure types. So, I wrote a little script that goes through all of the msglog files and finds good candidates to toss (ie, "No such user", "Account Terminated", etc.). With just a day's worth of tweaking the script, I've managed to get the pending queue down to about 1/3 of what it was. But I figured I'd ask... does anybody already have a script for doing this (or maybe a better way altogether, since this script has to be explicitly run periodically)? - Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Postfix doesn't reject empty senders
On January 28, 2004 12:48 pm, Tomàs Núñez Lirola wrote:
> My smtp server (postfix) was receiving a lot of mails with empty senders
> ("mail from:<>"), and it sends them as they was from
> "[EMAIL PROTECTED]". I want to change this behaviour, so I added to
> main.cf the line
Bounces are sent from the null sender, blocking such messages is usually a bad
idea.
--
Fraser Campbell <[EMAIL PROTECTED]> http://www.wehave.net/
Georgetown, Ontario, Canada Debian GNU/Linux
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
--On Wednesday, January 28, 2004 18:54 -0500 [EMAIL PROTECTED] wrote: I'm curious why you say that. I have exim on 3 smtp gateway machines servicing 11G+ email/day, hundreds of thousands of actual messages, doing LDAP lookups for routing, and MailScanner/f-prot running on all the boxes. FYI we've had serious problems with f-prot -- it chokes up on PDF files, going into infinite loop until it times out. Seriously, I'm not looking for a fight, just info. When I did performance tests on all the MTAs a few years back, exim beat the crap out of everything. Tim -- < Tim Sailer (at home) >< Coastal Internet, Inc. << Network and Systems Operations >< PO Box 726 << http://www.buoy.com >< Moriches, NY 11955 << [EMAIL PROTECTED]/[EMAIL PROTECTED] >< (631)399-2910 (888) 924-3728 << < -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Michael Loftis Modwest Sr. Systems Administrator Powerful, Affordable Web Hosting GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E
Re: Postfix doesn't reject empty senders
It is an RFC requirement to accept <> as a valid MAIL FROM -- almost all
bounce messages use this as well as certain other circumstances, to
indicate they do not wish to receive a bounce message in the event of a
delivery error. I don't even think that postfix allows it to be turned off
at all.
--On Wednesday, January 28, 2004 18:48 +0100 Tomàs Núñez Lirola
<[EMAIL PROTECTED]> wrote:
Hi
My smtp server (postfix) was receiving a lot of mails with empty senders
("mail from:<>"), and it sends them as they was from
"[EMAIL PROTECTED]". I want to change this behaviour, so I added to
main.cf the line
'smtpd_sender_restrictions = reject_non_fqdn_sender'
thinking that "<>" is not a fqdn. But after that, postfix still sends
them. So I added
'smtpd_sender_restrictions = reject_non_fqdn_sender,
reject_unknown_sender_domain'
but this way I get the same response:
helo k
250 mydomain.com
mail from:<>
250 Ok
rcpt to:[EMAIL PROTECTED]
250 Ok
data
354 End data with .
fds
fdsfsf
fdsfs
.
250 Ok: queued as B4F7C3EFF
quit
221 Bye
RTFM'ing, I don't find any more option to reject this kind of senders, so
I don't know what to do...
Am I doing anything wrong? Can anyone please help me?
Thank you very much
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
--
Michael Loftis
Modwest Sr. Systems Administrator
Powerful, Affordable Web Hosting
GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E
Re: Postfix doesn't reject empty senders
On Mi, Jan 28, 2004 at 06:48:54 +0100, TomÃs NÃÃez Lirola <[EMAIL PROTECTED]> wrote: > > > RTFM'ing, I don't find any more option to reject this kind of senders, so I > don't know what to do... > Am I doing anything wrong? Can anyone please help me? You must not reject messages with an empty envelope-from since those are delivery status notifications (aka "error messages"). Regards, Franz Georg KÃhler
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
On Thu, Jan 29, 2004 at 10:36:29AM +1100, Craig Sanders wrote: > i can't answer your question, but here's some relevant advice for you: > > exim doesn't scale. if you want performance, switch to postfix. I'm curious why you say that. I have exim on 3 smtp gateway machines servicing 11G+ email/day, hundreds of thousands of actual messages, doing LDAP lookups for routing, and MailScanner/f-prot running on all the boxes. Seriously, I'm not looking for a fight, just info. When I did performance tests on all the MTAs a few years back, exim beat the crap out of everything. Tim -- >< >> Tim Sailer (at home) >< Coastal Internet, Inc. << >> Network and Systems Operations >< PO Box 726 << >> http://www.buoy.com >< Moriches, NY 11955 << >> [EMAIL PROTECTED]/[EMAIL PROTECTED] >< (631)399-2910 (888) 924-3728 >> << ><
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
Craig Sanders wrote: i can't answer your question, but here's some relevant advice for you: exim doesn't scale. if you want performance, switch to postfix. Yeah... well... I've already moved every other machine I deal with over to Courier. I like it because it's one-stop-shopping for all of my mail needs (ie, smtp, pop, and imap modules as well as an ssl version of each), because it supports authenticated smtp (which I understand Exim4 does now but too late for me), and also because it has a variety of authentication methods. We just haven't had the time to figure out how to port all of our virtual domains over to Courier yet, so we're still using Exim for the time being. - Joe
Postfix doesn't reject empty senders
Hi
My smtp server (postfix) was receiving a lot of mails with empty senders
("mail from:<>"), and it sends them as they was from
"[EMAIL PROTECTED]". I want to change this behaviour, so I added to
main.cf the line
'smtpd_sender_restrictions = reject_non_fqdn_sender'
thinking that "<>" is not a fqdn. But after that, postfix still sends them. So
I added
'smtpd_sender_restrictions = reject_non_fqdn_sender,
reject_unknown_sender_domain'
but this way I get the same response:
helo k
250 mydomain.com
mail from:<>
250 Ok
rcpt to:[EMAIL PROTECTED]
250 Ok
data
354 End data with .
fds
fdsfsf
fdsfs
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
> exim doesn't scale. if you want performance, switch to postfix. Is there good documentation available for postfix? Last time I looked I could not find anything close to the quality of exim's. I'd be happy if that has changed though! Take care, Dale -- Dale E. Martin, Clifton Labs, Inc. Senior Computer Engineer [EMAIL PROTECTED] http://www.cliftonlabs.com pgp key available
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
On Wed, Jan 28, 2004 at 01:23:02PM -0800, Joe Emenaker wrote: > The directory was using 17 megs that really hurts performance on an ext2/ext3 partition. some other filesystems (e.g. reiser, xfs) aren't affected so badly by huge directories. > I'm not talking about the FILES in the directory... I'm talking about > the directory ENTRIES (filename, inode number, etc.). I was forced to > just say "screw it!" and I mv'd the input and msglog folders to other > names and then created new, empty ones so that our mail server wouldn't > buckle under the load. > > But anyway, like the subject line says, my real question is: why doesn't > Exim ever clean this stuff out itself? i can't answer your question, but here's some relevant advice for you: exim doesn't scale. if you want performance, switch to postfix. craig
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
--On Wednesday, January 28, 2004 18:54 -0500 [EMAIL PROTECTED] wrote: I'm curious why you say that. I have exim on 3 smtp gateway machines servicing 11G+ email/day, hundreds of thousands of actual messages, doing LDAP lookups for routing, and MailScanner/f-prot running on all the boxes. FYI we've had serious problems with f-prot -- it chokes up on PDF files, going into infinite loop until it times out. Seriously, I'm not looking for a fight, just info. When I did performance tests on all the MTAs a few years back, exim beat the crap out of everything. Tim -- < Tim Sailer (at home) >< Coastal Internet, Inc. << Network and Systems Operations >< PO Box 726 << http://www.buoy.com >< Moriches, NY 11955 << [EMAIL PROTECTED]/[EMAIL PROTECTED] >< (631)399-2910 (888) 924-3728 << < -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Michael Loftis Modwest Sr. Systems Administrator Powerful, Affordable Web Hosting GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Postfix doesn't reject empty senders
It is an RFC requirement to accept <> as a valid MAIL FROM -- almost all
bounce messages use this as well as certain other circumstances, to
indicate they do not wish to receive a bounce message in the event of a
delivery error. I don't even think that postfix allows it to be turned off
at all.
--On Wednesday, January 28, 2004 18:48 +0100 Tomàs Núñez Lirola
<[EMAIL PROTECTED]> wrote:
Hi
My smtp server (postfix) was receiving a lot of mails with empty senders
("mail from:<>"), and it sends them as they was from
"[EMAIL PROTECTED]". I want to change this behaviour, so I added to
main.cf the line
'smtpd_sender_restrictions = reject_non_fqdn_sender'
thinking that "<>" is not a fqdn. But after that, postfix still sends
them. So I added
'smtpd_sender_restrictions = reject_non_fqdn_sender,
reject_unknown_sender_domain'
but this way I get the same response:
helo k
250 mydomain.com
mail from:<>
250 Ok
rcpt to:[EMAIL PROTECTED]
250 Ok
data
354 End data with .
fds
fdsfsf
fdsfs
.
250 Ok: queued as B4F7C3EFF
quit
221 Bye
RTFM'ing, I don't find any more option to reject this kind of senders, so
I don't know what to do...
Am I doing anything wrong? Can anyone please help me?
Thank you very much
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
--
Michael Loftis
Modwest Sr. Systems Administrator
Powerful, Affordable Web Hosting
GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
* Joe Emenaker schrieb am 28.01.04 um 22:23 Uhr: > Here's a question that has always been bugging me. > > Ever since we moved from smail to exim many years ago at my isp, exim > never seems to discard messages in the input queue. > > Even though the single retry rule is the stock one (which retrys for > something like 4 days), we end up with stuff that is weeks... months > old. Periodically, it would get pretty full and we'd notice that there > were about 10 queue runners going and so I'd go in and do a "find" and > remove anything older than 14 days or so. I *had* to do a find, because > doing an "ls" would just sit there an churn for about a half-hour. > > Anyhow, as our customer base has grown and as their e-mail usage has > grown, the problem has reached an all-time high. With this SCO DDoS > virus going around, I had occasion to go clean out the input queue > again. > > The directory was using 17 megs > > I'm not talking about the FILES in the directory... I'm talking about > the directory ENTRIES (filename, inode number, etc.). I was forced to > just say "screw it!" and I mv'd the input and msglog folders to other > names and then created new, empty ones so that our mail server wouldn't > buckle under the load. > > But anyway, like the subject line says, my real question is: why doesn't > Exim ever clean this stuff out itself? > additional to the other postings something like ignore_errmsg_errors_after = 16h is also useful regards -marc -- +--+ | --> http://www.links2linux.de <-- | | | +---Registered-Linux-User-#136487http://counter.li.org +
Re: Postfix doesn't reject empty senders
On Mi, Jan 28, 2004 at 06:48:54 +0100, TomÃs NÃÃez Lirola <[EMAIL PROTECTED]> wrote: > > > RTFM'ing, I don't find any more option to reject this kind of senders, so I > don't know what to do... > Am I doing anything wrong? Can anyone please help me? You must not reject messages with an empty envelope-from since those are delivery status notifications (aka "error messages"). Regards, Franz Georg KÃhler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
On Thu, Jan 29, 2004 at 10:36:29AM +1100, Craig Sanders wrote: > i can't answer your question, but here's some relevant advice for you: > > exim doesn't scale. if you want performance, switch to postfix. I'm curious why you say that. I have exim on 3 smtp gateway machines servicing 11G+ email/day, hundreds of thousands of actual messages, doing LDAP lookups for routing, and MailScanner/f-prot running on all the boxes. Seriously, I'm not looking for a fight, just info. When I did performance tests on all the MTAs a few years back, exim beat the crap out of everything. Tim -- >< >> Tim Sailer (at home) >< Coastal Internet, Inc. << >> Network and Systems Operations >< PO Box 726 << >> http://www.buoy.com >< Moriches, NY 11955 << >> [EMAIL PROTECTED]/[EMAIL PROTECTED] >< (631)399-2910 (888) 924-3728 << >< -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
Craig Sanders wrote: i can't answer your question, but here's some relevant advice for you: exim doesn't scale. if you want performance, switch to postfix. Yeah... well... I've already moved every other machine I deal with over to Courier. I like it because it's one-stop-shopping for all of my mail needs (ie, smtp, pop, and imap modules as well as an ssl version of each), because it supports authenticated smtp (which I understand Exim4 does now but too late for me), and also because it has a variety of authentication methods. We just haven't had the time to figure out how to port all of our virtual domains over to Courier yet, so we're still using Exim for the time being. - Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Postfix doesn't reject empty senders
Hi
My smtp server (postfix) was receiving a lot of mails with empty senders
("mail from:<>"), and it sends them as they was from
"[EMAIL PROTECTED]". I want to change this behaviour, so I added to
main.cf the line
'smtpd_sender_restrictions = reject_non_fqdn_sender'
thinking that "<>" is not a fqdn. But after that, postfix still sends them. So
I added
'smtpd_sender_restrictions = reject_non_fqdn_sender,
reject_unknown_sender_domain'
but this way I get the same response:
helo k
250 mydomain.com
mail from:<>
250 Ok
rcpt to:[EMAIL PROTECTED]
250 Ok
data
354 End data with .
fds
fdsfsf
fdsfs
.
250 Ok: queued as B4F7C3EFF
quit
221 Bye
RTFM'ing, I don't find any more option to reject this kind of senders, so I
don't know what to do...
Am I doing anything wrong? Can anyone please help me?
Thank you very much
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
> exim doesn't scale. if you want performance, switch to postfix. Is there good documentation available for postfix? Last time I looked I could not find anything close to the quality of exim's. I'd be happy if that has changed though! Take care, Dale -- Dale E. Martin, Clifton Labs, Inc. Senior Computer Engineer [EMAIL PROTECTED] http://www.cliftonlabs.com pgp key available -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
Maarten Vink wrote: Does the output of the "mailq" command provide any useful information about these messages? My first guess would be that you're dealing with "frozen" messages Yup. A lot of them are frozen. If that is the case, have a look at the "timeout_frozen_after" setting; this will automatically remove messages after being frozen for a certain period. I'm already using: timeout_frozen_after=48h but that doesn't seem to be doing anything. - Joe
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
On Wed, Jan 28, 2004 at 01:23:02PM -0800, Joe Emenaker wrote: > The directory was using 17 megs that really hurts performance on an ext2/ext3 partition. some other filesystems (e.g. reiser, xfs) aren't affected so badly by huge directories. > I'm not talking about the FILES in the directory... I'm talking about > the directory ENTRIES (filename, inode number, etc.). I was forced to > just say "screw it!" and I mv'd the input and msglog folders to other > names and then created new, empty ones so that our mail server wouldn't > buckle under the load. > > But anyway, like the subject line says, my real question is: why doesn't > Exim ever clean this stuff out itself? i can't answer your question, but here's some relevant advice for you: exim doesn't scale. if you want performance, switch to postfix. craig -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
On Wed, Jan 28, 2004 at 01:23:02PM -0800, Joe Emenaker wrote: > Even though the single retry rule is the stock one (which retrys for > something like 4 days), we end up with stuff that is weeks... months > old. Periodically, it would get pretty full and we'd notice that there These messages are probably marked by Exim as "frozen". Search for that term in Exim's documentation for more info. You may enable Exim to automatically remove frozen messages after some period with the following directive: timeout_frozen_after = 3d Marcin
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
* Joe Emenaker schrieb am 28.01.04 um 22:23 Uhr: > Here's a question that has always been bugging me. > > Ever since we moved from smail to exim many years ago at my isp, exim > never seems to discard messages in the input queue. > > Even though the single retry rule is the stock one (which retrys for > something like 4 days), we end up with stuff that is weeks... months > old. Periodically, it would get pretty full and we'd notice that there > were about 10 queue runners going and so I'd go in and do a "find" and > remove anything older than 14 days or so. I *had* to do a find, because > doing an "ls" would just sit there an churn for about a half-hour. > > Anyhow, as our customer base has grown and as their e-mail usage has > grown, the problem has reached an all-time high. With this SCO DDoS > virus going around, I had occasion to go clean out the input queue > again. > > The directory was using 17 megs > > I'm not talking about the FILES in the directory... I'm talking about > the directory ENTRIES (filename, inode number, etc.). I was forced to > just say "screw it!" and I mv'd the input and msglog folders to other > names and then created new, empty ones so that our mail server wouldn't > buckle under the load. > > But anyway, like the subject line says, my real question is: why doesn't > Exim ever clean this stuff out itself? > additional to the other postings something like ignore_errmsg_errors_after = 16h is also useful regards -marc -- +--+ | --> http://www.links2linux.de <-- | | | +---Registered-Linux-User-#136487http://counter.li.org + -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
Joe Emenaker wrote: Here's a question that has always been bugging me. Ever since we moved from smail to exim many years ago at my isp, exim never seems to discard messages in the input queue. Even though the single retry rule is the stock one (which retrys for something like 4 days), we end up with stuff that is weeks... months old. Periodically, it would get pretty full and we'd notice that there were about 10 queue runners going and so I'd go in and do a "find" and remove anything older than 14 days or so. I *had* to do a find, because doing an "ls" would just sit there an churn for about a half-hour. Does the output of the "mailq" command provide any useful information about these messages? My first guess would be that you're dealing with "frozen" messages. These are messages that exim is unable to send *and* can't be returned to the original sender. If that is the case, have a look at the "timeout_frozen_after" setting; this will automatically remove messages after being frozen for a certain period. Regards, Maarten Vink
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
Maarten Vink wrote: Does the output of the "mailq" command provide any useful information about these messages? My first guess would be that you're dealing with "frozen" messages Yup. A lot of them are frozen. If that is the case, have a look at the "timeout_frozen_after" setting; this will automatically remove messages after being frozen for a certain period. I'm already using: timeout_frozen_after=48h but that doesn't seem to be doing anything. - Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: I/O performance issues on 2.4.23 SMP system
Benjamin Sherman said on Wed, Jan 28, 2004 at 03:16:56PM -0600: > >I've got some machines in nearly the same configuration. What I ended up > >doing was to put an `append="mem=1G"' in the lilo.conf boot stanza for the > >kernel I was using, and rebooted the machine in question. > > > >This does reduce the available memory in the machine to 1GB, but solves the > >IO problem. In my case, it was much faster, even though MySQL couldn't > >buffer nearly as much as with 4GB. > Thanks, Mark. I will probably try this with 3GB instead of 1GB. Did you try > that? Yes; it didn't work. The problem (bug) is that block device IO has to go through buffers that are below 1GB. The memory manager doesn't know this, so what happens is that the IO layer requests a block of memory below 1GB, and the swapout daemon (kswapd) then runs around like a madman trying to free pages, instead of shuffling pages that don't need to be below 1GB to higher memory addresses. Since many of the pages below 1GB can't be freed (they belong to active programs), the IO starves. With 1GB of memory, both the IO layer and the swapout daemon are working with the same view of memory, so the bug is concealed, and performance is good. I have heard of people trying 2GB, and having it work, but it didn't for me. M pgpoDfLP7KTv2.pgp Description: PGP signature
Why doesn't Exim ever clean out /var/spool/exim/input?
Here's a question that has always been bugging me. Ever since we moved from smail to exim many years ago at my isp, exim never seems to discard messages in the input queue. Even though the single retry rule is the stock one (which retrys for something like 4 days), we end up with stuff that is weeks... months old. Periodically, it would get pretty full and we'd notice that there were about 10 queue runners going and so I'd go in and do a "find" and remove anything older than 14 days or so. I *had* to do a find, because doing an "ls" would just sit there an churn for about a half-hour. Anyhow, as our customer base has grown and as their e-mail usage has grown, the problem has reached an all-time high. With this SCO DDoS virus going around, I had occasion to go clean out the input queue again. The directory was using 17 megs I'm not talking about the FILES in the directory... I'm talking about the directory ENTRIES (filename, inode number, etc.). I was forced to just say "screw it!" and I mv'd the input and msglog folders to other names and then created new, empty ones so that our mail server wouldn't buckle under the load. But anyway, like the subject line says, my real question is: why doesn't Exim ever clean this stuff out itself? - Joe
Re: I/O performance issues on 2.4.23 SMP system
* Is the I/O patch referenced (by Ingo Molnar) available for 2.4.24? Possibly; it's certainly not merged into 2.4.24. Can anyone point me to the specific patch? I've got some machines in nearly the same configuration. What I ended up doing was to put an `append="mem=1G"' in the lilo.conf boot stanza for the kernel I was using, and rebooted the machine in question. This does reduce the available memory in the machine to 1GB, but solves the IO problem. In my case, it was much faster, even though MySQL couldn't buffer nearly as much as with 4GB. Thanks, Mark. I will probably try this with 3GB instead of 1GB. Did you try that? -- Benjamin Sherman Software Developer Iowa Interactive, Inc 515-323-3468 x14 [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
On Wed, Jan 28, 2004 at 01:23:02PM -0800, Joe Emenaker wrote: > Even though the single retry rule is the stock one (which retrys for > something like 4 days), we end up with stuff that is weeks... months > old. Periodically, it would get pretty full and we'd notice that there These messages are probably marked by Exim as "frozen". Search for that term in Exim's documentation for more info. You may enable Exim to automatically remove frozen messages after some period with the following directive: timeout_frozen_after = 3d Marcin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why doesn't Exim ever clean out /var/spool/exim/input?
Joe Emenaker wrote: Here's a question that has always been bugging me. Ever since we moved from smail to exim many years ago at my isp, exim never seems to discard messages in the input queue. Even though the single retry rule is the stock one (which retrys for something like 4 days), we end up with stuff that is weeks... months old. Periodically, it would get pretty full and we'd notice that there were about 10 queue runners going and so I'd go in and do a "find" and remove anything older than 14 days or so. I *had* to do a find, because doing an "ls" would just sit there an churn for about a half-hour. Does the output of the "mailq" command provide any useful information about these messages? My first guess would be that you're dealing with "frozen" messages. These are messages that exim is unable to send *and* can't be returned to the original sender. If that is the case, have a look at the "timeout_frozen_after" setting; this will automatically remove messages after being frozen for a certain period. Regards, Maarten Vink -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: I/O performance issues on 2.4.23 SMP system
Benjamin Sherman said on Tue, Jan 27, 2004 at 03:49:24PM -0600: > So, I have a couple of questions because this box made it to production > before the problem was discovered and I can't test as I'd like. > * If I were to use 64GB HIGHMEM support. Would this problem go away? Nope. > * Is the I/O patch referenced (by Ingo Molnar) available for 2.4.24? Possibly; it's certainly not merged into 2.4.24. > * Is the patch available individually, if so, where can it be found? I > googled quite a bit, but didn't find anything definite. > > Any thoughts or suggestions? I've got some machines in nearly the same configuration. What I ended up doing was to put an `append="mem=1G"' in the lilo.conf boot stanza for the kernel I was using, and rebooted the machine in question. This does reduce the available memory in the machine to 1GB, but solves the IO problem. In my case, it was much faster, even though MySQL couldn't buffer nearly as much as with 4GB. M pgpv7xXO6Gh3N.pgp Description: PGP signature
Re: I/O performance issues on 2.4.23 SMP system
Benjamin Sherman said on Wed, Jan 28, 2004 at 03:16:56PM -0600: > >I've got some machines in nearly the same configuration. What I ended up > >doing was to put an `append="mem=1G"' in the lilo.conf boot stanza for the > >kernel I was using, and rebooted the machine in question. > > > >This does reduce the available memory in the machine to 1GB, but solves the > >IO problem. In my case, it was much faster, even though MySQL couldn't > >buffer nearly as much as with 4GB. > Thanks, Mark. I will probably try this with 3GB instead of 1GB. Did you try > that? Yes; it didn't work. The problem (bug) is that block device IO has to go through buffers that are below 1GB. The memory manager doesn't know this, so what happens is that the IO layer requests a block of memory below 1GB, and the swapout daemon (kswapd) then runs around like a madman trying to free pages, instead of shuffling pages that don't need to be below 1GB to higher memory addresses. Since many of the pages below 1GB can't be freed (they belong to active programs), the IO starves. With 1GB of memory, both the IO layer and the swapout daemon are working with the same view of memory, so the bug is concealed, and performance is good. I have heard of people trying 2GB, and having it work, but it didn't for me. M pgp0.pgp Description: PGP signature
Re: Intel SRCU42X SCSI RAID contoller
Hi, On Wed, 28 Jan 2004, Marcin Owsiany wrote: > Hi! > > Forgive me the cross-post, but this is rather urgent for me :-/ > > Does anyone know if the Debian kernel in woody-proposed-updates (2.4.22) > supports Intel SRCU42X SCSI RAID contoller? > > Intel's web page says that it is supported by Suse and RH, but they make > a binary driver available for download (megaraid.o). The source is > included, so probablu it the same as in stock kernel, but could anyone > confirm this? > Not sure. I can't find it in the official kernel 2.4.23 (www.kernel.org), or I am looking over it. What I can find is a driver with the same module name: CONFIG_SCSI_MEGARAID: This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490, 467, 471 and 493 SCSI host adapters. This is the old and very heavily tested driver but lacks features like clustering. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called megaraid.o. - Either this module is compatible with your mega raid, or suse and rh gave a very poor name. I have looked to the kernel patches, but I could not find information about CONFIG_SCSI_MEGARAID, so I assume it is disabled by default. If you don't need to boot from your controller, you can compile the module afterwards, otherwise a module isn't good enough and you should compile your custom kernel before installation. Greetz, Sebas -- English written by Dutch people is easily recognized by the improper use of 'In principle ...' The software box said 'Requires Windows 95 or better', so I installed Linux. Als Pacman in de jaren '80 de kinderen zo had be?nvloed zouden nu veel jongeren rondrennen in donkere zalen terwijl ze pillen eten en luisteren naar monotone electronische muziek. (Kristian Wilson, Nintendo, 1989)
oilafu
-- Virus Warning Message (on imivs01) Found virus WORM_MIMAIL.R in file data.txt .exe (in data.zip) The file data.zip is moved to /wload/imap/app/trend/var/quarantine/virSKFPIbyMw. The Barclays Internet mail system's virus scanner detected a virus in this email message, the virus has been removed. Please either inform the sender or if you have any questions, contact your 1st Level Help Desk. - The message contains Unicode characters and has been sent as a binary attachment. -- Virus Warning Message (on imivs01) data.zip is removed from here because it contains a virus. - Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons.
Why doesn't Exim ever clean out /var/spool/exim/input?
Here's a question that has always been bugging me. Ever since we moved from smail to exim many years ago at my isp, exim never seems to discard messages in the input queue. Even though the single retry rule is the stock one (which retrys for something like 4 days), we end up with stuff that is weeks... months old. Periodically, it would get pretty full and we'd notice that there were about 10 queue runners going and so I'd go in and do a "find" and remove anything older than 14 days or so. I *had* to do a find, because doing an "ls" would just sit there an churn for about a half-hour. Anyhow, as our customer base has grown and as their e-mail usage has grown, the problem has reached an all-time high. With this SCO DDoS virus going around, I had occasion to go clean out the input queue again. The directory was using 17 megs I'm not talking about the FILES in the directory... I'm talking about the directory ENTRIES (filename, inode number, etc.). I was forced to just say "screw it!" and I mv'd the input and msglog folders to other names and then created new, empty ones so that our mail server wouldn't buckle under the load. But anyway, like the subject line says, my real question is: why doesn't Exim ever clean this stuff out itself? - Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: I/O performance issues on 2.4.23 SMP system
* Is the I/O patch referenced (by Ingo Molnar) available for 2.4.24? Possibly; it's certainly not merged into 2.4.24. Can anyone point me to the specific patch? I've got some machines in nearly the same configuration. What I ended up doing was to put an `append="mem=1G"' in the lilo.conf boot stanza for the kernel I was using, and rebooted the machine in question. This does reduce the available memory in the machine to 1GB, but solves the IO problem. In my case, it was much faster, even though MySQL couldn't buffer nearly as much as with 4GB. Thanks, Mark. I will probably try this with 3GB instead of 1GB. Did you try that? -- Benjamin Sherman Software Developer Iowa Interactive, Inc 515-323-3468 x14 [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature
Re: I/O performance issues on 2.4.23 SMP system
Benjamin Sherman said on Tue, Jan 27, 2004 at 03:49:24PM -0600: > So, I have a couple of questions because this box made it to production > before the problem was discovered and I can't test as I'd like. > * If I were to use 64GB HIGHMEM support. Would this problem go away? Nope. > * Is the I/O patch referenced (by Ingo Molnar) available for 2.4.24? Possibly; it's certainly not merged into 2.4.24. > * Is the patch available individually, if so, where can it be found? I > googled quite a bit, but didn't find anything definite. > > Any thoughts or suggestions? I've got some machines in nearly the same configuration. What I ended up doing was to put an `append="mem=1G"' in the lilo.conf boot stanza for the kernel I was using, and rebooted the machine in question. This does reduce the available memory in the machine to 1GB, but solves the IO problem. In my case, it was much faster, even though MySQL couldn't buffer nearly as much as with 4GB. M pgp0.pgp Description: PGP signature
Re: Intel SRCU42X SCSI RAID contoller
Hi, On Wed, 28 Jan 2004, Marcin Owsiany wrote: > Hi! > > Forgive me the cross-post, but this is rather urgent for me :-/ > > Does anyone know if the Debian kernel in woody-proposed-updates (2.4.22) > supports Intel SRCU42X SCSI RAID contoller? > > Intel's web page says that it is supported by Suse and RH, but they make > a binary driver available for download (megaraid.o). The source is > included, so probablu it the same as in stock kernel, but could anyone > confirm this? > Not sure. I can't find it in the official kernel 2.4.23 (www.kernel.org), or I am looking over it. What I can find is a driver with the same module name: CONFIG_SCSI_MEGARAID: This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490, 467, 471 and 493 SCSI host adapters. This is the old and very heavily tested driver but lacks features like clustering. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called megaraid.o. - Either this module is compatible with your mega raid, or suse and rh gave a very poor name. I have looked to the kernel patches, but I could not find information about CONFIG_SCSI_MEGARAID, so I assume it is disabled by default. If you don't need to boot from your controller, you can compile the module afterwards, otherwise a module isn't good enough and you should compile your custom kernel before installation. Greetz, Sebas -- English written by Dutch people is easily recognized by the improper use of 'In principle ...' The software box said 'Requires Windows 95 or better', so I installed Linux. Als Pacman in de jaren '80 de kinderen zo had be?nvloed zouden nu veel jongeren rondrennen in donkere zalen terwijl ze pillen eten en luisteren naar monotone electronische muziek. (Kristian Wilson, Nintendo, 1989) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
oilafu
-- Virus Warning Message (on imivs01) Found virus WORM_MIMAIL.R in file data.txt .exe (in data.zip) The file data.zip is moved to /wload/imap/app/trend/var/quarantine/virSKFPIbyMw. The Barclays Internet mail system's virus scanner detected a virus in this email message, the virus has been removed. Please either inform the sender or if you have any questions, contact your 1st Level Help Desk. - The message contains Unicode characters and has been sent as a binary attachment. -- Virus Warning Message (on imivs01) data.zip is removed from here because it contains a virus. - Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons.
Intel SRCU42X SCSI RAID contoller
Hi! Forgive me the cross-post, but this is rather urgent for me :-/ Does anyone know if the Debian kernel in woody-proposed-updates (2.4.22) supports Intel SRCU42X SCSI RAID contoller? Intel's web page says that it is supported by Suse and RH, but they make a binary driver available for download (megaraid.o). The source is included, so probablu it the same as in stock kernel, but could anyone confirm this? regards Marcin -- Marcin Owsiany <[EMAIL PROTECTED]> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216
Intel SRCU42X SCSI RAID contoller
Hi! Forgive me the cross-post, but this is rather urgent for me :-/ Does anyone know if the Debian kernel in woody-proposed-updates (2.4.22) supports Intel SRCU42X SCSI RAID contoller? Intel's web page says that it is supported by Suse and RH, but they make a binary driver available for download (megaraid.o). The source is included, so probablu it the same as in stock kernel, but could anyone confirm this? regards Marcin -- Marcin Owsiany <[EMAIL PROTECTED]> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Ecartis: Post sent to moderator.
>> Post to list xmail Post submitted to moderator for reason: Non-member submission to closed-post list. --- Ecartis v1.0.0 - job execution complete.
Ecartis: Post sent to moderator.
>> Post to list xmail Post submitted to moderator for reason: Non-member submission to closed-post list. --- Ecartis v1.0.0 - job execution complete. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
