>> On Tue, 7 Mar 2023, John Stoffel via Postfix-users wrote:
>>
>>> So what's the option for a more upto date version of DKIM milter for debian?
>>
>> rspamd does DKIM, SPF, DMARC and ARC (and lots more), and doesn't segfault
>> (so
>> far ;-)
>
>
>I'm STILL trying to figure out rspamd's documenta
>Michael W. Lucas is writing a book about "Run Your Own Mail Server"
>featuring the Postfix mail server. Michael has written and published a
>Chapter 0 that gives an impression what the book will contain. Besides
>the technical aspects, the book will cover the email ecosystem and how
>to fit well i
>>Michael W. Lucas is writing a book about "Run Your Own Mail Server"
>>featuring the Postfix mail server. Michael has written and published a
>>Chapter 0 that gives an impression what the book will contain. Besides
>>the technical aspects, the book will cover the email ecosystem and how
>>to fit w
Client has an appliance (Axion RTAC) that sends email based reports. I don't
have access to the appliance or its docs. It used to send its emails to an
Exchange server that has been decommissioned. I'm trying to get it to send to
my postfix server. I have it whitelisted for postfix checks.
I need to allow a domain to bypass my RBL checks. I'm doing something wrong,
or I'm misunderstanding what I'm checking from my logs. I'd be grateful for an
assist to remedy.
This box is an old postfix install Postfix version 2.2.10. (I know, working on
migrating)
main.cf: (full postcon
>I can tell you there is significant spam from that Microsoft IP space. That
>spamcop doesn't have false positives, but rather due to >the sharing of IP
>space, senders that aren't spammers get tarred with the same brush as the
>spammers. I did a grep on the maillog >files and that is a firehos
>Scott Techlist via Postfix-users:
>> I need to allow a domain to bypass my RBL checks. I'm doing something
>> wrong, or I'm
>misunderstanding what I'm checking from my logs. I'd be grateful for an
>assist to remedy.
>>
>
>> check_sender_access hash:/etc/postfix/sender_checks,
>
>That directive checks the email address which is used in the SMTP MAIL
>FROM command.
>
>I believe you need to use check_client_access to check the verified
>client hostname instead of check_sender_access.
>
>
Bill & Noel, thank you both f
>>Depending on whether omain is client or sender or ...
>>
>>...
>>reject_unauth_destination
>>...
>>check_client_access hash:/pathname
>>reject_rbl_client example.com
>>...
>>
>>Or
>>
>>...
>>reject_unauth_destination
>>...
>>check_sender_access hash:/pathna
Noel:
As I understand from your explanation, if I keep my
parent_domain_matches_subdomains = smtpd_access_maps
Then the preceding dot format is moot/not needed. Only
outbound.protection.outlook.com OK
Check.
>The reason it doesn't work is you're confusing sender and client.
In
>All of these entries are using the LOGIN mech. Unless you have an
>extremely old outlook express MUA (or similar) you xan and should be
>using the PLAIN mech. You can eliminate all of the above attacks by
>removing LOGIN from the list of mechs you accept.
Peter:
I too see a lot of these so I w
>The web form results in an automated email saying, "Your ip addresses are not
>blocked." from Comcast. This is a difficult group to interact with.
Last time I went through this I found they were using some 3rd party scoring
company. And for a small server like mine, I wasn’t even on that c
12 matches
Mail list logo
