This is an interesting behavior, to put it mildly. How am I supposed

to notify my users to please log off now? How about in the middle of the

night, when the server does a reboot? Many connections will be still

active, but no user will be active to close them.

Will this be fixed in the next release?

Not sure what to tell you.  These functions are only completed when the client completes the transaction by closing the connection.  If the connection is broken then the EXPUNGING mail that the person using the connection expects to be able to recover might be worse than than leaving the mail undeleted.  This is especially true when the loss of mail is usually considered a greater problem than not deleting mail.  In addition, many mail clients, including t-bird can send a manual expunge under user control after they do a delete to confirm the deletion without closing the connection.

We had similar perfomance problems with initial authentication while 802.1-Authentication was activated in the client but not supported by our Netware-Servers.

Greetings

Olaf

Mercury can serve multiple domains, you just need to point an MX record to it (by creating a new A record in that domain connected to your public IP, or by using mail.cruizers.biz). In local domains you should then simply add  "mail --> domain2.com"  and, if you created a new A record,  "mail --> mail.domain2.com".

Mailboxes in Mercury aren't domain specific, so mail for dennis@domain1.com will be delivered to the same mailbox as mail for dennis@domain2.com. It can be separated by using domain specific aliases, though.

As Mercury itself doesn't separate between domains there is no administrative interface to access users for just one domain. There is a daemon that provides a web interface for a number of administrative tasks, though (newest version: http://downloads.serieguide.se/webtools.zip). It's possible to create an administrative layer on top of Mercury to handle domains separately, but it's a rather extensive undertaking. There are plans to include other ways to handle multiple domains in the next major version of Mercury.

/Rolf 

For people that might have tried starting Mercury as a service without a license... That's not going to work. Buy a license if you want it to run Mercury as a service.

: "Licenses are required for commercial use of Mercury/32, and will modify the program's status bar to reflect the licensed status of the server when installed. You will also need a license if you wish to run Mercury as a Windows Service." 

Right, less obvious username/password combinations will probably help! ;)

/Rolf

There is more information about the licensing terms for Mercury here:  

Geez! Well that was so painfully obvious for me to hear! *face palm*... Was just on the way out the door for work and didn't have time to scout around the application looking.

Thanks for that!

So to summarize, PMail was set to delete immediately, which worked, but deleting after 1 week using Mac Mail didn't work as the "Offer only unread mail" option won't allow that. Unchecking "Offer only unread mail" will make it possible to have POP3 clients delete messages after a specified time.

/Rolf

Thanks - That took care of the relay but had to surrender the mail services back to the original server as the ip is black listed and we are getting hit by something that I can't describe here.  I am going to look deeper and start a new post

THanks to everyone -

Bob

I COULD KISS YOU!!!!

It's been days - with this struggle.  And now I see light.

thanks

Michele

> Actually it's not all that difficult to send a deffered  message, you

send yourself a message

> and then just copy the raw text into the new

message with the added Remail header and send it to maiser.

You're perfectly right, but I hope you will agree that this could be quite uncomfortable if you have to do it more than a few times in a row :-)

> That said, if this is really a critical task then you might want to switch to PMail since it does this automatically.  ;-)

I do use Pmail (since 1994, actually...) but I seem to recall the remail extension only worked in a LAN set up, ie when Pmail is allowed to put messages directly into Mercury's queue. Am I wrong?

Thanks again and regards,

  Corrado

It worked. Thanks a lot Rolf.

hmm - good point. We're using IMAP actually, not POP3, maybe that's the reason?

I'll do a test with POP3 as well.

I doubt if this will make any difference at all since I was reading my 130 character subject sent with Thunderbird  3 through Mercury to GMail and a local account using Webmail,  POP3 and IMAP4. 

I did do a test with sending a line greater that 127 character Subject with PMail (v4.53 beta 2) and it appears that PMail will truncate the subject to 127 characters when building the actual message.  I get this using both the internal mailer and Mercury UDG.  I did not try this with any of the release versions of PMail.

Below is a MercuryS session log.  The last time doesn't look right.

19:10:12.671: Connection from 74.71.55.217, Fri Aug 20 19:10:12 2010<lf>
19:10:12.671: << 220 lucky.syr.edu ESMTP server ready.<cr><lf>
19:10:12.718: >> EHLO ZZ<cr><lf>
19:10:12.718: << 250-lucky.syr.edu Hello ZZ; ESMTPs are:<cr><lf>250-TIME<cr><lf>
19:10:12.718: << 250-SIZE 0<cr><lf>
19:10:12.718: << 250 HELP<cr><lf>
19:10:12.968: >> STARTTLS<cr><lf>
19:10:12.968: << 502 STARTTLS not enabled by administrator.<cr><lf>
19:10:12.015: --- Connection closed normally at Fri Aug 20 19:10:12 2010. ---

The offline problem is probably due to a bug in MercuryX. Disable that module unless you actually need to use it. If you use it please install this patch:

/Rolf 

For understanding this correct, with literal addresses meant "username@192.168.0.1".

Not exactly, the literal addressing is username@[192.168.0.1] Here's the section of RFC 532, the standard for handling server to server transactions.

4.1.3.  Address Literals

   Sometimes a host is not known to the domain name system and
   communication (and, in particular, communication to report and repair
   the error) is blocked.  To bypass this barrier, a special literal
   form of the address is allowed as an alternative to a domain name.
   For IPv4 addresses, this form uses four small decimal integers
   separated by dots and enclosed by brackets such as [123.255.37.2],
   which indicates an (IPv4) Internet Address in sequence-of-octets
   form.  For IPv6 and other forms of addressing that might eventually
   be standardized, the form consists of a standardized "tag" that
   identifies the address syntax, a colon, and the address itself, in a
   format specified as part of the relevant standards (i.e., RFC 4291
   [8] for IPv6).

   Specifically:

   IPv4-address-literal  = Snum 3("."  Snum)

   IPv6-address-literal  = "IPv6:" IPv6-addr

   General-address-literal  = Standardized-tag ":" 1*dcontent

   Standardized-tag  = Ldh-str
                     ; Standardized-tag MUST be specified in a
                     ; Standards-Track RFC and registered with IANA

   dcontent       = %d33-90 / ; Printable US-ASCII
                  %d94-126 ; excl. "[", "\", "]"

   Snum           = 1*3DIGIT
                  ; representing a decimal integer
                  ; value in the range 0 through 255

   IPv6-addr      = IPv6-full / IPv6-comp / IPv6v4-full / IPv6v4-comp

   IPv6-hex       = 1*4HEXDIG

   IPv6-full      = IPv6-hex 7(":" IPv6-hex)

   IPv6-comp      = [IPv6-hex *5(":" IPv6-hex)] "::"
                  [IPv6-hex *5(":" IPv6-hex)]
                  ; The "::" represents at least 2 16-bit groups of
                  ; zeros.  No more than 6 groups in addition to the
                  ; "::" may be present.

   IPv6v4-full    = IPv6-hex 5(":" IPv6-hex) ":" IPv4-address-literal

   IPv6v4-comp    = [IPv6-hex *3(":" IPv6-hex)] "::"
                  [IPv6-hex *3(":" IPv6-hex) ":"]
                  IPv4-address-literal
                  ; The "::" represents at least 2 16-bit groups of
                  ; zeros.  No more than 4 groups in addition to the
                  ; "::" and IPv4-address-literal may be present.

If they want not setup the server accepting literal addresses, which tools available to forwarding mails this way?

There are none.  You can remove this domain from your local domain if you are not receiving mail via MercuryS and then Mercury core would resend the mail off the server using MercuryE to the other server.

Having a reverse DNS (PTR) record for the website as well sounds like a good idea anyway. If you want to use only one NIC for mail ports it should be possible to do so using TCP/IP filtering, but it might be some work to get it right.

/Rolf 

Mercury filtering can only move messages into new mail folders, so you could move them to a different user, but not to another folder within a mailbox.

Several users have requested more functionality related to IMAP filtering just like you want, but I don't know when that will appear.

 Thanks for your encouraging reply.

 I am trying to implement this first in a virtual environment  and then will shift to a physical system.

When installing mercury, its asking for pmail, so that mercury can 'impersonate' /send message on user's behalf - this is what I understood.  I think, that part will be of interest.

I will update my findings here.

 Thanks again.

So..... Am I right in thinking that if a connection to the smtp server uses smtpauth then its ip address does not need to appear in the Connection Control list? Or are the 2 comments above mentioning authentication suggesting that having an all encompassing range is ok so long as smtpauth is required for relaying?

Correct, the use of ESMTP AUTH is the normal way that is used to block the spammers from relaying off your server while allowing remote users to relay.