Am 08.09.2012 10:01, schrieb Ralf Hildebrandt:
> When sending lots of mails (mass mailings) via many machines, one
> quickly realizes that the current concept of smtp_fallback_relay is
> a bit problematic:
>
> * The mass mailing gets (randomly) distributed to n machines
> * these n machines try sending out the mails assigned to them and will
> encounter mechanisms like postscreen or greylisting mechnisms
> * thus the initial delivery fails
> * the mail gets passed to the smtp_fallback_relay
>
> I wonder if a time based smtp_fallback_relay ("pass the mail to the
> smtp_fallback_relay after a certain period of time has expired") or
> using the smtp_fallback_relay after a certain number of delivery
> attempts (>=1) would be a worthwile addition to Postfix.
>
> Something like
>
> smtp_fallback_relay_delivery_threshold = 1
>
> would be backwards compatible to the current behaviour, while allowing
> the admin to specify
>
> smtp_fallback_relay_delivery_threshold = 2
>
> or even
>
> fallback_transport_maps _relay_delivery_threshold = 3
>
> which would allow a machine to "defeat" greylisting, while still using
> smtp_fallback_relay for the "tough cookies".
>
> Thoughts?
>
Hi Ralf,
yes if cascade postfix servers
for deliver out i.e mass mail via
smtp_fallback_relay parameter , there should be some parameters
to honor i.e greylisting etc at recipient mailservers
i wonder it isnt allready possible.......
no alternate way with extra master.cf entries or tranport setups etc
possible yet to configure to goal this ?
i speculate about setup in master.cf with transport
for special recipient domain
and using some parameter change with transport
like some of them here
http://www.postfix.org/postconf.5.html#transport_destination_concurrency_failed_cohort_limit
and perhaps fallback_transport_maps ?
anyway it would be more easy with
configurable smtp_fallback_relay parameters
more thoughts anybody?
--
Best Regards
MfG Robert Schetterer
