Ticket #304 (new enhancement)

Opened 4 years ago

Last modified 4 years ago

dynamic lookup for downstream MX lookup

Reported by: dmorton Owned by: dmorton
Priority: low Milestone: 1.1.0
Component: PHP scripts Version:
Severity: normal Keywords:
Cc:

Description

In cases where rescuing an email may need to go to different downstream MX's, we can do a special config case where an email's MX record is examined to find the host to deliver to, but still on the unscanned port.

Of course, the mail server has to be locked down to only accept mail from Maia...

Change History

Changed 4 years ago by dmorton

  • owner changed from rjl to dmorton

Changed 4 years ago by dmorton

  • milestone changed from 1.0.2 to 1.1.0

Changed 4 years ago by dmorton

  • priority changed from normal to low

One big issue with this - If the downstream is delayed, or down, it will

stall amavisd-maia, and then cause the message to be requeued upstream from maia, which means it will be scanned again. This could cause a horrendous backlog for maia to reprocess, cause duplicates in Maia's cache, and possibly bring a server down under load.

I'm leaning against it now; better to use a MTA transport like #392 and let a real MTA handle the delivery.

Note: See TracTickets for help on using tickets.