Pegasus Mail & Mercury

Bounces are expected to have <> as sender (to avoid mail loops) and it might not be a good idea to block them. You might for instance get a bounce of an (important) message actually sent by a local user. You could how ever try using a global filtering rule to move all bounce messages to a special mailbox that you can check periodically:

Headers: Reply-to

Contains this text:  <>

Move message to another user

Parameter: bounces

GrayWall won't help with bounces as they are sent by real mail servers (that will retry), it only delays it a bit.

/Rolf
 

If you get SpamHalter properly trained and optionally use GrayWall you will get rid of most of the spam from user mailboxes. Blocking countries by IP address may be possible but I would advise against it.

/Rolf 

Also, how do you set the filter to reject messages with nothing in the FROM field? I tried to put one in with a blank, but it does not seem to be working.

There are two things here.  One is a MAIL FROM: <> and the other is the missing or blank From: field in the message.  

1.    The MAIL FROM: <> is mail from a mail server IAW RFC 2821 and you do not want to block these.  You especially do not want to reject them since that will get you on black lists as a non-compliant server that MUST accept mail from this address.

2.    The missing or blank From: field is a different story.  You can block this if you wish since every RFC 2822 message MUST have a From: field.  You should be able to gin up a filter looking for "  " in the From: field and do with it as yuo will. 

 

---

Thomas R. Stephenson
San Jose, California
Member of Pegasus Mail Support Team

Well, all seems to be quieting down on their Mercury. I think they will be dealing with spam rejections from other servers for a day or two, but they can handle that. I do appreciate all your help. If it chokes again, I will be back!