Re: [spamdyke-users] TLS and LibreSSL

[BC via spamdyke-users]

Thank you, Sam.  I wentwith the traditional OpenSSL just to be sure.


On 6/4/2018 8:06 PM, Sam Clippinger via spamdyke-users wrote:
I have no idea -- I've never used LibreSSL.  As long as they've only 
updated the internal library code and not changed the API, it'll 
probably work fine.


-- Sam Clippinger




On May 26, 2018, at 2:42 PM, BC via spamdyke-users 
mailto:spamdyke-users@spamdyke.org>> 
wrote:




Will spamdyke compile with TLS using the LibreSSL libraries?


___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
https://spamdyke.org/mailman/listinfo/spamdyke-users

Re: [spamdyke-users] TLS and LibreSSL

[Sam Clippinger via spamdyke-users]

I have no idea -- I've never used LibreSSL.  As long as they've only updated 
the internal library code and not changed the API, it'll probably work fine.

-- Sam Clippinger




On May 26, 2018, at 2:42 PM, BC via spamdyke-users 
 wrote:

> 
> Will spamdyke compile with TLS using the LibreSSL libraries?
> 
> ___
> spamdyke-users mailing list
> spamdyke-users@spamdyke.org
> https://spamdyke.org/mailman/listinfo/spamdyke-users

___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
https://spamdyke.org/mailman/listinfo/spamdyke-users

Re: [spamdyke-users] ip-whitelist-entry Not Working

[Sam Clippinger via spamdyke-users]

Yes and no -- comment delimiters are only allowed at the start of a line, not 
in the middle (allowing mid-line comments would have required making the config 
file parser much smarter).  However, because the parser is expecting to find an 
IP address on each line and the line begins with an IP address, it matches.  
Technically that's a bug... but it's helpful in this case.

If the message "FILTER_WHITELIST_IP" is appearing, the IP is matching the entry 
and the connection is being whitelisted; the message should be getting 
delivered.  What other log messages are you seeing from spamdyke?  Are there 
any DENIED log entries?  If you aren't seeing either ALLOWED or DENIED, the 
client isn't completing the SMTP transaction for some reason.  Sometimes this 
happens when spamdyke injects its output into the SMTP transaction and a client 
is written to expect a very specific response.  I suggest using the 
full-log-dir option to capture the entire transaction to a file so you can see 
exactly what each side is sending and where the connection is being broken.

-- Sam Clippinger




On Jun 3, 2018, at 1:41 PM, Eric Broch via spamdyke-users 
 wrote:

> can you have a comment (# philsdiscourse) on your IP whitelist entry line? 
> maybe, remove '#philsdiscourse'  and see what happens.
> 
> 
> On 6/3/2018 12:05 PM, Philip Rhoades via spamdyke-users wrote:
>> People,
>> 
>> I am trying to use my host qmail server as a relay for a docker container 
>> that is running on the host but mails are not being accepted - I have this 
>> in spamdyke.conf:
>> 
>>   ip-whitelist-entry=172.17.0.6 # philsdiscourse
>> 
>> and I see this in the logs:
>> 
>>   Jun  4 03:53:59 prix spamdyke[28801]: FILTER_RDNS_MISSING ip: 172.17.0.6
>>   Jun  4 03:53:59 prix spamdyke[28801]: FILTER_WHITELIST_IP ip: 172.17.0.6 
>> entry: 172.17.0.6 # philsdiscourse
>> 
>> but there is no ALLOW line that follows and the mail fails to be delivered - 
>> what am I missing?  If I use swaks from the container, mail does get 
>> delivered OK but that is because spamdyke is being bypassed . .
>> 
>> Thanks,
>> 
>> Phil.
> 
> -- 
> Eric Broch
> White Horse Technical Consulting (WHTC)
> 
> ___
> spamdyke-users mailing list
> spamdyke-users@spamdyke.org
> https://spamdyke.org/mailman/listinfo/spamdyke-users

___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
https://spamdyke.org/mailman/listinfo/spamdyke-users