absolute message TTL is 14 days ?

it seems any message has a maximum time where it can stay in any queue :

snoopy # > ./imsimta cache -view

channel : ims-ms

file name : /mail/messaging/msg-snoopy/imta/queue/ims ms/019/ZY0H570020BLZVD0.00

subdirectory : 19

enqueue time : 7-Nov-2002 15:09:32.00

last delivery attempt : 7-Nov-2002 15:09:32.00

processing priority : 1

destination system : ims-ms

recipient count : 1

message size : 3529 (kbytes)

owner : mailserv

expiration date : 21-Nov-2002 15:09:32.00

this would mean the message will be rejected when it's expiration time has come, ignoring the fact that it maybe should stay any longer due to some overquota retention policy.

I have put a retention time of 30 days for any message if it can't be delivered to an overquota user. When the message is spooled to an overquota user, i effectively receive some notification mail saying that it will try for another 28 days, then one week later, another mail saying it will try for another 21 days.

However, after 14 days, the mail gets rejected, with a message "manually aborted by postmaster"

i suspect this comes from this "expiration date". (it's too much a coincidence)

The question is : where can i change this expiration date (which seems to be set when the mail is enqueued for the first time) to reflect my retention policy of 30 days ?

Thanks

[1448 byte] By [709035] at [2007-11-25 8:29:41]
# 1

The 28 days seem to be written in your "ims-ms" channel definition in the imta.cnf. The TTL depends on the "notices" keyword. Whatever value you set there should be the TTL in days. Don't know why the message bounces after 14 day. Maybe you should set a policy of 30 days in your "defaults" channel definition and remove the one from "ims-ms"?

Just a thought.

Joerg

joerg gastner at 2007-7-1 14:58:08 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...