RE: Newbie SASL Auth with Dovecot problem

> > > I also tried port 25 and 587 from a separate machine that has an IP > > address > > in mynetworks. In that case, EHLO is not even recognized: > > > > telnet 587 > > 220 ESMTP Postfix (Ubuntu) > > EHLO client.example.com > > 502 5.5.2 Error: command not recognized > > HELO client.example.c

Re: Number of address in "To:"

On 29 Jun 2016, at 9:57, mmgomess wrote: Hi friends. I need to limit the number of addresses in the "To:" in messages from my server domain users. It is possible? Yes. To limit based on the message "To:" header you would need either to use header_checks or an external content filter. Note

Re: Newbie SASL Auth with Dovecot problem

On 28 Jun 2016, at 2:39, Michael Fox wrote: I also tried port 25 and 587 from a separate machine that has an IP address in mynetworks. In that case, EHLO is not even recognized: telnet 587 220 ESMTP Postfix (Ubuntu) EHLO client.example.com 502 5.5.2 Error: command not recognized HELO client

Re: OT DMARC question

On 27 Jun 2016, at 20:17, Paul R. Ganci wrote: I notice that postfix generates bounce messages that without going through some effort do not get DKIM signed. I have setup my incoming gateway server so that messages to my email subscribers are bounced using a local_recipient_map. However I rece

RE: reject_sender_login_mismatch

> > Specify, for example: > > smtpd_sender_login_maps = hash:/etc/postfix/sasl_senders, >pcre:/etc/postfix/sasl_default_senders > > Where the contents of sasl_default_senders is, for example: > > root# cat sasl_default_senders > /^(.*)@domain$/ $1 > > Which restrict

Re: reject_sender_login_mismatch

On 07/01/2016 01:19 PM, Michael Fox wrote: I’m confused about how the reject_sender_login_mismatch restriction works. I can understand the value of this mapping if you want to allow a given SASL login to use multiple MAIL FROM addresses. But is there a way to require that the MAIL FROM address

reject_sender_login_mismatch

I'm confused about how the reject_sender_login_mismatch restriction works. "reject_sender_login_mismatch Reject the request when $smtpd_sender_login_maps specifies an owner for the MAIL FROM address, but the client is not (SA

RE: how to prevent MX lookup of virtual_mailbox_domain

> > Jun 30 20:12:31 myhost postfix/submission/smtpd[28379]: warning: Unable > to > > look up MX host for my.virtual.domain: Host not found, try again > > > > Why is this happening? > > Because YOU configured something that requires MX lookups: > check_*_mx_access, reject_unknown_sender_domain, > r

Re: how to prevent MX lookup of virtual_mailbox_domain

Michael Fox: > Jun 30 20:12:31 myhost postfix/submission/smtpd[28379]: warning: Unable to > look up MX host for my.virtual.domain: Host not found, try again > > Why is this happening? Because YOU configured something that requires MX lookups: check_*_mx_access, reject_unknown_sender_domain, reje

Re: Configuration for rate limited Amazon SES relay

Rohit Shriwas: Checking application/pgp-signature: FAILURE -- Start of PGP signed section. > I should add I have the following limits set in master.cf as well: > > smtp unix - - n - 10 smtp > relay unix - - n - 10 smtp > > I th

Re: postfix update and sender_dependent_default_transport_maps

Eric Abrahamsen: > postfix/qmgr[25734]: 9BFA02B82C5: from=, size=796, > nrcpt=1 (queue active) > postfix/pr-out/smtp[25807]: 9BFA02B82C5: to=, > relay=verifier.port25.com[38.95.177.125]:25, delay=1.2, > delays=0.88/0.02/0.24/0.09, dsn=2.6.0, status=sent (250 2.6.0 message > received) > postfix/

Re: SPF option in Postfix 3

Am 01.07.2016 um 11:46 schrieb Postfix User: > Just my 2 cents, but why don't you try contacting the port maintainer, > oha...@freebsd.org and asking him if he can clear this problem up? > Since compiling postfix with a third-party SPF library patch is > not recommended, the maintainer should do so

Re: SPF option in Postfix 3

On Fri, 1 Jul 2016 11:01:00 +0200, Matthias Fechner stated: >Am 30.06.2016 um 04:51 schrieb Noel Jones: >> IIRC the FreeBSD ports postfix configuration SPF option will compile >> postfix with a third-party SPF library patch, which is not >> recommended. >> >> The recommended way to do SPF checking

Re: SPF option in Postfix 3

Am 30.06.2016 um 04:51 schrieb Noel Jones: > IIRC the FreeBSD ports postfix configuration SPF option will compile > postfix with a third-party SPF library patch, which is not recommended. > > The recommended way to do SPF checking in postfix is with a policy > service plugin, which is what it look

Re: Configuration for rate limited Amazon SES relay

I should add I have the following limits set in master.cf as well: smtp unix - - n - 10 smtp relay unix - - n - 10 smtp I think this, along with the following in main.cf: default_destination_rate_delay = 1s default_destination_