Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-13 23:57 UTC

Threads

Browse threads

Page 20 of 25 · 1201 threads matched

Greylist exiting

Started 2005-09-19 by leighklotz

1 messages 0 attachments Last activity 2005-09-19

Statistics Script?

Started 2005-09-01 by Michael Wallendahl

2 messages 0 attachments Last activity 2005-09-08

AFK for a few days

Started 2005-08-22 by manu@netbsd.org

2 messages 0 attachments Last activity 2005-08-22

milter-greylist crash

Started 2005-07-29 by cruiskeenconsulting

5 messages 0 attachments Last activity 2005-08-01

acl whitelist domain

Started 2005-07-11 by Theresa Klarr

2 messages 0 attachments Last activity 2005-07-11

greylisting reliablity?

Started 2005-07-06 by Nils-Henner Krueger

2 messages 0 attachments Last activity 2005-07-06

enhanced greylist.db?

Started 2005-07-03 by fredrik.pettai@vattenfall.com

3 messages 0 attachments Last activity 2005-07-04

Feedback on 2.0rc5

Started 2005-06-18 by manu@netbsd.org

6 messages 0 attachments Last activity 2005-06-20

reload config and die

Started 2005-06-15 by Steve Ladendorf

3 messages 0 attachments Last activity 2005-06-16

mx-syncing

Started 2005-06-08 by Fredrik Nyberg DC

8 messages 0 attachments Last activity 2005-06-10

GL Problems

Started 2005-05-31 by MW Mike Weiner (5028)

2 messages 0 attachments Last activity 2005-05-31

configuration options

Started 2005-05-25 by Martin Paul

2 messages 0 attachments Last activity 2005-05-25

install annoyance

Started 2005-05-24 by Steven Stern

2 messages 0 attachments Last activity 2005-05-25

Greylist as opt-in

Started 2005-05-20 by Steven Stern

12 messages 0 attachments Last activity 2005-05-22

Solaris man pages

Started 2005-05-03 by manu@netbsd.org

3 messages 0 attachments Last activity 2005-05-03

Less logging?

Started 2005-04-21 by Thomas Cameron

3 messages 0 attachments Last activity 2005-04-21

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.