s beyond the capabilities of what I was initially thinking of.
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
On 13/08/18 21:19, @lbutlr wrote:
> On 12 Aug 2018, at 17:29, Stuart Longland wrote:
>> We have a problem where some smart-arse spammers/phishers are spoofing
>> the From address, specifying our domain as their from address. In one
>> case, the person in question uses my pe
e from the internal network. i.e.
if client_ip not in 192.168.0.0/16:
header_checks = regexp:/etc/postfix/incoming_header_checks
then in that incoming_header_checks I can block it with:
/^(Return-Path|From): .*@longlandclan.id.au>$/ REJECT
The alternative of course is to do some
ver which should open
the floodgates and let all the mail for our office flood to the newly
configured mail infrastructure.
Many thanks.
Regards,
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
signature.asc
Description: OpenPGP digital signature
ut that should be an easier job.)
Is it possible to nominate both servers as being the destinations for
both domains so that a single email sent to user@domain is sent to both
internal servers?
Regards,
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's
nt inside the PGP message (probably
discarding anything outside). You want to avoid changing things between
BEGIN and END though because that might cause signature invalidation.
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
signature.asc
Description: OpenPGP digital signature
On 12/09/15 08:24, Stuart Longland wrote:
> This is just a wild guess on my part, but could that possibly be matching:
>
>> > -BEGIN BLAH-
>^^^
>> > yadda yadda yadda
> ^
>> > -END BLAH-
> ^^^
^^
> yadda yadda yadda
^
> -END BLAH-
^
and giving you: $1="BEGIN", $2=" BLAH-\r\nyadda yadda
yadda\r\n-END BLAH"?
What happens if you try
/[ \t\r\f]*-(BEGIN|END)([A-Z ]*)-[ \t\r\f]*/ REPLACE -$1$2-
Original-To: m...@vk4msl.yi.org
Delivered-To: stua...@longlandclan.yi.org
although the following is fine too:
Return-Path:
X-Original-To: stua...@longlandclan.yi.org
Delivered-To: stua...@longlandclan.yi.org
X-some-other-header: m...@vk4msl.yi.org
(where X-some-other-header maybe gets repeated, that is fine
