On the Opt In, yep, thats what we're doing.  We're using the integrated list manager for unsubscribes, and manually entering in new subscribers.  It's a static list usually, very few adds, so manual entry isn't an issue. Future lists may be much larger and more active, so I may have to design a web page to get the data into the list file.  We'll see

On the spam label, I may have come across a separate error that was causing it.  The DNS Entry for reverse lookups was fat fingered, I'm getting that fixed now.  Sorry for the false alarm on that. 

I run a 501C3 not for profit.  My purpose for using Mercury is two fold: list management for Marketing and offloading mail from our primary mail server.  I don't want to relay messages off our network server, I'm trying to make Mercury handle it all.  Fortunately, it can do that.

The first problem I'm running into though is a big one.  Any messages sent out from Mercury are automatically labeled as spam, and dropped into the spam folder.  Our subscribers are A, typically older people who are not technical and thus won't go through a spam folder, and B, want our messages and have signed up to receive them.  

My belief is the header is the reason for the spam label.  Has anyone else seen this, and anyone have any luck fixing the header?  

I run a 501C3 not for profit.  My purpose for using Mercury is two

fold: list management for Marketing and offloading mail from our

primary mail server.  I don't want to relay messages off our network

server, I'm trying to make Mercury handle it all.  Fortunately, it can

do that.

I assume you are using a opt-in mailing list where all of the members of the list have requested the mail from your mailing list.

The first problem I'm running into though is a

big one.  Any messages sent out from Mercury are automatically labeled

as spam, and dropped into the spam folder.  Our subscribers are A,

typically older people who are not technical and thus won't go through

a spam folder, and B, want our messages and have signed up to receive

them.  

This has very little or nothing to do with Mercury in itself, it has more to do with the anti-spam systems setup by the receivers.

1.   If you are using MercuryE to send mail then you must have a fixed IP address and this IP address must not be on any blacklists.  Normally randomly assigned IP address connecting to a host are classified as spam or rejected out of hand.

2.  The content of the message must not be spammy; many many marketing type message are automatically marked as spam by the anti-spam unless the receiver has whitelisted your sending e-mail address.  

My belief is the header is the reason for the

spam label.  Has anyone else seen this, and anyone have any luck fixing

the header?

Not sure what header you are talking about.  The spam label in a message is generally added by the receiver.  You can verify this by using session logging to see exactly what is being sent by either MercuryE or MercuryC to the receiving host.  If you could point out what header you are talking about we may be able to help.