Sam, thank you very much for your answer. It is as you describe ... header
without the "From"
Ej:
Oct 4 01:08:44 ns spamdyke[15166]: ALLOWED from: (unknown) to:
i...@dominio.cl origin_ip: 157.55.234.249 origin_rdns:
mail-db3hn0249.outbound.protection.outlook.com auth: (unknown) encryption:
Sam,
On 2015-10-12 09:45, Sam Clippinger via spamdyke-users wrote:
I'm not sure I understand your question. If you want to block messages
without a "From" line in their header, spamdyke can't do that. You may
be able to use a secondary filter like maildrop to delete the message
after it is
I guess so, but remember the wildcarding uses globbing, not regexes. What I
mean is: using "?*" is equivalent to just "*". Also, the line has to contain
at least one colon or spamdyke won't use it (message headers always use a colon
to separate the field name from the value).
Why not just
On 2015-10-02 15:42, Philip Rhoades via spamdyke-users wrote:
Sam,
On 2015-09-26 01:12, Sam Clippinger via spamdyke-users wrote:
The header blacklist file has a different format from the sender
blacklist file, so just copying entries from one to the other won't
work. You need to provide a
Sam,
On 2015-10-02 23:47, Sam Clippinger via spamdyke-users wrote:
I guess so, but remember the wildcarding uses globbing, not regexes.
What I mean is: using "?*" is equivalent to just "*".
Right.
Also, the line
has to contain at least one colon or spamdyke won't use it (message
headers
Sam,
On 2015-09-26 01:12, Sam Clippinger via spamdyke-users wrote:
The header blacklist file has a different format from the sender
blacklist file, so just copying entries from one to the other won't
work. You need to provide a pattern that matches the line(s) in the
message header -- in your
Martin,
On 2015-09-26 22:10, Martin H. Sluka via spamdyke-users wrote:
Sam wrote:
For testing, you certainly can use telnet -- I do it all the time.
Tip: You might want to have a look at Swaks (Swiss Army Knife
for SMTP, http://www.jetmore.org/john/code/swaks/).
I find it very convenient
Sam wrote:
> For testing, you certainly can use telnet -- I do it all the time.
Tip: You might want to have a look at Swaks (Swiss Army Knife
for SMTP, http://www.jetmore.org/john/code/swaks/).
I find it very convenient for testing and monitoring purposes,
especially if you want to perform
The header blacklist file has a different format from the sender blacklist
file, so just copying entries from one to the other won't work. You need to
provide a pattern that matches the line(s) in the message header -- in your
mail client, you should have an option to "view message source" or
Sam,
On 2015-09-15 07:27, Sam Clippinger via spamdyke-users wrote:
Actually, no. The sender-blacklist-* and recipient-blacklist-* filters
operate on different data from the header-blacklist-* filters. The
reason is because the sender and recipient addresses are given during
the SMTP protocol
Actually, no. The sender-blacklist-* and recipient-blacklist-* filters operate
on different data from the header-blacklist-* filters. The reason is because
the sender and recipient addresses are given during the SMTP protocol and
aren't part of the message itself -- the addresses you see in
People,
One variety of spam that is successfully delivered to me has a different
"From:" addresses but the same "Reply-To:" address - I can't see a way
of blocking these mails in the conf file via the "Reply-To:" address -
is it possible?
Thanks,
Phil.
--
Philip Rhoades
PO Box 896
Cowra
Sam,
On 2015-09-14 11:38, Sam Clippinger via spamdyke-users wrote:
I'm not entirely sure I understand your question... if the Reply-To
address is always the same, you should be able to block it using the
header blacklist filter.
Ah . . OK - I will try that but doesn't that mean that:
I'm not entirely sure I understand your question... if the Reply-To address is
always the same, you should be able to block it using the header blacklist
filter. If you're wanting to compare the Reply-To address to the From address
or the sender address, spamdyke doesn't have that ability.
--
14 matches
Mail list logo
