NothingI've seen will cause this to happen and I've used some really lightweight WinXP workstations to process the mail.  For a number of years I user a 64K P90 XP Home to service the mail using POPFileD without any problems at all.

Well, I installed ClamWall instead of F-Prot. It's working smoothely so far - promising!

Cheers!

I change the pop3 client config for our users :

Now in local account field I enter the external email address (user1@company.com)

 Everything seems to be OK

Thank you for the ideas,

The main reason for the server side filter would be the PDA and SmartPhone users that only want to check their spam-folders when they are in office.

I think using reg-ex for building the mail adresses would be a little complicated (because of the firstname.lastname combinations)

Claudius

This is probably due to one of the odd anti-spam technique used by the receiving domain that requires a rDNS for your static IP address, though ineffective, it is still implemented by mail admins in many places.

You will need to ensure that your ip resolves to a valid DNS name  eg. mail.yourdomain.com or at least someserver.yourisp.com and not Non-existent domain when you do a nslookup.

The other possibility is that your range of IPs are within dynamic ip address pool known to ISPs and they may ban mails coming from it. In such instance, you can only send it through your ISP or contact the domain's hostmaster directly.

Thanks for your reply, David.

I confess I am not sure it happened the way I describe, but it was the only thing that made sense to me at the time.  I will investigate the whitelisted senders and see if I can figure out where it all went wrong.

[quote user="MartinB"]

Any way to block emails that are dated incorrectly ?? 

eg:

if date is earlier that 1st Jan 2008 the drop ??
I get lots of spam with dates going back years...
 [/quote]

Not at the SMTP level. You can use the Content Control and some rule like:

IF NOT HEADER "Date" MATCHES "* 2008 *" WEIGHT 100 TAG "Probably faked Date header"

but actually I wouldn't recommend it. It will probably also hit on mails without a date header, which is a RFC violation but unfortunately often the case with commercial newsletters and such. Besides, you have to remind the rule if all of a sudden at the beginning of 2009 all incoming mail is treated as spam.

Best regards,

Nico

I've not been able to recreate this.

As soon as it happens, I'll post details.

David - any plans with IMAP filtering ?? 

I still haven't solved my problem, but I've managed a workaround.

 I used a M/32 Policy to run NAV from the commandline without using VirProt (which doesn't appear to work).

 Regards.

Stephen.

I figured it out.  My wife's inbox is "wife". I created an alias "wife@mydomain.com", which is associated with a filter file, "wife.rul".

The filter file puts all the email in the "wife" inbox, and then selectively forwards emails to the BlackBerry:

# First save all email in the Pegasus inbox
Always Copy "wife"
# Now select which email get dropped
If header "S" contains "Daily Comics" Exit ""
If header "FE" contains "newsletters@news.com" Exit ""
# Anything else is forwarded to the BB
Always Forward "wife@blackberry.net"

When delivering email to "wife@mydomain.com", Mercury always uses the alias, so all email, including BCC goes through the alias. 

As Thomas suggested, I did use a list type filter for the list of senders that should not be forwarded.

It takes 85 seconds to establish the IMAP connection and get the status

of my folder, and another 10 seconds to apply mail filters.

Seems like a very long time.  I've got an account with 250 folders and it does not take all that long.  I've no filters running but opening takes less than ten seconds I am only getting status on the new mail folder though.  I've got folders with over 15K messages that I really do not want to be checked every time I connect.

FWIW, slow opening and closing of WinPMail can be caused by a  bad hierarch.pm file.

You may upgrade and run unlicensed for 90 days. After that it's merely a conscience question, Mercury does NOT mis-behave from day 91.

To your issue: If you have any problems with GUI-generated local users after upgrading to 4.62 pls let us know - you should not have to reload Mercury when adding users through the GUI.

Next step is to set up mercury that it either sends all these e-mails

to our internal mailserver, or our mailserver takes the mails via pop3

protocol from mercury. When i get it done i probably will buy mercury

for our backup mail-system.

If the server can pull via POP3 from a domain mailbox then you can use that.  My Mercury NLM server on Netware does not have that capability so I push the mail using a batch file and BASIC program. I'm running the BASIC program compiled now.  All this program does is take the CNM files and add the "glue" headers and save it as a 101 file to the Mercury/32 queue.   I'm using a third party WAIT.COM program to make this happen every 5 minutes.  http://www.plop.at/en/tools.html  I've been using this for a few months now for the domain Novell-tstephenson.com and it's works quite well.

-------------------------------------------------------------------------------------------- MX.bat ---------------------------------------------------------------------------------------------------- 

ECHO OFF
:LOOP
CD c:\pmail\mail\novell
dir c:\pmail\mail\novell\*.cnm > c:\pmail\mail\novell\files.txt
REM CALL c:\qb45\qb /RUN c:\pmail\mail\novell\MX.BAS
call c:\pmail\mail\novell\mx.exe
move *.101 c:\mercury\queue
DEL c:\pmail\mail\novell\files.txt
call c:\pmail\mail\novell\wait -m 5
GOTO LOOP

 ------------------------------------------------------------------------------------------ MX.BAS ------------------------------------------------------------------------------------------------

REM MX.BAS This program was developed to send mail from a "domain" account to a different
REM server via SMTP.  It takes the CNM RFC 2822 message body, extracts the SMTP addresses
REM and then saves it as a 101 file.  The CNM import file is a directory listing
REM of the CNM files in the "domain" user account.

CLS
REM Set the path to the domain mailbox and the new domain name.
PATHSPEC$ = "c:\pmail\mail\novell\"
Domain$ = "@[192.168.1.3]"

REM Read in the CNM files
OPEN PATHSPEC$ + "files.txt" FOR INPUT AS #1
       
WHILE NOT EOF(1)
    REM Read the CNM directory listing
    LINE INPUT #1, Line$
    REM Check to see if this is a CNM file else skip it.  The CNM file is always 8.3.
    IF RIGHT$(Line$, 3) = "CNM" THEN File$ = RIGHT$(Line$, 12) ELSE GOTO SKIP
    
    REM Read the CNM file
    OPEN PATHSPEC$ + File$ FOR INPUT AS #2
       
    REM Get the MAIL FROM: and RCPT TO: addresses for the glue headers.
    REM I'm using the Sender: for the MAIL FROM: address. It may be blank
    REM for locally delivered mail but a blank MAIL FROM: works for me.
    WHILE NOT EOF(2)
        LINE INPUT #2, Line$
        IF LEFT$(Line$, 14) = "X-Envelope-To:" THEN RCPTTO$ = MID$(Line$, 16, LEN(Line$))
        IF LEFT$(Line$, 7) = "Sender:" THEN MAILFROM$ = MID$(Line$, 9, LEN(Line$))
    WEND
    REM Close the CNM file.
    CLOSE #2

    REM Change the domain name to the new domain in the RCPT TO: address.
    FOR I = 1 TO 100
        IF MID$(RCPTTO$, I, 1) = "@" THEN RCPT2$ = MID$(RCPTTO$, 1, I - 1) + Domain$
    NEXT I

    REM If the SMTP address was in brackets add the trailing bracket.
    IF LEFT$(RCPT2$, 1) = "<" THEN RCPT2$ = RCPT2$ + ">"

    REM Write the 101 file in Glue header format.
    OPEN PATHSPEC$ + File$ FOR INPUT AS #2
    OPEN PATHSPEC$ + LEFT$(File$, 8) + ".101" FOR OUTPUT AS #3
    REM Write the MAIL FROM:, RCPT TO: and blank line.
    PRINT #3, "$$ " + MAILFROM$
    PRINT #3, RCPT2$
    PRINT #3, ""
    REM Write the rest of the RFC 2822 body to the 101 file.
    WHILE NOT EOF(2)
        LINE INPUT #2, Line$
        PRINT #3, Line$
    WEND
    REM Close the CNM and 101 Files.     
    CLOSE 2
    CLOSE 3
    REM Delete the CNM file
    KILL PATHSPEC$ + File$
SKIP:
WEND
CLOSE
SYSTEM
END

[quote user="PHR"] Many thanks for your prompt reply. For me and I think for most users it is only necessary to have Mercury automatically started at boot time even when no user logs onto the server. Being myself a system developper I know the difficulties to "convert" a program to a Windows service especially when there is some interaction with the desktop. [/quote]

We have a specialized user account that logs in automatically, and thus starts Loader from the autostart section. This user account has very little user rights within the machine and the domains. Not until Mercury gets a native Windows service support will we change our approach.

Dear David,

I also got the "Noticeboard filename generation error" only after updating to mercury v4.7. Switching back to good old v4.5 and the problem seems to disappear as wel.

Some noticeboards are responding with the error. We use it as a mailarchive all in and outgoing mail is backupped so about 100 mails or more are stored on the noticeboartd-systems.

Hope it wil give you the information required to solve the issue

GreetzZZZ René Russchen

Thanks Rolf, that is working well.

The "Invoke a daemon" has not worked in the past for me.  I tried this with ModulePoll in v4.5x.  Not really tested v4.6 yet but I suspect this still does not work.  I do get this to work using the ModulePoll aliases though.

Hi! I've tried filling this directly in the "Commandline" field but it seems to be too long and it was always cut off after saving the policy; so I wrote a batch file named "nod32.bat" and saved it in the Mercury folder:

@echo off
"c:\programmi\eset\eset nod32 antivirus\ecls.exe" /base-dir="c:\programmi\eset\eset nod32 antivirus" /arch /sfx /rtp /adware /unsafe /unwanted /pattern /adv-heur /log-file=%2 %1

In the "Commandline" field: x:\mercury\nod32.bat ~X ~R

In the "Result file" field: ~R

The path is for the Italian WinXP installation and should be changed to fit other systems.
It seems to work but I'm unable to test it with an EICAR file because my provider seems to have an antivirus on its servers that simply delete the mail without me receiving any advise. My other gmail account simply doesn't allow me to send the "Infected" email.

Can someone test it please?

Thanks.

The connection errors were due to port 25 being blocked. But as you say, if you can use your ISPs SMTP server directly the case is solved.

/Rolf
 

If Pegasus was sending with file based queue submission, not SMTP, then MercuryS (SMTP server module) may not be loaded.

Add this module to Mercury. 

Make sure to set the anti-relaying controls (top two boxes ticked at minimum), or be certain there is no access from outside.