Postfix 3.0.3 TCP interface Panic error condition

Hi Folks, I have compiled postfix 3.0.3. Using the ldap interface for the following maps everything works as designed. However, if I use theTCP interface, I am getting a panic error condition. Config eg virtual_alias_maps = tcp:removed-host-name-here:9871 virtual_mailbox_domains = tcp:removed-

Postfix RCPT TO parameters

Hi All, I have been looking at postfix 2.11.1 code base. It appears SMFIR_ADDRCPT_PAR is for the milter to add new recipient with parameters to the current message. I need my milter to receive the RCPT TO parameters. Does postfix provide support for passing these arguments to the milter? Char

Re: Drop connection based on Enhanced Error Code

Noel Jones wrote: On 2/23/2015 10:33 AM, Charles Orth wrote: Hi All, At this time, we're relying on extended error code 5.2.1 to drop the connection. I suppose you're referring to the 521 reply code. We'd like to a more robust set of extended error codes (RFC5

Drop connection based on Enhanced Error Code

Hi All, At this time, we're relying on extended error code 5.2.1 to drop the connection. We'd like to a more robust set of extended error codes (RFC5248) which also drop the connection. Has there been any discussion on Postfix providing a new feature where we can configure specific extended s

Re: maximal_queue_lifetime not honored

s for you help. Viktor Dukhovni wrote: On Mon, Feb 02, 2015 at 10:19:24AM -0500, Charles Orth wrote: bounce_queue_lifetime = 4h Well, you said that you expect a 30 minute lifetime, but clearly you should have expected at least four hours. Can you explain why you need a dedicated queue

Re: maximal_queue_lifetime not honored

bounce_queue_lifetime = 4h Viktor Dukhovni wrote: On Thu, Jan 29, 2015 at 06:25:28PM -0500, Charles Orth wrote: maximal_queue_lifetime = 30m And bounce_queue_lifetime is?

maximal_queue_lifetime not honored

We are seeing some issues with our bounce complex. This complex only handles bounces so if we can't deliver them, they are typically discarded. We are expecting mail to be removed after 30 minutes but we're queuing on the complex where some mails messages are around for 10+ hours. I am curious

Redirect all DSN messages to a secondary host

Hi, I would like to redirect all DSN messages to the same bounce complex. In the case where the recipient's endpoint is SMTP (author's endpoint is LMTP) and the recipient address does not accept the mail from this author (or recip address doesn't exist), the bounce message is redirected as co

milter extension for recipient DSN

Hi, Has there been any thoughts on support for passing recipient DSN information to milter protocol (eg rcpt_dsn macro)? Charles