Sponsored Content
Full Discussion: Procmail or Spamassassin?
Top Forums UNIX for Dummies Questions & Answers Procmail or Spamassassin? Post 302310687 by WendyTinley on Sunday 26th of April 2009 11:16:38 AM
Old 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

Spamassassin

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

sendmail + procmail + spamassassin

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

New RPM package(clamav, postfix, spamassassin, mailscanner) - PSCM

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

can't run spamassassin

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

Qmail/SpamAssassin: Modifying outbound email subjects.

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

Problem installing spamassassin CentOS 5.5

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

Some mails not scanned by SpamAssassin 3.4.1 w sendmail/procmail on Fedora 21

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
MADVISE(2)						      BSD System Calls Manual							MADVISE(2)

NAME
madvise, posix_madvise -- give advice about use of memory SYNOPSIS
#include <sys/mman.h> int madvise(void *addr, size_t len, int advice); int posix_madvise(void *addr, size_t len, int advice); DESCRIPTION
The madvise() system call allows a process that has knowledge of its memory behavior to describe it to the system. The advice passed in may be used by the system to alter its virtual memory paging strategy. This advice may improve application and system performance. The behavior specified in advice can only be one of the following values: MADV_NORMAL Indicates that the application has no advice to give on its behavior in the specified address range. This is the system default behavior. This is used with madvise() system call. POSIX_MADV_NORMAL Same as MADV_NORMAL but used with posix_madvise() system call. MADV_SEQUENTIAL Indicates that the application expects to access this address range in a sequential manner. This is used with madvise() system call. POSIX_MADV_SEQUENTIAL Same as MADV_SEQUENTIAL but used with posix_madvise() system call. MADV_RANDOM Indicates that the application expects to access this address range in a random manner. This is used with madvise() system call. POSIX_MADV_RANDOM Same as MADV_RANDOM but used with posix_madvise() system call. MADV_WILLNEED Indicates that the application expects to access this address range soon. This is used with madvise() system call. POSIX_MADV_WILLNEED Same as MADV_WILLNEED but used with posix_madvise() system call. MADV_DONTNEED Indicates that the application is not expecting to access this address range soon. This is used with madvise() system call. POSIX_MADV_DONTNEED Same as MADV_DONTNEED but used with posix_madvise() system call. MADV_FREE Indicates that the application will not need the information contained in this address range, so the pages may be reused right away. The address range will remain valid. This is used with madvise() system call. MADV_ZERO_WIRED_PAGES Indicates that the application would like the wired pages in this address range to be zeroed out if the address range is deallocated without first unwiring the pages (i.e. a munmap(2) without a preceding munlock(2) or the application quits). This is used with madvise() system call. The posix_madvise() behaves same as madvise() except that it uses values with POSIX_ prefix for the advice system call argument. RETURN VALUES
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error. ERRORS
madvise() fails if one or more of the following are true: [EINVAL] The value of advice is incorrect. [EINVAL] The address range includes unallocated regions. [ENOMEM] The virtual address range specified by the addr and len are outside the range allowed for the address space. LEGACY SYNOPSIS
#include <sys/types.h> #include <sys/mman.h> int madvise(caddr_t addr, size_t len, int advice); int posix_madvise(caddr_t addr, size_t len, int advice); The include file <sys/types.h> is necessary. The type of addr has changed. SEE ALSO
mincore(2), minherit(2), mprotect(2), msync(2), munmap(2), compat(5) HISTORY
The madvise function first appeared in 4.4BSD. The posix_madvise function is part of IEEE 1003.1-2001 and was first implemented in Mac OS X 10.2. BSD
June 9, 1993 BSD
All times are GMT -4. The time now is 01:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy