Topic: Multidrop ... anyone found the magic formula?

[MSmith]

A long-standing issue I've had with SME multidrop mode is its poor handling of listservs, BCC'd messages and the like.  I know the problem is technically not insurmountable because such great products as the Mercury mailserver can handle anything thrown at them, address-wise.  And while a direct incoming port 25 connection is great, it isn't always the most practical solution for a given network.

SO ... has anyone figured out how to generalize the SME multidrop mode so it's smarter about how it distributes what it picks up?

Failing that, can anyone suggest a good mailserver-oriented distro that could be a delegate mailserver behind a SME box or other router -- and is friendly to one of middling competence and little time?  The aforementioned Mercury server is good, but I'd prefer not to use it as it's a Windows program and I prefer Linux for servers.

Thanks for your attention, gentlemen and ladies.

[gocdo]

Providing the mail is received by SME it will work fine.

If you use fetchmail then a BCC will fail. Full stop. It will either deliver to a default or catchall address (if set) or be bounced with no delivery address. Doesn't matter if you use mercury (and I use that as well), sme, sendmail, exchange or any other environment.

A BCC address does not include the to: address in the header envelop. It has been discussed at length in this  and other forums.  

If you get your email server set as the highest priority MX record for the domain it will be fine.

K

[MSmith]

Reckon it's calls to Bellsouth & Cox to get those static IPs set up & arrange for port 25 to be unblocked.  Thanks for the input.