On 01/06/2014 03:33 PM, Viktor Dukhovni wrote:
On Mon, Jan 06, 2014 at 01:17:41PM -0500, Eric Cunningham wrote:
The problem is entirely with the monstrosity below:
smtpd_recipient_restrictions =
reject_unauth_pipelining,
reject_non_fqdn_recipient,
Fine
Hi, I've encountered a problem with Windows-based devices, such as
Windows Phones, being unable to send mail through postfix. The problem
and resolution are described at
http://answers.microsoft.com/en-us/winphone/forum/wp8-wpemail/smtp-authentication-for-outgoing-emails-via-a/2132a705-e1d0-401
On 10/4/2011 4:19 PM, wolfgang wrote:
On 2011-10-04 21:36, Eric Cunningham wrote:
postmap -q 'e...@whoi.edu'
pcre:/etc/postfix/access/final_recipient_access
Great suggestion for this, unfortunately, it returns nothing:
# postmap -q 'e...@whoi.edu'
pcre:/etc/postfix/access
postmap -q 'e...@whoi.edu' pcre:/etc/postfix/access/final_recipient_access
Great suggestion for this, unfortunately, it returns nothing:
# postmap -q 'e...@whoi.edu' pcre:/etc/postfix/access/final_sender_access
#
-Eric
Hello,
My postfix installation is having trouble accepting email from a
particular source to any recipients and I haven't been able to ascertain
the cause so I can address the problem. Here's a logfile extraction:
Oct 4 11:53:52 postal1 postfix/smtpd[19496]: connect from
fwall.fidcouns.com
On Tue, Apr 12, 2011 at 03:21:06PM -0400, Eric Cunningham wrote:
Wietse Venema wrote:
Eric Cunningham:
Apr 12 13:15:10 postal2 postfix/smtpd[22543]: NOQUEUE: reject:
RCPT from hsarelay1t.mail.mylife.com[216.52.223.210]: 554 5.7.1
: Sender address rejected: Access denied;
from= to= proto=ESMTP
Darek M wrote:
On Tue, Apr 12, 2011 at 3:21 PM, Eric Cunningham wrote:
Yes, that's correct, but not intentionally nor explicitly. I've tried
explicitly accepting the sender address in my smtpd_recipient_restrictions'
final_sender_access file but that has no effect.
-Eric
Wietse Venema wrote:
Eric Cunningham:
Apr 12 13:15:10 postal2 postfix/smtpd[22543]: NOQUEUE: reject: RCPT from
hsarelay1t.mail.mylife.com[216.52.223.210]: 554 5.7.1
: Sender address rejected: Access denied;
from= to= proto=ESMTP
helo=
The recipient address is legit and working for other
nf -n output is attached.
Thank you.
-Eric Cunningham
--- Begin Message ---
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases, ldap:ldap
anvil_rate_time_unit = 60s
append_dot_mydomain = yes
body_checks = pcre:/etc/postfix/access/body_access
broken_sasl_auth_clients = yes
command_d
Is there a way to exempt postmas...@my.domain, ab...@my.domain and
u...@my.domain from header_checks and body_checks while still
maintaining the functionality of those checks?
-Eric
Noel Jones wrote:
Eric Cunningham wrote:
I want e...@sanguine.whoi.edu to continue delivery to my imap
account. In fact, that happened perfectly in my previous postfix
configuration.
... it worked previously due to a bug in permit_mx_backup. That bug has
been corrected.
Ahh...finally
Noel Jones wrote:
Apparently, sanguine.whoi.edu not listed in any of the postfix address classes.
Which address class do you expect this to be? Then you'll know where the
domain must be listed.
This is one document you need to understand:
http://www.postfix.org/ADDRESS_CLASS_README.html
...
virtual_alias_domains = $virtual_alias_maps
virtual_alias_maps = hash:/etc/postfix/virtual, ldap:vldap
These are all your address class definitions. We can't see into your
virtual_alias_maps to know what domains might be listed there. You can
show us "postmap -q sanguine.whoi.edu hash:/et
I guess I'm still missing something so here's my 'postfix -n' output and
logfile showing the rejection.
-Eric
for postfix to accept mail for a domain (from anywhere), the domain
needs to be found in one (and only one of):
- mydestination (this is for mail delivered to a unix a
list all the MX hosts as there are
hundreds and that list is not always static. I'm certain Postfix must
be capable of performing MX lookups and directing the emails accordingly.
-Eric
mouss wrote:
Eric Cunningham a écrit :
Thanks Victor. Ok, so I:
- removed .$mydo
a fresh postconf -n for a more detailed & updated
picture.
Regards,
-Eric
Victor Duchovni wrote:
On Fri, May 01, 2009 at 01:54:03PM -0400, Eric Cunningham wrote:
I think I've found a/the fix for re-enabling the original behavior of my
transport maps and MX relaying.
I think I've found a/the fix for re-enabling the original behavior of my
transport maps and MX relaying. I added .$mydomain to mydestination in
main.cf. This is in addition to $mydomain which was already in
mydestination.
$mydomain vs. .$mydomain is subtle but apparently important.
transport_maps simply routes accepted messages by overriding DNS.
That's what I want to continue to do, as had occurred happily before the
postfix upgrade.
To accept mail, the envelope recipient *must* be in mydestination,
relay_domains, virtual_alias_domains or virtual_mailbox_domains.
All
Why don't you simply restore the old working main.cf and master.cf
files, and then execute as root:
# postfix upgrade-configuration
This is easier that trying to figure out how to rebuild the old
configuration from scratch.
PS If the recipient domains are not local, then they must be listed
Sorry, thank you for the clarification, Brian. 'postconf -n' output is
now attached. I've already run 'postmap transport' and 'postfix reload'
but that didn't help.
I did find a quasi-workaround to this by adding the subdomains from
transport to relay_domains but that will be clumsy at best
tion that hasn't surfaced until
the upgrade? Any ideas on how to address this?
Thanks!
=====
Eric Cunningham
Computer and Information Services - http://www.whoi.edu/CIS
Woods Hole Oceanographic Institution - http://www.whoi.ed
21 matches
Mail list logo
