04-28-2009
I have a bit of experience with both Spamassassin and procmail, but how would you define non-existent addresses ? Also, what is the MTA on your OS ?
7 More Discussions You Might Find Interesting
1. Linux
I have a Linux red hat 9 router running. I have spamassassin runnning and it is putting emails into the users home folders. The question is how do the users go through the file?
Frank (0 Replies)
Discussion started by: frankkahle
0 Replies
2. Solaris
Hello, I'm triying to install senmail + procmail + spamassassin, but i've been having trouble with the first part, i cant install procmail...
im using solaris 9, i have already installed sendmail, then i tried to install procmail and everything goes right, , then edit the /etc/mail/sendmail.cf... (1 Reply)
Discussion started by: sx3v1l_1n51de
1 Replies
3. News, Links, Events and Announcements
Hi all,
I have created a new rpm package integrating
postfix, spamassassin, clamav and mailscanner. This
should help to eliminate the hassle of installing and
making these applications work together.
The latest package include:
* Clamav: 0.87.1
* MailScanner: 4.47.4-1
*... (0 Replies)
Discussion started by: janetbindner
0 Replies
4. Solaris
Hey,
i use solaris 10, and i need tu use spamassassin, so i dowload it and install it following the instructions (download the missing CPAN packages), so "make" and "make install" go well, but when i attempt to test spamassassin with
shell# spamassassin -t < sample-spam.txt
i got this :
... (2 Replies)
Discussion started by: wodel
2 Replies
5. UNIX for Advanced & Expert Users
I have a software product that tags all outbound emails which I am trying to remove. Does anyone know how to do this using qmail?
I also have spam assassin running, I have a feeling it is possible to modify a subject using a rules file? Anyone know?
Thanks for any advice.
xian (1 Reply)
Discussion started by: r0sc0
1 Replies
6. UNIX and Linux Applications
Hi every body
I am facing problem installing spamassassin on my CentOS - Direct Admin VPS
The installation ended with the following error
REQUIRED module out of date: Archive::Tar
optional module missing: Digest::SHA
optional module missing: Mail::SPF
optional module missing: IP::Country... (0 Replies)
Discussion started by: rizwan65
0 Replies
7. UNIX for Advanced & Expert Users
We have a user who has about a 50% missed rate on spam detection. I'm wondering if his user prefs or something is preventing scanning of all messages?
SpamAssassin version 3.4.1, running on Perl version 5.20.3, sendmail Version 8.15.2
The contents of the user_prefs file:
# How many points... (2 Replies)
Discussion started by: RobbieTheK
2 Replies
LEARN ABOUT OPENSOLARIS
mem
mem(7D) Devices mem(7D)
NAME
mem, kmem, allkmem - physical or virtual memory access
SYNOPSIS
/dev/mem
/dev/kmem
/dev/allkmem
DESCRIPTION
The file /dev/mem is a special file that provides access to the physical memory of the computer.
The file /dev/kmem is a special file that provides access to the virtual address space of the operating system kernel, excluding memory
that is associated with an I/O device.
The file /dev/allkmem is a special file that provides access to the virtual address space of the operating system kernel, including memory
that is associated with an I/O device. You can use any of these devices to examine and modify the system.
Byte addresses in /dev/mem are interpreted as physical memory addresses. Byte addresses in /dev/kmem and /dev/allkmem are interpreted as
kernel virtual memory addresses. A reference to a non-existent location returns an error. See ERRORS for more information.
The file /dev/mem accesses physical memory; the size of the file is equal to the amount of physical memory in the computer. This size may
be larger than 4GB on a system running the 32-bit operating environment. In this case, you can access memory beyond 4GB using a series of
read(2) and write(2) calls, a pread64() or pwrite64() call, or a combination of llseek(2) and read(2) or write(2).
ERRORS
EFAULT Occurs when trying to write(2) a read-only location (allkmem), read(2) a write-only location (allkmem), or read(2) or write(2) a
non-existent or unimplemented location (mem, kmem, allkmem).
EIO Occurs when trying to read(2) or write(2) a memory location that is associated with an I/O device using the /dev/kmem special
file.
ENXIO Results from attempting to mmap(2) a non-existent physical (mem) or virtual (kmem, allkmem) memory address.
FILES
/dev/mem Provides access to the computer's physical memory.
/dev/kmem Provides access to the virtual address space of the operating system kernel, excluding memory that is associated with an
I/O device.
/dev/allkmem Provides access to the virtual address space of the operating system kernel, including memory that is associated with an
I/O device.
SEE ALSO
llseek(2), mmap(2), read(2), write(2)
WARNINGS
Using these devices to modify (that is, write to) the address space of a live running operating system or to modify the state of a
hardware device is extremely dangerous and may result in a system panic if kernel data structures are damaged or if device state is
changed.
SunOS 5.11 18 Feb 2002 mem(7D)