Updated to 1.3.10 - discarding: not on mydomains - archive_only_mydomains=0

Issue #1139 closed
T. Matyas created an issue

Updated from 1.3.7 to 1.3.10 →

piler[22058]: 0/FYC6GY0G1LFDUFAD: discarding: not on mydomains
piler[22067]: 9/1GWXB12YBOXSLT3B: discarding: not on mydomains
piler[22061]: 3/ID92IWJLTQQOI6ZA: discarding: not on mydomains

although we have archive_only_mydomains=0 in piler.conf!?
Until 1.3.7 we newer saw “discarding: not on mydomains”….

Comments (2)

  1. T. Matyas reporter

    Today I made some more inverstigations:
    discarding: not on mydomains:
    1.3.10 affected
    1.3.9 affected
    1.3.8 affected

    Jan 27 16:07:45 mailarchive piler-smtp[18834]: received: 1X22HEX7975EC3LI, from=noreply.wiki@storage.dsi, size=5347, client=192.168.1.3, fd=6, fsync=47916
    Jan 27 16:07:45 mailarchive piler-smtp[18834]: disconnected from 192.168.1.3 on fd=6 (0 active connections)
    Jan 27 16:07:46 mailarchive piler[18846]: 9/1X22HEX7975EC3LI: discarding: not on mydomains
    Jan 27 16:07:46 mailarchive piler[18846]: 9/1X22HEX7975EC3LI: 40000000601181cc2142658c00d6d25843c9, size=5347/0, attachments=0, reference=, message-id=howtochatrev1611760063@wiki.dsi>, retention=0, folder=0, delay=0.1011, status=discarded

    1.3.7 - OK
    Jan 27 16:23:24 mailarchive piler-smtp[28785]: received: VHGI3VFIL0YOW0X7, from=noreply.wiki@storage.dsi, size=5117, client=192.168.1.3, fd=6
    Jan 27 16:23:24 mailarchive piler-smtp[28785]: disconnected from 192.168.1.3 on fd=6 (0 active connections)
    Jan 27 16:23:25 mailarchive piler[28794]: 6/VHGI3VFIL0YOW0X7: 4000000060118577025df30c00ba0cbe9b28, size=5117/2656, attachments=0, reference=, message-id=it-howtochatrev1611761002@wiki.dsi, retention=9127, folder=0, delay=0.3970, status=stored

    The thing is, that I do not understand what is happening here.
    piler.conf and also piler.conf.dist contains archive_only_mydomains=0
    But somehow >1.3.7 ignore(s) this setting. 1.3.10 has also problem with security_header= (see my other bug report).
    We have an internal TLD “.dsi”
    Over the GUI, I add some domain mappings years ago, and for 1.3.10 (maybe also for >1.3.7) I added some new mappings for the daily mail traffic.
    Sporadically we get emails from our servers with @servername.dsi. The thing is, I cannot add “dsi” as a TLD over the GUI. I also do not want to do that.
    Why is the setting archive_only_mydomains=0 ignored since 1.3.8?

  2. Log in to comment