> On 7 Dec 2018, at 1:23 am, Matus UHLAR - fantomas wrote:
>
> Anyway, sorry for the noise.
>
> however, my questions weren't responded and still apply:
>
> Are those cf files properly configured? Can postfix connect to the
> database?
> What's in the logs?
>
> and also the
> On 6 Dec 2018, at 02:00, Matus UHLAR - fantomas wrote:
>
>> On Mon Dec 03 2018 04:27:43 Matus UHLAR - fantomas
>> said:
>>> pleaase, get a decent MUA, not applemail that tries to encode everything as
>>> internet links (and messes up thge plaintext version of mail).
>
> On 04.12.18
On 5 Dec 2018, at 07:34, Bill Cole
wrote:
> On 2 Dec 2018, at 20:31, James Brown wrote:
>
>> I’m trying to set up a new mail server on macOS Mojave and it almost works.
>> Dovecot for IMAP is working.
>
> This is a bad idea. Mojave (like High Sierra and Sierra before it) is unfit
> for
Greetings, Viktor Dukhovni!
>> On Dec 6, 2018, at 2:19 PM, Andrey Repin wrote:
>>
>> In other words, if I have multiple different messages to the same
>> destination,
>> I can't know if they will be delivered through single connection?
>> And can't control it?
> If the inter-message spacing
> On Dec 6, 2018, at 2:19 PM, Andrey Repin wrote:
>
> In other words, if I have multiple different messages to the same destination,
> I can't know if they will be delivered through single connection?
> And can't control it?
If the inter-message spacing exceeds the either of:
Greetings, Viktor Dukhovni!
>>> The default amount of delay that is inserted between individual deliveries
>>> over the same message delivery transport, regardless of destination. If
>>> non-zero, all deliveries over the same message delivery transport will
>>> happen one at a time.
>>
>> To me,
> On Dec 6, 2018, at 1:28 PM, Andrey Repin wrote:
>
>> The default amount of delay that is inserted between individual deliveries
>> over the same message delivery transport, regardless of destination. If
>> non-zero, all deliveries over the same message delivery transport will
>> happen one at
Greetings, Wietse Venema!
>> default_transport_rate_delay = 15s
I'd like to ask for clarification, as man page wording is not clear.
The original wording is
> The default amount of delay that is inserted between individual deliveries
> over the same message delivery transport, regardless of
Greetings, Wietse Venema!
> Wietse:
>> > I don't think that there is a 'standard' policy that 'works' for
>> > delivery from every site to every site.
>> >
>> > Nowadays you get a policy exception from 'big' receivers, and you
>> > come up with transport_maps with different 'classes' of delivery
On 6 Dec 2018, at 12:13, Dominic Raferd wrote:
On Thu, 6 Dec 2018 at 16:37, Bill Cole <
postfixlists-070...@billmail.scconsult.com> wrote:
On 6 Dec 2018, at 11:15, Dominic Raferd wrote:
Have you verified that the inode number changes?
no, I will check how to do this
'ls -li' is your
On Thu, 6 Dec 2018 at 16:37, Bill Cole <
postfixlists-070...@billmail.scconsult.com> wrote:
> On 6 Dec 2018, at 11:15, Dominic Raferd wrote:
>
> >> Have you verified that the inode number changes?
> >>
> >
> >
> > no, I will check how to do this
>
>
> 'ls -li' is your friend.
>
Thanks, I have
On 12/6/2018 10:46 AM, Rich Shepard wrote:
> On Thu, 6 Dec 2018, Noel Jones wrote:
>
>> Wild guess: some spammer used your own address as sender, and the
>> connection was rejected by some of your spam controls, probably an
>> rbl.
>
> Noel,
>
> There are certainly many rejected by a couple
On Thu, 6 Dec 2018, Noel Jones wrote:
Wild guess: some spammer used your own address as sender, and the
connection was rejected by some of your spam controls, probably an rbl.
Noel,
There are certainly many rejected by a couple of rbls as well as by other
postfix UCE checks. Why these two
On 6 Dec 2018, at 11:15, Dominic Raferd wrote:
>> Have you verified that the inode number changes?
>>
>
>
> no, I will check how to do this
'ls -li' is your friend.
Thanks for the swift response - see below.
On Thu, 6 Dec 2018 at 16:10, Wietse Venema wrote:
> Dominic Raferd:
> > I am using incrond to monitor an mbox file (in /var/mail) for changes,
> but
> > it is failing to trigger when postfix adds an incoming mail to the file.
>
> Possible causes:
>
> -
Rich Shepard:
> Today's pflogsumm report includes this rejection:
>
> Recipient address rejected: Please see http (total: 2)
> 2 rshep...@appl-ecosys.com
>
> Since this is my address I'm curious why two incoming messages were rejected
> when many more were passed. I'd
On 12/6/2018 9:59 AM, Rich Shepard wrote:
> Today's pflogsumm report includes this rejection:
>
> Recipient address rejected: Please see http (total: 2)
> 2 rshep...@appl-ecosys.com
>
> Since this is my address I'm curious why two incoming messages were
> rejected
> when many
Dominic Raferd:
> I am using incrond to monitor an mbox file (in /var/mail) for changes, but
> it is failing to trigger when postfix adds an incoming mail to the file.
Possible causes:
- Your file system does not set the file mtime when Postfix appends
to the file. Fix: don't disable mtime
Today's pflogsumm report includes this rejection:
Recipient address rejected: Please see http (total: 2)
2 rshep...@appl-ecosys.com
Since this is my address I'm curious why two incoming messages were rejected
when many more were passed. I'd appreciate advice on how I can
I am using incrond to monitor an mbox file (in /var/mail) for changes, but
it is failing to trigger when postfix adds an incoming mail to the file.
(It triggers fine however if I touch the file.)
I may be barking up the wrong tree but I wonder if this is because instead
of merely appending to the
Wietse:
> > I don't think that there is a 'standard' policy that 'works' for
> > delivery from every site to every site.
> >
> > Nowadays you get a policy exception from 'big' receivers, and you
> > come up with transport_maps with different 'classes' of delivery
> > agents that are configured
On Mon Dec 03 2018 04:27:43 Matus UHLAR - fantomas
said:
pleaase, get a decent MUA, not applemail that tries to encode everything as
internet links (and messes up thge plaintext version of mail).
On Dec 6, 2018, at 3:00 AM, Matus UHLAR - fantomas wrote:
X-Mailer: Apple Mail
Thank you Wietse,
wouldn't default_transport_rate_delay = 15s
be a safe setting to relax the whole transport a bit?
from a receivers perspective, that's something i would like to see instead
of having ongoing delivery.
Am Do., 6. Dez. 2018 um 14:41 Uhr schrieb Wietse Venema <
> On Dec 6, 2018, at 3:00 AM, Matus UHLAR - fantomas wrote:
>
>> On Mon Dec 03 2018 04:27:43 Matus UHLAR - fantomas
>> said:
>>> pleaase, get a decent MUA, not applemail that tries to encode everything as
>>> internet links (and messes up thge plaintext version of mail).
>
> On 04.12.18
Stefan Bauer:
> stuff/best practice that makes the process more effective.
>
> i'm certain that remote sites prefer one way over the other.
I don't think that there is a 'standard' policy that 'works' for
delivery from every site to every site.
Nowadays you get a policy exception from 'big'
Greetings, Stefan Bauer!
> ack. but i was looking for advices like e.g:
> initially defer mail delivery for lets say a minute to be able to send out
> a bunch of mails to same recipient in a single session instead of having 100
> independant sessions.
For queue management, look at
Hi Jaco,
Although this is not exactly what you are asking, but we're working on
HTTP SASL authentication, so one level below the HTML forms that you are
talking about.
http://internetwide.org/blog/2018/11/15/somethings-cooking-4.html
There is an early Docker Demo with a plugin to add SASL to
ack. but i was looking for advices like e.g:
initially defer mail delivery for lets say a minute to be able to send out
a bunch of mails to same recipient in a single session instead of having
100 independant sessions.
stuff/best practice that makes the process more effective.
i'm certain that
Greetings, Stefan Bauer!
>>> we're running a small relay-service and looking for best practice to
>>> deliver mails to remote sites regarding concurrent delivery and so on.
>>
>>
>>> Sometimes, we have customers that are sending several mails per second to
>>> same recipients.
>>
>>
Its no user issue. Its a real and legal use case that customers send
several mails / second to same recipient over a long period (software tests
whatever).
Am Do., 6. Dez. 2018 um 12:50 Uhr schrieb Andrey Repin :
> Greetings, Stefan Bauer!
>
> > Hi,
>
>
> > we're running a small relay-service
Greetings, Stefan Bauer!
> Hi,
> we're running a small relay-service and looking for best practice to
> deliver mails to remote sites regarding concurrent delivery and so on.
> Sometimes, we have customers that are sending several mails per second to
> same recipients.
> What is best
Hello there
Anybody out there have had any success with httpform authentication
using Cyrus SASL? I am able to compile Cyrus SASL with the following
mechanisms:
saslauthd 2.1.26
authentication mechanisms: getpwent pam rimap shadow httpform
And to link the SASL libraries to Postfix, but how
Hi,
we're running a small relay-service and looking for best practice to
deliver mails to remote sites regarding concurrent delivery and so on.
Sometimes, we have customers that are sending several mails per second to
same recipients.
What is best practice to handle this?
We would like to
On 05.12.18 23:24, Voytek wrote:
# grep connectmain.cf
smtpd_client_connection_rate_limit = 12
smtpd_client_connection_count_limit = 5
sorry.. and thank you.
another dumb question:
so if I have 25 clients on a NATed LAN, that's my connection count limit,
isn't it ?
may be and may not
On Mon Dec 03 2018 04:27:43 Matus UHLAR - fantomas
said:
pleaase, get a decent MUA, not applemail that tries to encode everything as
internet links (and messes up thge plaintext version of mail).
On 04.12.18 13:47, @lbutlr wrote:
What do you base this statement on? I’ve been using
35 matches
Mail list logo
