RFC1123 is updated by, among others, RFC5321 which says in section 4.1.4:
An SMTP server MAY verify that the domain name argument in the EHLO
command actually corresponds to the IP address of the client.
However, if the verification fails, the server MUST NOT refuse to
accept a message on that bas
again,
John
--
John Hascall
Team Lead, Network Infrastructure, Authentication, & Directory Services
IT Services, The Iowa State University of Science and Technology
On Wed, Jan 7, 2015 at 2:16 PM, Viktor Dukhovni
wrote:
> On Wed, Jan 07, 2015 at 02:07:25PM -0600, John Hascal
ng else...?
Thanks,
John
--
John Hascall
Team Lead, Network Infrastructure, Authentication, & Directory Services
IT Services, The Iowa State University of Science and Technology
On Wed, Jan 7, 2015 at 1:12 PM, Viktor Dukhovni
wrote:
> On Wed, Jan 07, 2015 at 07:54:03PM +0100, Jean Bruen
There may be other ways to do this, but I use a (locally written) milter to
do this.
John
On Mon, Nov 10, 2014 at 9:00 AM, shamu...@gmail.com
wrote:
> hello all, I have a server with postfix and I want the following setup:
>
> 1. Only certain sender addresses can send email to patterned email
>
*alias: :include:/list/of/members/in/a/file*
So in the included file is it just one recipient per line or ?
Thanks again,
John
On Fri, Nov 7, 2014 at 12:48 PM, Viktor Dukhovni wrote:
> On Fri, Nov 07, 2014 at 12:05:03PM -0600, John Hascall wrote:
>
> > THANK YOU!
>
> N
THANK YOU!
That's working.
John
On Fri, Nov 7, 2014 at 11:58 AM, Viktor Dukhovni wrote:
> On Fri, Nov 07, 2014 at 11:51:29AM -0600, John Hascall wrote:
>
> > alias:
> > recip1, recip2, recip3, ..., recipN, continue-1
> >
> > continue-1:
> >
In sendmail, when an alias grew
too
long, you did:
alias:
recip1, recip2, recip3, ... recipN, continue-1
continue-1:
recip
N+1,
recipN+2, ... etc
This seems not to work in postfix.
How do I deal with really long aliases (~50,000 addresses)?
Thanks,
John
