Search results

  1. L

    Task history doesn't show backups anymore

    Other task logs look normal. Partial output from journalctl from yesterday. Nothing unusual afaics. Nov 21 22:30:12 atl-vm03 proxmox-backup-proxy[333160]: starting new backup on datastore 'atl-vm04': "vm/109/2022-11-21T21:30:04Z" Nov 21 22:30:12 atl-vm03 proxmox-backup-proxy[333160]: download...
  2. L

    Task history doesn't show backups anymore

    No new ones are showing up. I can still see the old ones. Backup jobs are still running successfully, yes.
  3. L

    Task history doesn't show backups anymore

    Hello, I used to have entries in "Task History" for each container or VM that informed about the daily backup. Since January 11th 2022, there are no further entries anymore. The filter is set to show ALL entries. Should it really be like this? Is there a way for the backup entries to be shown...
  4. L

    Backup eines Exchange Server: Best Practice

    Hi Gregor, hattest Du hier eine Lösung zu gefunden? Gruß, Lars
  5. L

    Filtering with match fields: RegEx not working as expected

    Not sure, but I think there could have been quotation marks in the mails that were not filtered out (the first ones surely didn't have those). I have adapted the filter to ^"?Medizin-Shop"? and didn't get any more mails since a week, so I guess this should be ok.
  6. L

    Custom spam rule: Which element is responsible?

    ok, understood
  7. L

    Custom spam rule: Which element is responsible?

    I would still have quite a long list after splitting up. Besides, it would be a bit clumsy. Could the logging be improved to e.g. include the element ID? At least if the list wasn't changed after a mail was blocked, this would precisely tell me what to look for.
  8. L

    Custom spam rule: Which element is responsible?

    Hello, I have setup a custom spam rule that contains multiple elements for filtering against reply-to, subject, etc.. This custom rule is linked in "Mail Filter > Rules". It wouldn't be feasible to create a single rule for each element. Now, when a mail is rejected, in the logs I can only see...
  9. L

    Filtering with match fields: RegEx not working as expected

  10. L

    Filtering with match fields: RegEx not working as expected

    Restart looks ok to me: Sep 22 16:47:57 gateway pmg-smtp-filter[495614]: Process Backgrounded Sep 22 16:47:57 gateway pmg-smtp-filter[495614]: 2022/09/22-16:47:57 main (type Net::Server::PreFork) starting! pid(495614) Sep 22 16:47:57 gateway pmg-smtp-filter[495614]: Binding to TCP port 10023 on...
  11. L

    Filtering with match fields: RegEx not working as expected

    No problem. Here is the output from my system: https://pastebin.com/vkK61Wxb Any idea what I should check next? Is there a way to debug this? Log more verbose information?
  12. L

    Filtering with match fields: RegEx not working as expected

    Where can I find the log you posted?
  13. L

    Filtering with match fields: RegEx not working as expected

    Here is a fresh example. Header: https://pastebin.com/x1R3734e SMTP log: https://pastebin.com/gNuM29Nw
  14. L

    Filtering with match fields: RegEx not working as expected

    proxmox-mailgateway-container: 7.1-2 (API: 7.1-7/4d02e400, running kernel: 5.13.19-4-pve) pmg-api: 7.1-7 pmg-gui: 3.1-3 clamav-daemon: 0.103.7+dfsg-0+deb11u1 ifupdown: residual config ifupdown2: 3.1.0-1+pmx3 libarchive-perl: 3.4.0-1 libjs-extjs: 7.0.0-1 libjs-framework7: 4.4.7-1...
  15. L

    Filtering with match fields: RegEx not working as expected

    Hi, I have configured amongst other things these two rules: Match field: Reply-To Value: ^K2 for mails with Reply-To: K2 <ykfirxx@forestions.nl> Match field: From Value: ^Medizin-Shop for mails with From: Medizin-Shop <iftiywr@alfasells.de> Test string is ok using the part after "Reply-To: "...
  16. L

    [SOLVED] Anchoring regex in What object

    Ok, thanks.
  17. L

    [SOLVED] Anchoring regex in What object

    According to https://forum.proxmox.com/threads/mail-object-test-button-not-working.78899/post-349390 regexes should implicitly be anchored, but it seems to me this is not the case (anymore), see screenshot. I would expect the test to fail. I know I can simply change my regex to start with ^...
  18. L

    Spam filter rule to check subject for part of recipient name

    I didn't find a solution and ended up using a single filter rule for each user, e.g. "j doe[ ,:].*"
  19. L

    Spam filter rule to check subject for part of recipient name

    Thanks, but that's not a generic solution.
  20. L

    Spam filter rule to check subject for part of recipient name

    No, it's "j doe You want this"
Top Bottom
Back