> On Aug 23, 2017, at 9:25 AM, Tom Browder wrote:
>
> or the first time I can remember, I just glanced through the postfix multi
> info and it looks like it might be the way to go for my use: managing a
> remote, internet-connected, multi-domain mail server via my local laptop
> connected wit
If anyone needs for future testing
openssl s_client -starttls smtp -connect mail6.uits.uconn.edu:587
openssl s_client -connect 137.99.26.36:465
Replace IP/hostname with yours.
-ALF
-Angelo Fazzina
Operating Systems Programmer / Analyst
University of Connecticut, UITS, SSG, Server Systems
860
On Mon, Aug 21, 2017 at 10:21 Tom Browder wrote:
>
> On Mon, Aug 21, 2017 at 09:13 Rick van Rein wrote:
>
>> Hi
>
> ...
>
>> @Tom, to get back to your original question, a plain & simple mailing
>> list is a bed of nails... even when you do it really nicely, perhaps
>> even still when you canoni
Deniss:
> Hello,
>
> I looking for a way to speed up delivery for specified sender's domain
> when incoming queue is overloaded.
When the road to the airport is clogged, everyone has to wait.
BTW, Postfix has the smtp_fallback_relay feature for moving
deadbeat destinations to a different queue.
Allen Coates:
> Is there any way of reducing the TTL of the postscreen temporary whitelist?
As of Postfix 3.1, these are the defaults:
postscreen_bare_newline_ttl = 30d
postscreen_dnsbl_max_ttl = ${postscreen_dnsbl_ttl?{$postscreen_dnsbl_ttl}:{1}}h
postscreen_dnsbl_min_ttl = 60s
postscreen_greet_
Hello,
I looking for a way to speed up delivery for specified sender's domain
when incoming queue is overloaded.
I have idea how to achieve this by using another postfix instance and
looping messages through it.
May be it is possible to configure qmgr scheduler to prioritize messages
by senders
Is there any way of reducing the TTL of the postscreen temporary whitelist?
I am having problems with spammers repeatedly getting through postscreen
with a "PASS OLD" result.
While I can't stop them trying, at least I can cost them time by making
them run the full postscreen gauntlet more frequen
On 23 August 2017 at 08:00, sreeranj s wrote:
> Thanks Dominic.
>
> Let me explain what exactly is the issue.
> Some of the external email server rejects email from our email servers
> with 450 error. HELO name not resolvable in public DNS. To fix the issue I
> have tried to change smtp_helo_name
Am 22.08.2017 um 23:15 schrieb Alef Veld:
Does anyone know how to setup postfix in such a way so that clients can "auto
configure" (you just fill in the email address and password and it guesses the
settings)
I apologise if this is not a postfix thing perse.
https://automx.org/en/
--
Alex J
