Be sure to CHECK your mail via POP3 first. Due to widespread Internet SPAM abuse, we are unable to operate an "open relay" that would allow anyone to send mail from our server. As such, we use what's called "POP Authentication based selective relaying". When you authenticate via POP3, your IP address is added to a list of IP addresses that are temporarily allowed to relay through us without restrictions.

In order to successfully send mail through Access 1 mail servers your email client must pass your username and password before email is sent. The following instructions will instruct you on how to configure Outlook Express.

DLS dialup customers should use mail.dls.net as the SMTP (outgoing) and POP3 (incoming) mail servers. For DLS web hosting customers, please see question 3.1. If you are dialing up outside of the Chicagoland area, you must use a mail client that supports SMTP authentication (such as Outlook Express or Netscape Messenger) and configure it to use the same settings as for POP3. For example, if your email address was joe@dls.net, you would use joe as the username for POP3 and for SMTP authentication.

Our Outgoing (SMTP) mail server requires some kind of authentication of who you are, to ensure only authorised users can use our mail server. This error message means you have not authenticated. There are two ways of authenticating. When you download mail, you then have a window of a few minutes to send e-mail using our SMTP server provided you do not disconnect from the internet in between. In Outlook Express, the "Send and Receive" button does this the other way around.

Apache inadvertantly compiled the wrong expat XML parser into itself. Rebuild Apache, this time using the --disable-rule=EXPAT option. Fields cannot have the same name, even if they've been deleted. This is because you might have older stories around that use the old name, and still republish them to templates that use the old name. The solution is to give the new version of the field a different name, but make the ''Label'' the same.

Yes, you can. We do have anti-spam protection that mandates that you check your e-mail first so we can add your IP address to a list of hosts that are allowed to relay through us.

The email server is not allowing you to send mail because it does not recognize your IP address. You are likely not connected to Grande directly, but rather (a) dialed into another provider, (b) at your office, or (c) travelling. Simply CHECK your email before attempting to send. This will permit your current location to send email for a period of 30 minutes. Each time you successfully check your email, your full 30 minute 'send window' will be refreshed.

This is probably because you set up your mail client to use ValueWeb's mail server to send mail via SMTP. Due to problems with spam being routed through ValueWeb's mail server, you must now use your internet service provider's mail server to send outgoing mail.

Most well configured SMTP servers will not allow a user from outside of their own local domain to send a message to users that are also outside of that domain. You can send a message in from outside, or out from inside, but you can't send a message to your buddy at IBM through the MindSpring SMTP servers if you are, say, at AOL. This is to prevent spammers from abusing SMTP servers. This will happen if you are using a MailMan installation at a different location than your SMTP server.

Make sure that you are using smtp-yourdomain.com as your Outgoing Mail Server and your "From Email-id" is yourname@yourdomain.com. Every bounced message contains an error message, which is normally a self explanatory one. If an error has come from any of FutureNet Technologies's Mail Server, it will contain the name of that server with extension futurenettechnologies.com (e.g. pop1.futurenettechnologies.com, smtp2.futurenettechnologies.com).

Our system is designed to work with SMTP authentication (enabling instructions below). We do however have a backup system that may take up to one minute to enable mail delivery without SMTP authentication causing the 'Relaying Denied' error. Subsequent attempts should result in successful mail delivery.

This message is coming directly from the SMTP server and it is letting you know that you are not allowed to send messages through it from your current network location. SMTP servers can be configured to send messages for anyone that connects to them, but this is rarely the case in the real world. Due to the SMTP abuse by spammers and mass-mailers, the network administrators had to close their SMTP servers to only allow their clients to send mail.

SMTP authentication is required In order to prevent spamemrs from accessing the outgoing mail server and using your account to send spam. Run through the mail settings of the e-mail client you are using and make sure the Account Name is set to your username (all lowercase) and password is correct by deleting it and retyping it in

Try again in a couple minutes. This happens all the time because your sockets do not always close when they are supposed to. This message does NOT mean you're banned.

If you get a Code 403 "Access Denied" message when you try to post a message or reply, or when you try to access a message from the Forum, it's because either you, someone using the IP address you currently have, or someone from your class C IP block has been identified as a board spammer (or flamer) and has been banned. Generally we ban IP blocks only in cases of spamming, but it's possible that innocent people in the same block could be banned in the process.

For added security you have to check your mail before you can send mail using your account. For example in Microsoft's Outlook you just need to click the "Send & Receive" button before you send any mail through us.

If you wish to only provide data (of the hosts that your DenyHosts daemon has blocked) to the denyhosts.net server but not receive hosts that have been denied by others you can set your SYNC_DOWNLOAD to no. The default is yes but only applies if synchronization mode has been enabled.

There are two things that can cause this error. The first is that you have not logged in and checked your email within the past 20 minutes so your IP has not been given SMTP access. The 2nd is the program on the server that logs IP's for SMTP access has died. If you believe its the 2nd of the two, send in a ticket and we'll get things straightened out right away.

Please don't bombard the list with test messages. If you feel the need to determine whether the server is running, send a 'help' command. To do this, address a message to <requests@british-steel.org>. No need to put anything in the Subject or Body of the message as it'll be ignored.