well what am i supposed to use???
One way is to create a GMail account for just the purpose of sending mail via MercuryC.
right, so you're saying i need this to help prevent my outgoing emails
being identified as spam. i was confused before because i thought you
meant i need it for sending local mail (by which, to be clear, i mean
mail destined for example to user1@localhost, which mercury should
stick into a test mailbox on the same system).
since mercury is relaying the message through my gmail account, is what
you suggested really necessary?
I think so. Have you looked at the headers on the messages you are sending. The Mercury/32 server is going to identify itself in these headers for each message sent through this host.
since merc is just essentially (afaik)
logging into the gmail account and giving gmail a message to send, why
should the real original destination matter? i mean i use thunderbird
to send mail from my computer all the time, that's essentially doing
exactly the same thing merc is doing here, and there's no problem with
mail being identified as spam there...
Not really, mail sent via T-bird is being send directly to the ISPs SMTP host for processing. Mail sent by your application (or T-bird) via MercuryS is being processed via MercuryS and queued, Mercury core and queued and MercuryC. Each process is adding a Recieved line to the message.
Here's the headers put on by Peter's Mercury/32 server for the message I got from the comunity server. The web process is sending the mail via MercuryS. If you are using "localhost" as both the name of the system and the domain then it will show at least 3 times in the message. If you are forwarding mail from ma local user there can be many more instances.
Received: from Spooler by mail.praktit.se (Mercury/32 v4.62) ID MO0003BA;
10 Jul 2008 01:16:31 +0200
Received: from spooler by mail.praktit.se (Mercury/32 v4.62);
10 Jul 2008 01:16:26 +0200
Received: from web2 (192.168.1.20) by mail.praktit.se (Mercury/32 v4.62) with
ESMTP ID MG0003B4; 10 Jul 2008 01:16:22 +0200
This message was first received by MercuryS and queued as MG0003B4, then processed by core and queued as MO00003BA and finally taken from the queue by MercuryE for delivery to my server.