2.建立資料庫 postmap hash:/etc/postfix/reject_domains

3.設定 main.cf [root@mail ~]# vi /etc/postfix/main.cf 加在第一行 smtpd_recipient_restrictions =      check_recipient_access hash:/etc/postfix/reject_domains,permit

4.重啟postfix 設定 [...]]]> 1.建立阻檔網域清單
[root@mail ~]# vi /etc/postfix/reject_domains
xxx.com.tw reject
存檔

2.建立資料庫
postmap hash:/etc/postfix/reject_domains

3.設定 main.cf
[root@mail ~]# vi /etc/postfix/main.cf
加在第一行
smtpd_recipient_restrictions =
     check_recipient_access hash:/etc/postfix/reject_domains,permit

4.重啟postfix 設定
[root@mail ~]#postfix reload

=======================================

針對特定使用者阻擋轉寄的網域

參考網址:http://ithelp.ithome.com.tw/question/10024729

可以透過 smtpd_restriction_classes 來實現
1. 將想受限制的使用者清單指定一個 smtpd_restriction_classes
vi reject_users

檢視原始檔複製到剪貼簿列印關於

1. user1@mydomain.com reject_class   
2. user2@mydomain.com reject_class 

user1@mydomain.com reject_class
user2@mydomain.com reject_class

postmap hash:/etc/postfix/reject_users

2. 將想受限制的 domain 清單也作一個 map

vi reject_domains

檢視原始檔複製到剪貼簿列印關於

1. domain1.com reject   
2. domain2.com reject 

domain1.com reject
domain2.com reject

postmap hash:/etc/postfix/reject_domains

3. 設定 postfix

vi main.cf

檢視原始檔複製到剪貼簿列印關於

1. # 宣告 smtpd_restriction_classes 
2. smtpd_restriction_classes = reject_class   
4. # 說明這個 class 的檢查規則
5. reject_class = check_recipient_access hash:/etc/postfix/reject_domain   
7. # 現在要改用 check_sender_access 來檢查使用者了
8. smtpd_recipient_restrictions =   
9.         check_sender_access hash:/etc/postfix/reject_user,   
10.         permit_mynetworks,   
11.         ………………… 

# 宣告 smtpd_restriction_classes
smtpd_restriction_classes = reject_class

# 說明這個 class 的檢查規則
reject_class = check_recipient_access hash:/etc/postfix/reject_domain

# 現在要改用 check_sender_access 來檢查使用者了
smtpd_recipient_restrictions =
        check_sender_access hash:/etc/postfix/reject_user,
        permit_mynetworks,
        .....................

4. 重啟 postfix, 測試

參考出處 : http://www.360doc.com/content/11/0808/23/7470455_139037303.shtml

CentOS 5.5關閉IPV6 發表於 2011/07/08 由 winds 可以修改下面兩個文件以阻止IPv6內核模塊的加載： /etc/modprobe.conf –內核模塊配置文件 /etc/sysconfig/network –網絡配置文件

1. # vim /etc/modprobe.conf 在其中加入下面這一行，

install ipv6 /bin/true

保存並退出。

2. # vim /etc/sysconfig/network 在其中加入下面配置項：

NETWORKING_IPV6=no IPV6INIT=no

保存並退出文件，重啟網絡與服務器：

# service network restart [...]]]> 測試過確定可行!

參考出處 : http://www.360doc.com/content/11/0808/23/7470455_139037303.shtml

CentOS 5.5關閉IPV6
發表於 2011/07/08 由 winds
可以修改下面兩個文件以阻止IPv6內核模塊的加載：
/etc/modprobe.conf –內核模塊配置文件
/etc/sysconfig/network –網絡配置文件

1. # vim /etc/modprobe.conf
在其中加入下面這一行，

install ipv6 /bin/true

保存並退出。

2. # vim /etc/sysconfig/network
在其中加入下面配置項：

NETWORKING_IPV6=no
IPV6INIT=no

保存並退出文件，重啟網絡與服務器：

# service network restart
# reboot

如果想檢查當前IPv6是否已禁用，可以使用下列命令：

# lsmod | grep ipv6
# ifconfig -a

簡易測試環境:

網路: 1Gbps FreeNAS主機資訊:

簡易測試方式:

1.使用 Client XP 連 CIFS(網芳)傳檔

XP下載:(會飄 39~42居多)  

XP上傳:(比較平穩快速,幾乎都在55以上)

2.使用 XP 執行 vSphere 連線掛載 NFS,使用vSphere 的Browse Datastore的上下傳測試

上傳:(慘不忍賭,大部份都卡在幾kb,偶爾跳一兩秒15mb…) [...]]]> FreeNAS 8.0.1 BETA 2 之 NFS 與 CIFS(W網芳)傳輸測試(BETA 3 因設定 storage 權限設定異常無法測試)

簡易測試環境:

網路: 1Gbps
FreeNAS主機資訊:

簡易測試方式:

1.使用 Client XP 連 CIFS(網芳)傳檔

XP下載:(會飄 39~42居多)
 

XP上傳:(比較平穩快速,幾乎都在55以上)

2.使用 XP 執行 vSphere 連線掛載 NFS,使用vSphere 的Browse Datastore的上下傳測試

上傳:(慘不忍賭,大部份都卡在幾kb,偶爾跳一兩秒15mb…)
 

下載:(平穩約45~47)

本想用來當ESX第二台備份用,看來要再等等看了,看那時候這種問題可排除。

試了一下發現，如果只有一顆硬碟，且安裝時當開機系統，那這顆硬碟就會是純開機的硬碟，進 Freenas 後,這顆硬碟就不算是可用媒體範圍，建議將系統安裝在一個2g的USB隨身碟裡當開機系統(當然設備要支援usb開機才行)。

參考網址:http://blog.weithenn.org/2009/06/freebsdpostfix-amavisd-new-uvscan.html

切換至 Ports Tree 路徑安裝 Procmail 套件(請尊重 weithenn 的辛勞!!)

#cd /usr/ports/mail/procmail //切換至安裝路徑 #make install clean //安裝套件並清除安裝過程中不必要的檔案

修改 Postfix 設定檔 main.cf 內容如下

#vi /usr/local/etc/postfix/main.cf //修改 Postfix 設定檔 mailbox_command = /usr/local/bin/procmail //加入此行 (自訂的規則會套用至所有帳號)

編寫過濾規則設定檔 Promailrc 下列過濾規則為收集網路上資料而成的範例。(請尊重 weithenn [...]]]> 利用 procmail 的過濾信件(Postfix )

參考網址:http://blog.weithenn.org/2009/06/freebsdpostfix-amavisd-new-uvscan.html

Procmail 部份 (自訂郵件收送規則)

步驟1.安裝 Procmail 套件

切換至 Ports Tree 路徑安裝 Procmail 套件(請尊重 weithenn 的辛勞!!)

#cd /usr/ports/mail/procmail //切換至安裝路徑
#make install clean //安裝套件並清除安裝過程中不必要的檔案

步驟2.修改 Postfix 設定檔 (main.cf)

修改 Postfix 設定檔 main.cf 內容如下

#vi /usr/local/etc/postfix/main.cf //修改 Postfix 設定檔
mailbox_command = /usr/local/bin/procmail //加入此行 (自訂的規則會套用至所有帳號)

步驟3.編寫過濾規則 (procmailrc)

編寫過濾規則設定檔 Promailrc 下列過濾規則為收集網路上資料而成的範例。(請尊重 weithenn 的辛勞!!)

• 所有使用者的過濾條件： /usr/loca/etc/procmailrc
• 個別使用者的過濾條件： .procmailrc (使用者家目錄下透過 .forware 來啟動 procmail)

使用者可透過在個人家目錄下 .forward 加入如下內容來達到自訂個人過濾條件的目的 (請依個人喜好擇一即可)

#cat ~/.forward
"| /usr/local/bin/procmail" //加入此行 (方式一)
"|IFS=' ' && exec /usr/local/bin/procmail -f- || exit 75 $USER" //加入此行 (方式二)

以下為自訂所有使用者的過濾條件，其中的 /dev/null 可以換成別的目錄 (ex./var/virusmails)。內容如下 (當然您可依個人需求新增/刪除)

#vi /usr/loca/etc/procmailrc
VERBOSE=off
LOGFILE=/var/log/procmail.log
###########################################################################
###Procmail 寄進來的郵件依下列規則逐一過濾，未符合底下規則的信件都放行 ###
###Subjcet 主旨 ###
###Content-Type: ###
###########################################################################
############ KLEZ.G Virus ############
:0b
* ^Subject:.*(Let's be friends)
/dev/null
###
:0b
* ^Subject:.*A funny game
/dev/null
###
:0b
* ^Subject:.*Hello\,.*\,how are you.*
/dev/null
###
:0 B
* ^Content-Type:.*audio/x-wav.*
* ^.*name=.*\.(scr|SCR)
/dev/null
###
:0 B
* ^Content-Type:.*audio/x-midi.*
* ^.*name=.*\.(scr|SCR)
/dev/null
###
:0 B
* ^Content-Type:.*application/octet-stream.*
* ^.*name=.*\.(scr|SCR)
/dev/null
###
:0 Bb
* ^This game is my first work.*
* ^You\'re the first player.*
* I.*you would .* it.*
/dev/null
###
:0 Bb
* .*This is a.*patch.*
* ^I .* you would.*it.*
/dev/null
###
:0 Bb
* .*iframe src=3Dcid.*height=3D0 width=3D0.*
/dev/null
###
:0 B
* ^Content-Type:.*multipart/mixed.*
* name="ANTI_CIH.EXE"
/dev/null
###
:0b
* ^Subject:.*W32.Klez.*removal tools.*
/dev/null
############## Nimda Virus ###############
:0 Bh
* ^Content-Type:.*audio/x-wav.*
* name="readme.exe"
/dev/null
###
:0 Bh
* ^Content-Type:.*audio/x-wav.*
* name="sample.exe"
/dev/null
###
:0 B
* ^Content-Type:.*multipart/mixed.*
* name="readme.exe"
/dev/null
###
:0 B
* ^Content-Type:.*multipart/mixed.*
* name="sample.exe"
/dev/null
###
:0 B
* ^Content-Type:.*application.*
* name="readme.exe"
/dev/null
###
:0 B
* ^Content-Type:.*application.*
* name="sample.exe"
/dev/null
############# SirCam Virus ############
:0 Bh
* I send you this file in order to have your advice
/dev/null
############# PE.BRID.A ############
:0 H
* ^X-Mailer: EBT Reporter.*$
/dev/null
###
:0 B
* ^.*[Nn][Aa][Mm][Ee]=README\.EXE.*$
/dev/null
#############廣告信 (下列三種挑一個吧) ##############
:0:
* ^X-Spam-Flag:.*YES
/dev/null
:0:
* ^X-Spam-Level:.\*\*\*\*\*
/dev/null
:0:
* ^X-Spam-Status:.*Yes
/dev/null

建立 Procmail Log 以便後續觀察 Procmail 運作狀況，若要允許使用者的 Procmail 過濾規則也可寫入該 Log 的話則權限請設定為 666(請尊重 weithenn 的辛勞!!)

#touch /var/log/procmail.log //建立 Procmail Log
#chmod 666 /var/log/procmail.log //允許使用者的 Procmail 過濾規則也可寫入

步驟4.測試過濾規則

在測試過程中可以針對 A funny game 主旨來進行測試並且把 /dev/null 改成/var/virusmails。寄此主旨的信件給使用者然後使用 mailstat 來觀察。

#mailstat -km /var/log/procmail.log

步驟5.如何過濾中文廣告信

由於中文編碼 (中文廣告信) 進入系統後會顯示為亂碼，因此若是您直接在過濾規則內打中文是無法過濾中文廣告信的，所以請安裝 mmencode 套件，將中文字轉換為 MIME Code。

#cd /usr/ports/converters/mmencode //切換到安裝路徑
#make install clean //安裝並清除過程中不必要的檔案

MIME 定義兩種編碼方法：Base64 與 QP(Quote-Printable) 而含有 MIME 編碼的郵件若您查看它的源始碼會含有 "This is a multi-part message in MIME format." 這樣的句子。

• Base64： 預設值，將整個檔案資料重新編碼為 7bits
  • 以下將中文字 打炮 轉換成 MIME 編碼中的 Base64 以及將 Base64 轉換回中文

#echo "打炮" | mmencode //中文轉換為 Base64
pbSstgo=
#echo "pbSstgo=" |mmencode -u //Base64 轉換為中文
打炮

• QP (Quote-Printable)： 將 8bits 中文資料轉換為 7bits
  • 以下將中文字 打炮 轉換成 MIME 編碼中的 QP 以及將 QP 轉換回中文

#echo "打炮" | mmencode -q //中文轉換為 QP
=A5=B4=AC=B6
#echo "=A5=B4=AC=B6" | mmencode -q -u //QP 轉換為中文
打炮

在 Procemail 過濾規則 (procmailrc) 中可以接受 Base64 及 QP 的 MIME 編碼，以下過濾規則中為郵件主旨中只要有打炮這二個中文字眼就把該 Mail 移到 /dev/null 去。

:0b
* ^Subject:.*(pbSstgo=)* //Base64 Code
/dev/null
:0b
* ^Subject:.*(=A5=B4=AC=B6)* //QP Code
/dev/null

/^Subject:.*You’ve received a greeting ecard/ DISCARD /^Subject:.*Pharmacy Discount ID*/ DISCARD /^Subject:.RE: DISCOUNT ID*/ DISCARD

我重新啟動了MailScanner後，以後這個主旨垃圾信就連進來都不會進來了 那你說，垃圾信可以換一個主旨再來啊，沒錯啊，就好像防毒軟體常常要更新一樣啊，它可以變啊，我也可以增加啊，反正我已經有防垃圾信的機制，再配合手動增加這種幾乎是一模一樣的主旨來過濾，幾乎九成九都可以過濾 記住，沒有一個防毒或是防垃圾信的軟體是全自動且百分之百，認真的管理才是最重要的^_^

將/etc/httpd/conf.d/welcome.conf改名或刪除後即可正常使用。

In MailScanner.conf ensure [...]]]> Releasing mail from the quarantine – queue files

For the purposes of this, I’m assuming you have set up a single (safe!) postfix instance, with messages going to the HOLD queue, before being processed by MailScanner and sent to the INCOMING queue. You also need to be saving whole messages as queue files.

In MailScanner.conf ensure that you have

# When you quarantine an entire message, do you want to store it as
# raw mail queue files (so you can easily send them onto users) or
# as human-readable files (header then body in 1 file)?
Quarantine Whole Messages As Queue Files = yes 

Quarantined emails are by default kept in /var/spool/MailScanner/quarantine and sorted into subdirectories by date. With any luck it will be dead easy to find, as MailScanner will have sent a message including text along the lines of either:

A: If it’s a quarantined virus, or other dangerous content.

“Note to Help Desk: Look on the <Your text> in /var/spool/MailScanner/quarantine/20050309 (message
6BC5E368497.3C3A6).” 

MailScanner keeps such quarantined emails in their own directories, thus the directory containing the quarantined message will be (in this example): /var/spool/MailScanner/quarantine/20050309/6BC5E368497.3C3A6. In this directory, you should see the original queue file, named as a 10 digit hex number matching the name of the directory. There should also be copies of any attachments that may have been picked up by the virus scanning engine or file filtering.

B: If it’s a quarantined spam

"Your system administrators will need the following information:
Server name: <Your Server>
Message id: 46EE0E18151.CE630
Date code: 20080509"

MailScanner keeps all spam on a given day in the same directory, thus the directory containing the quarantined message will be (in this example): /var/spool/MailScanner/quarantine/20080509/spam.

If you want to check the original message use:

# postcat <filename>

Releasing an email from quarantine is a simple matter of replacing the queue file back into the Postfix queue, so that it gets sent. The permissions on the file are wrong, however and must be changed.

# chmod 700 <filename>

The file must now be moved into /var/spool/postfix/incoming. There may be 16 directories in there (Collectively referred to as ‘hashed queue files’) each corresponding to a hexadecimal digit, depending which version of Postfix you are running. First check if you have hashed queue files by:

# ls /var/spool/postfix/incoming

If no directories are listed then follow the instructions below but do not add the trailing letter/ number.

The file must be placed in the directory which corresponds to the first digit of the filename. So in the example above, it must go into /var/spool/postfix/incoming/6. We must also be sure to preserve the ownership and permissions of the file when moving it, so we use “cp -p”. If the message is a spam, we must also remove the trailing 6 characters.

Thus for the example above:

# cp –p 6BC5E368497 /var/spool/postfix/incoming/6

or for the example quarantined spam

# cp –p 46EE0E18151.CE630 /var/spool/postfix/incoming/4/46EE0E18151

The email will disappear from the queue and be delivered.

Thanks to Joshua Hirsh for the details and Stef Morrell for writing the document

Releasing mail from the quarantine – with a bash script

Maybe it’s too circuitous for you to do all the steps in the section above to release a mail. For this I wrote a tiny script to release very easily. To use this script you should set the MailScanner environment identically to the article above.

To use this script copy it to a file and make it executable.

The Syntax: release.sh <Message-ID> (e.g. release.sh 5B604228086.932F0)

#!/bin/sh

if [ -z "$1" ]; then
        echo "Syntax: release.sh <Message-ID> i.e. 5B604228086.932F0 (case sensitive)"
        exit
fi

#change in the quarantine folder
folder=`find /var/spool/MailScanner/quarantine/ -name $1`
cd $folder

#set the mailfile executable
mailname=`echo $1 | cut -d . -f 1`
chmod u+x $mailname

#lets get the first character
char=`echo $1 | cut -b 1-1`

#copy the mail
cp -a $mailname /var/spool/postfix/incoming/$char/

echo Mail $mailname released

Releasing mail from the quarantine – message files

If you don’t quarantine the complete queue file, but instead have the rfc822 message file, releasing messages are actually a bit simpler (for postfix) than the above, since you can use the postfix sendmail convenience program.

In MailScanner.conf you have

Quarantine Whole Messages As Queue Files = no 

and in the quarantine directory you have a file called message (this is the complete human-readible message, but without the envelope info). Just do

cd /path/to/quarantine/dir
sendmail -t -i < message

to send the message to the recipient(s) as found in the message file, or

cd /path/to/quarantine/dir
sendmail -i alternate_recipient@example.net < message

to send the message to an alternate recipient (of course you can combine them). The -i option is to avoid terminating the message prematurely on a spurious single “.” on a line in the message file.

If you use MailWatch, this can also release the message iff you don’t quarantine the whole message file as the queue file, although this uses a different method to release messages from the GUI.

Releasing mail from the quarantine – queue files postfix (again)

In a larger environment with many hosts and thousands of quarantined emails per day, we’ve found it impractical to reply to each email released or deleted from a queue, and simply process it without fanfare. The code below is modified from the release.sh above to accomodate moving the released mail back into postfix using the original mail ID. In addition, our postfix install required us to rename the queue file to its shortname, that is, the 10 or 11 character filename before postfix would accept the email into the queue.

The Syntax: release.sh <Message-ID> (e.g. release.sh 5B604228086.932F0)

#!/bin/sh

if [ -z "$1" ]; then
        echo "Syntax: release.sh <Message-ID> i.e. 5B604228086.932F0 (case sensitive)"
        exit
fi

#change in the quarantine folder
folder=`find /var/spool/MailScanner/quarantine/ -name $1 | sed -e "s/$1//g"`
cd $folder

#set the mailfile executable
mailname=`echo $1 | cut -d . -f1`
chmod u+x $1

#lets get the first character
char=`echo $1 | cut -b 1-1`

#copy the mail
cp -a $1 /var/spool/postfix/incoming/$char/$mailname

The following is for recent postfixes (2.3, 2.4) which seem to have a flat incoming directory:

#!/bin/sh

# this is the final destination for the mail to be released:
# postfix's incoming queue
POSTFIX_DEST=/var/spool/postfix/incoming

# check for valid parameters
if [ -z "$1" ]; then
        echo "Syntax: release.sh <Message-ID>"
        echo "Example: release.sh 678362AC.9CFE7"
        exit
fi

# find the specific mail in the quarantine folders
folder=`find /var/spool/MailScanner/quarantine/ -name $1`

mailname=`echo $1 | cut -d . -f1`

# copy the mail
if [ -e $POSTFIX_DEST/$mailname ] ; then
        echo "ERROR: $mailname already in $POSTFIX_DEST! EXITING"
        echo "This should not happen"
        exit 255
fi

cp -avi "$folder/$mailname" "$POSTFIX_DEST/$mailname"

# make it 0700 so that the mail is deemed ready
chmod 0700 $POSTFIX_DEST/$mailname

Releasing mail from the quarantine – the one liner

sudo install -m 0700 -o postfix <source message> /var/spool/postfix/incoming

Releasing mail from the quarantine – alias with intelligence

integrate() {
  # integration: antonym of quarantine
  # Pass the message ID as obtained from user's email as $1
  DEST=$(postconf queue_directory | cut -d= -f2)/incoming
  SOURCE=$(find /var/spool/MailScanner/quarantine -name "$1")
  install --verbose --mode=0700 --owner=postfix $SOURCE $DEST
}

Updated bash script

Line 9 on initial bash script returned filename with full path and not folder, as expected. Instructions at the top also used the cp -p option, and not -a. Instead of cd’ing to quarantine folder, this will do the copy and preserve permissions.

#!/bin/sh

if [ -z "$1" ]; then
        echo "Syntax: release.sh <Message-ID> i.e. 5B604228086.932F0 (case sensitive)"
        exit
fi

#find the quarantined file and set permissions
quarantined_file=`find /var/spool/MailScanner/quarantine/ -name $1`
chmod u+x $quarantined_file

#truncate the filename
mailname=`echo $1 | cut -d . -f 1`

#lets get the first character
char=`echo $1 | cut -b 1-1`

#copy the mail, destination is the truncated filename
cp -p $quarantined_file /var/spool/postfix/incoming/$char/$mailname

echo Mail $mailname released

內容為:

Archive: Number of messages: 5 Tries Message Last Tried ===== ======= ========== 6 3553C24D80D2.A0925 Sat Oct 30 04:57:38 2010 6 10ED024D80EC.AC79E Sat Oct 30 04:56:25 2010 6 2FF5D24D80D7.AD62C Sat Oct 30 04:53:05 2010 [...]]]> 最近MAIL常出現主旨為 : Problem Messages

內容為:

Archive:
Number of messages: 5
Tries Message Last Tried
===== ======= ==========
6 3553C24D80D2.A0925 Sat Oct 30 04:57:38 2010
6 10ED024D80EC.AC79E Sat Oct 30 04:56:25 2010
6 2FF5D24D80D7.AD62C Sat Oct 30 04:53:05 2010
6 DC7FD24D80BD.AC95D Sat Oct 30 04:43:07 2010
6 73A4D24D80C2.A16DF Sat Oct 30 04:42:41 2010

找著找著找到了Mailscanner 的 Archive 用法

文章出處:http://i-yow.blogspot.com/2009/07/archive-mailby-mailscanner.html

=====================================================

邪惡的Archive Mail備份郵件(By MailScanner)
MailScanner有一個邪惡又好用的功能：『Archive Mail』
這個比Forward還要厲害的功能，當你想要存留(備份)用戶收、發的信件時，用這就就對了~

1.啟動Archive功能
vim /etc/MailScanner/MailScanner.conf
Archive Mail = /etc/MailScanner/archive.rule

2.編輯Archive規則
vim /etc/MailScanner/archive.rule
基本規則如下：
FromOrTo: User@mail.com* yes forward Admin@mail.com.tw
(收件者或寄件者) (關鍵字，可配合萬用字元) (yes，啟用規則) (forward，動作) (Forward的目標)

※Archive Mail不但可以過濾到本機網域的帳號，也可以以外部帳號作為關鍵字，只要有經過MailScanner掃描的都可以做處理。
※以上只是簡單的例子，Archive Mail還有許多變化跟應用

======================================================

Large Mailbox threshold: 40MB (41943040 bytes)   Warning: Large mailbox: teresa.wu (1151343331)   Warning: Large mailbox: karen.wang (489717393)

GOOGLE了一下知道怎麼改這個設定:

在 [root@mail ~]# vi /usr/share/logwatch/default.conf/services/sendmail-largeboxes.conf中 <==CentOS 5.5內位置有變動