Blocklist Help
Blocked? To check, get info and resolve listings go to
Associated Documents
SBL Delisting Procedure
To request the removal of an SBL listing, the ISP to whom the listed IP address belongs must contact the SBL Team, by email, using the dynamic 'mailto' link visible on the SBL record page. The SBL Team operates 24 hours a day, seven days a week and normally removes listings quickly once notified by the ISP that the spam problem has been terminated. [1]
It is important to only contact the SBL Team address and not other Spamhaus addresses, as the Spamhaus Project consists of a number of distinct teams each with a particular role and make up. Spamhaus teams include but are not limited to: the SBL team, the XBL team, the PBL Team, the DBL Team, the ROKSO Team, the European Review Team. Only the SBL Team has access to and can handle removal of SBL listings.
It is essential that the spam issue the listing concerns has been terminated before asking for the removal of the listing. If the SBL Team have reason to believe the issue is ongoing they can not remove the listing. [2]
If for some reason even though the issue was terminated there remains some residual problem which does not satisfy the SBL Team that the listing can be removed, the issue can be referred to Spamhaus' European Review Team for reevaluation. The European Review Team also has the responsibility for reviewing and handling disputes of SBL listings which are alleged to be incorrect.
The procedure for removing an SBL listing starts at the specific listing's online record, an SBL web page detailing what is listed and why. At the end of each SBL record page is a section titled &Removal Procedure&. The Removal Procedure section gives the email address for the SBL Team and the Subject reference for the removal request.
Each SBL record specifies the reason for listing the IP Address or IP Range. Normally this will be due to being a direct source of spam, hosting a landing site or other services implicated or determined to be behind the spam. Normally each SBL record also contains evidence in the form of a sample of a spam message received or a link to a web site advertised in a spam, or contains DNS Trace Evidence showing the results of DNS analysis on the domain or IP range and/or Whois records.
Special handling is employed for showing evidence of spam sent to spamtraps or evidence supplied by trusted 3rd party intelligence. Spamhaus obtains samples of spam from a number of reliable sources including Spamhaus' own . In order to protect the usefulness of these sources, the source will not be revealed and parts of spam samples deemed to uniquely identify the source can and will be redacted. [3]
[1] Where we have a proven working relationship with any Internet Service Provider, the SBL team implicitly trusts the Internet Service Provider's Abuse Manager and will normally remove listings on the Abuse Manager's word that the reason for listing has been corrected or terminated.
[2] In the case of SBL listings of IPs under the control of known (ROKSO-listed) professional spammers, where listings are often made preemptively based on the gangs past performance and history, an SBL listing will normally remain in place until the gang has been completely removed from the ISPs' network.
[3] Spamhaus can not divulge the e-mail addresses of
or of trusted users who supply spam evidence. A request for such addresses, so that the bulk email sender can wash them from his list, is analogous to one who either intentionally or unintentionally sends pornography to minors, who then asks for a list of those minors so he will not continue to commit the crime. The responsibility for complying with Spamhaus SBL policy and preventing UBE being sent begins and ends with the bulk email sender.
Search by SBL Record#I installed siebel 8.0 but siebel service stops after few minutes and siebsrvr log throws
SBL-SVR-00026: Unable to allocate shared memory.
I have deleted the .shm file siebesrvr\admin and restarted the gateway and siebel service but even though siebel service stops after few minutes
Popular White Paper On This Topic
Best Answer
Mark this reply as the best answer?(Choose carefully, this can't be changed)
&br/>Unable to allocate shared memory.
&br/>Explanation
&br/>The above error message is reported in the log files when the Siebel server
&br/> fails to start up. In most cases, one or more additional error messages al
&br/>so accompany this one, for example SBL-SVR-00005.
&br/>These errors might be reported for the following known reasons:
&br/>There is a shared memory file that is maintained by each Siebel server unde
&br/>r the &admin& directory of its root installation ($SIEBEL_ROOT\admin on bot
&br/>h UNIX and windows). This file follows the naming convention [&$EnterpriseN
&br/>ame>.&$ServerName>.shm]. It is built upon server startup, and destroyed upo
&br/>n shutdown. If this file cannot be created successfully upon server startup
&br/>, the above error message can be reported. Possible reasons for this file t
&br/>o not be created successfully are:
&br/>1. The clean up routine upon shutdown did not clean this file possibly beca
&br/>use of an abnormal termination of the Siebel server service.
&br/>2. Possible disk space issues are preventing the creation of this file.
&br/>3. Lack of permissions on this directory or folder or file by the service o
&br/>wner account.
&br/>4. The wrong Oracle client for example a version 8 client which is running
&br/>on the Siebel Server is being used to connect to an Oracle version 9 databa
&br/>se. In this scenario, the error was reported when the user was trying to ru
&br/>n the srvrmgr utility and was not able to connect to the database via the O
&br/>DBC Datasource. To confirm, try using the srvrmgr utility and check the app
&br/>ropriate ServerMgr_xxxx.log files for any additional errors like: [DataDire
&br/>ct][ODBC Oracle driver][Oracle]ORA-24316: illegal handle type.
&br/>Corrective Action
&br/>For the above known behaviors, try the following corrective steps:
&br/>1. Make sure the Siebel Server service(s) are shutdown completely before sh
&br/>utting down the Siebel Gateway Server service. Check if the above .shm file
&br/> is still present in spite of a successful Siebel server shutdown. After ma
&br/>king a copy of the old *.shm (if it was left behind after a server shutdown
&br/>), delete it and restart the service, and verify whether a new *.shm file i
&br/>s created and if that allowed the server to start up properly.
&br/>2. Provide for ample disk space and comply with the memory requirements of
&br/>a typical Siebel installation. For more information refer to the appropriat
&br/>e System Requirements and Supported Platforms Guide (SRSP) located on Suppo
&br/>rtWeb. Change request 12-H7JTG6 has been logged to address the product enha
&br/>ncement request of checking for available disk space before starting the se
&br/>rver.
&br/>3. Grant necessary privileges and permissions to the Siebel Server service
&br/>owner account. NOTE: The following bookshelf version is also applicable to
&br/>the version listed in the header of this error message documentation. For m
&br/>ore information about the Siebel Service Owner Account, refer to Siebel Boo
&br/>kshelf version 7.8 > Siebel Installation Guide for (Microsoft Windows or UN
&br/>IX): Servers, Mobile Web Clients, Tools > Preparing for Installation > Gene
&br/>ral Considerations in Planning Your Siebel Deployment > Creating the Siebel
&br/> Service Owner Account.
&br/>4. Make sure you are using the correct ODBC datasource when running the srv
&br/>rmgr utility. You can follow the instructions in FAQ 1113 for further infor
&br/>mation about testing the ODBC datasource. If you have more than one Oracle
&br/>client running on the Siebel Server, ensure the PATH environment variable i
&br/>s configured to use the correct client software based on the database versi
&br/>on you are running. Confirm you can connect to the database using the nativ
&br/>e database tool outside of the Siebel application." id="ctl00_m_m_i_ctl00_gr_ctl01_bestanswerbody" class="textarea-bestanswerhidden" name="bestanswerbody" answerbodyId="1436763" />
replied May 8, 2007
I found this on support web pl go through it..
Unable to allocate shared memory.
Explanation
The above error message is reported in the log files when the Siebel server
fails to start up. In most cases, one or more additional error messages al
so accompany this one, for example SBL-SVR-00005.
These errors might be reported for the following known reasons:
There is a shared memory file that is maintained by each Siebel server unde
r the "admin" directory of its root installation ($SIEBEL_ROOT\admin on bot
h UNIX and windows). This file follows the naming convention [&$EnterpriseN
ame>.&$ServerName>.shm]. It is built upon server startup, and destroyed upo
n shutdown. If this file cannot be created successfully upon server startup
, the above error message can be reported. Possible reasons for this file t
o not be created successfully are:
1. The clean up routine upon shutdown did not clean this file possibly beca
use of an abnormal termination of the Siebel server service.
2. Possible disk space issues are preventing the creation of this file.
3. Lack of permissions on this directory or folder or file by the service o
wner account.
4. The wrong Oracle client for example a version 8 client which is running
on the Siebel Server is being used to connect to an Oracle version 9 databa
se. In this scenario, the error was reported when the user was trying to ru
n the srvrmgr utility and was not able to connect to the database via the O
DBC Datasource. To confirm, try using the srvrmgr utility and check the app
ropriate ServerMgr_xxxx.log files for any additional errors like: [DataDire
ct][ODBC Oracle driver][Oracle]ORA-24316: illegal handle type.
Corrective Action
For the above known behaviors, try the following corrective steps:
1. Make sure the Siebel Server service(s) are shutdown completely before sh
utting down the Siebel Gateway Server service. Check if the above .shm file
is still present in spite of a successful Siebel server shutdown. After ma
king a copy of the old *.shm (if it was left behind after a server shutdown
), delete it and restart the service, and verify whether a new *.shm file i
s created and if that allowed the server to start up properly.
2. Provide for ample disk space and comply with the memory requirements of
a typical Siebel installation. For more information refer to the appropriat
e System Requirements and Supported Platforms Guide (SRSP) located on Suppo
rtWeb. Change request 12-H7JTG6 has been logged to address the product enha
ncement request of checking for available disk space before starting the se
3. Grant necessary privileges and permissions to the Siebel Server service
owner account. NOTE: The following bookshelf version is also applicable to
the version listed in the header of this error message documentation. For m
ore information about the Siebel Service Owner Account, refer to Siebel Boo
kshelf version 7.8 > Siebel Installation Guide for (Microsoft Windows or UN
IX): Servers, Mobile Web Clients, Tools > Preparing for Installation > Gene
ral Considerations in Planning Your Siebel Deployment > Creating the Siebel
Service Owner Account.
4. Make sure you are using the correct ODBC datasource when running the srv
rmgr utility. You can follow the instructions in FAQ 1113 for further infor
mation about testing the ODBC datasource. If you have more than one Oracle
client running on the Siebel Server, ensure the PATH environment variable i
s configured to use the correct client software based on the database versi
on you are running. Confirm you can connect to the database using the nativ
e database tool outside of the Siebel application.
Best Answer
Mark this reply as the best answer?(Choose carefully, this can't be changed)
replied Aug 26, 2010
Thanks aarora_98, Deleting shm file worked for me.
This thread has been closed due to inactivity.
Get Answers - It's Free
If you're looking for Siebel - General Discussions help, sign up and take advantage of 17,985
Siebel professionals who are here to help you.
PCMag Digital GroupBlocklist Help
Blocked? To check, get info and resolve listings go to
Associated Documents
SBL Policy & Listing Criteria
The Spamhaus Block List (&SBL&) Advisory is a database of IP addresses which do not meet Spamhaus's policy for acceptance of inbound email and therefore from which Spamhaus does not recommend the acceptance of electronic mail.
IP addresses are listed on the SBL because they appear to Spamhaus to be under the control of, or made available for the use of, senders of Unsolicited Bulk Email (&spammers&). The SBL database will normally include IPs identified to Spamhaus's best ability as likely direct spam sources, spammer hosting/DNS, spam gangs and spam support services.
SBL listings are based on Spamhaus' definition of &Spam& meaning &Unsolicited Bulk Email& (&UBE&) (see: ). Spamhaus does not evaluate the content or legality of spam, merely whether a message is spam by our definition or not. The responsibility for complying with Spamhaus SBL policy and preventing UBE being sent begins and ends with the bulk email sender.
SBL listings are based on evidence which has satisfied the SBL team that the IP address or IP range is under the control of a spammer, spam operation or a spam support service and represents an unwanted nuisance or threat to mail systems using the SBL.
SBL listings are immediate and, in the case of known spam operations, are preemptive. The SBL does not require warnings or have a 'grace period' and does not require physical evidence of spam received from any specific IP to qualify a listing (in the case of known spam gangs, any IPs under their control are listed on sight). Warnings are however normally sent to block owners and/or Upstreams before listing large netblocks.
The criteria for listing IP addresses in the SBL is:
SBL Listing Criteria
Spam Sources
Sources of unsolicited bulk email sent to Spamhaus
or submitted to Spamhaus by trusted 3rd party intelligence.
Spam Services
Servers, including mail, web, dns and other servers identified as being an integral part of a spam operation or being under the direct control of spammers.
Spam Operations
Known spam operations and gangs listed in Spamhaus
registry, including preemptively listing new IPs each time known spammers move to new hosts.
Spam Support Services
Services providing service to known spam operations listed on , services providing 'bullet-proof hosting' for spam service purposes, services obfuscating or anonymising spam senders, services selling or providing hosting for the sales or distribution of spamware or address lists, and networks knowingly hosting spammers as either stated or de facto policy.
Notifications of Listings
Spamhaus maintains a database of worldwide Internet Service Providers which includes the ISP's contact address for abuse issues (where known). On creating a new SBL record the SBL database automatically emails a notification of the listing to the ISP's abuse contact (where known).
IP addresses are removed immediately from the SBL database upon receipt by the SBL Team of notification from the IP owner (the Internet Service Provider responsible for assigning or routing the IP address) that the reason for listing has been corrected or terminated. See
for a detailed description of delisting policy and procedure.
Spamhaus does not perform scans to update SBL records. It is the ISP's responsibility to advise the Spamhaus Project of any changes which affect a listing. On being advised of changes, Spamhaus will endeavor to amend the listing as quickly as possible.
If not removed manually from the database, all SBL records eventually time out and are automatically removed. Each SBL record has a timeout value set by the record Editor as deemed appropriate for the listing. Unidentified spam sources normally have a short time-out of 2, 7 or 14 days, persistent spammers may have a timeout set at 6 months, while known spam gangs with ARIN-assigned IPs will normally have the timeout set at one year or more.
Search by SBL Record#[转载]ASA上的SBL（Start&Before&Logon）配置
支持雷哥！
一，场景描述：
目前大多数的企事业单位都使用微软的域集成（或为安全考虑采用3A结合域控），只有合法的域用户才能够访问公司内部的数据资源。公司内部设备（PC等）加入域是很容易的事情，但是如果是职员出差在外或在家里处理CASE，若不方便加入域，想要访问内部资源的话，就有一定的难度了。因此，思科在其ASA上加入SBL（Start Before
Logon）这个Feature，在PC开机运行系统之前通过Anyconnect使用SSLVPN拨入公司内部，获取内部地址，那样再启用域用户就方便多了！
SBL这个feature，数年前就被思科引入到ASA的OS中了（8.0），但是除了思科官网的配置文档外，真的还没有其他的介绍。
三，需求：
1，各网段地址如拓扑所示
A，ASA的outside网段为202.100.1.0/24，inside网段为172.16.1.0/24，DMZ网段为10.1.1.0/24
B，文件服务器，DC，DNS以及ACS等服务器均在DMZ
2，分别用两台笔记本来模拟Win7操作系统的移动用户和XP系统的SOHO用户来完成Tasks
三，说明：
1，Cisco Adaptive Security
Appliance Software Version 9.0(1)
Manager Version 7.0(2)
（若完成SBL，anyconnect必须是2.2以上版本）
四，配置：
1，为了Anyconnect能够正常的工作，首先要解决的是防火墙的证书问题。这个实验采取了最偷懒的方式：防火墙自签名证书。在处理证书之前，我们要先在Win7上做个主机映射。如下图所示：
3，ASA配置并产生证书：
crypto key generate rsa label
asa.yeslab.net modulus 1024
crypto ca trustpoint CA
enrollment self
fqdn asa.yeslab.net
subject-name cn=asa.yeslab.net, ou=yeslab, o=security
keypair asa.yeslab.net
crl configure
ssl trust-point CA
4，ASA申请自签名的证书：
ASA(config)# cry ca enroll
WARNING: The certificate
enrollment is configured with an fqdn
that differs from the system fqdn.
If this certificate will be
used for VPN authentication this
may cause connection problems.
Would you like to continue with
this enrollment? [yes/no]: yes
% The fully-qualified domain name
in the certificate will be: asa.yeslab.net
% Include the device serial number
in the subject name? [yes/no]: no
Generate Self-Signed Certificate?
[yes/no]: yes
ASA(config)#
5，Win7加载证书：
第一步，ASA配置网管
http server enable 500
http 0.0.0.0 0.0.0.0
aaa authentication http console
username ccie password ccie
privilege 15
Win7通过输入来启用ASMD
6，检查证书加载情况：
7，再次通过ASDM来网管ASA，就不会出现证书报错的问题：
8，进入Anyconnect配置：
第一步：在防火墙Outside接口启用WEBVPN，加载anyconnect软件，并激活SVC
enable Outside
anyconnect image disk0:/ anyconnect-win-3.1.01065-k9.pkg
anyconnect enable
第二步，配置推送给客户的地址池和隧道分割列表
ip local pool ippool 123.1.1.1-123.1.1.20
access-list split extended permit
ip 172.16.1.0 255.255.255.0 any
第三步，配置组策略，并调用地址池和隧道分割列表
group-policy yeslabpolicy
&&internal
group-policy yeslabpolicy& attributes
&vpn-tunnel-protocol ssl-client
ssl-clientless
&split-tunnel-policy
tunnelspecified
&split-tunnel-network-list value
&address-pools
value ippool
第四步：配置用户名和密码，并在用户属性下调用group-policy
username yeslabuser password cisco
username yeslabuser attributes
& vpn-group-policy yeslabpolicy
Win7上配置：
第一步：运行ASDM
第二步：拨SSLVPN
第三步：加载Anyconnect
第四步：安装Anyconnect
第五步：安装成功后，会自动拨号，并在右下方有小锁图标
第六步：在没启用SBL功能的前提下，查看Win7系统的控制面板—程序和功能
9，通过ASDM来配置SBL
第一步：在anyconnect client
profile中定义SBL的xml文件
第二步：编辑我们定义的SBL的profile，勾选“user start before
第三步：编辑group-policy，也就是我们定义的yeslab.policy
点击anyconnect
client---optional client modules to download，选择anyconnect SBL
点击anyconnect
client---client profiles to download，选择我们定义的SBL这个profile
我们在ASA上通过命令来看下定义的SBL这个XML文件
明显的，已经启用SBL这个feature。
10，进入Win7系统的配置
第一步：首先要加载个机器证书
导出根证书：
通过MMC来加载机器证书：
开始导入证书：
一定要是一个受信任的根证书颁发机构：
查看证书：
11，再次通过Anyconnect来拨SSLVPN，拿配置SBL的策略
查看Win7系统的控制面板—程序和功能就会出现
12，OK，见证奇迹的时刻到了，我们现在重启Win7。
在没进入系统前，提示按 ctrl+alt+delete组合键
随后进入选择项
XP系统的PC我就不给大家介绍了，基本和Win7是一样的，SBL的相关视频会很快推出，敬请关注！
以上网友发言只代表其个人观点，不代表新浪网的观点或立场。