Re: Huge active queue and system idle, not delivering

Le 08/01/2010 03:03, Wietse Venema a écrit : Patrick Chemla: But the CPU of the box is idle more than 80%. It is clear that it is not a matter of CPU, nor memory, nor disk. Something in the number of processes/users/simultaneous tasks is blocking. Indeed, the symptom of blocking i

Re: Huge active queue and system idle, not delivering

Le 08/01/2010 00:43, Victor Duchovni a écrit : On Fri, Jan 08, 2010 at 12:30:34AM +0200, Patrick Chemla wrote: Jan 7 22:02:57 postfix postfix/qmgr[26441]: 5B91F873F6: removed Jan 7 22:02:57 postfix postfix/smtp[27180]: 375DDD5923: to=, relay=a139.localpc2105.com[10.0.0.139]:25, conn_use=5

Re: Confusing sasl configuration examples

On Thu, Jan 7, 2010 at 5:14 PM, mouss wrote: > ... > To allow relay, you need to configure smtpd_recipient_restrictions. By > default, this contains >        permit_mynetworks >        reject_unauth_destination > so if you don't change it, only "mynetworks" can relay. so you need to > add permit_s

Re: Huge active queue and system idle, not delivering

Patrick Chemla: [ Charset ISO-8859-1 unsupported, converting... ] > Le 08/01/2010 00:43, Victor Duchovni a ?crit : > > On Fri, Jan 08, 2010 at 12:30:34AM +0200, Patrick Chemla wrote: > > > > > >> Jan 7 22:02:57 postfix postfix/qmgr[26441]: 5B91F873F6: removed > >> Jan 7 22:02:57 postfix postf

Re: Huge active queue and system idle, not delivering

On Fri, 08 Jan 2010 15:24:25 +0200, Patrick Chemla > When I telnet a70.localpc2105.com 25 I get an immediate response. I assume you are telnet'ing from the Postfix server with the queue delay problem. At this point, after you receive the 220, type: ehlo your.postfix-server.tld and time the d

Re: Confusing sasl configuration examples

On Fri, Jan 08, 2010 at 08:37:16AM -0500, Shaun T. Erickson wrote: > Yes, this is what is shown in the SASL Howto and how I have had > my server's submission port configured in the past. > > However, in the 2.6.2 postfix distribution I'm trying to configure > now, the default definition of the su

Re: Confusing sasl configuration examples

/dev/rob0: > On Fri, Jan 08, 2010 at 08:37:16AM -0500, Shaun T. Erickson wrote: > > Yes, this is what is shown in the SASL Howto and how I have had > > my server's submission port configured in the past. > > > > However, in the 2.6.2 postfix distribution I'm trying to configure > > now, the defau

maildrop transport, why using ${nexthop} instead of ${domain}

Hi. Just for my understanding http://www.postfix.org/MAILDROP_README.html#direct uses "-d ${us...@${nexthop}". Why is nexthop used instead of domain? And when would these two be different? Thanks, Philippe.

Re: maildrop transport, why using ${nexthop} instead of ${domain}

Philippe Cerfon: > Hi. > > Just for my understanding > http://www.postfix.org/MAILDROP_README.html#direct uses "-d > ${us...@${nexthop}". > Why is nexthop used instead of domain? And when would these two be different? Like Rome, Postfix was not built in one day. Unfortunately these is no wa

Re: Huge active queue and system idle, not delivering

Wietse Venema: > Patrick Chemla: > > Le 08/01/2010 00:43, Victor Duchovni a ?crit : > > > On Fri, Jan 08, 2010 at 12:30:34AM +0200, Patrick Chemla wrote: > > > > > > > > >> Jan 7 22:02:57 postfix postfix/qmgr[26441]: 5B91F873F6: removed > > >> Jan 7 22:02:57 postfix postfix/smtp[27180]: 375DD

question about smtp_connection_cache

Hi folks I have a Centos 5.3 Box running postfix 2.6.3 . I use an smarthost in a per user authentication basis. I meant every local user has a passwrod to use against the smarthost. My question is, in this conditions is it possible to take advantage of smtp_connection_cache so all the queued me

Re: question about smtp_connection_cache

Davy Leon: > Hi folks > > I have a Centos 5.3 Box running postfix 2.6.3 . > I use an smarthost in a per user authentication basis. I meant every local > user has a passwrod to use against the smarthost. > My question is, in this conditions is it possible to take advantage of > smtp_connection_ca

Re: Huge active queue and system idle, not delivering

On Fri, Jan 08, 2010 at 03:24:25PM +0200, Patrick Chemla wrote: > When I do telnet a139.localpc2105.com 25, I get immediate response. What does "response" mean? Immediate connection completion means nothing. Do you get a 220 banner right away? Do you get all of it or just the first line in a mul

Re: Confusing sasl configuration examples

On Fri, Jan 08, 2010 at 10:23:38AM -0500, Wietse Venema wrote: > /dev/rob0: > > On Fri, Jan 08, 2010 at 08:37:16AM -0500, Shaun T. Erickson wrote: > > > Yes, this is what is shown in the SASL Howto and how I have had > > > my server's submission port configured in the past. > > > > > > However, in

Re: Confusing sasl configuration examples

/dev/rob0: > On Fri, Jan 08, 2010 at 10:23:38AM -0500, Wietse Venema wrote: > > /dev/rob0: > > > On Fri, Jan 08, 2010 at 08:37:16AM -0500, Shaun T. Erickson wrote: > > > > Yes, this is what is shown in the SASL Howto and how I have had > > > > my server's submission port configured in the past. > >

Virtual reject reason

Hello, I'm pretty new to Postfix, and I'm experimenting with using it for our new inbound MTA. Is it possible to customize the following error message? MAIL FROM: 250 2.1.0 Ok RCPT TO: 550 5.1.1 : Recipient address rejected: virtualdomain.com In this sanitized example, "virtualdomain.com" is

Re: Virtual reject reason

Christopher Hackman: > Hello, > > I'm pretty new to Postfix, and I'm experimenting with using it for our new > inbound MTA. Is it possible to customize the following error message? > > MAIL FROM: > 250 2.1.0 Ok > RCPT TO: > 550 5.1.1 : Recipient address rejected: > virtualdomain.com Depending

Tie a mail with log files?

Just I wanted to know if there is currently a good way to tie messages with log files? I mean, to see that ID (like 8BA216E7D7) into some mail header or similar... Perhaps add it with maildrop -A? signature.asc Description: This is a digitally signed message part.

Re: Tie a mail with log files?

On 1/8/2010 2:14 PM, Kārlis Repsons wrote: Just I wanted to know if there is currently a good way to tie messages with log files? I mean, to see that ID (like 8BA216E7D7) into some mail header or similar... Perhaps add it with maildrop -A? The QUEUEID is logged in the Received: header. This wi

Re: Tie a mail with log files?

Kārlis Repsons a écrit : > Just I wanted to know if there is currently a good way to tie messages with > log files? I mean, to see that ID (like 8BA216E7D7) into some mail header or > similar... No. the queue id is not in the delivered message. note that the queue id is not unique. > Perhaps a

Re: Tie a mail with log files?

mouss a écrit : > Kārlis Repsons a écrit : >> Just I wanted to know if there is currently a good way to tie messages with >> log files? I mean, to see that ID (like 8BA216E7D7) into some mail header or >> similar... > > No. the queue id is not in the delivered message. argh. of course, the que

Re: Tie a mail with log files?

On 1/8/2010 2:21 PM, mouss wrote: Kārlis Repsons a écrit : Just I wanted to know if there is currently a good way to tie messages with log files? I mean, to see that ID (like 8BA216E7D7) into some mail header or similar... No. the queue id is not in the delivered message. Sure it is. Receive

Re: question about smtp_connection_cache

Thanks Wietse. Very usefull your answer. I was making a huge mistake. Thanks - Original Message - From: "Wietse Venema" To: "Postfix users" Sent: Friday, January 08, 2010 11:35 AM Subject: Re: question about smtp_connection_cache Davy Leon: Hi folks I have a Centos 5.3 Box runni

Re: Tie a mail with log files?

On Friday 08 January 2010 20:27:09 Noel Jones wrote: > Well, you can always look up the Message-ID: header, which is > logged by qmgr, and find the QUEUEID that way. Thanks! Was quite the same thing I waned. That uniqueness is not crucial right now... signature.asc Description: This is a digita

Re: Confusing sasl configuration examples

Shaun T. Erickson a écrit : > On Thu, Jan 7, 2010 at 5:14 PM, mouss wrote: >> ... >> To allow relay, you need to configure smtpd_recipient_restrictions. By >> default, this contains >>permit_mynetworks >>reject_unauth_destination >> so if you don't change it, only "mynetworks" can

Re: Confusing sasl configuration examples

/dev/rob0 a écrit : > On Fri, Jan 08, 2010 at 10:23:38AM -0500, Wietse Venema wrote: >> /dev/rob0: >>> On Fri, Jan 08, 2010 at 08:37:16AM -0500, Shaun T. Erickson wrote: Yes, this is what is shown in the SASL Howto and how I have had my server's submission port configured in the past. >>>

Re: forward problem: mail delivered twice

nik600 a écrit : > On Mon, Jan 4, 2010 at 11:26 PM, mouss wrote: >> nik600 a écrit : >>> On Mon, Jan 4, 2010 at 12:52 PM, nik600 wrote: Dear all i've installed a postfix server with mysql support. i've also set-up a custom filter script shell that calls spamc and som

Re: question about smtp_connection_cache

Davy Leon: > Thanks Wietse. Very usefull your answer. I was making a huge mistake. Thanks If you have multiple SASL accounts with the same provider, then you may want to set "smtp_connection_cache_on_demand = no". At some point someone may add code that labels the connection cache with the SASL

Re: maildrop transport, why using ${nexthop} instead of ${domain}

On Fri, Jan 8, 2010 at 4:40 PM, Wietse Venema wrote: > Like Rome, Postfix was not built in one day. > > Unfortunately these is no way to AUTOMATICALLY find all the pieces > of documentation that need to be updated when a new feature (such > as ${domain}) is introduced. Ah so they're the same? Coul

Re: maildrop transport, why using ${nexthop} instead of ${domain}

Philippe Cerfon: > On Fri, Jan 8, 2010 at 4:40 PM, Wietse Venema wrote: > > Like Rome, Postfix was not built in one day. > > > > Unfortunately these is no way to AUTOMATICALLY find all the pieces > > of documentation that need to be updated when a new feature (such > > as ${domain}) is introduced.