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.
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.
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
For all the frustration that these delays bring both you as the program and us as the end users... You software has always been well worth the wait!!! I think I can hold out a little longer ;-)
Well, try nil, and if that doesn't work either in your programming environment check if there is an alignment problem in the daemon (I believe Mercury expects byte aligned data).
Maybe a basic filter rule for 'failure' in the subject and MOVE to admin or a temp user for review?
Keeps them out of the users boxes.
You just have to ride it out, it will stop eventually.
PS
"..and no relaying at all."
If you have outgoing mail you are relaying. Any mail accepted by your server addressed to a non-local domain must be relayed to the server that handles that domain. [:)]
I assume you mean that you do not relay mail from non-local sources. [:)]
We don't use synonyms in our installation so I have no experience of this. This is what the manual says about it, though:
If you have created synonyms on your system using the Pegasus Mail PMGRANT utility, you will need to use the CH_SYN.EXE utility supplied with Mercury to build a synonym database for Mercury, and enter the name and location of that file here. (note that if running in NDS mode, you will use the NDS-aware synonym builder NSYNONYM.EXE instead).
1. Open the Configuration / Protocol modules dialog in Mercury.
2. Uncheck MercuryE
3. Check MercuryC
4. Click OK and restart Mercury.
5. Open the Configuration / MercuryC SMTP client dialog and fill in the name of your ISP's SMTP server as well as username and password (according to the information you have received from your ISP). It might be a good idea to enter a name for a general log file as well. Increase the value for TCP/IP timeout to at least 300. Leave the rest as it is for the time being.
Yes, SpamHalter processes the message before it gets to the rules, so you can create rules to handle messages tagged by SpamHalter the way you prefer. The recommended procedure is to move them to a special mailbox that you can review to make sure there are no false positives.
I have a couple of excluded addresses in an email list (status = X) (*). When I do a review of the list (via email), the excluded addresses appear as normal active subscribed addresses. (Whereas disabled addresses, and those not receiving mail, are described as such.) Bit of a shock to see apparently signed up!
Is there something wrong with my installation or is it always like this?
(*) yes, I know, probably not overly useful seeing as they could sign up with new addresses
My ISP has made it tough to send e-mails if the sender's e-mail address isn't the one registered with them. I run a mailing list and would like to continue doing so, the problem of course is that I can't register all the senders' e-mail addresses at my ISP. When an e-mail arrives from the list the FROM is: Mail Server @ me.com on behalf of but the internal From address is just sender@otherISP.com. I would like to change it so that the FROM address is mailserver@me.com and the reply-to is sender@otherISP.com
Is that something that's doable?
Thanks, Eric
PS: I've written daemons for Mercury in the past and wouldn't mind doing it that way...