Hallo, Antispam content filtering di internet mail umumnya pakai spamassasin atau turunannya, dan spamassasin telah membuatkan petunjuk bagaimana mensiasati agar mail tidak mendapatkan spam score yang tinggi jika dikirim ke mail server domain yang menggunakan spam assassin sebagai antispam content filteringnya.
http://wiki.apache.org/spamassassin/AvoidingFpsForSenders Kali ini hanya akan dibahas beberapa diantaranya saja Tip: Use a domain name which is identified by a verifiable IP address. Make sure that if someone checks on the domain of your From address and Reply-To address that these addresses are valid, and the machine that would receive any Reply email can be identified. Pada pengisian account profile di email client, kalau ada isian Reply-To <address> maka dikosongkan saja isinya. Tip: Using SPF identification for your domain helps. It won't flag you as a good guy directly, but it will prevent bad guys from successfully masquerading as you. Bisa diaktifkan SPF record, akan tetapi pakai policy yang netral (neutral) atau (maksimum) SoftTail, jangan paranoid mode (fail). SPF record bisa dibuat dengan bantuan dari sini http://www.spfwizard.net/ lalu minta ke DNS hoster (bisa ISP, Domain Registrar atau DNS hoster) untuk membuatkan SPF record di authoritative DNS. Tip: If you're using HTML emails, use high quality HTML emails. Don't use tools which generate horrendous HTML (example: MS Word). They often leave signs behind (like empty tags, eg: <B></B>) which are generally found in spam. Make sure your HTML is valid (run it through a decent validator). Unbalanced tags and invalid tags will also flag an email as spam. If you use a title, make sure the title is meaningful -- the default titles generated by HTML tools are often used as spamsign Hindari penggunaan mail format yang tidak standar di Internet seperti RTF (Rich Text Format), gunakan plain-text atau HTML Tip: Don't use 'bulk-mailing' tools used by spammers (i.e., advertised in spam). These are overwhelmingly used to send spam, so SpamAssassin blocks mail sent by those tools as soon as possible. In particular, if the product's feature list includes 'stealth sending' or similar, that's a danger sign. Kalau kirim mail ke banyak recipient dengan BCC:, kolom TO: jangan dikosongkan, bisa diiisikan TO: <alamat sendiri> atau <alamat rekan kerja>. Tip: Be visible and public in your domain and hosting registrations. If people who check for you to see whether you might be a spammer, or to complain/ask about your emails, finds bogus entries in your registrations, or "private" or "hidden" annotations, that strongly suggests you are a spammer, hiding from an outraged public. If you are open about who you are in your registration emails, you'll get some complains and some queries. Answer those honestly and fully, and you should stay out of blacklists. Make sure you have active and monitored abuse <at> and postmaster <at> addresses. Register them with abuse.net. Pastikan akun [email protected] dan [email protected] terdaftar di address aliases http://mdaemon.dutaint.co.id/13.6.1/alias_aliases.htm Tip: Test your email with SpamAssassin. Send your draft to/through a system with SpamAssassin running, and see how it scores. If your email hits a number of high-scoring SA rules, then you can determine why and reduce your email's score. Lakukan test mail ke spamassassin spam score test, misalkan ke http://spamscorechecker.com/ http://www.mail-tester.com/ --- dilanjutkan ke bagian 2 --> -- syafril ------- Syafril Hermansyah MDaemon-L Moderators, running MDaemon 14.0 Beta B SecurityPlus 4.1.5 Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon. -- --[MDaemon-L]------------------------------------------------ Milis ini untuk Diskusi antar pengguna MDaemon Mail Server. Netiket: http://www.netmeister.org/news/learn2quote Arsip: http://mdaemon-l.dutaint.com Dokumentasi : http://mdaemon.dutaint.co.id Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com Versi terakhir MD 13.6.2, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 2.1.2, PP 2.0.1
