On 2019年04月08日 07:11, Robert Kudyba wrote: >> On 2019年04月01日 08:30, Robert Kudyba wrote: >>> squirrelmail-1.4.23-0.fc29.20180816.noarch, on Fedora 29.with >>> dovecot-2.3.3-1.fc29.x86_64 >>> >>> I posted on the Dovecot mailing list, >>> https://urldefense.proofpoint.com/v2/url?u=https-3A__dovecot.org_pipermail_dovecot_2019-2DMarch_115335.html&d=DwIDaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=Bv9dq-idzM46f6V7QOlrUYrahxWhTUpJl-j6iq-4Zi0&s=OzX1PznRcjkg17ckyO8YW0LrIrQ30cU2T_9Vz-7sYeA&e= >>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__dovecot.org_pipermail_dovecot_2019-2DMarch_115335.html&d=DwIDaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=Bv9dq-idzM46f6V7QOlrUYrahxWhTUpJl-j6iq-4Zi0&s=OzX1PznRcjkg17ckyO8YW0LrIrQ30cU2T_9Vz-7sYeA&e=>, >>> and their admin suggested finding a setting in SquirrelMail. >>> >>> I have wforce running correctly with Dovecot, see >>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_PowerDNS_weakforced&d=DwIDaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=Bv9dq-idzM46f6V7QOlrUYrahxWhTUpJl-j6iq-4Zi0&s=JHN4LqGbDbscmG8Wjxa-jc2ZZUXmfl-1NIWeCBNYfTQ&e=. >>> However, the IP logged is always of the SquirrelMail server or >>> localhost. Is there e plugin or setting that I can change to get >>> weakforced to correctly show the end user IP? >> >> Well, I've had code sitting around for a while that implements RFC2971 >> (ID command), so I just committed it. You can use it for this purpose >> by putting something like this into your config/config_local.php >> >> $imap_id_command_args = array('remote-host' => '###REMOTE ADDRESS###'); >> >> If you don't care about Dovecot's response in SquirrelMail and want to >> save a few CPU cycles, add this too: >> >> $do_not_parse_imap_id_command_response = TRUE; >> >> The code will show up in our next daily snapshot for 1.4.23 or get a >> patch here: >> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_p_squirrelmail_code_14813_&d=DwIDaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=Bv9dq-idzM46f6V7QOlrUYrahxWhTUpJl-j6iq-4Zi0&s=ETlU011LA1MyPDbshefZFbr0bKcA1NUSe4MdnxK0Btg&e= > > > Thanks Paul! I tried the new code. Squirrelamil is definitely slower > with these options added. If you have metrics or profiling traces that quantify this, I'd love to see that. The added code does (should) not add all that much - it's just a single extra and very simple IMAP ID command. Did you use the configuration variable that disables response parsing? > And still no source IP of end user but perhaps > there logs may shed a light? Or what should auth_policy_server_url be? The rest of your question is about Dovecot, it is not relevant to this list. I suggest first sniffing the IMAP connection to make sure the ID command with the IP address is being sent and acknowledged by Dovecot, then synchronizing your configuration and debugging that. The Dovecot list is the best place to continue asking for help as long as the ID command is working as it should. ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
