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.
> Hi, there, I installed the free version of Mercury 32 that came with > Xampp (a suite of free tools for building an apache/php server). I'm > going to be testing/developing a web application (drupal) on my local > machine). Drupal requires that the server have smtp (for password > authentication, etc). In fact, you can't even install Drupal locally > unless you have an SMTP server running. Hence, my reason for Mercury > 32.
Ok,
> I am pretty clueless about what exactly I need to do. Can someone > point me to the steps? When I open the Mercury 32 control Panel, I see > windows for SMTP server and SMTP client (and IMAP server, etc). > Success would probably mean that I can send a message which would be > sent through Mercury to an outside web address (gmail, etc). If I > choose File --> Send email message, I get a email send window, with > postmaster@localhost as my sending address. I try a test message to > the outside; no success. (I even checked gmail's spam filter).
What you really need to do is verify the setup, XAMPP does not do a very good job of setting up Mercury by default.
1. MercuryS is used to receive the mail from an outside source and you need to turn on session logging to see if the mail is being received from Drupal.
2. Next, XAMPP sets up MercuryE as the outbound client by default. Any port 25 blocking will cause a failure. If you do not have a fixed IP address then most major servers will reject your connection as spam. You need to convert to MercuryC to relay through your ISP's SMTP host to send the mail.
> > I am on Vista. Do I need to create an exception on the Windows Firewall. Which port? Is that the only problem?
MercuryE and MercuryC both use port 25 for outbound mail. MercuryS uses port 25 inbound but since it's only receiving a local connection from Drupal this should not be affected by the firewall.
> Do I need to create a local user name for SMTP?
Yes, there must be a postmaster local account.
> > Is File --> Send email message the best mechanism for verifying that a > message has gone through? What about doing smtp on the command line?
I do telnet to the host to verify. Here's a sample session. The ones with 250 and 354 are from the server, the others I typed in.
Start | Run telnet svl78zxa97.lmms.lmco.com 25
You will see something like the following. The ones with the numbers are from the server, the others I typed in.
<< 220 ESVCS.lmms.lmco.com Mercury/32 v3.01 SMTP/ESMTP server ready. >> EHLO SVL78ZXA97 << 250-ESVCS.lmms.lmco.com Hello SVL78ZXA97; ESMTPs are: << 250-TIME << 250-SIZE 5000000 << 250-8BITMIME << 250-AUTH CRAM-MD5 << 250 HELP >> MAIL FROM:<support@stephens.sj.scruznet.com> SIZE=517 << 250 Sender and size (517) OK - send RCPTs. >> RCPT TO:<support@stephens.sj.scruznet.com> << 250 Recipient OK - send RCPT or DATA. >> DATA << 354 OK, send data, end with CRLF.CRLF >> From: "Thomas R. Stephenson" <support@stephens.sj.scruznet.com> >> To: support@stephens.sj.scruznet.com >> Date: Wed, 2 Feb 2000 11:35:28 -0800 >> Subject: Test #4 >> >> Mail body >> . << 250 Data received OK. >> QUIT
> (Unfortunately, the Mercury local online help is in hlp format and > incompatible with Vista. (I tried downloading the hlp reader for Vista > from MS, with no success).
As a courtesy to our users (in a K-12 educational environment) I have had postmaster errors enabled. This, in turn, automatically generates delivery failure notifications to senders... all is good - right?
Wrong in today's environment. You should be using the reject at MercuryS to ensure that only the sending server gets the ejections. If you receive and then bounce you are bouncing to what could very easily be a forged address contained in the RFC 2822 message body.
Well... all was good - I occasionally check things here using mxtoolbox.com (most helpful, BTW) and today I find that I am listed with backscatter.org :-(...
Not that big a deal since this blacklist has a huge false positive rate that there are very few users.
From what I gather, having the delivery failure errors enabled is probably what has me listed. I like having the failures give the end user some idea as to the error(s) of their way(s) but don't know how I can keep these failure notifications from being delivered off campus.
Correct, the mail was probably accepted by some SMTP server supporting your domain and then bounced as being a non-local user creating what is called backscatter. If you are receiving via MercuryD you should never bounce the message but simply send it to the default user for handling manually.
I use Mercury/32 as a relay to a back-end server and don't really want to keep up a manual list of 300+ users (synonyms) and wonder if there is a better (or any) way of keeping the delivery failures enabled and not continue to be listed on backscatter.org?
The back-end server should never bounce mail received from Mercury/32 but send it to a postmaster account for manual processing.
[quote user="Ellie Kennard"]Is It istevenkennard.com or just stevenkellard.com ?"[/quote]
My typo.
[quote]Note the spelling of the second email where in reality you had actually written stevenkennard.com - so how could THAT have happened? Pegasus? Transmission? Mercury?[/quote]
Corrected within 20 seconds, but not before the email was sent. :(
I assume that you are getting all mail via MercuryS.
The first thing that comes to mind is that the RCPT TO: address is not the same as the From: address.
The second is that you deleted the user with Mercury/32 running and did not use the CTRL+Manage local users and/or restart Mercury so that the address was not deleted from memory.
Changing of the IP address should have no affect on this.
1- But, in my mail client I can configure if I want that mails remind x days in my ISP server, for me this option is essential because my boss sometimes works via webmail of the ISP server. I could create a clone account in the ISP server, but I would like if i can configure this via mercury mail.
2- Ok, that's ok, I will do it through my mail client.
David has reported having fixed the MercuryX problem, and we the testers will most likely receive 4.73 RC within a week with additional issues addressed.
Rolf's HttpServer now also works with Mercury running as a native service.
E 20090915 121135 a94 Error connecting to RBQITEXCHVS01.XCTC.CTC.NHS.UK.
This can be caused by a number of reasons.
1. Port 25 is being blocked by your ISP and this is not your ISPs SMTP relay host.
2. Port 25 is being blocked by your firewall.
3. Mercury/32 is being blocked by your firewall.
As a test try using Start | Run telnet tstephenson.com 25 to verify that you get the answer 220 tstephenson.com ESMTP server ready. If you do not then port 25 is being blocked. BTW I cannot connect to RBQITEXCHVS01.XCTC.CTC.NHS.UK either.