Afficher un message
Vieux 01/02/2007, 20h13   #8
Grant Taylor
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Mail Delivery Subsystem messages --> /dev/null

Alex Moen wrote:
> Well, the files are all q (lower case), and of course, d (lower case). No
> upper case Q's are in the directory.


....

> No instances of panic or save in the log files (grep -iw panic
> /var/log/maillog ; grep -iw save /var/log/maillog) other than those that are
> contained in domain names or e-mail addresses.


Ok, this makes me think that the files are not from abandoned / orphaned
messages.

> This would be a great , and actually would probably solve the problem.
> Is there an example somewhere that explains how to do this? And, what is
> the reason that this is not the default behavior?


Put the following in your mc file and rebuild your cf.

define(`confDOUBLE_BOUNCE_ADDRESS', `address@domain.tld')

Update `address@domain.tld' respectively.

Configure what ever email address you use to then route any messages
that come in to it to /dev/null.

> I think milters are great, but as I explained before we had a very nasty
> experience with them in the past and are very concerned with the outcome of
> that experience, especially the fact that no one could explain why the
> milter or Solaris 8 did what it did. We definitely do not want to go
> through that again, as it was very detrimental to the company and disruptive
> to our customers. We may try them again when we upgrade our server to
> Solaris 9 or 10 on new hardware, but not on 8.


*nod* I would consider that a bit over cautious, but caution is not
necessarily a bad thing. If / when you do try milters again on what
ever platform and / or OS you know some symptoms to look for before they
get out of hand.



Grant. . . .

  Réponse avec citation
 
Page generated in 0,05106 seconds with 9 queries