Skip to main content
Jan_Scholten
Jan_Scholten
New Member
January 27, 2009
Question

Blacklist import

  • January 27, 2009
  • 3 replies
  • 3100 views
I am trying to import email adresses to a personal blacklist. Antispam -> Black/Whitelist -> Personal ->Blacklist ->[choose File] -> restore. I use a textfile with one email-adress per line. But trying to restore this file does not work " Not a valid file: line 1." Any hints?

    3 replies

    rwpatterson
    rwpatterson
    New Member
    January 27, 2009
    Welcome to the forums The white/black list needs to be in a specific format. Use this tool to convert the raw email addresses: http://camerabob.dyndns.org:5190/Fortigate/emailbwl.cgi
    Jan_Scholten
    Jan_ScholtenAuthor
    New Member
    January 27, 2009
    I was trying to use the " restore" link on the GUI. The " backup" link does provide a file as one email per line. But fails to import/restore such (selfcreated) list. If i use the link you provided.. in whichpart do i configure the blacklist for a specific user? The http://camerabob.dyndns.org:5190/Fortigate/emailbwl.cgi does a 
    config spamfilter emailbwl
    But i want a personal blacklist (only for recipient me@mydomain.tld)
    rwpatterson
    rwpatterson
    New Member
    January 27, 2009
    Add the email on the left, click the convert button, and copy the output to a file, or paste into the CLI. If you already have entries in the list, make sure you start with a unique ' edit' number to not overwrite the already existing ones. If you only have the one address, just use the GUI to add it. (' AntiSpam > Black/White list > E-Mail Addresses > Create New' will create the list name. Next step would be to add the entry. Just follow along. It' s pretty intuitive. Whn done, add this list to the protection profile.)
    Jan_Scholten
    Jan_ScholtenAuthor
    New Member
    January 27, 2009
    I think i know why i didn' t understand you.. I am talking about a Fortimail, not a Fortigate.. So i am probably better in the fortimail forum.. As a final comment: It happens to be the encoding of the file, which was UCS-2 little Endian but must be ANSI for being imported correctly
    Terms & ConditionsAccessibility statement