similar to: Dovecot 2.0+LMTP: Legal MAIL FROM rejected?

Displaying 20 results from an estimated 800 matches similar to: "Dovecot 2.0+LMTP: Legal MAIL FROM rejected?"

2019 Jun 14
2
Dovecot LMTP rejecting mail from address with apostrophe
Hi, I have an OpenSMTPD / Dovecot installation on an OpenBSD server. I recently came across an issue where Dovecot LMTP would reject a message sent to a local user from an address which contains a single apostrophe (e.g. firstname.o'lastname at example.com). Apparently apostrophe, as well as a number of other special characters, are valid characters in the local part of the email address
2013 Jul 04
2
DOVECOT 2.2.4 = 501 5.5.4 Unsupported options in LMTP
Hi, Sorry for my english. My problem: *************************************************** dspam-3.9.0 (dspam-3.10.2 all the time segmentation fault) dspam.conf .................... # DeliveryHost /var/run/dovecot/lmtp # same error as IP DeliveryHost 127.0.0.33 DeliveryPort 24 DeliveryProto LMTP .................... ServerHost 192.168.1.34 ServerPort
2019 Jun 18
1
Dovecot LMTP rejecting mail from address with apostrophe
On 17.6.2019 14.07, Michal Krzysztofowicz wrote: > >> On 15 Jun 2019, at 21:09, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: >> >> >>> On 15 June 2019 10:56 Daniel Lange via dovecot <dovecot at dovecot.org> wrote: >>> >>> >>> Am 15.06.19 um 00:36 schrieb Michal Krzysztofowicz via dovecot: >>>> Would you know if
2015 Mar 20
0
Access to shares is denied after upgrading from 3.6.3 (openSUSE 12.1) to 4.1.17 (openSUSE 13.2)
On 20/03/15 06:11, Reinhard Ni?l wrote: > Hi Marc, > > Am 19.03.2015 um 22:53 schrieb Marc Muehlfeld: > >> Am 19.03.2015 um 14:35 schrieb Nissl Reinhard: >>> When I try to access share \\platon\root<file:///\\platon\root> as >>> fee\administrator I get the following: >>> >>> platon:~ # smbclient -c dir -W fee -U administrator%secret
2015 Mar 20
0
Access to shares is denied after upgrading from 3.6.3 (openSUSE 12.1) to 4.1.17 (openSUSE 13.2)
can you try this also copy past it, but set the admin pass fist. then whats the output. SAMBA_NT_ADMIN_PASS="PUT_YOUR-ADMINISTRATOR_PASSWORD_HERE" SETFQDN=`hostname -f` echo "NT Authentication test" echo ${SAMBA_NT_ADMIN_PASS}| smbclient //localhost/netlogon -U Administrator -c 'ls' echo "Kerberos Authentication" echo ${SAMBA_NT_ADMIN_PASS} | kinit
2018 Oct 19
2
Request: option to hide user IP/HELO content from mail sent via submissiond
For reasons of user privacy and security I usually configure submission servers to not include accurate IP address and HELO information of authenticated users. (Usually replacing it with a private-use domain / IPv6 address.) Dovecot submission (2.3.2) will produce a header something like this (where ?10.22.36.10" is a public IP address) Received: from [192.168.1.184] ([10.22.36.10]) by
2015 Mar 20
4
Access to shares is denied after upgrading from 3.6.3 (openSUSE 12.1) to 4.1.17 (openSUSE 13.2)
Hi Marc, Am 19.03.2015 um 22:53 schrieb Marc Muehlfeld: > Am 19.03.2015 um 14:35 schrieb Nissl Reinhard: >> When I try to access share \\platon\root<file:///\\platon\root> as fee\administrator I get the following: >> >> platon:~ # smbclient -c dir -W fee -U administrator%secret //platon/root >> Domain=[FEE] OS=[Unix] Server=[Samba
1999 Apr 02
0
NETATALK support removed in SAMBA 2.0.3?!
I've just done a: ./configure --with-netatalk --with-mmap --with-ssl --with-quotas on my Linux 2.0.36/intel server... built samba 2.0.3 [release] successfully testparms is happy, my WinDoze clients are working smoothly (good job, Samba dudes!) I notice the netatalk.c file never gets compiled, doing mass-grep's (in all source/lib directories) on WITH_NETATALK don't show any
2004 May 01
1
Managed switch? | PRIO chain
Saw this command on slashdot (http://ask.slashdot.org/article.pl?sid=04/03/24/0434224&mode=flat&tid=126&tid=95 ) to basically make a box behave like a managed switch: "tc qdisc add dev eth1 root tbf rate 250kbit latency 20ms burst 2kb" Followup:
2017 Sep 07
0
login case sensitivity
On 7 September 2017 at 16:07, Alexander Dalloz <ad+lists at uni-x.org> wrote: > Am 07.09.2017 um 20:07 schrieb hw: >> >> Gordon Messmer wrote: >>> >>> On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: >>>> >>>> This was always >>>> problematic because DNS hostnames and email addresses in the RFC >>>> standards
2017 Sep 08
0
login case sensitivity
On Thu, September 7, 2017 14:07, hw wrote: > Gordon Messmer wrote: >> On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: >>> This was always problematic because DNS hostnames and >>> email addresses in the RFC standards were case insensitive >> >> >> Not quite. SMTP is required to treat the "local-part" of the RCPT >> argument as
2017 Sep 07
3
login case sensitivity
Am 07.09.2017 um 20:07 schrieb hw: > Gordon Messmer wrote: >> On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: >>> This was always >>> problematic because DNS hostnames and email addresses in the RFC >>> standards were case insensitive >> >> >> Not quite.? SMTP is required to treat the "local-part" of the RCPT >> argument as
2011 Aug 31
2
lmtp bouncing -- Invalid parameters (in reply to MAIL FROM command)
I just configured postfix' virtual_transport to point at my dovecot director, but am seeing occational problems like this: Aug 31 11:50:06 smtpgw postfix/lmtp[5339]: 69E2F5410D: to=<email at example.net>, relay=loadbalancers.example.net[192.168.42.17]:24, delay=0.15, delays=0.14/0.01/0/0, dsn=5.5.4, status=bounced (host loadbalancers.example.net[192.168.42.17] said: 501 5.5.4 Invalid
2019 Jun 14
0
Dovecot LMTP rejecting mail from address with apostrophe
Am 14.06.19 um 16:20 schrieb Michal Krzysztofowicz via dovecot: > Jun 14 11:57:34 atlantic smtpd[42606]: 21749fd12ac76b57 mda delivery evpid=56aed6237d6444a0 from=<firstname.o'lastname at example.com> to=<me at example.org> rcpt=<me at example.org> user=me delay=0s result=PermFail stat=Error ("mail.lmtp: LMTP server error: 501 5.5.4 Invalid FROM: Invalid character in
2019 Jun 14
2
Dovecot LMTP rejecting mail from address with apostrophe
> On 14 Jun 2019, at 17:01, Daniel Lange <DLange at debian.org> wrote: > > Am 14.06.19 um 16:20 schrieb Michal Krzysztofowicz via dovecot: >> Jun 14 11:57:34 atlantic smtpd[42606]: 21749fd12ac76b57 mda delivery evpid=56aed6237d6444a0 from=<firstname.o'lastname at example.com> to=<me at example.org> rcpt=<me at example.org> user=me delay=0s
2017 Oct 26
2
Bug: lmtp proxy does not quote local parts with spaces
There seems to be a bug with RFC822 processing in ltmp proxying that doesn't quote local parts that, for example, contain spaces. director config: director_username_hash = %Ln lmtp_proxy = yes recipient_delimiter = + protocol lmtp { auth_socket_path = director-userdb auth_username_chars = auth_username_format = %Ln passdb {
2018 Aug 20
1
Strange problem on lmtp with dovecot 2.3.2.1
Hi to all i have compiled and installed dovecot 2.3.2.1 on debian 6 with success but now i'm facing a strange problem on communication from postfix installed on server A with dovecot installed on server B (which version is 2.3.2.1). All incoming emails delivered from esternal from server A to server B with LMTP is rejected with this message error "smtpgw postfix/lmtp[1772]: 6194CA00B3:
2005 Apr 05
1
Jakarta-Tomcat 1.2.10 problem
The connector is not loading my servlets? I am writing down my httpd.conf and workers.properties Httpd.conf LoadModule jk_module modules/mod_jk.so <ifModule mod_jk.c> JkWorkersFile /usr/local/jakarta-tomcat-5.5.4/conf/workers.properties JkLogFile /etc/httpd/logs/mod_jk.log JkLogLevel info JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories JkLogStampFormat "[%a %b %d
2017 Oct 26
2
Bug: lmtp proxy does not quote local parts with spaces
On 26/10/2017 18:38, Alexander Dalloz wrote: > Am 26.10.2017 um 12:20 schrieb David Zambonini: >> >> There seems to be a bug with RFC822 processing in ltmp proxying that >> doesn't >> quote local parts that, for example, contain spaces. > > Newer related RFCs are RFC 5321 and 5322. Typo, meant to say RFC2822, which they still supercede, not that the
2017 Nov 01
2
Bug: lmtp proxy does not quote local parts with spaces
Hi again, I've not heard anything further regarding this bug, so I've had a look at the code. To restate the bug in a more precise way: LMTP in dovecot treats external RFC822 email addresses in the envelope recipient and internal usernames as almost identical/interchangeable. This is incorrect and leads to issues when attempting to use director as an LMTP proxy to proxy to recipients