And I would use "check_client_access" instead?
Yes. Note that trailing comments are not part of the Postfix
map syntax. Any comment must occupy its entire line.
Good to know. I would have screwed this up at some point if I haven't
already.
You can use a CIDR map if you prefer,
Hi,
Postfix isn't the right thing for that. It's a mail
server, not a mail client. You'll need to investigate
the documentation for the mail client that you use when
reading and sending mail.
For example, with mutt, you can give it a list of all
of your email addresses with an "alternates"
On Wed, Sep 01, 2021 at 11:49:46PM -0400, Steve Dondley
wrote:
> My scenario: I have several email accounts: EmailA, EmailB, EmailC, EmailD,
> etc.. Then I have a fifth gmail account, EmailE, that I use to
> funnel/forward all my other email addresses to. The gmail account then
> forwards all
On Wed, Sep 01, 2021 at 09:49:21PM -0400, Steve Dondley wrote:
> > I would have opted for "client" rather than "sender" checks, provided a
> > sufficiently stable/comprehensive range of source IP addresses for the
> > forwarding host were available.
>
> OK, took a quick look at the documentation
My scenario: I have several email accounts: EmailA, EmailB, EmailC,
EmailD, etc.. Then I have a fifth gmail account, EmailE, that I use to
funnel/forward all my other email addresses to. The gmail account then
forwards all email to my main email, EmailA. Yeah, it's a mess. Yes, I
will
I would have opted for "client" rather than "sender" checks, provided a
sufficiently stable/comprehensive range of source IP addresses for the
forwarding host were available.
OK, took a quick look at the documentation on this but still left with
questions. So would "client" be the same as
On Wed, Sep 01, 2021 at 04:05:55PM -0400, Steve Dondley wrote:
> Thank you. Problem solved. For the benefit of others:
>
> 1) Add /etc/postfix/sender_checks file:
>
> amazonses.com OK
>
> 2) Add check to smtpd_recipient_restrictions config in main.cf:
>
> smtpd_recipient_restrictions =
Anything else I can try?
Yes, far better to disable SPF checks on hostB when receiving mail from
hostA.
Thank you. Problem solved. For the benefit of others:
1) Add /etc/postfix/sender_checks file:
amazonses.com OK
2) Add check to smtpd_recipient_restrictions config in main.cf:
On 2021-08-30 13:01, Sebastian Hyrwall wrote:
The reason I thought of trying this is because I recently had emails
sent to a completely legit domain that happened to reside on some
shared server which got dnsbl listed everywhere.
On 30.08.21 15:46, Benny Pedersen wrote:
On Wed, 1 Sep 2021, Leandro Santiago wrote:
Hey All,
Looks like my original mail from Hadmut got eaten by voracious
thread-cleaning. Sorry for the top post.
I use sendmail in my daily life, not postfix, but I have a ~100 line perl
script that basically:
Looks for:
Sep 1 06:51:42 prime
Hi Hadmut (and list :-)),
I've been part of a team working on an open source monitoring tool
specialized on Postfix called Lightmeter and one of the features we are
working at the moment are brute force attack analysis.
We are on early development stages of the feature, looking for feedback
On Wed, Sep 01, 2021 at 06:37:59AM -0400, Steve Dondley wrote:
> So I followed the instructions at
> http://www.postfix.org/ADDRESS_REWRITING_README.html#generic for generic
> mapping and set that up. I modified main.cf with:
Which leads you to http://www.postfix.org/generic.5.html
TABLE
smtp_generic_maps = hash:/etc/postfix/smtp_generic_map
Forgive the typo in this email. I have it correctly entered in the
actual config file as: "smtp_generic_maps =
hash:/etc/postfix/smtp_generic_maps"
I have a mail server the receives email from a website. The website uses
Amazon SES to send its email out. This email gets sent to
somebody@HOST_A address. Then, the email client on the server has a
filter installed to forward to a local address and then to an email
address on another adrees,
14 matches
Mail list logo
