I'm not sure, but canonical address mapping sounds like
what you want:
http://www.postfix.org/ADDRESS_REWRITING_README.html#canonical
This isn't the same as just delivering an email to an
alias address. It actually rewrites envelope and
message header addresses.
If this does what you want
Now my additions. If you are using RoundCube then almost certainly
RoundCube is using IMAP/IMAPS to communicate with a back end imapd
server. A backend imapd that is most likely Dovecot? This drifts
off-topic for Postfix so further discussion should be in a different
mail group, probably a
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, someth
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" di
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 eventuall
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 HO
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:
smtpd_re
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, s
I'm looking at config documentation for solr on dovecot:
https://doc.dovecot.org/configuration_manual/fts/solr/
In the suggested solrconfig.xml file
(https://raw.githubusercontent.com/dovecot/core/master/doc/solr-config-7.7.0.xml),
it has the following line:
7.7.0
I'm running solr version 8
So are you saying that amavis would replace the uses of the sendmail
command here to deliver the email? I'm not familiar with amavis. I'll
search on it.
yes.
Perhaps you could replace the sendmail with postfix' lmtp command.
But I'm not sure whether if could work and wht exact syntax to use
No. As Matthias pointed out, these are the settings before the content
filter (hint: it is before spamassassin).
Unfortunately, your configuration uses the /usr/sbin/sendmail command
to inject filtered mail back into Postfix. That uses the same Postfix
pickup service for new mail and for filte
smtp inet n - y - -smtpd
-o content_filter=spamassassin
-o receive_override_options=no_address_mappings
So it looks like I have the no_address_mappings after the content
filter already. Is that right?
no, you have no_address_mappings BEFORE the content f
By doing the virtual_alias_maps *before* instead of after the content
filter, so that the content filter sees the final envelope recipient.
This is done by by NOT having ("receive_override_options" with
"no_address_mappings") before the content filter and by having
("receive_override_options" with
I'm using system users on my machine.
I've got the following in /etc/postfix/main.cf:
virtual_alias_maps = hash:/etc/postfix/virtual
I've got the following in my alias table at /etc/postfix/virtual:
st...@dondley.com s
I've got the following in master.cf:
user=debian-spamd argv=/usr/bin/spam
Sending to pe...@example.org works with these SA settings in master.cf:
smtp inet n - y - -smtpd
-o content_filter=spamassassin
-o receive_override_options=no_address_mappings
spamassassin unix - n n - - pipe
user=debian-spa
OK, I found the solution. So the command needed for me was:
user=debian-spamd argv=/usr/bin/spamc -u ${user} -f -e
/usr/sbin/sendmail -oi -f ${sender} ${recipient}
${recipient} returns the full email address whereas I just wanted the
bit before the @ sign (the user name).
user=d
spamassassin unix - n n - - pipe
user=debian-spamd argv=/usr/bin/spamc -f -e /usr/sbin/sendmail
-oi -f ${sender} ${recipient}
I modified the above to:
user=debian-spamd argv=/usr/bin/spamc -u ${recipient} -f -e
/usr/sbin/sendmail -oi -f ${sender} ${rec
I'd like to configure postfix so the configuration settings in the
per-user configuration file at ~/.spamassassin/user_prefs get applied.
This user_prefs config file is used with the spamassassin command as
evidenced with spamassassin -D < spam.txt. But as far as I can tell, the
user_prefs fil
On Fri, Mar 5, 2021 at 4:26 AM Viktor Dukhovni
wrote:
>
> On Fri, Mar 05, 2021 at 03:41:06AM -0500, Steve Dondley wrote:
>
> > Here are postfix config file: https://pastebin.com/bZxjHF5y
>
> I don't usually go chasing pastebin URLs...
>
> > Hopefully something j
> 1. new email comes in, is delivered to content filter, with bcc to
> always_bcc recipient.
> 2. content filter re-injects email into the queue for final delivery,
> postfix performs final delivery, with bcc to the always_bcc recipient?
>
> Since these are 2 separate deliveries (with different rou
> You may also have disabled recipient duplication. We will
> never knwo unles yo reveal yur configration as described
> in http://www.postfix.org/DEBUG_README.html#mail.
I've been looking at this a lng time tonight. Despite my best
efforts, I did not find a reason for the duplicate email.
I
> If 'always_bcc' produces three copies (with spamassassin turned on)
> for one email message with three recipients, then Postfix is
It's actually generating 3 emails even if sending to only one recipient.
> mis-configured, for example, to deliver three one-recipient messages
> to the content fil
> do a lot of your own homework (because everyone here is busy). If this
> doesn't appeal, consider using a recipe for a postfix-based mail server
> such as https://mailinabox.email/ or https://www.iredmail.org/. You lose
> the flexibility of a bespoke setup but you get back some of your life -
> I
hat in (which I apparently do), how do I
properly stop duplicates from happening?
On Thu, Mar 4, 2021 at 2:17 PM Steve Dondley wrote:
>
> I think I found the root cause of the problem (other than me being a
> clueless idiot). I had this in my master.cf:
>
> smtp inet n -
I think I found the root cause of the problem (other than me being a
clueless idiot). I had this in my master.cf:
smtp inet n - y - -smtpd
-o content_filter=spamassassin
submission inet n - y - -smtpe
-o content_filter=spamassassin
After staring at these logs some more and piecing together the advice
here, here's my understanding of what's happening:
* Mail comes in via smtpd as user sends mail. It's going to 3
recipients. I'm not sure who those might be. Maybe the catchall
account and the two users the email is going to?
*
Here's an anonymized pastebin example of my actual log entries of an
outgoing email that generated 3 copies: https://pastebin.com/cw2XB5jp
to the "catchall" mailbox.
> It is worthwhile to know if the duplicates are caused by adding
> multiple 'always_bcc' addresses to the same queue file.
>
> Look
> - mail comes to postfix (smtp or local injection)
> = address mappings (always_bcc) happen
> - postfix sends mail to spamassassin
> - spamassassin scans mail and sends to postfix
> = address mappings (always_bcc) happen
>
> one of those should be avoided by no_address_mappings but choose wise
> The info can be found in the maillog file, and the Received: headers
> of the messages as delivered. Welcome to the vortex.
After a close inspection of the headers, I can see that all the email
received have headers injected by spamassassin and this revealing
line:
"Received: by email.example.c
> you only use should no_address_mappings if your mail loops back, not
> generally - you usually want alias expantion, canonical mapping, and
> automatic BCC (at least if you configure any of those).
Sorry, I don't follow you.
I'm on debian. As far as I can gather, all mail related activity is
lo
On Thu, Mar 4, 2021 at 7:48 AM Dominic Raferd wrote:
>
> On 04/03/2021 11:42, Steve Dondley wrote:
> >> On 03.03.21 18:23, Steve Dondley wrote:
> >>> I have enabled the always_bcc setting with:
> >>>
> >>> always_bcc = exam...@example.org
>
>
>
>
> >-o content_filter=spamassassin
>
> the question is, how does spamassassin push mail back to postfix.
I have no earthly idea. Not sure how SA works, exactly. And it makes me
wonder if I'm breaking spam assassin by adding
-o receive_override_options=no_address_mappings
to my configuratio
> On 03.03.21 18:23, Steve Dondley wrote:
> >I have enabled the always_bcc setting with:
> >
> >always_bcc = exam...@example.org
> >
> >It works, but I'm getting everything three times. How do I prevent
> >duplicates?
>
> this can happen if you
PM Wietse Venema wrote:
>
> Steve Dondley:
> > OK, I found some guidance here:
> > http://www.postfix.org/ADDRESS_REWRITING_README.html
> >
> > Adding in "-o receive_override_options=no_address_mappings" to the
> > smtpd section worked.
> >
>
hat explains it?
On Wed, Mar 3, 2021 at 6:23 PM Steve Dondley wrote:
>
> I have enabled the always_bcc setting with:
>
> always_bcc = exam...@example.org
>
> It works, but I'm getting everything three times. How do I prevent duplicates?
--
Prometheus Labor Communication
I have enabled the always_bcc setting with:
always_bcc = exam...@example.org
It works, but I'm getting everything three times. How do I prevent duplicates?
37 matches
Mail list logo
