As follows
smtpd_recipient_restrictions =
reject_invalid_hostname,
reject_non_fqdn_sender,
reject_non_fqdn_recipient,
reject_unknown_sender_domain,
reject_unknown_recipient_domain,
reject_unauth_pipelining,
check_recipient_access hash:/etc/po
Le 11/01/2010 09:27, Stan Hoeppner a écrit :
Patrick Chemla put forth on 1/11/2010 1:02 AM:
Le 10/01/2010 23:58, Stan Hoeppner a écrit :
On a technical level I'm happy you got it working. Just please tell
us you're
not sending mass spam with this setup.
--
Stan
I have to d
Patrick Chemla put forth on 1/11/2010 1:02 AM:
> Le 10/01/2010 23:58, Stan Hoeppner a écrit :
>> On a technical level I'm happy you got it working. Just please tell
>> us you're
>> not sending mass spam with this setup.
>>
>> --
>> Stan
>>
>
> I have to do it for a customer who send as he sa
Le 11/01/2010 01:13, Wietse Venema a écrit :
Patrick Chemla:
Wietse,
Please try the following, as asked half a week ago:
postconf -e smtp_connection_cache_on_demand=no
postfix reload
and report if this makes a difference.
Wietse
I have tested this sin
Le 10/01/2010 23:58, Stan Hoeppner a écrit :
On a technical level I'm happy you got it working. Just please tell us you're
not sending mass spam with this setup.
--
Stan
I have to do it for a customer who send as he said, only opt-in mass
emails. He has a big blacklisted email database w
Stefan Foerster:
> One of the greatest improvements in the 2.7 tree is the ability to
> defer transmission of received messages to a SMTP proxy until the
> message receiption completes (smtpd_proxy_options = speed_adjust).
Can you be more specific about the benefits?
Wietse
Patrick Chemla:
> Wietse,
> >> Please try the following, as asked half a week ago:
> >>
> >> postconf -e smtp_connection_cache_on_demand=no
> >> postfix reload
> >>
> >> and report if this makes a difference.
> >>Wietse
> >>
> I have tested this since yesterday night.
>
> I got
Patrick Chemla put forth on 1/10/2010 3:00 PM:
> Wietse,
>>> Please try the following, as asked half a week ago:
>>>
>>> postconf -e smtp_connection_cache_on_demand=no
>>> postfix reload
>>>
>>> and report if this makes a difference.
>>> Wietse
>>>
> I have tested this since yes
Wietse,
Please try the following, as asked half a week ago:
postconf -e smtp_connection_cache_on_demand=no
postfix reload
and report if this makes a difference.
Wietse
I have tested this since yesterday night.
I got some problems with Linux per user number of processes
On 1/10/10 10:32 PM, Martijn de Munnik wrote:
On Jan 10, 2010, at 9:24 PM, Eero Volotinen wrote:
On 1/10/10 10:17 PM, Martijn de Munnik wrote:
Hi List,
This is not a real postfix related question…
We offer e-mail services to our customers and some of our customers have a hard
time configur
On Jan 10, 2010, at 9:24 PM, Eero Volotinen wrote:
> On 1/10/10 10:17 PM, Martijn de Munnik wrote:
>> Hi List,
>>
>> This is not a real postfix related question…
>>
>> We offer e-mail services to our customers and some of our customers have a
>> hard time configuring their mail client. I notic
On 1/10/10 10:17 PM, Martijn de Munnik wrote:
Hi List,
This is not a real postfix related question…
We offer e-mail services to our customers and some of our customers have a hard
time configuring their mail client. I noticed that most mail clients try to
'find' the correct settings when an a
Hi List,
This is not a real postfix related question…
We offer e-mail services to our customers and some of our customers have a hard
time configuring their mail client. I noticed that most mail clients try to
'find' the correct settings when an account is configured. So the mail client
(at le
Dr. Lars Hanke:
> Apparently postfix missed the switching of nameservers and did not learn
> of the new DNS until restart. Is this a bug or a feature?
Like most programs, Postfix never reads /etc/resolv.conf.
Instead, that file is read by the NSSWITCH system library functions,
and the DNS system
Stefan Foerster:
> * Wietse Venema :
> > For STATISTICAL load balancing you can get by with multiple IP
> > addresses per proxy filter "host" name. However this requires new
>
> The main difference I see here is that delivery to a content_filter
> will try more than one server, giving us not only
* Wietse Venema :
> For STATISTICAL load balancing you can get by with multiple IP
> addresses per proxy filter "host" name. However this requires new
The main difference I see here is that delivery to a content_filter
will try more than one server, giving us not only (statistical) load
balancing,
On Sun, 10 Jan 2010 11:32:34 +0100
"Dr. Lars Hanke" wrote:
> I had a quite strange issue. About a week ago my bind9 broke down and I
> could not get it running again on the same machine. So moved it to
> another machine and changed the /etc/resolv.conf of my machines to try
> both IP. Apparent
Stefan Foerster:
> So, my question is: Are there any plans to further enhance Postfix's
> functionality as far as SMTP proxy filtering is concerned, and make
> that kind of load balancing available to pre-queue setups using
> smtpd_proxy_filter?
For TRUE load balancing you need a stateful system t
Kārlis Repsons a écrit :
> Hi,
> maildrop seems to reject any efforts on my part, take a look at this:
>
> Tried using maildrop with postfix as described in the second part of [1], but
> it failed. strace showed me:
> "connect(3, {sa_family=AF_FILE,
> path="/var/lib/courier/authdaemon/socket"...}
One of the greatest improvements in the 2.7 tree is the ability to
defer transmission of received messages to a SMTP proxy until the
message receiption completes (smtpd_proxy_options = speed_adjust).
However, compared to the content_filter setting, it stil lacks some
functionality: A content filte
Hi,
maildrop seems to reject any efforts on my part, take a look at this:
Tried using maildrop with postfix as described in the second part of [1], but
it failed. strace showed me:
"connect(3, {sa_family=AF_FILE, path="/var/lib/courier/authdaemon/socket"...},
110) = -1 ENOENT (No such file
or dir
* "Dr. Lars Hanke" :
> I had a quite strange issue. About a week ago my bind9 broke down and I
> could not get it running again on the same machine. So moved it to
> another machine and changed the /etc/resolv.conf of my machines to try
> both IP. Apparently everything worked fine.
>
> Today
I had a quite strange issue. About a week ago my bind9 broke down and I
could not get it running again on the same machine. So moved it to
another machine and changed the /etc/resolv.conf of my machines to try
both IP. Apparently everything worked fine.
Today I was puzzled that the correspondi
23 matches
Mail list logo
