Automatically Drop Deffered Mail -PM to thread

[mmorse]

PM converted into thread:

haniko
Automatically Drop Deffered Mail
Dear Sir

How can I dropped email from deferred email, if destination mail not found.
Thank

Regards
Hendri

You don't want mail to be re-tried for delivery?
Keep in mind all the possible things that could be in the way of mail delivery, a net outage on your end, ISP outage, power outages, heavy traffic on either end, someone down for weekend maintenance, etc.

The mail in the deferred queue will retry for about 4 days (I believe).
(there's a number of max retries you can set with that-but by default it appears to be spaced out to 4 days.)

Define 'Automatically Drop Deffered'
Do you want to lower the number of retries?
Lower the number of days it attempts those retries?
Shorten the time that it retries? (ie every minute vs every hr etc)

You can also delete them manually via the admin console.

[haniko]

Dear Sir

I want this, if the destination mail server not found in 1 day, all
mail on deferred mail automatically deleted.
How can I do this option Sir ?
Thanks.

Regards
Hendri

[mmorse]

maximal_queue_lifetime (default: 5d) The maximal time a message is queued before it is sent back as undeliverable.
Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). The default time unit is d (days).
Specify 0 when mail delivery should be tried only once.

---
You essentially want maximal_queue_lifetime in postfix's main.conf
However, you cannot edit main.conf directly-it will overwrite on every startup. (essentially you will never get a change to apply it via a postfix refresh.)

so:

>su zimbra
and read up on maximal_queue_lifetime via:
>man 5 postconf (scroll down/search for the maximal_queue_lifetime section)
to learn how postconf works also read:
>man postconf

----
also kinda relevant to you/anyone else searching this thread later:

queue_run_delay (default: 300s) The time between deferred queue scans by the queue manager; prior to Postfix 2.4 the default value was 1000s.
This parameter should be set less than or equal to $minimal_backoff_time.
Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). The default time unit is s (seconds).

minimal_backoff_time (default: 300s) The minimal time between attempts to deliver a deferred message; prior to Postfix 2.4 the default value was 1000s.
This parameter also limits the time an unreachable destination is kept in the short-term, in-memory, destination status cache.
This parameter should be set greater than or equal to $queue_run_delay.
Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). The default time unit is s (seconds).

maximal_backoff_time (default: 4000s) The maximal time between attempts to deliver a deferred message.
This parameter should be set to a value greater than or equal to $minimal_backoff_time.
Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). The default time unit is s (seconds).

[haniko]

Dear Sir

I try using the command line

postconf -e maximal_queue_lifetime 1d

but I Found the error message

/opt/zimbra/postfix-2.2.9/sbin/postconf: fatal: missing '=' after attribute name: "maximal_queue_lifetime"

what wrong for this command

[phoenix]

Originally Posted by haniko

fatal: missing '=' after attribute name: "maximal_queue_lifetime"

It tells you in the error message, there's a missing '=' sign i.e. = 1d

[haniko]

After I write

postconf -e maximal_queue_lifetime='1d'

I run this command :

$ zmcontrol shutdown
$ zmcontrol restart
$ postconf -d

but

the parameter in main.cf not change

maximal_queue_lifetime = 5d

what wrong sir ?

[phoenix]

The format of the command is wrong: postconf -e maximal_queue_lifetime = 1d

[haniko]

what the right command line sir ?

[phoenix]

Originally Posted by haniko

what the right command line sir ?

I've already given it to you in the post above. You could always look at the postfix manual for the correct format!