On Tue, Jan 10, 2023 at 05:10:41PM -0800, Dan Mahoney wrote:
> Construct an email like this:
>
> To: support-st...@dayjob.org
> From: Support Staff
> BCC: internal-al...@dayjob.org
So far, so good. Presumably, once this leaves the MUA, the initial
envelope the MUA hands off to the MSA (or
Dan Mahoney skrev den 2023-01-11 02:10:
So much for keeping our company domain off of the postfix mailling
lists, LOL. Redacting moving forward.
lol https://webrate.org/site/dayjob.com/
example.org is better choise since its designed for examples
rule of thump do not use domains not owned
So much for keeping our company domain off of the postfix mailling lists, LOL.
Redacting moving forward.
Rather than try to reply to every point you cited, let me start over:
Our process to send to this list would do the following:
Construct an email like this:
To: support-st...@dayjob.org
Charles Sprickman skrev den 2023-01-11 00:43:
Any pointers on what direction to go with this?
start postconf -e "smtpd_sasl_authenticated_header = no" or remove it in
main.cf or master.cf overrides, its not needed to add your sasl auth
user logins to send mails
i use roundcube webmail so
Howdy,
I'm thinking that for my personal mail server I would like to stop showing the
world the IP that I'm sending email from, for various reasons, but mostly
privacy.
I see lots of sketchy options out there using header checks, but I'd ideally
like to not just strip out the first received
On Tue, Jan 10, 2023 at 03:02:36PM -0800, Dan Mahoney wrote:
> We are already using the alias-function as you suggest:
>
> support-contacts: support-st...@isc.org,
> :include: /usr/local/etc/rt42/contact-alias.lst
I don't see an "owner-support-contacts"
Viktor,
I apologize for the off-list email — I would like to add some context here, but
also not mention my day job by name specifically on a public mailing list.
We are already using the alias-function as you suggest:
support-contacts: support-st...@isc.org,
On Tue, Jan 10, 2023 at 01:07:40PM -0800, Dan Mahoney wrote:
> Does anyone know of a simple remailer tool that can be used inside an
> aliases (via a pipe) file that will:
If you configure:
# Add explicit domain if $myorigin is not right here
owner-somelist: somelist-request
All,
Does anyone know of a simple remailer tool that can be used inside an aliases
(via a pipe) file that will:
* ‘explode’ messages out to a group statically defined in a textfile.
* not expose my original envelope sender and recipients?
Office365 is rejecting when they see our internal alias
This requires a milter or other content filter.
Wietse
Happy new year everybody,
I have a filter in my header_checks file that redirects messages send to
undisclosed recipients
to a mailbox to monitor and fw to intended users if of any value like
this :
/(^To:\ undisclosed-recipients\:\;)|(To:\ undisclosed-recipients\:\ ;)/
REDIRECT
11 matches
Mail list logo
