Postfix docs Search Results:

Looking for spam in entire archive - Found 51 matches in 21 files
Showing results 1 - 21
Postfix Add-on Software, Feb 8 2008
virus/spam content filters |
Virus/SPAM content filters
amavisd-new utility, a high-performance interface between MTA and virus/SPAM scanners.
Dr.Web anti-virus & anti-spam for Telecoms and businesses with heavy mail traffic; available as solution and SDK.
MPP for Postfix antivirus, antispam, archival, access control, content filtering, thresholds, auto-black lists, spam traps, and more.
spampd spam filtering, transparent SMTP/LMTP proxy using SpamAssassin, in Perl by Maxim Paperno.
Anti-spam gateway

Postfix Add-on Software, Feb 8 2008
virus/spam content filters |
Virus/SPAM content filters
amavisd-new utility, a high-performance interface between MTA and virus/SPAM scanners.
Dr.Web anti-virus & anti-spam for Telecoms and businesses with heavy mail traffic; available as solution and SDK.
MPP for Postfix antivirus, antispam, archival, access control, content filtering, thresholds, auto-black lists, spam traps, and more.
spampd spam filtering, transparent SMTP/LMTP proxy using SpamAssassin, in Perl by Maxim Paperno.
Anti-spam gateway

Postfix Virtual Domain Hosting Howto, Feb 8 2008
This is not without risk. Spammers nowadays try to send mail from (or mail to) every possible name that they can think of. A catch-all mailbox is likely to receive many spam messages, and many bounces for spam messages that were sent in the name of anything@example.com.
Line 14: The commented out entry (text after #) shows how one would implement a catch-all virtual mailbox address. Be prepared to receive a lot of spam, as well as bounced spam that was sent in the name of anything@example.com.
This is not without risk. Spammers nowadays try to send mail from (or mail to) every possible name that they can think of. A catch-all mailbox is likely to receive many spam messages, and many bounces for spam messages that were sent in the name of anything@example.com.

http://www.postfix.org/linuxmag.200006/postfix.html, Feb 8 2008
VERBOSE=off LOGABSTRACT=none MAILHOME=$HOME/Mail FRIENDS=$MAILHOME/friends SPAM=$MAILHOME/spam WORK=$MAILHOME/work LISTS=$MAILHOME/lists
:0 * ^Subject: .*FREE .* $SPAM
Generell sollte man möglichst wenig Rechnern Zugriff gestatten; nicht nur um sich und seine Benutzer zu schützen, sondern auch um dem Phänomen SPAM entgegenzuwirken, das täglich Millionen von Dollar an Kosten verursacht - irgendjemand muß ja für das Datenaufkommen zahlen!
Die Möglichkeiten, externe Programme in Postfix einzubinden, sind sehr vielfältig. Beispielsweise könnte der Administrator eine automatische Ver/Entschlüsselung von Mails vom Firmensitz zu einer Außenstelle implementieren, damit sie "unterwegs" nicht lesûar sind. Außerdem kann ein SPAM-Filter an zentraler Stelle eingebaut werden. Ein solcher ist wesentlich einfacher zu verwalten als Procmail-Filter für jeden einzelnen Benutzer. Der Fantasie der Mailadministratoren sind (fast) keine Grenzen gesetzt. (hmi)

Catching up with Wietse Venema, creator of Postfix and TCP Wrapper, Feb 8 2008
Linuxsecurity.com: What is your take on spam and the role the MTA plays in helping to prevent it?
Wietse: Stopping email that contains spam is not fundamentally different from stopping email that contains viruses.
In both cases, complex content analysis is better done outside the mail system. That allows people to choose the best mail system and the best spam/virus software for their environment.
And in both cases, a lot of spam or viral email comes from systems that have no business sending email directly across the Internet.
These are often PCs on residential networks that have been compromised via some worm of virus, and that are under remote control by criminals that use those systems to send spam and/or to infect more systems. These rogue systems can often be recognized by the way they implement the email protocols wrongly, if not by their residential IP address.

Postfix Howtos and FAQs, Feb 8 2008
Adaptech Systems class AS220 is a two-day course on Postfix and email security including a spam quarantine system that was developed to work with Postfix.
Filtering spam with Postfix with spf, postgrey and Amavis by Kirk Strauser.
Anti-SPAM Gateway Using OpenBSD, Postfix, Amavisd-new, SpamAssassin, Razor and DCC
Postfix UCE/anti-spam guide by Jeffrey Posluns.

Postfix After-Queue Content Filter, Feb 8 2008
NOTE: in this time of mail worms and forged spam, it is a VERY BAD IDEA to send viruses back to the sender address, because the sender address is almost certainly not the originator. It is better to discard known viruses, and to quarantine material that is suspect so that a human can decide what to do with it.
NOTE: in this time of mail worms and spam, it is a BAD IDEA to send known viruses or spam back to the sender, because that address is likely to be forged. It is safer to discard known viruses and to quarantine suspicious content so that it can be inspected by a human being.

Postfix Bottleneck Analysis, Feb 8 2008
For example, in the output below we see the top 10 lines of the (mostly forged) sender domain distribution for captured spam in the "hold" queue:
The "hold" queue plays little role in Postfix performance, and monitoring of the "hold" queue is typically more closely motivated by tracking spam and malware, than by performance issues.

Postfix Content Inspection, Feb 8 2008
This method inspects mail BEFORE it is stored in the queue, and uses Postfix's built-in message header and message body inspection. Although the main purpose is to stop a specific flood of mail from worms or viruses, it is also useful to block a flood of bounced junk email and email notifications from virus detection systems. The built-in regular expressions are not meant to implement general SPAM and virus detection. For that, you should use one of the content inspection methods described below. Details are described in the BUILTIN_FILTER_README and BACKSCATTER_README documents.
The more sophisticated content filtering software is not built into Postfix for good reasons: writing an MTA requires different skills than writing a SPAM or virus killer. Postfix encourages the use of external filters and standard protocols because this allows you to choose the best MTA and the best content inspection software for your purpose. Information about external content inspection software can be found on the Postfix website at http://www.postfix.org/, and on the postfix-users@postfix.org mailing list.

Postfix Address Rewriting, Feb 8 2008
Appending Postfix's own domain sometimes creates the appearance that spam is sent by local users.

Postfix Configuration Parameters, Feb 8 2008
Optional lookup tables with all valid addresses in the domains that match $relay_domains. Specify @domain as a wild-card for domains that have no valid recipient list, and become a source of backscatter mail: Postfix accepts spam for non-existent recipients and then floods innocent people with undeliverable mail. Technically, tables listed with $relay_recipient_maps are used as lists: Postfix needs to know only if a lookup string is found or not, but it does not use the result from table lookup.

Postfix Address Rewriting, Feb 8 2008
Appending Postfix's own domain sometimes creates the appearance that spam is sent by local users.

Postfix Configuration Parameters, Feb 8 2008
Optional lookup tables with all valid addresses in the domains that match $relay_domains. Specify @domain as a wild-card for domains that have no valid recipient list, and become a source of backscatter mail: Postfix accepts spam for non-existent recipients and then floods innocent people with undeliverable mail. Technically, tables listed with $relay_recipient_maps are used as lists: Postfix needs to know only if a lookup string is found or not, but it does not use the result from table lookup.

Postfix and Mailman deliver enhanced e-mail security and performance, Feb 8 2008
Mailman has been designed for a Webified world. All actions -- subscription requests, list administration, management reports -- can be performed either through a Web interface or more traditional textual commands. Moreover, Mailman integrates archiving, digests, Usenet gateways, spam protection, and bulk mailing. Improved customization and filtering are planned after the first official release.

SecurityPortal - Postfix - The Sendmail replacement part II, Feb 8 2008
Blocking Spam

Postfix Backscatter Howto, Feb 8 2008
A plea to virus or spam scanner operators: please do not make the problem worse by sending return mail to forged sender addresses.

Postfix Configuration Parameters, Feb 8 2008
Optional lookup tables with all valid addresses in the domains that match $relay_domains. Specify @domain as a wild-card for domains that have no valid recipient list, and become a source of backscatter mail: Postfix accepts spam for non-existent recipients and then floods innocent people with undeliverable mail. Technically, tables listed with $relay_recipient_maps are used as lists: Postfix needs to know only if a lookup string is found or not, but it does not use the result from table lookup.

Postfix Address Verification, Feb 8 2008
At some point in cyberspace/time, a list of frequently forged MAIL FROM domains could be found at http://www.monkeys.com/anti-spam/filtering/sender-domain-validate.in.

Postfix SMTP Access Policy Delegation, Feb 8 2008
It is relatively safe to turn on greylisting for specific domains that often appear in forged email. At some point in cyberspace/time a list of frequently forged MAIL FROM domains could be found at http://www.monkeys.com/anti-spam/filtering/sender-domain-validate.in.

Postfix Address Rewriting, Feb 8 2008
Appending Postfix's own domain sometimes creates the appearance that spam is sent by local users.

Non-English Postfix Information, Feb 8 2008
Postfix, anti-virus/spam howto by Deniz Akkus Kanca.

New Query: Rank by:
Search results by Webglimpse Advanced Site Search Engine