But you need Dovecot or something similar and eventually an email client, so I don't quite follow you here. You have a client, they have filters, so just use that filter. Now if you want to set up a system where t
"As a relatively simple example, I use amavisd-new and Spamassassin to
flag mail with a spam header. Then Dovecot LMTP with sieve looks for
this header and if it is present it delivers to the user's "Spam" folder."
Well this is interesting. I have a similar setup for postfix. With my desktop
em
On 27/06/16 15:50, Chip wrote:
> So to be clear SPF and DKIM milters have the ability to add headers,
The milter protocol does, and I believe that the vast majority of SPF
and DKIM milters available can do so.
> then the MDA can make a decision on *that* header
Correct, but you need to use a 3rd
So to be clear SPF and DKIM milters have the ability to add headers,
then the MDA can make a decision on *that* header - I don't want any
more processing based on headers, sender and recipient as the whole
shebang prior to the MDA was supposed to take care of the most critical
part - was it SPF
On 27/06/16 08:44, Chip wrote:
> John Doe receives email at john...@abc.com.
>
> He is ONLY to receive email that is fully DKIM and/or SPF compliant from
> anyone at the xyz.com company.
[Summary: the rest would go to another folder]
This is fairly simple to do, but does require some external co
Well the detection and rewrite is the hard part. ;-) But now I'm convinced it is the only solution at the server side, and really the best solution. Postfix has so many places to hook that I bet it could be done.
Ok this is good. But the project cannot use mail clients, only mail
servers because post processing calls other programs not related to
postfix or exim or any program similar.
Now the idea of rewriting subject is the best I've heard so far - is
there a facility in Postfix to do that based on
I think that is in the Claws email client. To do this filtering in postfix, you would need a "parallel" mailbox to place the suspect messages. Then your client would just read both the good mailbox and the bad mai
Very interesting and thanks for sending.
Now if you look at the command line, reproduced below, is that a command
line calling a file that contains the message(s) to be examined, or is
this something put in Postfix somewhere? Pardon my ignorance.
To add SPF filtering, add a filter with cond
I'd say you are onto something. http://www.willamowius.de/claws-spf.htmlUnfort
There is dkimverify and spfquery, two command line tools that you can
run against a message in the first case and a domain with ip in the
second case.
Trivial to put in a script and run against messages for sorting.
No?
On 06/26/2016 09:14 PM, li...@lazygranch.com wrote:
It does look like S
It does look like SpamAssassin has a SPF hook. https://spamassassin.apache.org/
This projects is not for normal email delivery but an esoteric use not
usually associated with email - can't really divulge more but I'm starting
to see no easy solution. There are spf scripts that can run against files
separately from the stuff built into spam assassin and postfix/exim etc.
On Jun
Well maybe. If your client supports extra folders per each mailbox and you can
access those folders, then yes. Most clients do have such folders, but the are
designed to be used with "filters" built in the client. The filters probably
aren't sophisticated enough to check DKIM or SPF, which is w
Thanks,
So it just may be easier to deliver all messages to a folder then have a
cron job run some spf/dkim checking script against the emails.
On 06/26/2016 05:53 PM, Bill Cole wrote:
On 26 Jun 2016, at 16:44, Chip wrote:
I'm wondering if Postfix can do the following easily.
Nope, not *e
That was my conclusion, but I figured to wait for a guru to comment.
My understanding is there is a plugin for Thunderbird that checks DKIM and/or
SPF. I no longer run Thunderbird, so I didn't pursue this. But it seems to me
this is better handled at the client.
If someone comes up with a way
Thanks again for your help. I found out that thunderbird, etc was
ignoring the SSL/TLS AUTH "requirement" and sending the data over the
TLS without authentication (since it was on the local network, it would
send successfully). The android was not as forgiving since it always was
on the remote
Yeah, I you're right. The auth login I was seen was for putting the sent
email into dovecot's sent folder, NOT for logging into the smtp server.
So SASL is needed for TLS, but not for plain text. I'll go back to the
drawing board with enabling SASL.
Sorry, been dealing with sendmail, haven't u
On 26 Jun 2016, at 16:44, Chip wrote:
I'm wondering if Postfix can do the following easily.
Nope, not *easily*.
It's a real dog to get this setup in Exim.
Or Sendmail, or probably ANY MTA that isn't tightly integrated to robust
local delivery, mailstore, and mail access subsystems OR whic
OK, perhaps I don't understand. I am not using saslauthd at all. It's
not even installed.
Why do other clients (e.g.: Thunderbird, Apple Mail) work and do an
authentication just fine over TLS (breaking RFC I guess because it's
still not advertised as per debug_peer logging)?
However, if I c
On 26 Jun 2016, at 17:17, E M Recio wrote:
> smtpd_sasl_auth_enable = no
That's your problem right there...
Bill,
Thanks for the feedback. I will update the configuration to use port
587, disabling SMTP AUTH on 25 completely, as soon as I get this working
at all. As per the debug documentation, attached is the skimmed down
output from the commands in the documentation.
Postconf -n and postconf -Mf
I'm wondering if Postfix can do the following easily. It's a real dog
to get this setup in Exim.
Here is the scenario.
John Doe receives email at john...@abc.com.
He is ONLY to receive email that is fully DKIM and/or SPF compliant from
anyone at the xyz.com company.
Sometimes people send J
On 26 Jun 2016, at 15:55, E M Recio wrote:
So I have TLS and AUTH working just fine in almost every email client
that I use. I have confirmed that it's encrypted, and authenticating
correctly, so my settings are OK (for those two things used together).
The problem I am having is when enabling
So I have TLS and AUTH working just fine in almost every email client
that I use. I have confirmed that it's encrypted, and authenticating
correctly, so my settings are OK (for those two things used together).
The problem I am having is when enabling the following feature:
smtpd_tls_auth_only
25 matches
Mail list logo
