[pfx] Re: Reject mail by language
On 4/18/23 23:38, Viktor Dukhovni via Postfix-users wrote: > On Wed, Apr 19, 2023 at 11:33:36AM +0800, tom--- via Postfix-users wrote: > >> I got a lot of spams (20+ every day) like the following for which i even >> don't know what language they were. >> > >> مميز المنتدى العربي الثالث > > The script is Arabic. Language is harder for an MTA to deduce. A > priori any of > > - Arabic > - Farsi > - Urdu > - ... > > Though in this case actually Arabic. I'd focus more on the client IP, > sender domain, ... than the content language. If this is a private mail server for only a small number of people, any mail in a script that none of the users can read is almost guaranteed to be spam, and would not be useful even if it wasn’t. -- Sincerely, Demi Marie Obenour (she/her/hers) OpenPGP_0xB288B55FFF9C22C1.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Postfix as relay server let us send messages with anothyer domain than ours
On 4/11/23 17:24, Viktor Dukhovni via Postfix-users wrote: > On Tue, Apr 11, 2023 at 03:34:09PM -0300, Roberto Carna via Postfix-users > wrote: > >> But we have realized that if we send messages using another domains >> than ourdomain1.com, the messages reach the recipients in Gmail, >> Hotmail and other public mail platforms. > > Perhaps as well considering how to address this, you might also consider > whether you're addressing the right problem... > > When an authorised message is slated to leave your network, the > consequences are least signficant when it purports to originate from > somebody else's domain. > > - Many receiving systems are liable to reject a message purporting > to originate from an unexpected domain (based on DMARC, ...). > > - There's little risk of reputational or financial damage if > the message does not impersonate a sender in your domain. > > On the other hand, if the message *is* from your domain, but > is an unauthorised message misleading your customers or business > partners, ... *then* you have a problem. > > While Postfix can to some extent enforce envelope to sender mismatches, > the real concern is usually the "From:" header, ... whose content is not > the MSAs job to enforce. A milter must be used for this. Since this, along with DMARC, is a core responsibility of a modern MTA, I am curious if making this a part of Postfix itself (as Exim did) has been considered. -- Sincerely, Demi Marie Obenour (she/her/hers) OpenPGP_0xB288B55FFF9C22C1.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: use object storage as message store
On 3/12/23 01:21, Bill Cole via Postfix-users wrote: > On 2023-03-12 at 00:03:32 UTC-0500 (Sun, 12 Mar 2023 00:03:32 -0500) > Phil Stracchino via Postfix-users > is rumored to have said: > >> On 3/11/23 19:04, pyh--- via Postfix-users wrote: >>> Hello list, >>> >>> Is it possible to use an object storage system (like aws's S3) to >>> store >>> message files? if this can be implemented we may have a more >>> persistent >>> storage for email. AFAIK aws's S3 has three replicas for each file in >>> their system by default. >> >> >> S3 really isn't intended to be used that way. I'm not sure how you'd >> make that work and it would probably be a bad idea. > > Agreed. > > As far as Postfix specifically is concerned (i.e. the queues) S3 would > be a performance disaster. Is this because Postfix is designed assuming that queue access has low latency, and therefore does not try to hide the latency with asynchronous operations and batching? -- Sincerely, Demi Marie Obenour (she/her/hers) ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org