[quote user="Bidul63"]

Hello,

I have a Mercury Transport System (V 1.48) for Novell NetWare.

Is it possible to modify the SMTP port to 26 (default value is 25) ? How I can do this, what are the modification to do in Mercury.ini ?

Not possible, the port 25 is fixed in the program.  You can change the port on Mercury/32 though and you can use Mercury/32 as a front-end to Mercury.

 Thank for your answer.

 Bidul63.

Thank you ver much!

Konrad

Hi,

The message come from outside network.

I have now tick 3 checkboxes :

* Do not permit SMTP relaying of nonlocal email

* Use Strict Relaying instructions (see help)

* Authenticated SMTP connections may relay mail

 Hope this will work.

Thanks for the advise.

If you telnet to MercuryI you'll find what commands are supported. Have to check - sounds very interesting.

Is there some firewall running on the server that might block SMTP, POP3 or IMAP connections? Try using Telnet to connect to port 25 and 110 to see what happens.

/Rolf 

It worked.

I created a htl-maiser Pegasus Mail account on both servers, edited the mercury.ini file on the HTL server so that it contained:

[Maiser]

Maiser:          HTL-Maiser   # 'Username' of mail server account

Helpfile:        C:\MERCURY\Mercury\MAISER.HLP   # Help sent on failed maiser requests

Lookupfile:      C:\MERCURY\Mercury\MAISER.LKP   # Format file for the 'lookup' command

Send_dir:        C:\MERCURY\Mercury\SENDABLE   # Directory for the 'send' command

Logfile:         C:\MERCURY\Logs\Maiser\~y-~m-~d.LOG   # Mail server log file

Notify:          C:\MERCURY\Mercury\TMP   # Dir. for pending 'notify' commands

NoList:          N   # If 'Y', disable the 'list' command

Local_only:      Y   # If 'Y', local 'notify' commands only

and replaced every instance of 'maiser' with 'htl-maiser' in the *.mer files in the root of the Mercury installation folder.

All mail for these lists is now accepted by the APS server. The HTL server polls the pop3 box and collects the mail for htl-maiser, and all introductory emails sent to subscribers after they ahve successfully joined a list contain the correct htl-maiser@heritagelincs.org address.

Hoorah!

They are just text files, open a couple with notepad (or better) and have a look.

If MercS is listening on your internet interface it could well be spam.

[quote user="Joerg"][quote user="Thomas R. Stephenson"]

Again not sure what this means.  If this is the MAIL FROM: address of the sending server can't you just change this to match a valid email address on your system? 

[/quote]

Here my summary again.

The managing card of the server is a DELL DRAC5 card. This card creates its own e-mail sender address ( DRAC5@[192.168.21.244] )when sending notification e-mails. This sender address is not adjustable. I'm only able to set an address of a recipient, a message text and a SMTP server IP address.

Now I have adjusted Mercury S to receive those "non-local" e-mails from the server. Mercury S hands over them to the Mercury Relay Client which tries to dispatch them to the ISP SMTP server. But this will be rejected  by the ISP because of non-registered domain ([192.168.21.244]). That's clear.

 Is it rejecting the From: address or the MAIL FROM: address?    

Now I'm searching for an opportunity to change the "non-local" address of the DRAC5 card to a already registered address (at the ISP) when processing in Mercury. May be I could solve it in the same way like the "translation" of e-mail addresses for our users. For example: My nmae is Joerg Mueller, my Pegasus login name is "jm". This normally causes to a sender address like jm@domain.com. But our registered ISP addresses read j.mueller@domain.com. Now I have created a synonym.mer file where all local user addresses will be translated to the official ISP addresses. This works properly.

Personally I change the MERCURY UDG via pconfig.exe from

 *Reply address format :  "~p" <~L~L~8@host.domain>

to

*Reply address format :  "~p" <~r>

and the users "Reply To:" address is used in place of the ~r.  This allows the users to have multiple identities with different From: addresses.

May be I could solve my DRAC5 problem in a similar manner?

Not really since this is a forward and it's going to be using the original From: address in the forwarding.   If you are not allowed to  change the it then you might have to send to a local address and then pull via IMAP4/POP3 from the outside world.  You might also talk to your ISP and explain the problem to them and ask them how to handle this.

One more thing.  Do you have a fixed IP address?  Does the ISP block port 25?  If the answers are Yes and NO then try using MercuryE and bypass the ISPs rules. 

regards

Joerg

Thanks.

The guy who was doing the web page tried it out last friday - I gave him the full MLSS address with the custom port number and it worked a treat.

Excellent, I was able to find and correct the function in phpbb, thanks for the help.

At least try the new version out. If the added functionality can help you in various ways you may find that the license fee is well spent. [:)]

/Rolf 

Can I just move the mailboxes somehow to another server and still have Mercury32 know how to use them?

No you cannot.  The user new mail directory must be on the Netware server.  Now the users can of course change the location of the home mail directory separately and there is a tool available with WinPMail PB1 (mbxmaint.exe)  to make this a lot easier.  You can run this tool in the batch mode as well.

thnx for helping me, it was a firewall, thnx again

No, you can't assign rights to a mailbox to a group of users. You could create a separate mailbox and give all users in the group the password, of course, but then you would need to change the password if someone is removed from the group to be sure to prevent access. Another solution would be to copy all messages for the group to the individual mailboxes of the group members. This can be done using a list or by creating an alias connected to a rule.

/Rolf

This is another way of solving the same thing:

Hello David,

I currently have the mercury.exe setup as a service.  I'll change it to use the loader and keep an eye on it.

Thanks,

Ed

Thank you - at least I can stop looking.

Definitely upgrade to the latest, 4.62

Hi

 this happen two/three times per day and always same address 0X0001008b

Assuming that gmx.de is the domain that this server is supposed to handle mail for you need to check the Local domains section in Mercury core configuration. Have a look at the help text to see how to do it.

If gmx.de is not your domain you are acting as an open relay, which is very bad. In that case go to MercuryS configuration, Connection control to correct it. Having the first two checkboxes checked (strict restrictions) is a good start; more information about the options are in Mercury help or the manual.

As for the error message, "555 5.5.2 Syntax error. j2sm5603868mue.4" doesn't look like a message from Mercury. Switch on session logging for the module in question to see what actually happens. (Remember to switch it off again, though.)

/Rolf