hard to help unless to can tell us exactly what you are trying to do and what is failing.  Mercury/32 is not all that difficult to setup and sending mail via MercuryE or MercuryC only requires a couple of configuration entries.

 

> I sent a msg from my hotmail account to my mercury account. They
> arrived ok, but a reply back doesnt work. After my initial post I tried
> some other accounts ( like my work) and noticed they all are resolving
> to 205.178.187.13. this mean I have some kind of DNS issue I assume.

Not necessarily, but in this case it looks like it's not resolving correctly

hotmail.com, MX, 5, mx4.hotmail.com
hotmail.com, MX, 5, mx1.hotmail.com
hotmail.com, MX, 5, mx2.hotmail.com
hotmail.com, MX, 5, mx3.hotmail.com

    mx1.hotmail.com, A, 65.54.244.136
    mx1.hotmail.com, A, 65.54.245.8
    mx1.hotmail.com, A, 65.54.244.8
    mx2.hotmail.com, A, 65.54.244.40
    mx2.hotmail.com, A, 65.54.244.168
    mx2.hotmail.com, A, 65.54.245.40
    mx3.hotmail.com, A, 65.54.244.72
    mx3.hotmail.com, A, 65.54.244.200
    mx3.hotmail.com, A, 65.54.245.72
    mx4.hotmail.com, A, 65.54.244.232
    mx4.hotmail.com, A, 65.54.245.104
    mx4.hotmail.com, A, 65.54.244.104

Are you sure you are pointing to the DNS hosts in MercuryE?


>
> 18:53:08: processing job MO000017
> Resolved CN for 'hotmail.com' to 205.178.187.13

This IP address give a rDNS of www.networksolutions.com


> Connecting to 205.178.187.13
> Connection error.
>
> 19:11:48: processing job MO00001D
> Resolved CN for '<deleted domain>.com' to 205.178.187.13
> Connecting to 205.178.187.13
> Connection error.
>

Thanks a lot, Thomas, that's useful advice.

All I get is "message not successfully sent."

Is there a way of finding out why? Without this, it becomes rather impossible to debugg & fix.

If you turn on session logging in Configuration | MercuryS then each TCP/IP transaction will be logged in a TCP[4 hex digits].MS  Point the session logging to drive:\mercury\logs\mercuryS and then make sure the directory exists.

Am I supposed to do some set-up work first?

1.    Verify that mercury/32 is properly setup to receive the mail via MercuryS. 

2.    Read up a bit on SMTP transfers to ensure you can tell a good TCP/IP session from a bad one.  

3.    Read the Mercury manual to figure out how it's supposed to be configured. 

I sorted it out. I was using MS-Excel to edit the file (removing duplicates, double @@'s, spaces etc from the addresses), and when saving as a text file it was saving it as unicode. After I opened the txt file and saved it as an ANSI text file, Mercury could import the addresses. Phew!

Only via a daemon since only daemons get access to the the QCF control files containing RCPT TO: addresses.  If you are sending via the Mercury/32 queue you might be able to write something to process the "glue" headers of the 101 file to catch these.

Thanks a lot, Thomas. Now I know what to do in future.

Use Configuration | MercuryS | Connection control and select the first two options to turn off relaying and to turn on strict local relaying.  You can then check the third option to allow and setup the auth password file that contains the username and passwords to be used to allow specific users to relay.

 

Yes.

I have created a shortcut which links to:

I copied it to c:\documents and settings\all users\desktop

It then appears on everyone's desktop when they logon. When they click it, they are prompted for a user name - it's just the same as a local installation and the end user does not notice any difference.

And Mercury will manage all mail as you say, so long as it is configured correctly.

Very many thanks.   

I didn't know that but it has worked and I can now continue my 15 years use of Pegasus.

J Booth 

The SquirrelMail team did include the Return Receipts fix in the final release: 

**************************************
*** SquirrelMail Stable Series 1.4 ***
**************************************

Version 1.4.15 - 23 May 2008
----------------------------
  - Fix saving of Read Receipts to Sent folder.
  - Converted Romanian (ro_RO) to UTF-8.
  - Converted Slovak (sk_SK) to UTF-8.
  - Converted Swedish (sv_SE) to UTF-8.

Thanks Rolf - there were 2 instances running. I now have just one on the go and can now see the mail coming in.

Cheers!

 

Do you have any other system monitoring tools installed, including anti-virus/anti-malware? Also, was your OS pre-installed? Sometimes the OS is customised and is difficult to re-configure. It might be worth a call to the PC supplier to discover if this is the case.

If your ISP will not allow you to relay through them, there are companies that provide email relay services.  One is Tzolkin ().  We have used them in the past for their Dynamic DNS service and they were very reliable.  They have different usage levels; under $50 (US) a year, for 2000 messages per month.  Hope this helps.

Ah! The penny has dropped :)

So, as said, the setup is wrong and their mail server does not recognise the RCPT data as being local. I understand.

Thanks very much!

Get Mercury set up with IMAP running.

Add the IMAP profile to Thunderbird.

Copy mails from 'mbox' folders to IMAP folders.

I would suggest leaving them on your own Mercury IMAP server if you have a static IP (or use dyndns.org for dynamic IP).

But if you want to GIFT ALL YOUR DATA to Google, go ahead.

[quote]

Resistance is futile .... you will be assimilated.

[/quote]

[:)]

 

Unless your ISP offers IMAP access (for an IMAP client like Pegasus or Thunderbird, but NOT Mercury) then yopu will need to log onto the webmail interface and copy any mail you want from the subfolders into the INBOX, then POP-ing via Mercury will collect it.

The idea is that you provide an exported function that sets a variable in the dll that controls if the main daemon function will be active or not. There are severals ways to do it, a dialog window with a checkbox for instance. Below is Pascal code for a simple configuration function (this one only shows a message box).

/Rolf

 

function configure (var m:TMInterface; name, parameter: pChar):shortint;export;cdecl;
begin
  messagebox(MainW, pChar('Parameter is '+parameter), name, MB_OK);
  Result:=1;
end;

I'm not quite sure what your setup is, but 'localhost' at least has a meaning - a fictional 'domain.com' only works if you have your own DNS server or you alter all the host files.

Perhaps if you explain what it is you are trying to achieve and how many computers are involved, then someone may be able to assist.

I have finally had time to look at POPFile version 1.0.0. The current version of the POPFile Daemon for Mercury (POPFileD 1.22.4) works fine with POPFile 1.0.0.

The only caveat is that after installing (or updating or reinstalling) POPFile, you *must* reinstall POPFileD again.

I also made a minor tweak in the installation instructions, so I would recommend downloading a new copy of the Daemon at the usual place:

http://users.adelphia.net/~homedale/popfiled

I'd appreciate hearing if anyone is using POPFileD. Send your "postcards" to popfiled [at] markmatrix.com