Member Avatar for cussel

hi all :)

i've problem with spam email in ubuntu 1204 LTS use ispconfig3,...
each spam email detected by server (ispconfig3) it's not send to client (outlook), its stopped in sever,..
how to allow/by pass all email contain spam to client???
what must i set???

please help me :(

  • 2 Contributors
  • 2 Replies
  • 367 Views
  • 3 Hours Discussion Span
  • Latest Post Latest Post by cussel

Dani AI

Generated

Short summary and safe path: is right that some legitimate messages are false positives, and ’s question (“why?”) is valid — blindly turning spam filtering off is risky. A safer approach is to have the server tag suspected spam and deliver it (so Outlook/clients can filter), and to whitelist trusted senders or tweak per-domain/user thresholds in ISPConfig rather than disabling protection entirely.

To “tag-and-pass” at the gateway (recommended): amavisd controls what happens to scored spam — change its action so spam is delivered but marked. On Debian/Ubuntu this is done in the amavis conf (usually /etc/amavis/conf.d/50-user); set the final spam destiny to pass and enable a subject tag, then restart amavis/postfix. Example lines you can add to 50-user:

$final_spam_destiny = D_PASS;
$sa_spam_subject_tag = '***SPAM*** ';
$sa_spam_modifies_subj = 1;

After editing restart the services (example): sudo service amavis restart and sudo postfix reload. (amavisd.de.postfix.org)

If you only need to allow specific senders/domains, use SpamAssassin whitelists instead of global changes. Add rules to /etc/spamassassin/local.cf (or per-user ~/.spamassassin/user_prefs) like:

whitelist_from alice@example.com
whitelist_from *@trusted.example.org
# or use safer whitelist_from_rcvd rules

Using whitelist_from_rcvd is safer against forged From headers. (spamassassin.apache.org)

ISPConfig specifics: ISPConfig exposes spam policies (tag/tag2/kill levels) in the panel; the underlying values live in the dbispconfig.spamfilter_policy table, so you can adjust sensitivity per-policy or per-mailbox in the UI (or via DB if you know what you’re doing). For a multi-tenant setup tweak policies rather than turning off filtering globally. ()

Troubleshooting & cautions: back up configs before editing, watch /var/log/mail.log (grep for amavis) to confirm what happens, and test with known-good and GTUBE test messages. Delivering spam increases user risk (malware/phishing) — tag-and-pass plus client rules or per-sender whitelists gives the best balance of safety and flexibility. (help.ubuntu.com)

Recommended Answers

All 2 Replies

Member Avatar for rubberman

And you want to do this because? ...

Member Avatar for cussel
  1. not all email SPAM are really SPAM
  2. sometimes between users have to comunication before but suddenly it's said SPAM by mail server

while solution: i must by pass/ allow email said spam manually :(
so, what must i set to by pass/ allow email sai spam by mail server???

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.