This is fixed in current versions of Mercury, so please upgrade. The removed attachment will be replaced with at text like this:

   Filename:            Test.zip 

The rule may remove MIME parts you want to keep as well, so you may need to check that there is a filename (a regular expression looking for "?*" will do it).

/Rolf 

Did you check MercuryS logs for connection attempts? It actually looks very much like there is some other program answering on port 25 on your server (assuming that you are trying to send, not receive).

/Rolf

[quote user="MartinTruckenbrodt"]what willl happen if I'm deleteing the CNM files manually?[/quote]

Well, you will get rid of the message - that is what a mail client will do in deleting an email in the mailbox. So long as you don't have the mailbox open using another client I don't think it will cause a problem.

This is not an error message from Mercury but from the receiving SMTP server.

There are two ways to change how messages are sent to list members. In Distribution you can have Mercury create up to 20 separate jobs for delivery ("fanout"), in Error handling you can select VERP-based to have separate delivery for each member. From Mercury help:

"VERP-based error handling   VERP stands for "Variable Envelope Return-path Processing": when using this method, every recipient in the list gets a separate copy of every message sent to the list, and in that copy of the message, a special version of the Return-path field is created that allows Mercury to work out the individual list and subscriber from any errors that get returned to it."

/Rolf 

Hello Chris,

thank you very much for the answer!

I've done a Outgoing & Always trigger rule. I've selected the action 'Copy message to another user' and put in the name of the user.

Bye Martin

Hello,

problem sloved.

I've been looking still add the core modules configuration. Now I've been looking at the MercuryS SMTP Server configuration.

Bye Martin

Disable MercuryX unless you actually use it. If you use it you will need to download this patch:

http://community.pmail.com/files/folders/patches/entry24194.aspx

/Rolf 

The From header is normally set by the program that creates the message, in this case Pegasus Mail, so that's where you should look for the sender address. If you can't find it, please post to the Pegasus Community Support forum about it.

/Rolf 

OK, I´ll tray to do it next week.

Thanks. 

Hello all,

This was posted on the old mail list, but I think that list is little frequented, so am x-posting
here in the hopes that I can get this sorted quickly. Thanks in advance for any help.

I thought I would narrow down one of the issues that I am having with Mercury to make it hopefully a bit less to wade through.

I am a listmum on a group and need, from time to time, to send out emails from the email address
that is received by all listmums.This email is forwarded to each of our main email accounts, and I
am able to receive them, at this point, with no problems. Obviously I cannot poll that email
account, as the mail is forwarded to me.

I have listed the domain in the various configurations in my list of domains in the mercury.ini file. I am using Pegasus Mail.
iistudio: prodig.org
iistudio: prodig
iistudio: mail.prodig.org

I have an identity set up for this purpose and need that email address to be the 'from' address as well
as the 'reply to' address. I have also set it  to auto cc emails sent from that address to the listmoms@prodig.org email,
so all listmums are aware of any issues I am dealing with on my 'watch'.

I am not, however, able to send emails through Mercury using the sender's address as this listmum
address (listmoms(at)prodig.org). I need that to be the 'from' address as well as the 'reply to'
address. I have it set to auto cc emails sent from that address to the listmoms(at)prodig.org email,
so all listmums are aware of any issues I am dealing with on my 'watch'.

 Currently I am getting the following 4 error messages for each mail, when I send from that email
address as Mercury is refusing to process them. It says:

  --- Problems not related to specific addresses in the message:
   Job has invalid or illegal from address.
 *** listmoms(at)prodig.org

 *** "Ellie Kennard - duty Prodig Listmum" <listmoms(at)prodig.org>
   User "Ellie Kennard - duty Prodig Listmum" <listmoms(at)pr not known at this site.

--- Problems not related to specific addresses in the message:
   Job has invalid or illegal from address.
   *** Ellie(at)iistudio.com

  *** "Ellie Kennard - duty Prodig Listmum" <listmoms(at)prodig.org>
   User "Ellie Kennard - duty Prodig Listmum" <listmoms(at)pr not known at this site.

The strange thing is that Ellie(at)iistudio.com is a valid address on the system and one that I use regularly with no
difficulty.

How can I make this work, does anyone have any ideas? I do not have a fixed ip address (ISP only allows them for
business accounts which cost a fortune) but seem to have no difficulties in sending (now) from
a gmail address. I used to be able to do this with no problems but have made several changes to the
Mercury.ini file (under direction from Thomas Stephenson etc., who is,I think, away) and now am unable to make
this work.


Cheers!

Ellie

Fortunately this is just a test account with nothing important in it and will be deleted when everything works.  This was the only session that occurred when I logged into Sugar.  This confirms my suspicions that the problem is Sugar.

Thanks

>  Thank you, I can made it work now, and Happy New Year.

How was the problem solved?

If Verizon won't allow you to use port 25 for incoming or outgoing traffic I'm afraid it's game over. You will need to use their SMTP server for Internet communication. You can use Mercury (with MercuryC instead of MercuryE for deliveries, and using MercuryD to collect messages) in your local network if you like, though.

For sake of clearness I'll still comment on the various details. 

DNS: The error messages from Windows Live Mail indicate that you probably haven't succeeded to create the new A record (mailserver.mydomain.com). There should be just one MX record for the domain, and it should refer to mailserver.mydomain.com (not @).

[General]

myname:          mailserver.mydomain.com    <--  better with just the domain here in most cases (mydomain.com)

[Protocols]  <--- disable modules that you don't actually use (if you use MercuryX be sure to get the patch)

[MercuryS]
Strict_Relay : 0    <--- strict relaying control is recommended if MercuryS is communicating with the Internet

Alt_Server_Port : 25   <---- this can be 587

Interface : mailserver.mydomain.com    <--- in several places, will break functionality altogether, write # at the beginning of the line to comment it out

Session_logging : C:\xampp\MercuryMail\ESSIONS\MERCURYS   <--- missing S in path, it seems

[Domains]                             <--- check Mercury help for this
localhost: localhost                <--- seriously, is that the name of your server?
localhost: [127.0.0.1]             <--- [192.168.1.7] and public IP should be here

mydomain.com: mailserver.mydomain.com        <--- unless you use Netware the first part is always whatever you choose to call your server

[MercuryB]   <--- unexpected port selections, but I guess it would work

/Rolf 

I'm a new user and I'm having some problem setting up mercury/32.

At first, I set up mercury/32 on localhost with apache, php, etc and everything was fine, emails were able to be send successfully

But after I uninstalled everything (including mercury) and install WAMP+mercury back on the machine, mercury won't send mails anymore! It always got stuck in pending state. I can send emails directly from the mercury interface but mercury won't send emails generated by PHP

What seems to be the problem?

EDIT: Nevermind, turned out I set up the wrong postmaster

Well it's very strange, their server doesn't always communicate normally...

The sender only provided this one line of their log:

xxxxxx@xxxxx.com... Deferred: 403 4.7.0 TLS handshake failed.

Our own Mercury logs vary, usually the connection starts fine with an EHLO followed by STARTTLS followed by the usual DATA and stuff.  However, their server almost never (but sometimes does) sends a QUIT so almost all connections end up taking 35+ seconds to timeout before the mail is delivered.

As far as I can tell, the STARTTLS almost always gets logged as successful.

To be honest, I kind of suspect the sender is trying to make up excuses for a problem he doesn't understand and that he found a single log of TLS failing and hoped I might buy it.  It's hard to say though, because when he enabled SSLv2 on his end (he says he did) the mails seem to be getting delivered now.  I'm just not sure what to think.

That's the step before the core log entry. What we want to see now is what happened after that, when the message was processed by the module handling outgoing messages (MercuryE or MercuryC). Check configuration for the module for the path to the log file.

/Rolf 

I could really use the LDAP Synonyms listed under Configuration -> Network Support.

I don't use Pegasus Mail as my primary mail client but would greatly benefit from using LDAP lookups for valid email addresses. My Mercury/32 server is set up as an in and outbound relay for various servers and systems and is not my message store.

Is there any way to configure Mercury/32 to perform those LDAP lookups?

Happy Holidays to all

Thank you for the fast and precise reply.

grebbi

>>  So, if I needed to change the location of the Pegasus Mail submission queue could I simply enter the new path to the mail

>> submission (queue) directory (in UNC format) then hit "update configuration" instead of configuring it via PCONFIG?

> Yes, if you did not use identities or did not care that the From: address would always be the same for a user.  I make a number of changes to my UDG so I never use the functions in Mercury to > > modify the UDG.

At the moment I don't have an entry in the Configuration|Pegasus Mail field for the path to the Pegasus Mail executables so the path showing in the outgoing queue field is incorrect.  It is a shame that there isn't a way to enter the path to the executables and have the field for the outgoing queue be updated automatically from PMGATE.SYS.  I certainly don't want to risk updating the configuration just to get these fields to reflect valid paths but it sure mislead me for a few moments when they didn't.  A suggestion to David to fix this perhaps?

> BTW Brian, notice how much easier it is to follow a thread in the PMail mailing lists.  ;-)  I really hate this stupid editor!

AGREED!!!!  The only reason I post here is for maybe some additional perspective from the folks who are active here but aren't active on the list.  It sure is tedious communicating here though.  Of course, communicating with a handheld wireless device is tedious to me.  Is my age showing? <G>

There is no exception list in MercuryS blacklist handling. If you want to be able to take additional aspects into consideration you should change the blacklist definition to tag the message (add a header) instead of rejecting it, and then select the appropriate action using global filtering rules or a daemon.

/Rolf