still the way to deal
with such situations in 2020?
There is not much we can do to get rid the forwards, and we have many of
them, so a good solution would be welcome. :-)
We are running debian 10, btw.
Thanks!
MJ
...perhaps consider running it on a seperate machine. (perhaps even
a VM on your samba ADDC)
MJ
On 5/27/20 12:40 PM, Nick Piggott wrote:
Hi,
I'm not able to suppress the DOMAIN element of the username part on
*this* machine.
All the machines in the AD have a directive in their /etc/samba/smb.conf
, and not a local
account, or DOMAINB\username.
But in common practise, we never login anywhere with DOMAIN\username
And we also never have the issues you are describing, and no need fotr
mappings of any kind.
Are you *sure* you need your usernames in that format?
MJ
On 26/05/2020 13:50, Nick Piggott
would consider delivering mail back to the mailbox of u...@ourdomain.com
or maybe postmas...@ourdomain.com
So, if I understand correctly, I would set something like:
sieve_redirect_envelope_from = "<dedicated_u...@merit.unu.edu>"
(dovecot.conf)
Thanks again!
MJ
like to prevent NDRs for these
sieve-forwarded messages.
Is there a way to achieve this?
If it helps: the sieve-forwards are mostly to very few foreign domains,
so perhaps we could filter NDRs at some stage, based on coming-from
domain..?
Best regards,
MJ
get rid of this.
MJ
On 03/23/2018 12:58 AM, mj wrote:
Is there perhaps also another error code we can use, that blackholes the
email, instead of politely bouncing it with a "Diagnostic-Code:
X-Postfix; Destination domain blacklisted"?
I just found the "discard" option.
Thanks you again, Viktor!
MJ
it just for the time being, until we have
fixed the webform.
Your solution works super, thanks a lot!
Is there perhaps also another error code we can use, that blackholes the
email, instead of politely bouncing it with a "Diagnostic-Code:
X-Postfix; Destination domain blacklisted"?
MJ
REJECT
I postmapped the file and restarted postfix.
Alas... postfix is still happily forwarding emails to 1...@mail.ru to my
smarthost.
How can I make sure that this particular postfix instance will DISALLOW
sending ANY email to @mail.ru?
What am I missing?
Thanks in advance!
MJ
Here
Hi Wietse,
Super! I'll checkout the information provided.
Thanks a lot, it's appreciated! :-)
MJ
On 02/01/2018 04:04 PM, Wietse Venema wrote:
mj:
Anyone..?
On 01/30/2018 02:55 PM, lists wrote:
Hi,
The question can perhaps be made more generic like this:
Can postfix generate a *specific
e accounts
(with instructions who to contact to revert the situation) it would be
very easy: only move the user to the specific OU, and have the system do
the rest.
Can this be done?
(postfix 2.11.1 from debian wheezy, yes we know we should upgrade, and
we also will, but it runs rock solid...)
MJ
We're very happy with sogo. (https://sogo.nu/)
MJ
On 12/27/2017 08:40 AM, Philip Paeps wrote:
On 2017-12-27 13:08:44 (+1030), Mal wrote:
Interested to hear from those running a Postfix(MTA)/Dovecot(IMAP)
combo on what contacts & calendar server projects they are having
success with.
I
On 09/02/2017 01:16 PM, Patrick Ben Koetter wrote:
Mandatory STARTTLS*and* disallowing any shared-secret mechanism (CRAM-MD5,
DIGEST-MD5, NTLM) is a clever move.
This way you protect the identity while it is transported from the client to
the server and you are able to store the passwords
Hi,
Ok, so disallowing LOGIN is not a clever move :-)
Thanks for your answers!
MJ
On 09/02/2017 08:32 AM, Patrick Ben Koetter wrote:
* postfix <post...@ayni.com>:
On 09/01/2017 04:25 PM, mj wrote:
Just a small question: we currently use posfix with sasl authentication,
and folowin
clients use what auth type. So, are
all/most modern clients capable of doing PLAIN? (thunderbird, outlook
2010/2013) so could I simply disallow LOGIN?
MJ
Hi!
Right! Remove permit_sasl_authenticated and keep check_sasl_access
hash:/etc/postfix/sasl_list
Thanks! It works!
MJ
see much difference..? (except the indexed = $)
What am I missing/not seeing?
MJ
is postfix 2.11.2
MJ
Hi all,
On 08/08/2017 04:05 PM, Wietse Venema wrote:
mj:
In smtpd_client_restrictions, use check_sasl_access:
Thanks very much, for the replies, both on- and off-list!
MJ
. Is there a way to restrict that?
A simple list of usernames would work, or more advanced: dynamically
using an ldap lookup to check group membership.
Thanks in advance for pointers/tips,
MJ
features, this should improve delivery
with Yahoo MX.
Kind regards,
Olivier
--
Olivier MJ Crépin-Leblond, PhD
http://www.gih.com/ocl.html
--
Olivier MJ Crépin-Leblond, PhD
http://www.gih.com/ocl.html
yahoo.fr, yahoo.co.uk etc.)
I don't think that it's a Postfix problem at all because only Yahoo
causes this, so it much more likely to be a Yahoo problem.
Kind regards,
Olivier
--
Olivier MJ Crépin-Leblond, PhD
http://www.gih.com/ocl.html
of
the problem?
I have no trouble with reverse IPv6 DNS in my postfix headers. Looks
like a local DNS config error or mis-delegation.
Either way, I don't think it's a postfix issue at all.
--
Olivier MJ Crépin-Leblond, PhD
http://www.gih.com/ocl.html
issue either. Our sendmail-based MX have the same problem.
Kind regards,
--
Olivier MJ Crépin-Leblond, PhD
http://www.gih.com/ocl.html
Use the notation with the square brackets:
[::1]:10028
They are used to differentiate the colon used for separaring the port,
as opposed to a colon which is part of the IPv6 address.
Olivier
--
Olivier MJ Crépin-Leblond, PhD
http://www.gih.com/ocl.html
- Original Message -
From
What I meant Martin was that there was a space in the destination word, which
was written as destina tion rather than destination.
If you make
smtpd_recipient_restrictions = permit_mynetworks, reject_unauth_destination
Does it work?
Olivier
--
Olivier MJ Crepin-Leblond, Ph.D
Global
Also check SElinux if you are running this. It may prevent changes to the port
config from taking place.
You can see entries in the logfile called /var/log/messages
Regards,
Olivier
--
Olivier MJ Crepin-Leblond, Ph.D
Global Information Highway Ltd
http://www.gih.com/ocl.html
Dear Wietse,
thank you for your detailed explanation.
In the future, would you consider having unique identifiers generated
by an algorithm which would take into account the CPU ID (or other
unique identifier), process ID time, so as to make it a unique ID
worldwide, or is this not something
kill
all spam, but will also kill legitimate emails, and I'm not sure how your
clients will know about an email they did not receive. As others have said,
be careful because this might bite you back at some point.
On the other hand, it's your network so do as you see fit.
Cheers,
--
Olivier MJ
.
Regards,
Olivier
--
Olivier MJ Crepin-Leblond, Ph.D.
E-mail:[EMAIL PROTECTED] | http://www.gih.com/ocl.html
- Original Message -
From: Diego Ledesma [EMAIL PROTECTED]
To: Алексей Доморадов [EMAIL PROTECTED]
Cc: postfix-users@postfix.org
Sent: Friday, September 12, 2008 8:51 PM
Subject
STARTTLS command used when not advertised.
check your docs on how to disable smtp filtering in your firewall (look
for somthing like no ip inspect name yourrulename smtp...).
That solved it! Thank you very much to you Noel.
O.
--
Olivier MJ Crepin-Leblond, Ph.D.
E-mail:[EMAIL PROTECTED] | http
32 matches
Mail list logo
