Yep, working perfectly, thanks!
From: Bill Cole
To: Postfix users
Sent: 09.02.2020 2:12 AM
Subject: Re: check_sender_access not working on local senders
On 8 Feb 2020, at 17:25, simonh wrote:
> Hello,
>
> I am trying to automate anti-spam flood on our Plesk servers, and my
Hi
How to guess the message body’s language encoding if message didn’t have MIME
charset set? The message may be encoded with utf8, gb2312, gbk or something
others, but it didn’t have an charset header.
Thanks
On Sun, Feb 09, 2020 at 01:45:21PM +0300, wes...@199903.xyz wrote:
> How to guess the message body’s language encoding if message didn’t have MIME
> charset set? The message may be encoded with utf8, gb2312, gbk or something
> others, but it didn’t have an charset header.
Well, text/*, with the
On Sun, Feb 09, 2020 at 01:45:21PM +0300, wes...@199903.xyz wrote:
> How to guess the message body’s language encoding if message didn’t
> have MIME charset set? The message may be encoded with utf8, gb2312,
> gbk or something others, but it didn’t have an charset header.
You could run the text
Hi,
Is it possible for postfix to directly access the email addresses or
userlist from an Exchange server using either LDAP or AD? Perhaps someone
has an external script that can be used to build the recipient maps?
The results from my search have produced only other people looking
unsuccessfully
On Sun, Feb 09, 2020 at 07:03:12AM -0500, John Regan wrote:
> Is it possible for postfix to directly access the email addresses or
> userlist from an Exchange server using either LDAP or AD? Perhaps someone
> has an external script that can be used to build the recipient maps?
Postfix has LDAP ta
it should be. use ldap. active directory is nothing but a glorified ldap
server and listens on port 389.
Sent from my iPhone
> On Feb 9, 2020, at 7:04 AM, John Regan wrote:
>
>
> Hi,
>
> Is it possible for postfix to directly access the email addresses or userlist
> from an Exchange ser
On Sun, 9 Feb 2020 07:56:53 -0500, Curtis Maurand stated:
>it should be. use ldap. active directory is nothing but a glorified
>ldap server and listens on port 389.
If it were ldap over ssl the port is 636 I believe.
--
Gerard
On 2/9/20 12:39 PM, Gerard E. Seibert wrote:
On Sun, 9 Feb 2020 07:56:53 -0500, Curtis Maurand stated:
it should be. use ldap. active directory is nothing but a glorified
ldap server and listens on port 389.
If it were ldap over ssl the port is 636 I believe.
I stand corrected.
Hi,
I'm using an hourly shell script to retrieve from our AD the proper LDAP
records, and an AWK script to transform this output into an alias map (our
Exchange setup uses a different internal address from the public external
address). This alias map is later used to create a list of allowed re
10 matches
Mail list logo