44 reputation
8
bio website
location
age
visits member for 2 years, 9 months
seen May 21 at 6:51

Mar
10
awarded  Popular Question
Mar
6
comment Postfix locally redirected mail from sender_restrictions doesn't seem to correctly pass through virtual aliases
But a catch-all would still have to be defined in the virtual_aliases, and that's the part it's not reaching. But regardless, a catch-all is a pretty drastic, spam-attracting measure that I would not be interested in pursuing. For now, I've just redirected it to a gmail address which forwards it back. I just want to remove that additional, unnecessary hop.
Mar
5
comment Postfix locally redirected mail from sender_restrictions doesn't seem to correctly pass through virtual aliases
But the check_sender_access is triggering. The message is redirected. The problem is that the REDIRECTED message is not passing through the virtual_alias_maps.
Mar
5
awarded  Commentator
Mar
5
comment Postfix locally redirected mail from sender_restrictions doesn't seem to correctly pass through virtual aliases
Sorry. That was a typo in the question. I indeed have redirect, and it is working for external addresses.
Mar
5
revised Postfix locally redirected mail from sender_restrictions doesn't seem to correctly pass through virtual aliases
Typo
Mar
4
asked Postfix locally redirected mail from sender_restrictions doesn't seem to correctly pass through virtual aliases
Aug
30
comment Trouble with case-sensitive LDAP user logins to Dovecot
Many thanks. I have traditionally tried to stick with what was approved by Debian. While there were features in 2.x that I wanted to use, I wasn't comfortable with the risk of using an unmaintained package. Is that not a wise approach?
Aug
30
accepted Trouble with case-sensitive LDAP user logins to Dovecot
Aug
30
asked Trouble with case-sensitive LDAP user logins to Dovecot
Aug
25
accepted Tracking down the cause of a Postfix “Recipient address rejected: Access denied” error
Aug
24
comment Tracking down the cause of a Postfix “Recipient address rejected: Access denied” error
What about 465? I was initially wrong. It was 465 instead of 587.
Aug
23
revised Tracking down the cause of a Postfix “Recipient address rejected: Access denied” error
Was 465, not 587
Aug
23
answered Tracking down the cause of a Postfix “Recipient address rejected: Access denied” error
Aug
23
comment Tracking down the cause of a Postfix “Recipient address rejected: Access denied” error
But I stress again, that would not yield a Recipient address rejected: access denied error, would it? Wouldn't it be more like Relay access denied?
Aug
23
comment Tracking down the cause of a Postfix “Recipient address rejected: Access denied” error
example.com is not a virtual_alias_domain. It is defined in virtual_mailbox_domains. The domains in virtual_alias_domains are literally just that… alias domains. In /etc/postfix/virtual, they are mapped to virtual_mailbox_domains with: @example.co.uk @example.com.
Aug
23
revised Tracking down the cause of a Postfix “Recipient address rejected: Access denied” error
added 63 characters in body
Aug
23
comment Tracking down the cause of a Postfix “Recipient address rejected: Access denied” error
sender_access is empty, and helo_access is not related. Regardless, tests against helo generate a clearly different log error (Helo command rejected vs Recipient address rejected). What else would generate Recipient address rejected?
Aug
23
revised Tracking down the cause of a Postfix “Recipient address rejected: Access denied” error
added 230 characters in body
Aug
23
comment Tracking down the cause of a Postfix “Recipient address rejected: Access denied” error
After a certain date, no messages from this sender's company have been successfully delivered to any of the local users.