Re: 1.6 FORGED_MUA_MOZILLA Forged mail pretending to be from Mozilla
On 2020-09-23 at 14:46 -0500, Jerry Malcolm wrote: > My client is massively invested in AWS with many servers, databases, > and services unrelated to mail. Moving to another platform is not > an option. What is a good 'reputable' 3rd party service that I can > use as a proxy to make sure I have 'clean' mail? How is your client handling their 'normal' mails? An on-premises server? Microsoft 365 ? G Suite? Just send these communications through their normal email sending platform (get a user account and use those credentials to send through them), benefiting from the reputation their sending IPs already have for this company mails.
Re: free tlds considered as freemail ?
On 2020-11-09 at 11:42 +0100, Benny Pedersen wrote: > i mean if the tld is free, can the domain name be non free then ? Yes. Even though the TLD offers domains for free (not tlds for free :P) there is a paying layer where you can pay money for having them. I have seen a spammer use such kind of paid domain. Too bad, as it would have been simpler to have their domain canceled if iy was on the free tier. Regards
Re: awl postgresql
On 2023-01-04 at 10:24 +1300, Sidney Markowitz wrote: > If anyone else reading this is using 4.0.0 and postgres for AWL, are > you seeing or not seeing this problem? I can easily reproduce this with a quick install and manually providing the SQL from the code (output included below). Postgresql (tested on version 11) seem to be choking on the self-referential totscore in the update clause. It seems it can't assign a value from the row inside the DO UPDATE but only a constant. As a quick fix, removing the string “pg|” from the lines 309, 325, 341 and 358 will probably make the plugin work by making it use the fallback code with postgres. postgres=# CREATE TABLE awl ( postgres(# username varchar(100) NOT NULL default '', postgres(# email varchar(255) NOT NULL default '', postgres(# ip varchar(40) NOT NULL default '', postgres(# msgcount bigint NOT NULL default '0', postgres(# totscore float NOT NULL default '0', postgres(# signedby varchar(255) NOT NULL default '', postgres(# last_hit timestamp NOT NULL default CURRENT_TIMESTAMP, postgres(# PRIMARY KEY (username,email,signedby,ip) postgres(# ); CREATE TABLE postgres=# select * from awl; username | email | ip | msgcount | totscore | signedby | last_hit --+---++--+--+--+-- (0 rows) postgres=# insert into awl (username, email, ip, signedby) values ('john', 'jsm...@example.com', '127.0.0.1', '-'); INSERT 0 1 postgres=# select * from awl; username | email|ip | msgcount | totscore | signedby | last_hit --++---+--+--+--+ john | jsm...@example.com | 127.0.0.1 |0 |0 | -| 2023-01-04 02:45:24.769152 (1 row) postgres=# insert into awl (username, email, ip, signedby) values ('john', 'jsm...@example.com', '127.0.0.1', '-') ON CONFLICT (username, email, signedby, ip) DO UPDATE set msgcount = 5, totscore=totscore + 10; ERROR: column reference "totscore" is ambiguous LINE 1: ...ignedby, ip) DO UPDATE set msgcount = 5, totscore=totscore +... ^
Re: awl postgresql
On 2023-01-03 at 23:00 +0100, Benny Pedersen wrote: > https://github.com/apache/spamassassin/blob/trunk/lib/Mail/SpamAssassin/SQLBasedAddrList.pm#L289 > > $sql .= " ON CONFLICT (username, email, signedby, ip) DO UPDATE set > msgcount = ?, totscore += ?"; > > confirm is from my side needed it would fix it, i atleast like to > think it does A += doesn't (neccesarily) fix it. Perhaps it works on an higher version. postgres=# insert into awl (username, email, ip, signedby) values ('john', 'jsm...@example.com', '127.0.0.1', '-') ON CONFLICT (username, email, signedby, ip) DO UPDATE set msgcount = 5, totscore += 1; ERROR: syntax error at or near "+=" LINE 1: ...il, signedby, ip) DO UPDATE set msgcount = 5, totscore += 1; ^