Hi,
I am currently allowing "trusted" network IP addresses to send/relay
e-mail, as well as allowing SASL authenticated users to do the same
from whichever IP address (but enforcing MAIL FROM to be
username@mydomain). Both of these can send/relay e-mails to external
domains.
Now, I'd like to do t
On Wed, Oct 07, 2020 at 12:27:09AM +, Pau Peris wrote:
> I'm hosting my dad's webpage which has a contact form (which should be
> improved to avoid spam and/or bots) and from time to time someone
> types multiple email addresses in the from field of the form so
> contact emails with multiple f
Postfix version: 3.1.1
Hello List!
We have a customer with a setup of enforcing a match between account FROM
address and sasl username.
With the following this works as expected...
smtpd_reject_unlisted_recipient = yes
smtpd_reject_unlisted_sender = yes
smtpd_sender_login_maps = proxy:ldap:/o
I'm hosting my dad's webpage which has a contact form (which should be
improved to avoid spam and/or bots) and from time to time someone
types multiple email addresses in the from field of the form so
contact emails with multiple from addresses like "from:
h...@example.com, f...@example.net" are ge
On 10/6/2020 3:56 PM, Frank DiGennaro wrote:
Thanks for the reply. This is what I have in my 'virtual_users' file
verbatim. I've even kept the domain names and users the same.
# Regexp# User to forward to
/\d{10,}@fax.mobilepbx.net/ asterisk (I
On 10/6/2020 6:52 PM, Pau Peris wrote:
Hi,
is there a sender restriction to reject a message with multiple from
addresses? Which would be?
Thanks,
If you're seeing multiple addresses in a single From: header you may
be able to carefully craft a header_checks to detect them, but
detecti
Frank DiGennaro:
> Thanks for the reply. This is what I have in my 'virtual_users' file
> verbatim. I've even kept the domain names and users the same.
>
> # Regexp # User to forward to
> /\d{10,}@fax.mobilepbx.net/ asterisk (I've tried both
That is
Hi,
is there a sender restriction to reject a message with multiple from
addresses? Which would be?
Thanks,
--
Pau
Aquest correu electrònic conté informació de caràcter confidencial
dirigida exclusivament al seu/s destinatari/s en còpia present. Tant
mateix, queda prohibida la seva divulgació,
Thanks for the reply. This is what I have in my 'virtual_users' file
verbatim. I've even kept the domain names and users the same.
# Regexp# User to forward to
/\d{10,}@fax.mobilepbx.net/ asterisk (I've tried both
\d{10,} and [0-9]{10,} without s
Demi M. Obenour:
> On 10/6/20 12:46 PM, Wietse Venema wrote:
> > Demi M. Obenour:
> >> On 10/6/20 9:47 AM, Wietse Venema wrote:
> >>> allow 'not found' users, similar to smtpd_sender_login_maps
> >>
> >> Would it be possible to make this configurable? The documentation
> >> seems to imply that rej
On 10/6/20 12:46 PM, Wietse Venema wrote:
Demi M. Obenour:
On 10/6/20 9:47 AM, Wietse Venema wrote:
allow 'not found' users, similar to smtpd_sender_login_maps
Would it be possible to make this configurable? The documentation
seems to imply that reject_sender_login_mismatch considers ?not
fo
Frank DiGennaro:
> All;
>
> I've made progress with this problem. By adding virtual_alias_maps =
> regexp:/etc/postfix/virtual_users at the bottom of main.cf and adding the
> regexps below, and running "postmap /etc/postfix/virtual_users ", the two
> catch-alls work fine, but the "longer" matc
All;
I've made progress with this problem. By adding virtual_alias_maps =
regexp:/etc/postfix/virtual_users at the bottom of main.cf and adding the
regexps below, and running "postmap /etc/postfix/virtual_users ", the two
catch-alls work fine, but the "longer" matches do not and ultimately the
Demi M. Obenour:
Checking application/pgp-signature: FAILURE
-- Start of PGP signed section.
> On 10/6/20 9:47 AM, Wietse Venema wrote:
> > Demi M. Obenour:
> >> Patch (made against 3.5.7) attached. I lightly tested it locally and
> >> it seems to work, but there could very well be bugs. I am vi
On 06/10/2020 00:05, Wietse Venema wrote:
> John Fawcett:
>> Actually to be more precise: is it guaranteed to return not null and
>> with all the function pointers in the returned dict struct also not
>> null. I'm adding this because I think it does always return something
>> not null, but I'm not
On 10/6/20 9:47 AM, Wietse Venema wrote:
Demi M. Obenour:
Patch (made against 3.5.7) attached. I lightly tested it locally and
it seems to work, but there could very well be bugs. I am virtually
certain that I violated the Postfix coding style somewhere, sorry.
I can also send the patch inline
Demi M. Obenour:
Checking application/pgp-signature: FAILURE
-- Start of PGP signed section.
> On 10/5/20 6:15 PM, Wietse Venema wrote:
> > Demi M. Obenour:
> >> There was a recent vulnerability in OpenBSD due to libc malfunctioning
> >> in a set-uid-root program under very low resource limits. I
17 matches
Mail list logo