For now a good setup is all I need to have. For my programming I shouldn't need to know the internals of Mercury. A simple PHP-script should be enough to handle the mail when the configuration is right.
The problem is getting the SMTP host setup correctly is critical. The PHP part is a no brainer, you are simply sending a message via SMTP to port 25 of MercuryS. You can turn on session logging in MercuryS to see if it's properly received.
The problem is 99.99% of the time you do not have a fixed IP address and you cannot send mail using MercuryE since it will be bounced or simply deleted as spam by the receiving system. You need to setup MercuryC to do the sending.
If you would search on XAMPP in this forum you will see many many answers describing the problem and the process.
Time I don't have at the moment since I have to deliver the result of the final-asignment for my PHP course soon.
It's not really our job to tell you how to do your course work. ;-)
I am pretty sure this was a false alarm as although the server was down, no one seems to have sent any messages when this was the case, so I do not think that the lack of such messages in our archive account is surprising.
For some reason your client programs get out of sync with the server and mix up messages. This is most likely to happen if Mercury is restarted while the IMAP client is connected. If it happens in other circumstances check all the usual problem sources (disk errors, heavy fragmentation, other processes such as anti-virus programs interfering with Mercury's file access) on both client and server systems.
Note that in cases like this no data has been mixed up on the server, the mix up is in the client.
If mailboxes are only accessed via IMAP you could try switching on lingering mailboxes in Mercury core configuration / Files / Foldering subsystem settings and see if that makes any difference.
Mercury will simply use the available network resources, there are no bandwidth throttling settings. If you use MercuryE to deliver messages you can set the number of simultaneous deliveries in the configuration for that module, though.
Other than that I believe that certain firewalls and routers may allow you to limit the bandwidth used for individual protocols. To increase speed it's usually the Internet connection you should review, common connection methods like ADSL has rather limited speed for outgoing traffic.
Any one have any hints on how to configure NT Wrapper ?
Here's my mercury.ini Config file for NT Wrapper. You can put this into the NT Wrapper directory and then modify it to match your setup. Probably will have to delete a lot of the ENV_ lines or at least change them to match your systems environment.
I have tried updating to the latest version of Popfile, that does not seem to have made any different, emails with larger attachments of about 3 MB or bigger still come through as short messages from unknown if I run BOTH popfile and spamhalter.
I wondered if the order that Spamhalter and Popfile are defined in the ini file makes any difference or if I need to change the default ports for Popfile, but putting Popfile first instead of last does not seem to help either.
Currently I have spamhalter turned off and we are delivering spam, tagged as such, to our end users so if anyone has any other suggestions I would love to try them.
Im using Mercury mail server with java. I have configured the delivery receipt and read receipt with separate mail address in my java program for mercury server.
When i run the program, the delivery receipt is sent to recipient address and not to the email address given for delivery receipt. With read receipt im able to send to the email address configured to read receipt, but im also getting a copy of the mail in recipient email address.
When I inspected the delivery confirmation template files of mercury server, by default it has recipient email address[~T]. ~T is the substitution for recipient address template files.
Actually it should be able to get the address given in header of java program.Like this
Can anyone guide me how to override this to address in sucess delivery template with my own dynamic email address or how to override the same using java program?
i just want to ask if there is any settings i can make, that Mercury sends out with myaddress@provider.com because i cant use postmaster@localhost.
My domain provider don't provides free addresses.
I can only send mails out with my own mail address.
please tell me how i can change "postmaster" into myaddress or if ther is any other way to get this work?
The postmaster address is made up by adding the name you provided in Configuration | Mercury core | Internet name for this system, i.e. postmaster@<Internet name for this system> When sending mail Mercury/32 will only use the postmaster address when send mail like error messages unless you set the From: address in the message to the postmaster address.
I assume you are sending your mail using a SMTP mail client sending mail to MercuryS that is processed by Mercury core and then sent out using either MercuryE or MercuryC. If so turn on session logging in MercuryS to verify the From: address in the message you are sending.
Thanks for your help. I'm going to try to create the .mlf files with a script, first I have to understand its content.
# Mercury List Membership File for list 'hidden@novelltstephenson.com' # Mercury Mail Transport System, Copyright David Harris, 1993-2003 # # This file contains mailing list subscriber records in tab-delimited # format. Provided you are careful, you can edit it using a text editor # but you must make sure that the editor actually inserts TAB characters # when you press the TAB key. # # The fields within each subscriber record appear in this order: # # Status Single character in [A,N,D,V,X] # Address RFC822-reduced e-mail address # Name RFC822 Ctext/Qtext component for name # Flags 16 printable ASCII characters # Postings Postings since inception (8-digit, 0-padded) # SubsDate Subscription date, YYMMDDHHMMSS # SubmDate Last submission date # VacDate Vacation date # Password Password for user # Comment # # The first line in the file must remain exactly as it appears above, but # all the remaining comments in this block can be deleted if you wish. # The record format is not tolerant of errors. Dates must be exactly # 12 characters in length, using 0-padding as required. White space is # significant and preserved in all cases. The last line of this file must # always end with a CR/LF. # # We recommend that you use the Mercury user interface to maintain this # file unless you are very sure of what you 're doing.
Again, James Haley's BuildMLF makes this a lot easier.
Aliases should be used for providing additional names for an account, and is a one-to-one link. If you need wildcards to catch multiple addresses you should probably use a global rule with an expression.
Most of us are broke these days, so well done for making the effort. Here in the UK, there's a supermarket brand whose tagline is "every little helps" which I'm sure David Harris would go along with right now.