Re: Sending mail to custom transport and second server
- Original Message - From: Jeroen Geilman jer...@adaptr.nl To: postfix-users@postfix.org Sent: Tuesday, 5 June, 2012 7:51:47 PM Subject: Re: Sending mail to custom transport and second server recipient_bcc_maps = hash:/etc/postfix/backup_domains, with the following content: @example.netcatch...@second.postfix.box Depending on your specific setup, there may be much better solutions, but this is what you asked for verbatim. I'll look into it when I'm back at work tomorrow. However, I'm all for better solutions. The way Postfix receives and delivers is basically made clear; it receives because example.net is mydestination, so it considers it to be local, and then it delivers using the zarafa transport. Any alternatives for setting up a machine that acts as real-time backup are welcome.
Re: turn off mailer daemon returns
On Jun 5, 2012, at 16:04, Wael MANAI wrote: MM4 parameter X-Mms-Transaction-ID First, read up: http://www.google.com/search?q=top+posting Then have another look at the documentation; http://www.postfix.org/postconf.5.html#internal_mail_filter_classes http://www.postfix.org/postconf.5.html#header_checks http://www.postfix.org/header_checks.5.html With 'internal_mail_filter_classes = bounce' and the header_checks, you might be able to redirect your message, feed it to whatever software generates the 'X-Mms-Transaction-ID' for you, and then reinsert it for delivery. If the transaction ID is the same for all messages it might even be as easy as using a 'PREPEND' or 'REPLACE'. Cya, Jona -- Le lundi 04 juin 2012 à 13:51 +0200, DTNX Postmaster a écrit : On Jun 4, 2012, at 10:31, Wael MANAI wrote: I read the links and tried some configuration modifications with soft_bounce and internal_mail_filter_classes parameters but the notification is still sent to sender. I need to intercept this message in order to modify one parameter value before sending it. Which parameter value are you trying to modify? Cya, Jona
Re: [OT] frequent TRY_AGAINs and 10s timeouts, but *only* with b.barracudacentral.org
On Sun, 2012-06-03 at 00:03:06 +0100, Ned Slider wrote: On 02/06/12 17:44, Sahil Tandon wrote: ... I've separately engaged our DNS admins in case they could offer some insight, but it would be interesting to learn if others are experiencing the same issue /only/ with barracuda. I see similar in my bind logs on a server running SpamAssassin. The barracuda RBL is queried by default in SpamAssassin so I suspect the volume of queries they receive is pretty high. I assume it's a load issue at their end. I've been seeing such entries in my logs for months but it does seen to have got worse since around April of this year. ... Thanks to you and everyone else who replied on and off-list. I'll try to get someone's attention at barracuda. -- Sahil Tandon
Disable outbound smtp pipelining?
It seems we are running into an increased number of hosts that have broken smtp pipelining. We are able to resolve delivery issues to these hosts using the solution that Wieste recommended a couple weeks ago: http://www.mail-archive.com/postfix-users@postfix.org/msg44135.html However, I'm not sure I fully understand why this fixes the problem for outbound email. On outbound email, Postfix is acting as the client and therefore one might think that smtpd_discard_ehlo_keyword_address_maps would not have any affect, since this setting is supposed to suppress EHLO keywords in response to a client. Does smtpd_discard_ehlo_keyword_address_maps also ignore EHLO keyword responses it receives on outbound connections? I'm guessing so, because unless something else changed, the solution worked. In fact, the above mentioned thread that Wieste is responding to was also an outbound delivery issue, and so it seems he might be implying that smtpd_discard_ehlo_keyword_address_maps has an effect on outbound connections as well. Ok, so assuming this solution works for outbound connections, this solution would require that we create and maintain a list of perhaps thousands of servers that have this problem. Does anyone have any experience with just turning it off completely for all hosts? Which, I suppose would be done like this: smtpd_discard_ehlo_keywords = pipelining,silent-discard Aside from a little extra bandwidth, would this cause outbound deliveries to go horrendously slower on a busy mail server? And is there a way to only disable smtp pipelining for outbound connections only? I better stop asking questions now since I might be getting ahead of my self if my assumption about smtpd_discard_ehlo_keyword_address_maps does not actually apply to outbound email... Thanks, Curtis
