On Thu, 7 Jan 2010 00:49:23 -0800, Dennis Carr
wrote:
> 1) A better way to do this, using already existing mechanisms in
> Postfix, or...
Myabe have a look at this and tweak your server as necessary:
http://www.hardwarefreak.com/postfix-adsl-relay-config.txt
--
Stan
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 is in the third field of
the Postfix "delays" lo
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=59, delay=61550, delays=17019/44435/96/0.17,
Le 07/01/2010 20:37, Victor Duchovni a écrit :
On Thu, Jan 07, 2010 at 08:29:44PM +0200, Patrick Chemla wrote:
Here the logs:
This is just the qmgr(8) warnings about a clogged queue. Other than
telling us that all the mail is going to "localpc2105.com", this
is not very useful. Where
Le 07/01/2010 23:47, Stefan Caunter a écrit :
On Thu, Jan 7, 2010 at 1:25 PM, Patrick Chemla
wrote:
said "I just found that Postfix could send 1 million emails per hour
when I send less than a half million in 24 hours", but I can't make
sense of that, sorry.
I have to inject 2 t
Shaun T. Erickson a écrit :
> In the "Postfix SASL Howto", it says:
>
> In order to allow mail relaying by authenticated remote SMTP clients:
>
> /etc/postfix/main.cf:
> smtpd_recipient_restrictions =
> ...
> ...
>
> This is how I configured my submission port in the past. In
Dennis Carr a écrit :
> I'm running postfix 2.5.5-1.1 (Debian Stable) on my desktop, which I
> use to deliver mail to the internet via my server. Under optimal
> circumstances, I'd just have an IP address assigned to the box that's
> on the public network, but I'm on a single dynamic IP assigned b
On Thu, Jan 07, 2010 at 10:54:15PM +0100, Ralf Hildebrandt wrote:
> > It could be viewed that half a million delivered in 24 hours is fine.
> > Are you signing the mail? This can help with delivery rates to the
> > large webmailer mx destinations.
>
> There are many things to consider:
>
> * DKI
* Stefan Caunter :
> It could be viewed that half a million delivered in 24 hours is fine.
> Are you signing the mail? This can help with delivery rates to the
> large webmailer mx destinations.
There are many things to consider:
* DKIM signing - which is the prerequisite for getting into feedba
On Thu, Jan 07, 2010 at 04:47:14PM -0500, Stefan Caunter wrote:
> >
> > I have to inject 2 to 4 millions emails to the postfix box in 24 hours, and
> > I expect to deliver within the same delay.
> > Actually, I can't deliver more than 500,000 per 24h hours.
>
> It could be viewed that half a mill
On Thu, Jan 7, 2010 at 1:25 PM, Patrick Chemla
wrote:
>> said "I just found that Postfix could send 1 million emails per hour
>> when I send less than a half million in 24 hours", but I can't make
>> sense of that, sorry.
>>
>
> I have to inject 2 to 4 millions emails to the postfix box in 24 hou
Hi Brad,
Thank you for a respond.
Sorry for not gave a clear description of what I'm trying to do.
Here is what I want to get:
I want to make the server acted as a final destination for emails
addressed to our domain.
Currently our server is MASQed, the main MX is hosted in hosting
company and I u
> On Thu, Jan 7, 2010 at 2:14 PM, Wietse Venema wrote:
> > Wendigo Thompson:
> >> *** ENVELOPE RECORDS /var/spool/postfix/maildrop/F423E1976D72 ***
> >> message_size: ? ? ? ? ?444129 ? ? ? ? ? ? 556 ? ? ? ? ? ? ? 1
> >> ? ? ?2 ? ? ? ? ?444129
> >> message_arrival_time: Fri Aug ?1 15:23:30 2008
> >
Oh! You believe the messages were already delivered? That is a
relief -- when I found these messages I was alarmed that my
application was missing them. That's great news, Wietse -- thanks!
On Thu, Jan 7, 2010 at 2:14 PM, Wietse Venema wrote:
> Wendigo Thompson:
>> *** ENVELOPE RECORDS /var/sp
On Thu, Jan 07, 2010 at 02:08:12PM -0600, Wendigo Thompson wrote:
> Whoooah a lot of output from dtruss (I can't even pipe it to a file)
It writes to standard error, so you incant: "dtruss ... 2>file".
> so I'm not sure what you want me to do with that. The output from
> postcat is (its a littl
Wendigo Thompson:
> *** ENVELOPE RECORDS /var/spool/postfix/maildrop/F423E1976D72 ***
> message_size: 444129 556 1
> 2 444129
> message_arrival_time: Fri Aug 1 15:23:30 2008
> create_time: Fri Aug 1 15:23:31 2008
> named_attribute: rewrite_context=
Wietse Venema:
> Victor Duchovni:
> > On Thu, Jan 07, 2010 at 01:25:01PM -0600, Wendigo Thompson wrote:
> >
> > > Woops, I meant to say: message_size_limit is zero.
> > >
> > > I went all verbose and looking at pickup logs for the specific queue
> > > ID I mentioned earlier:
> > > Jan 7 13:16:20
Process 75242 (in the mail log) was 100 lines of message-id=<> lines
from cleanup. I'm guessing it's 100 of the messages that are stuck in
my queue and looking for a few of the ID's it seems like a good guess.
Whoooah a lot of output from dtruss (I can't even pipe it to a file)
so I'm not sure wh
Victor Duchovni:
> On Thu, Jan 07, 2010 at 01:25:01PM -0600, Wendigo Thompson wrote:
>
> > Woops, I meant to say: message_size_limit is zero.
> >
> > I went all verbose and looking at pickup logs for the specific queue
> > ID I mentioned earlier:
> > Jan 7 13:16:20 se001 postfix/pickup[57270]: w
On Thu, Jan 07, 2010 at 01:25:01PM -0600, Wendigo Thompson wrote:
> Woops, I meant to say: message_size_limit is zero.
>
> I went all verbose and looking at pickup logs for the specific queue
> ID I mentioned earlier:
> Jan 7 13:16:20 se001 postfix/pickup[57270]: warning: C9EBD24E12F23:
> messag
Woops, I meant to say: message_size_limit is zero.
I went all verbose and looking at pickup logs for the specific queue
ID I mentioned earlier:
Jan 7 13:16:20 se001 postfix/pickup[57270]: warning: C9EBD24E12F23:
message has been queued for 521 days
Jan 7 13:16:20 se001 postfix/pickup[57270]: C9E
Wendigo Thompson:
> To answer Victor, message_size_limit is so.
>
> For Wietse:
>
> 1) Pickup seems enabled, from master.cf:
> pickupfifo n - n 60 1 pickup
> -o content_filter=
Does the mail logfile show records of "pickup" daemon activity?
If there is none, t
On Thu, Jan 07, 2010 at 12:59:45PM -0600, Wendigo Thompson wrote:
> To answer Victor, message_size_limit is so.
This if far from a complete sentence. What is your current message size
limit? What are the sizes of the "stuck" messages? What logging is
generated by pickup (and cleanup) when pickup
To answer Victor, message_size_limit is so.
For Wietse:
1) Pickup seems enabled, from master.cf:
pickupfifo n - n 60 1 pickup
-o content_filter=
2) The files are there via ls, so it seems OK
3) Postfix logs under the mail. syslog facility. What level should
On Thu, Jan 07, 2010 at 08:29:44PM +0200, Patrick Chemla wrote:
> Here the logs:
This is just the qmgr(8) warnings about a clogged queue. Other than
telling us that all the mail is going to "localpc2105.com", this
is not very useful. Where are the logs from smtp(8)?
What transport is "localpc210
On Thu, Jan 07, 2010 at 07:43:55PM +0200, Patrick Chemla wrote:
> CPU is more than 85% idle on my postfix I5/750 box, but the outbound queue
> is very very slow.
Throughput == Concurrency / Latency
What destination are most of the messages in the queue going to?
What is the associated tran
Le 07/01/2010 20:00, Wietse Venema a écrit :
Patrick Chemla:
Hi,
I am running Postfix 2.5.6 on a Fedora 11 Linux system on a hardware
based Intel I5/750 Quad Core, 8 Gb memory, 160Gb SSD hard disk.
Incoming messages are entering very fast (500 smtp processes declared)
and the active queue
Le 07/01/2010 20:03, Barney Desmond a écrit :
2010/1/8 Patrick Chemla
Incoming messages are entering very fast (500 smtp processes declared) and
the active queue is actually of 2 millions messages waiting for delivery.
here is my main.cf file:
That's some very thorough information, y
In the "Postfix SASL Howto", it says:
In order to allow mail relaying by authenticated remote SMTP clients:
/etc/postfix/main.cf:
smtpd_recipient_restrictions =
...
...
This is how I configured my submission port in the past. In building
my new server, I see that the submissi
2010/1/8 Patrick Chemla
> Incoming messages are entering very fast (500 smtp processes declared) and
> the active queue is actually of 2 millions messages waiting for delivery.
>
> here is my main.cf file:
That's some very thorough information, you've provided plenty of
context and clear descrip
Patrick Chemla:
> Hi,
>
> I am running Postfix 2.5.6 on a Fedora 11 Linux system on a hardware
> based Intel I5/750 Quad Core, 8 Gb memory, 160Gb SSD hard disk.
>
> Incoming messages are entering very fast (500 smtp processes declared)
> and the active queue is actually of 2 millions messages
Hi,
I am running Postfix 2.5.6 on a Fedora 11 Linux system on a hardware
based Intel I5/750 Quad Core, 8 Gb memory, 160Gb SSD hard disk.
Incoming messages are entering very fast (500 smtp processes declared)
and the active queue is actually of 2 millions messages waiting for
delivery.
The
Wendigo Thompson:
> Hi Wietse:
>
> Answering your first question, the message in question does show up in find:
> 26701170 872 -rwx--1 _postfix wheel 444689 Aug 4
> 2008 /var/spool/postfix/maildrop/F423E1976D72
This is one of two messages that you mentioned.
> When I look
On Thu, Jan 07, 2010 at 11:04:13AM -0600, Wendigo Thompson wrote:
> Answering your first question, the message in question does show up in find:
> 26701170 872 -rwx--1 _postfix wheel 444689 Aug 4
> 2008 /var/spool/postfix/maildrop/F423E1976D72
Is this larger than your message
Hi Wietse:
Answering your first question, the message in question does show up in find:
26701170 872 -rwx--1 _postfix wheel 444689 Aug 4
2008 /var/spool/postfix/maildrop/F423E1976D72
When I look at the queue message, it is definitely representative of
what I process by the
Olhando de esguelha pra ver se nao estava sendo observado, Dennis Carr
rabiscou em Thu, 07/01/2010, 06:49h:
> Currently, the method of delivery to my server is by way of an ssh
> tunnel to my server (deliver on localhost 2525 to get to the server),
> but the problem lies herein of security - if
2010/1/8 Davy Leon :
> I'm getting this message in my /var/log/maillog everytime postfix delivers a
> message. The message is delivered, but it logs this message. How can I solve
> this?
>
> Jan 6 18:17:25 centrino postfix/smtp[3699]: certificate verification failed
> for smarthost.example.com: nu
Michael:
> On Fri, 08 Jan 2010 00:50:49 Wietse Venema wrote:
> > Michael:
> > > I want to deploy a system whereby it will do an SQL lookup and depending
> > > on the result will either continue processing the message as per usual or
> > > issue a 'temporary' reject (Ie: Over quota message).
> > >
>
Michael:
> On Fri, 08 Jan 2010 00:50:49 Wietse Venema wrote:
> > Michael:
> > > I want to deploy a system whereby it will do an SQL lookup and depending
> > > on the result will either continue processing the message as per usual or
> > > issue a 'temporary' reject (Ie: Over quota message).
> > >
>
Hi folks
I'm getting this message in my /var/log/maillog everytime postfix delivers a
message. The message is delivered, but it logs this message. How can I solve
this?
Thanks
Davy
Jan 6 18:17:25 centrino postfix/smtp[3699]: certificate verification failed
for smarthost.example.com: num=20
On Fri, 08 Jan 2010 00:50:49 Wietse Venema wrote:
> Michael:
> > I want to deploy a system whereby it will do an SQL lookup and depending
> > on the result will either continue processing the message as per usual or
> > issue a 'temporary' reject (Ie: Over quota message).
> >
> > This is on a relay
On Fri, 08 Jan 2010 00:50:49 Wietse Venema wrote:
> Michael:
> > I want to deploy a system whereby it will do an SQL lookup and depending
> > on the result will either continue processing the message as per usual or
> > issue a 'temporary' reject (Ie: Over quota message).
> >
> > This is on a relay
Michael:
> I want to deploy a system whereby it will do an SQL lookup and depending on
> the result will either continue processing the message as per usual or issue
> a 'temporary' reject (Ie: Over quota message).
>
> This is on a relaying/gateway machine so it does not have direct access to
>
I'm running postfix 2.5.5-1.1 (Debian Stable) on my desktop, which I
use to deliver mail to the internet via my server. Under optimal
circumstances, I'd just have an IP address assigned to the box that's
on the public network, but I'm on a single dynamic IP assigned by
Comcast that may or may not
44 matches
Mail list logo
