stefan novak:
> thx, i've implemented that already for dovecot.
>
> but i have the quota problem with users that are on our exchange
> server backend (it doesnt support this quota service)
>
> is there a way to tell postfix that it accepts only mail on the
> frontend when the backend server (tran
thx, i've implemented that already for dovecot.
but i have the quota problem with users that are on our exchange
server backend (it doesnt support this quota service)
is there a way to tell postfix that it accepts only mail on the
frontend when the backend server (transport smtp destination) says
Postfix as distributed by me has never nagged about obsolete 'access'
files, and I suggest that any complaints about such behavior are
directed at the downstream maintainer who introduced that behavior.
Wietse
Am 02.01.2018 um 19:59 schrieb stefan novak:
> Hello!
>
> we are using Postfix as our MX Server for several mailservers, mostly
> dovecot. We have now implemented an exchange Server as well.
>
> We are using the reject_unverified_recipient in combination with smtp
> transport-table to submit the
On 2 Jan 2018, at 10:24, Wietse Venema wie...@porcupine.org> wrote:
>
> @lbutlr:
>> On 1 Jan 2018, at 11:18, Wietse Venema wie...@porcupine.org> wrote:
>>> =20
>>> @lbutlr:
On 31 Dec 2017, at 16:41, @lbutlr wrote:
> Perhaps "are no longer part of the default Postfix install. If you =
>>
stefan novak:
> Is there a way to tell postfix to accept the E-Mail only when the
> exchange Server also wants to deliver it.
Postfix uses the RCPT TO command to find out if a server is willing
to accept the message.
In the case of Dovecot, there is a way to find out if a user is
over quota (talk
Hello!
we are using Postfix as our MX Server for several mailservers, mostly
dovecot. We have now implemented an exchange Server as well.
We are using the reject_unverified_recipient in combination with smtp
transport-table to submit the E-mail back to the exchange Server.
With our dovecot backen
> On Jan 2, 2018, at 12:24 PM, Wietse Venema wrote:
>
> I frequently install Postfix on a development machine, and I would
> certainly have noticed messages about an obsolete 'access' file
> (the access file on my development machine dates from 2005).
Indeed there have been very few additional
> On Jan 2, 2018, at 12:19 PM, James B. Byrne wrote:
>
> The constantcontact.com domain was added to our sender_access file:
>
> constantcontact.com REJECT
> .constantcontact.com REJECT
They are a large
@lbutlr:
> On 1 Jan 2018, at 11:18, Wietse Venema wie...@porcupine.org> wrote:
> >=20
> > @lbutlr:
> >> On 31 Dec 2017, at 16:41, @lbutlr wrote:
> >>> Perhaps "are no longer part of the default Postfix install. If you =
> are =3D
> >> not using them, they may be removed."?
> >=20
> > Per my previo
The constantcontact.com domain was added to our sender_access file:
constantcontact.com REJECT
.constantcontact.com REJECT
I must have done this but at some distant time in the past as I have
no recollectio
On 1 Jan 2018, at 11:18, Wietse Venema wie...@porcupine.org> wrote:
>
> @lbutlr:
>> On 31 Dec 2017, at 16:41, @lbutlr wrote:
>>> Perhaps "are no longer part of the default Postfix install. If you are =
>> not using them, they may be removed."?
>
> Per my previous email, Postfix 3.3 as distribute
12 matches
Mail list logo
