What software besides telnet are you using to connect?

Check here; however, it may be easier just to limit posting to member addresses. Of course that would depend on how one joins the list.

Could it be that the receiving server, not yours, has rejected the message owing to its size?

That's not much to go on, but there are a couple things that might fit your case: If your IP belongs to a block allocated to dial-up, DSL, or cable consumer accounts, some servers will not want to talk to you. If your IP has been blacklisted (see http://dnsstuff.com ) many servers will not want to t...

Is this a new installation? Have you run the diagnostics? That report should help. If your server is also a web server running IIS, be sure that you have disabled (stopped) the default SMTP virtual server.

• Open Windows Explorer on the PostOffices folder.
  Right-click and search for _*.*
  Delete the files (but not any user folders) that start with the underscore.

This will force ME to reconstruct the files on your customer's next visit.

Without glue or an A record other servers cannot reach you. Your MX record must point to an A record, not a CNAME. While changing this will give you connectivity, many servers will not accept your mail without a PTR record. You should add this to your zone file.

If you want to send mail from a web page, try this: <?php /** * * This is a replacement for PHP's built-in mail function, designed to * bypass various configuration snafus by talking directly to your * SMTP server. * * To use this function, replace 'mail.yourmailserver.com' with a * valid SMTP serve...

It sounds as though your installation is incorrectly configured. Did you see any error messages during installation? In the MMC, navigate to Diagnose and click to run the report. Examine the report for any failures. These will likely shed some light on your specific issues.

They actually do work well with real-world addresses. Do you experience other problems with non-local addresses? Start here for configuring the autoresponders and then look to DNS issues if you have problems sending regular messages to the same servers.

This is accomplished by using an MTA pickup event. You can learn more about these here.

Yes, we've found it to be the easiest for users and not too bad on the maintenance side as well.

The login user name isn't necessarily a public email address. Rather it is the mailbox name and post office name in the form <mailbox>@<post_office>. If you named your post offices to match the domain name and the user's mailboxes with their public address, then you can just have them log in with th...

Your customer is not authenticating. They can send to addresses hosted on your server, but not to non-local addresses. Have them change the mail client settings to "My server requires authentication" and select "use same settings as my incoming server." Alternately, you can enrol the customer's IP a...

That 12-hour delivery might be 12 seconds if it weren't for 100% on your CPU. Nonetheless, we haven't much to go on, so try to isolate your problem. First, open Task Manager so that you can monitor the CPU. Then open the MailEnable MMC and navigate to Services. Stop one service at a time until the C...