Sending Mail

With PocoMail, you have three options for sending mail, which you choose from the Compose New Message window (Composing Mail):

You can also revise queued mail by double-clicking on the message in the Out mailbox to reopen it in the Compose New Mail window.

The Draft mailbox - If you have messages that are "works in progress", those can be stored to the Draft mailbox. You can access these messages by double-clicking on them in the index for the Draft mailbox, which will expand the messages into the Compose New Mail window.

Encrypting Mail

PocoMail offers as part of its Privacy settings, the ability for mail to be "encrypted". If you have enabled mail encryption in Accounts Setup - Privacy, your mail will be encrypted.

Remember that PocoMail's mail encryption is for your benefit only, and is applied only to mail that you retain. This means that the recipient does not receive an encrypted e-mail. Further, as the security inherent in this encryption process is based on a password that you have specified, you will not be able to read any encrypted mail (incoming or outgoing or both, as specified in setup) without the password. If you should forget or lose this password, you will not be able to read encrypted e-mail.

"Splitting" Recipients

This option is enabled from the Sending Mail screen in Program Options.

This feature is an enhancement to deal with the fact that some ISPs or e-mail providers don't like a lot of e-mail messages from one sender - specifically, an e-mail message apparently from one account with an excessive number of multiple recipients - flooding their SMTP (outgoing mail) servers. Such messages could be construed as spam or at least, spam-like.

If this is the case with your ISP or e-mail provider, you may find that your e-mail notice to your gardening association, which has grown to 100 people in the past year (all of whom, of course, have e-mail), is being refused by the SMTP server.

However, since you have PocoMail (lucky you!) and set the Split message "threshold" for 25 recipients (and you know that your ISP/e-mail provider won't refuse that number of e-mail addresses), the e-mail list of your gardening fans will be split into four separate e-mails, each with 25 addresses. Upon sending, you will then have four separate retained copies in your "Sent" mailbox. If you use BCC field to send the message to multiple recipients you will still need to put a single address in the TO field to satisfy the SMTP server. If you split a message like this, PocoMail will retain the single TO address in each created message to ensure delivery.

Another issue that could affect delivery of these kinds of messages is if you use the Bcc: field to list all the addresses. This is done mainly to ensure the privacy of the addressees, of course, but in some cases could cause mail not to be "received". If some of your fellow gardeners have set a filter to "junk" or ignore any messages in which they are blind carbon-copied (bcc:), they will not receive the message.

An added benefit to having this split message feature is that you can use it to individually customize mail messages. For example, setting the split message "threshold" to one recipient will generate messages with only one e-mail address in the "To:" field. While this would work well when inviting a few friends to a barbecue, it could prove to be burdensome when sending such customized mail to the gardening club. You would have 100 copies of the message in your "Sent" mailbox!

You can also "force" split messages from the Compose New Message window by using Message, Split Message on Send/Queue. When you send the message, a dialog box will prompt you to specify the split threshold for recipients. Using this feature will not disable or override the split recipient threshold set in Program Options, and will affect only the current message.

Some issues with Sending Mail

If you are an experienced e-mail user with multiple e-mail accounts from multiple providers, you may already be aware of some of these pitfalls. The following discussion is more a "heads up!" for those who may wonder why they can't seem to send mail.

Authenticated Servers

Authenticated servers are those that can require:

POP authentication - POP mail must be checked first before outgoing mail is allowed to be processed through the SMTP server. In general, you don't have to check off Authentication in the Accounts Setup for this purpose. You can send mail for these accounts by queuing mail, and having queued mail sent after checking for new mail, an option available in General Options - Sending Mail.

SMTP authentication - The ISP/e-mail provider requires a separate authentication process to access the outgoing mail server. Often the authentication is a reiteration of the POP username and password. You can set up SMTP authentication in Accounts Setup - SMTP Settings. Check Use Authentication and fill in the appropriate information.

Blocked SMTP Servers

Some ISPs don't allow mail to be sent through their service using another "stranger" SMTP server. This is not done to annoy you, but is instituted as an added security measure to protect you and others from unethical use of an "open" SMTP server.

Say you have an internet account with GalaxyLink. You find that you can send and receive mail from your account with no problem, but can't send any mail from your other account set up for your Brainscan account. You check your settings over again for Brainscan - POP is setup for, SMTP is set up for, and you've triple-checked your username and password information. You check with GalaxyLink and find out that they do not allow other SMTP servers to be accessed through their service.

You don't have to give up your Brainscan account. All you need to do is set it up so that outgoing mail for your Brainscan account uses GalaxyLink's SMTP server. The simplest way to do this is to delete SMTP settings from the Brainscan account set up, and set GalaxyLink's server as the Default SMTP server in Program Options - Sending Mail. Alternatively, you can change the SMTP settings in Brainscan to reflect GalaxyLink's SMTP settings.