04-26-2009
Procmail or Spamassassin?
Hello, this is my first visit to your forum and I've searched previous threads for my answer but have not been able to find one. Apologies if there is one that I didn't discover.
Is there a way of bouncing or deleting spam that contains non-existent addresses in TO: field but is delivered due to genuine addresses containing in the BCC field?
This is beyond my field of expertise and probably will have to outsource for this issue to be resolved.
Discussion with various people give conflicting advice with one saying Spamassassin can be modified to solve this issue with others saying Procmail recipies are the way to go.
Please does anyone have any advice or can point me in the right direction?
Sincere best wishes and thanks in advance
Wendy
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
posix_madvise
posix_madvise(3C) Standard C Library Functions posix_madvise(3C)
NAME
posix_madvise - memory advisory information
SYNOPSIS
#include <sys/mman.h>
int posix_madvise(void *addr, size_t len, int advice);
DESCRIPTION
The posix_madvise() function advises the system on the expected behavior of the application with respect to the data in the memory starting
at address addr, and continuing for len bytes. The system may use this information to optimize handling of the specified data. The
posix_madvise() function has no effect on the semantics of access to memory in the specified range, although it may affect the performance
of access.
The advice to be applied to the memory range is specified by the advice parameter and may be one of the following values:
POSIX_MADV_NORMAL Specifies that the application has no advice to give on its behavior with respect to the specified range. It is
the default characteristic if no advice is given for a range of memory.
POSIX_MADV_SEQUENTIAL Specifies that the application expects to access the specified range sequentially from lower addresses to higher
addresses.
POSIX_MADV_RANDOM Specifies that the application expects to access the specified range in a random order.
POSIX_MADV_WILLNEED Specifies that the application expects to access the specified range in the near future.
POSIX_MADV_DONTNEED Specifies that the application expects that it will not access the specified range in the near future.
These values are defined in <sys/mman.h>
RETURN VALUES
Upon successful completion, posix_madvise() returns zero. Otherwise, an error number is returned to indicate the error.
ERRORS
The posix_madvise() function will fail if:
EINVAL The value of advice is invalid.
ENOMEM Addresses in the range starting at addr and continuing for len bytes are partly or completely outside the range allowed for the
address space of the calling process.
The posix_madvise() function may fail if:
EINVAL The value of len is zero.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe |
+-----------------------------+-----------------------------+
|Standard |See standards(5). |
+-----------------------------+-----------------------------+
SEE ALSO
mmap(2), madvise(3C), posix_madvise(3C), attributes(5), standards(5)
SunOS 5.11 14 Jul 2008 posix_madvise(3C)