Displaying 20 results from an estimated 9035 matches for "submissions".
Did you mean:
submission
2018 Dec 18
3
Apple mail fails with Submission
Postfix debug peer logging
Dec 18 17:08:11 mail postfix/submission/smtpd[10626]: >
server.example.org[XX.XX.XX.XX]:
250 2.1.5 Ok
Dec 18 17:08:11 mail postfix/submission/smtpd[10626]: watchdog_pat:
0x55ef4ec020180
Dec 18 17:08:11 mail postfix/submission/smtpd[10626]: vstream_fflush_some:
fd 10 flush 28
Dec 18 17:08:11 mail postfix/submission/smtpd[10626]:
vstream_buf_get_ready: fd 10 got 15
Dec
2019 Jan 07
1
Apple mail fails with Submission
After the submission with dovecot it sends it to postfix, the postfix log
is:
postfix/submission/smtpd[19509]: connect from example.org[192.168.1.1]
postfix/submission/smtpd[19509]: client=example.org[192.168.1.1],
sasl_method=PLAIN, sasl_username=test at example.org
postfix/submission/smtpd[19509]: *warning: non-SMTP command from
example.org <http://example.org>[192.168.1.1]:
2018 Dec 18
4
Apple mail fails with Submission
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 18 December 2018 at 02:30 Adi Pircalabu via dovecot <
<a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote:
</div>
2018 Dec 23
0
Apple mail fails with Submission
Hi,
Below, you have only the submission-login debug log (authentication).
I'm more interested in what happens after that. You'll need to enable
mail_debug=yes (at least for the user involved) to get that.
Regards,
Stephan.
Op 18/12/2018 om 17:17 schreef Ruud Voorjans:
> Postfix debug peer logging
>
> Dec 18 17:08:11 mail postfix/submission/smtpd[10626]: >
>
2018 Dec 18
0
Apple mail fails with Submission
doveconf -n output:
# 2.3.2.1 (0719df592): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.2 ()
# OS: Linux 4.18.0-12-generic x86_64 Ubuntu 18.10
# Hostname: mail.example.org
auth_debug = yes
auth_debug_passwords = yes
auth_mechanisms = plain login
auth_verbose = yes
director_mail_servers = XX.XX.XX.XX
hostname = mail.example.org
log_path = /var/log/dovecot.log
login_trusted_networks =
2006 Dec 14
1
[LLVMdev] MachineFunction.cpp!!!
Did someone make a change in MachineFunction and forget to update something?
g++ -I/Volumes/data/Wendling/llvm-submission/build/obj/obj-llvm/lib/CodeGen
-I/Volumes/data/Wendling/llvm-submission/build/obj/src/llvm/lib/CodeGen
-I/Volumes/data/Wendling/llvm-submission/build/obj/obj-llvm/include
-I/Volumes/data/Wendling/llvm-submission/build/obj/src/llvm/include
2019 Mar 11
2
submission-login: Fatal: master: service(submission-login):
Hi everyone!
I?m using dovecot 2.3.5. submission-login is crashing many times in a day:
Here is a sample error message:
dovecot: submission-login: Fatal: master: service(submission-login): child 34247 killed with signal 11 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service submission-login { drop_priv_before_exec=yes })
After I added drop_priv_before_exec, I got
2019 Aug 25
6
Feature wishlist: Allow to hide client IP/host in submission service
...ide the host and IP of clients (in the "Received" header) that use
the authenticated submission over port 587. In Postfix that's
possible (https://serverfault.com/q/413533/86332), but not very nice
to configure especially if you only want want to strip the Received
header for port 587 submissions, but not on port 25.
As far as I can see this configuration is not possible at all in the
Dovecot submission server because the function which adds the
Received header with the client's IP address
(smtp_server_transaction_write_trace_record) is always called in
submission-commands.c.
It would...
2019 Apr 19
1
haproxy + submission services -> postfix failure
Hi,
I have a nginx server which is using the proxy protocol to forward tcp
connections to dovecot. Dovecot is configured to be a submission
service for email to be sent. Then postfix should send the email
itself which is also using the ha proxy protocol. There are a few
moving parts in this problem so I'm not sure where the problem is. But
I want to ask if somebody can validate my dovecot
2019 Oct 11
2
Panic: file smtp-client-connection.c: line 1212 (smtp_client_connection_established): assertion failed: (!conn->connect_succeeded)
Hello,
after migrating from self-compiled Dovecot 2.3.3 to Dovecot 2.3.8 from
the repository (Ubuntu 18.04 LTS "Bionic" packages) I have issues with
the submission service. If I send an email, it will not be forwarded
and I get the following error message:
Oct 11 09:29:01 srv2 dovecot: submission(hativ at example.com)<15819><XFnL
eJ2U0rgqAoEMwMAIoDQqhHgB7k+O>: Panic: file
2019 Dec 11
2
Submission config being ignored
I'm having trouble setting up submission with Dovecot proxy. The submission config seems to be getting ignored, but I'm probably doing something wrong.
Expected behaviour: have messages sent to submission ports (25, 465) relayed to `submission_relay_host`.
--
root at imapproxy1:~# cat /etc/dovecot/conf.d/20-submission.conf
submission_logout_format = in=%i out=%o
submission_relay_host =
2017 Dec 11
5
New Dovecot service: SMTP Submission (RFC6409)
Hi,
As some of you know, I started implementing the SMTP submission proxy a
few years ago. It acts as a front-end for any MTA, adding the necessary
functionality for an SMTP submission service, also known as a Mail
Submission Agent (MSA) (https://tools.ietf.org/html/rfc6409). The main
reason I created this, back then, was implementing the BURL capability
(https://tools.ietf.org/html/rfc4468). The
2018 Apr 06
3
Compatibility of Submission in 2.3.1
Hi,
Dovecot 2.3.1 (8e2f634). When using submission one client of mine can not send messages. Directly sending through exim works. Seems that dovecot is too picky or follow the RFC too precise here to be compatible.
Here is the debug log (note the space between ?From:" and "<user2 at host.com>?):
Apr 6 12:02:08 mail dovecot: submission(user at
2019 Jun 09
1
RFC 8314 § 3.3 support at Dovecot submission proxy service?
...}
}
As per RFC 8314 ? 3.3, I would expect the following to work (which I did
not try), and if it already works, I even would expect this snippet part
of the future Dovecot example/default configuration:
service submission-login {
inet_listener submission {
#port = 587
}
inet_listener submissions {
#port = 465
#ssl = yes
}
}
And if it isn't supported yet, I would indeed like to raise this as feature
request. Note that 465 is named "submissions" as per RFC 8314 ? 7.3.
Kind regards
Robert Scheck
-------------- next part --------------
A non-text attachment was scru...
2020 Jul 19
5
I need some help with my Dovecot and Postfix configs - I'm unable to log in on my mail server
Hello,
currently I'm working on my first mailserver but I can't log in to the
account I made. For now my client (Mozlla Thunderbird) detects the
server config (STARTTLS, Port, ...) but it is "Unable to log in at
server. Probbly wrong configuration, username or passsword".
I know that I added username and password correctly so there must
something else be wrong.
I run
2020 Jan 08
2
re-submission of package after CRAN-pretest notes
It used to be the case that when I submitted a package and it gave notes
or warnings in the CRAN checks, I was required to bump the package
version before re-submission.
I hope this is no longer the case.? I recently submitted a package that
gave one fairly trivial NOTE, fixed that, and would like to re-submit.
-Michael
--
Michael Friendly Email: friendly AT yorku DOT ca
Professor,
2020 Sep 01
1
Dovecot Proxy
Hi Philon,
now, it's time for "Mahlzeit" ;-)
Sorry, that I read the wiki1 instead of wiki2. I thought the 1 means
that it is server one of ... my fault. Also not reading the first line
above the menu. My focus was really on the content. ;-)
Also my problem with the doc of Dovecot2 proxy is, that the document
https://doc.dovecot.org/configuration_manual/authentication/proxies/
2016 Feb 08
3
something wrong in package submission procedure/website
Yesterday I uploaded new rockchalk_1.8.97. Then I received email
saying that I needed to confirm the submission. Here's the message.
Dear Paul E. Johnson
Someone has submitted the package rockchalk to CRAN.
You are receiving this email to confirm the submission as the maintainer of
this package.
To confirm the submission to CRAN, follow or copy & paste the following
link into your
2019 Mar 28
2
v2.3.5.1 released
https://dovecot.org/releases/2.3/dovecot-2.3.5.1.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.5.1.tar.gz.sig
Binary packages in https://repo.dovecot.org/
??? * CVE-2019-7524: Missing input buffer size validation leads into
????? arbitrary buffer overflow when reading fts or pop3 uidl header
????? from Dovecot index. Exploiting this requires direct write access to
????? the index files.
2019 Mar 28
2
v2.3.5.1 released
https://dovecot.org/releases/2.3/dovecot-2.3.5.1.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.5.1.tar.gz.sig
Binary packages in https://repo.dovecot.org/
??? * CVE-2019-7524: Missing input buffer size validation leads into
????? arbitrary buffer overflow when reading fts or pop3 uidl header
????? from Dovecot index. Exploiting this requires direct write access to
????? the index files.