Hmm.  Access to the list at UA may be needed to follow this up - try the listowner with specific message times.  I know they stepped up their anti-spam protection a while back, but maybe this is a problem.

[quote user="PaulW"]

[quote user="Jean-François Berne"]Is it possible to allow weak identification for some IPs ? I can't find this in the 'Connection Control' tab of MercuryS config.[/quote]

If it is a fixed IP address on your LAN, you can put it in Connection Control and allow it to relay (if that's what you want).  No authentication applies then - assuming you don't have the bottom box ticked (Only authenticated connections may relay), and you could turn it off in the camera.

How do your other workstations on the lan send mail - by authentication or IP address allowed?

[/quote]

Answers:

• I HAD checked the box 'only authenticated SMTP connections may relay', which means that ...
  
• ... others workstations on LAN (and on WAN) sent authentification;
• camera had/has fixed IP

So I read again the help with your remarks in mind and actually solved the pb:

• uncheked  'only authenticated may relay', but with...
  
• ...strict local relaying
• just the camera's IP in allowed connections list
• kept weak auth. disabled
  

Now, all mail clients still must authenticate themselves with strong auth. - as they always did. Only the cam may relay without auth. at all, which is precisely what I needed.

Thank YOU !

JF 

[quote user="PaulW"]

I like Martin's rssmail - available in this site or at along with all his other Mercury / PMail utilities.

[/quote]

The last time I looked at RSSMail that was HTML-only.  Checking again I see that there is support for downloading enclosures using wget, which is quite nice if you use them (I don't yet).  (RSS2Email supports rendering enclosures but it doesn't autofetch.)

[quote user="PaulW"]

What advantages would rss2email give me - I couldn't find a feature set on the website?
[/quote]

The feature list is on the home page, but that's not enough.  You'd have to try it.  For me it's the way it generates plain text mails that work everywhere, my cell phone, my textmode readers, etc., and that it just does its job very well.  Supports ATOM too, uses SMTP and can mail each feed to one or more addresses, and loads of other stuff that just come from scripted tools like superb encoding support, nice wrapping of text, awesome formatting, multipart MIME, recognition of every tag there is, etc, etc.  It makes David Harris' postings to his blog very suitable for remailing to mailing lists, sets the headers according to publication and authorship, and just generally makes handling RSS actually fun.

[quote user="PaulW"]

Also, the link is bad - extra '/' at end.

[/quote]

Confounded IE, displays the bad link as visited even though it obviously isn't.  I swore I typed it in right ...

http://rss2email.infogami.com/

Cheers,

Sabahattin

Thanks
Anyway to sort this ?

I need to ensure the subject is changed before the email is sent out..

You should be able to solve that part by using Attributes / Originates from a non-local source / Move message to another user (instead of Always triggers).

/Rolf 

Thanks I try this over the next day or two and see how it goes.

An event daemon can access message headers and reject the message based on any criteria while still handled by MercuryS.

/Rolf 

[quote user="Peter Strömblad"]I've checked dessergroup2.demon.co.uk and it's not a valid domain[/quote]

It's a sub-domain.

[quote]The domain demon.co.uk also yields a number of warnings[/quote]

They look like minor issues even with your tools.  Certainly nothing that Mercury should stumble over.

Ah, that's true - at present Mercury only supports TLS when using MercuryC (SMTP relay module) for delivery, not MercuryE. Sorry for mixing it up.

/Rolf 

Great! 

Here is some information about the forum: h 

Please post additional questions about that to Feedback on this website.

/Rolf 

Thanks.

Anyone know of a quick daemon that will do this ?

I sort of agree with that, but I feel I should point out that it's not SpamHalter that's writing the console message, it's Mercury core. And Mercury core is only aware that a job in the queue was deleted by a daemon, it doesn't know the reason. 

/Rolf 

Certainly.

I'm submitting 5000 messages in rapid succession using a Java application which uses the javax.mail API.

The messages are small.... less than 1kb.

 I can send and receive low volumes no problem.

Not sure what the temp directory is.... where do I find this in the config? I'm running with the install defaults btw and running the latest  version 4.62.

 Anti-virus.... good thought! Yes, I do have real-time scanning going on. I've excluded the mercury directory and will test again tomorrow.

 Thanks

Under the Pop3 server config, make sure "Offer only unread mail to connected clients" is unticked.

This is really the only Mercury setting that effects this process, it is up to the client which messages to request.

"Mark retrieved mail as read" may or may not have an effect, you will have to experiment.

Depends on your smarthost. Some allow other domain names, some require them to be set up and 'allowed' first (gmail), some will refuse altogether.

MY ISP's mail server has gone off line, if I'm using port 110 it just reports a network error and carries on. If as I was doing, using port 995 and direct ssl it crashes mercury.

 It happens in 4.61 and 4.62, mercury crashes & hogs all the resources.

Error dump available if you need it.

Thanks

Mailing list activity is not shown clearly in the console logs so this could very well be normal. If your list is internal you will not see anything there. If you have MercuryE running and your lists are VERP enabled, you should see activity there for each message flowing out of your system.

As Rolf pointed out, you should upgrade from 4.5x to 4.62 as there are many fixes between the versions.

No.  The problem here is Mercury's forwarding mechanism.  For some obscure reason, it uses the resend strategy to forward mail from the forward file's author to the destination.  For precisely the reasons observed by the problem poster, this is the *wrong thing to do*.  Forwarding should preserve the return path of the sender and introduce an identical message (no modifications other than trace fields) into the queue, changing the recipient to the destination address.  The theory is that, while it is certainly the forward file's author who can do something about any errors, he is as likely to be unable to receive any pertinent error message forwarded to him as to receive the problem message.  For all practical purposes, he does not fall into the delivery path: the person for whom status notices are intended *is* the cause of the status notices, unlike a mailing list, where it makes perfect sense to take responsibility at another address mid-delivery.  It is therefore important that the sender be notified.  The local site configuration problem that resulted in the error condition can't be forwarded reliably, so it must be deposited in a physical mailbox or sent to Postmaster where no forwarding should be occurring or, if it is, it should be to a safe destination.  (Errors are sent with null sender, so there are no further loops if this problem report doesn't reach the Postmaster.)

Cheers,

Sabahattin

You need to use the regular expression option to match against a wildcard. So to catch any file attachment, click "Only check the name portion", put * in the textbox and check "This string is a regular expression".

/Rolf 

You need to put:

server: [192.168.1.10]

in the Local Domains section of Core config

Also you dont need the smtp client module for delivery to local users.