Transport Connection Limiting

Hello, Wonder if someone can point me in the right direction. We hold transport routes for loads of destinations and sometimes encounter an issue if one particular domain/route suddenly gets a hugh influx of mail. Say for instance one particular domain gets 10,000 emails, it could be ages before

mail server on vm

Hi all I have configured postfix on centos virtual machine it works fine but I can't add virtual domain to postfix it always refuse receiving via this domain Postconf -n output alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases broken_sasl_auth_clients = yes command_director

Re: mail server on vm

Amira Othman: > and the error I have is Recipient address rejected: User unknown in virtual > mailbox table;(when receiving ) The recipient DOMAIN matches virtual_mailbox_domains, but the recipient ADDRESS does not match virtual_mailbox_maps (or virtual_alias_maps). See: http://www.postfix.org/A

Re: Transport Connection Limiting

Dan S: > Hello, > > Wonder if someone can point me in the right direction. > > We hold transport routes for loads of destinations and sometimes encounter > an issue if one particular domain/route suddenly gets a hugh influx of mail. > > Say for instance one particular domain gets 10,000 emails,

Re: using header_checks to change message-id header

On Tue, Aug 16, 2011 at 2:35 AM, Ralf Hildebrandt wrote: > * Peter Blair : >> /Message-Id:\s+<(.*?)@my.domain.com>/   REPLACE Message-Id: >> <$1...@my.domain.net> > > Warning: this might also alter Resent-Message-Id: into Message-Id:!!! -1s/might/will/ Cheers! :)

Re: using header_checks to change message-id header

Thanks all for the help. I decided instead to just replace all instances of my internal domain using the following on my gateway server: /^(.*?)internal\.domain\.com(.*?)/ REPLACE ${1}pretend_name.domain.com${2} This is because it wasn't modifying the Resent-Message-Id headers. And on my in

Re: Using negative feedback to control sites returning "too many connects" warnings.

Can you confirm my understanding of the following settings. initial_destination_concurrency = 5 default_destination_concurrency_limit = 20 default_destination_concurrency_positive_feedback = 1/2 default_destination_concurrency_negative_feedback = 1 default_destination_concurrency_failed_cohort_li

Re: Using negative feedback to control sites returning "too many connects" warnings.

Donovan Bray: > Can you confirm my understanding of the following settings. No. You don't solve problems by playing with scheduler feedback. The entire concept of feedback is largely bogus, as shown by the measurements in SCHEDULER_README.html. Wietse > initial_destination_concurrency