Reputation
1,168
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
1 11 32
Impact
~67k people reached

Jun
18
comment ansible lineinfile escaped quotes go missing
@tedder42 This is invalid yaml syntax and doesn't work.
Jun
7
comment Can't enter the letter 'e' over ssh
Thanks, @EricRenouf, this helped me solve the problem! Check my answer for details if you are interested.
Jun
1
comment ansible print debug msg variable
Thanks! This works.
Jun
1
comment ansible print debug msg variable
ok: [127.0.0.1] => { "var": { "mosh_version.stdout_lines": [ "mosh 1.2.4a [build mosh-1.2.4-57-g9eeb2fb]" ] } } this works, I'd really prefer the custom message though ;-)
Jun
1
comment ansible print debug msg variable
There are no more syntax errors, but it doesn't work either: TASK: [ Print mosh version] ************************************** ok: [127.0.0.1] => { "msg": "Mosh" }
Jun
1
comment ansible command with_items
Can you explain the difference between command: "{{ item.command }} creates={{ item.file}}" and command: "{{ item.command }}" creates="{{ item.file}}"?
May
6
comment Reject incoming emails that use your own domain as sender
@masegaloeh Ahh, I see now. You are quite an postfix expert :-) Do you have any idea how much this check would cost (IO-wise) in comparison to the other two methods in my answer?
May
6
comment Reject incoming emails that use your own domain as sender
@masegaloeh Yeah but then legitimate senders couldn't use their domains either, because they are not listed in my virtual domains/destinations? :D
May
6
comment Reject incoming emails that use your own domain as sender
@masegaloeh It rejects all unkown sender addresses? How would that help?
May
6
comment Reject incoming emails that use your own domain as sender
@masegaloeh Can you explain? man postconf wasn't really clear on what reject_unlisted_sender does, it seemed to me that it does reject ALL unknown senders? (postfix.org/postconf.5.html#reject_unlisted_sender) Maybe it's a better way to do it than what I did.
May
6
comment Reject incoming emails that use your own domain as sender
@Dan look at the second method I listed, it is very similar to what you suggested.
May
5
comment Reject incoming emails that use your own domain as sender
Please have a look at my note regarding SPF/DKIM in the question.
May
5
comment Reject incoming emails that use your own domain as sender
Please have a look at my note regarding SPF/DKIM in the question.
May
5
comment is it possible to completely disable spamassassin using spamassassin user_prefs
Yeah. I suppose you mean to use transport_maps and have a 'non-filtering' transport with -o content_filter= or what's your idea?
May
5
comment How to reinject scanned mail into the queue using sendmail
One more note: I couldn't find very much information in regard to "final destination" transports in postfix and this suggests a different reason why virtual_transport can't be changed using -o virtual_transport=... Can you elaborate on this a bit more?
May
5
comment How to reinject scanned mail into the queue using sendmail
Perfect! That's exactly what I wanted to achieve.
May
5
comment How to reinject scanned mail into the queue using sendmail
Ah, right. Shouldn't content_filter via ACCESS table and FILTER action work even without another complete list of the virtual domains using the following setup: smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, check_sender_access regexp:$config_directory/apply_content_filter, permit and a apply_content_filter with content /.*/ FILTER spamassassin:dummy? Or are there any caveats/downsides to this?
May
3
comment How to reinject scanned mail into the queue using sendmail
Hi, thanks for the answer! I got a question about the simple filter setup: How does this not end in a loop without content_filter= in the pickup transport?
May
2
comment is it possible to completely disable spamassassin using spamassassin user_prefs
..another layer of complexity, like amavis. But I already explained all this in my previous comments...
May
2
comment is it possible to completely disable spamassassin using spamassassin user_prefs
Of course mails with multiple recipients (aka RCPT TO) get treated as multiple mails by MTAs, atleast when configured to so (in postfix: transport_destination_recipient_limit = 1). The option whitelist_to is however NOT only checking the RCPT TO envelope, but also various other headers (listed above), which can be set to anything by a potential spammer. I want to do exactly what you described, use the SQL user preferences (which already exist for spamassassin!) to decide whether mail should be scanned by SA or not. My question was about doing this with spamassassin, not by introducing..