emailrelay-help Mailing List for E-MailRelay (Page 2)
SMTP email proxy and relay server
Brought to you by:
graeme_walker
This list is closed, nobody may subscribe to it.
2005 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
|
Dec
(2) |
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
(1) |
Jul
(5) |
Aug
(6) |
Sep
(2) |
Oct
|
Nov
(1) |
Dec
|
2014 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(3) |
Sep
(3) |
Oct
(4) |
Nov
|
Dec
(5) |
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2022 |
Jan
(2) |
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2023 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(6) |
Dec
|
From: Amani H. <am...@e-...> - 2018-05-13 13:15:30
|
Hello All, We are not able to use E-MailRelay as proxy with SSL (not TLS) for both channels incoming and outgoing. SSL clients cannot connect to our proxy, and the proxy cannot connect to SSL SMTP server such as smtp.mail.yahoo.com:465 The start command is "D:\email relay\emailrelay.exe" --no-daemon --hidden --as-proxy smtp.mail.yahoo.com:465 --port 25 --admin 26 --server-tls "D:\email relay\rg_certificate.pem" --server-auth "D:\email relay\rg_emailrelay.auth" --client-tls --client-auth "D:\email relay\rg_emailrelay.auth" --spool-dir "C:\Windows\System32\spool\emailrelay" --filter "D:/email\ relay/rg_email_filter.bat" --log --verbose --log-file "D:\email relay\logs\emailrelay-%%d.log" --log-time Rg_emailrelay.auth file is something like below server PLAIN ere...@ya...<mailto:ere...@ya...> password server LOGIN ere...@ya...<mailto:ere...@ya...> password client PLAIN ere...@ya...<mailto:ere...@ya...> password The log and .bad files are attached, and the OS is Windows 10 64-bit. Please note that the above setup allows plain and TLS connections on port 25, but it doesn’t allow SSL connections. Also it can forward the emails to plain or TLS SMTP servers but not SSL servers. Best Regards … [cid:image002.jpg@01D3EAB8.1BAB9CB0][LINE] Amani M. Hamdan Research and Development Team Lead Mobile + 962 78 898 3820 Telephone + 962 6 585 3346 USA Office + 209 239 8000 Time Zone ( GMT + 2:00 - Amman ) Address Regional Office 210. Grand City 1 Building. Abdullah Ghosheh Street. Amman – Jordan. E-mail am...@e-...<mailto:am...@e-...> [LINE] Please consider the environment before printing. This email and any files transmitted with it may contain confidential or copyright material and are for the attention of the addressee only. If you have received this communication in error please notify the sender by email reply and then delete it from your system. |
From: Christoph P. <Chr...@pl...> - 2017-12-21 12:50:41
|
Hello, I forgot to mention the OS where the problem with non-forwarded emails occurs: It is armhf. Regards Christoph |
From: Christoph P. <Chr...@pl...> - 2017-12-15 07:58:28
|
Hello, on Monday, I sent an email with the same subject like in this email to the list. But so far, my message has not yet been approved by the list moderator, maybe because the email I had attached as an example for a message that emailrelay did not forward, was a spam email, so that maybe my own email was also identified as spam. But it is not and all other emails I got so far where the problem occurred contain private information, so I cannot publish them in a mailing list. So, please unlock my email from Monday for the mailing list. Regards Christoph |
From: Christoph P. <Chr...@pl...> - 2017-12-11 08:24:08
|
Hello, it seems that emailrelay has a bug that prevents some emails from being forwarded to the next destination. Due to the envelope file, the error reason is that the message is empty, but it is not. All emails I found so far where forwarding does not work have in common that they have attachments - which does not mean that all emails with attachments are not forwarded. I have attached such a not-forwarded email as an example - it's spam anyway, so contains no private information from me or others. Regards Christoph |
From: Christoph P. <Chr...@pl...> - 2017-12-07 15:14:18
|
Hello, it seems that emailrelay has a bug that prevents some emails from being forwarded to the next destination. All emails I found so far where forwarding does not work have in common that they have attachments - which does not mean that all emails with attachments are not forwarded. I have attached such a not-forwarded email as an example - it's spam anyway, so contains no private information from me or others. Regards Christoph |
From: Marc L. <mar...@uc...> - 2017-12-01 13:51:58
|
*Hello,* *I'm trying to compile emailrelay1.9 on openindiana-hipster (the opensource cousin of solaris).* *./configure went fine* root@catalina:/opt/emailrelay-1.9# ./configure checking for a BSD-compatible install... /usr/gnu/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/gnu/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking for ranlib... ranlib checking for gawk... (cached) gawk checking for grep that handles long lines and -e... /usr/gnu/bin/grep checking for make... make checking for ar... ar checking for gzip... gzip checking for doxygen... no checking for man2html... no checking for library containing gethostbyname... -lnsl checking for library containing connect... -lsocket checking how to run the C preprocessor... gcc -E checking for egrep... /usr/gnu/bin/grep -E checking for ANSI C header files... yes checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking whether time.h and sys/time.h may both be included... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for unistd.h... (cached) yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking for glob... yes checking for socklen_t... yes checking for ipv6... yes checking for getipnodebyname... yes checking for sin6_len... no checking for buggy ctime... no checking for pam headers in /usr/include/pam... no checking for linux pam... yes checking for getpwnam_r... yes checking for gmtime_r... yes checking for localtime_r... yes checking for setgroups... yes checking for pkg-config... no checking for QT... no checking for moc... no checking for pkg-config... no checking for zlib... yes checking for openssl... yes checking for glob... yes configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating src/glib/Makefile config.status: creating src/gssl/Makefile config.status: creating src/gnet/Makefile config.status: creating src/gauth/Makefile config.status: creating src/gsmtp/Makefile config.status: creating src/gpop/Makefile config.status: creating src/main/Makefile config.status: creating src/win32/Makefile config.status: creating src/gui/Makefile config.status: creating lib/Makefile config.status: creating lib/gcc2.95/Makefile config.status: creating lib/msvc6.0/Makefile config.status: creating bin/Makefile config.status: creating doc/Makefile config.status: creating etc/Makefile config.status: creating test/Makefile config.status: creating extra/Makefile config.status: creating debian/Makefile config.status: creating config.h config.status: executing depfiles commands *but when I try make, it fails on the following error* make[3]: Entering directory '/opt/emailrelay-1.9/src/glib' g++ -DHAVE_CONFIG_H -I. -I../.. -I../../lib/gcc4.9 -I/usr/include/security -g -O2 -MT gpam_linux.o -MD -MP -MF .deps/gpam_linux.Tpo -c -o gpam_linux.o gpam_linux.cpp gpam_linux.cpp: In constructor ‘G::PamImp::PamImp(G::Pam&, const string&, const string&, bool)’: gpam_linux.cpp:110:14: error: invalid conversion from ‘int (*)(int, const pam_message**, pam_response**, void*)’ to ‘int (*)(int, pam_message**, pam_response**, void*)’ [-fpermissive] m_conv.conv = converse ; ^ gpam_linux.cpp: In member function ‘std::string G::PamImp::name() const’: gpam_linux.cpp:180:49: error: invalid conversion from ‘const void**’ to ‘void**’ [-fpermissive] m_rc = ::pam_get_item( hpam() , PAM_USER , &vp ) ; ^ In file included from gpam_linux.cpp:40:0: /usr/include/security/pam_appl.h:186:1: note: initializing argument 3 of ‘int pam_get_item(const pam_handle_t*, int, void**)’ pam_get_item( ^ make[3]: *** [Makefile:470: gpam_linux.o] Error 1 make[3]: Leaving directory '/opt/emailrelay-1.9/src/glib' make[2]: *** [Makefile:254: all-recursive] Error 1 make[2]: Leaving directory '/opt/emailrelay-1.9/src' make[1]: *** [Makefile:368: all-recursive] Error 1 make[1]: Leaving directory '/opt/emailrelay-1.9' gmake: *** [Makefile:290: all] Error 2 *Any suggestion to solve this problem ?* * * *Thanks* *Marc* |
From: <in...@no...> - 2017-10-22 16:00:01
|
Hello Anyone around that could give som advice on how to use the emailrelay on a windows installation running Domino and ASSP. I am trying to implement a setup similar to: https://sourceforge.net/p/assp/wiki/ASSP_Advanced_Workflow/ using emailrelay I am running a windows 7 and Domino+ASSP on a ESXi VM-machine in a server hall in Stockholm It works "asis" but 2 problems/concerns - it seems that I need a "relay" to send outgoing mails from Donino thru ASSP (this gives me automatic whitelisting to people I send mail to) - I would like to create a DMZ with ASSP on the "outside" and send outgoing mails thru ASSP Tying to figure out a configuration I arrived to a total of 2 "pairs" (incoming and outgoing) of the relay running. 2 on the "outside" and 2 on the "inside" accessing 2 different storage files Currently ASSP delivers incoming mail to Domino on port 225 and will accept outgoing mail from Domino on port 325 (Currently Domino sends directly on port 25. It seems that sending thru ASSP does not wiork without a relay) I would appreciate some advice on how to set this up Best regards Ingvar Engelbrecht Skype: ingvare If everything seems under control, you're just not going fast enough -Mario Andretti ”If you don’t do your own thinking, others will do the thinking for you – it’s called fascism” — Jacque Fresco http://www.maieutic.com http://ingvare.wordpress.com/ |
From: <in...@no...> - 2017-10-20 16:26:04
|
Hi, Trying to understand how your email relay operates. Sometimes I get the impression that you start the program anb it runs with the specified parameters and then ends --- snip --- To get behaviour more like a proxy you can add the --poll option so that messages are forwarded continuously rather than on-demand. This example starts a store-and-forward server that forwards spooled-up e-mail every hour: --- snip --- The above description gives the impression that the program starts, runs and finishes unless you use "poll" What is the normal way the program runs? One-shot or continously? like: emailtrelay --as-server --port xx --spool /tmp1 is it a one shoot or is it sitting there doing its thing? Best regards Ingvar Engelbrecht Skype: ingvare If everything seems under control, you're just not going fast enough -Mario Andretti ”If you don’t do your own thinking, others will do the thinking for you – it’s called fascism” — Jacque Fresco http://www.maieutic.com http://ingvare.wordpress.com/ |
From: <in...@no...> - 2017-10-19 19:37:41
|
In my previous mail question I made a simple question. Since then I have been thinking and trying to figure out a configuration that makes use of your relay. Running without any relays does not work and the suggestion from ASSP forum is to use SMTP relay. See attached PDF document. Could you verify that this is a valid configuration? Could a simpler configuration be used? Best regards Ingvar Engelbrecht Skype: ingvare If everything seems under control, you're just not going fast enough -Mario Andretti ”If you don’t do your own thinking, others will do the thinking for you – it’s called fascism” — Jacque Fresco http://www.maieutic.com http://ingvare.wordpress.com/ |
From: <in...@no...> - 2017-10-19 09:30:11
|
Hi. My name is Ingvar Engelbrecht, long time programmer. I am running a windows 7 under a VM-machine (ESXi) My mail program is IBM Domino ( I used to do a lot of programming contracts for Domino-installations). I also use the ASSP anti spam program. This combo works well except for also routing outgoing mail thru ASSP. A suggestion from the ASSP support suggest that I run a relay between Domino and ASSP for outgoing mail (the advantage of running outgong mail thru ASSP is that I get automatic "white listing ´" of outgoing mails. For some unknown reason it does not work to send directly from Domino to the ASSP Relayng port so the ASSP support suggests that i run a SMTP relay between Domino and ASSP for outgoing mails. After searching for a program I ended up with your program. Maybe it is an "overkill" but I would like to ty it The documentation is a bit "overwelming" so I wonder if you could assist. :-) For outgoing mails I would like to use a store and forward approach to "isolate" ASSP and Domino. From a port on Domino (as 125) to a port on ASSP (as 227) Thats all Please advice :-) Best regards Ingvar Engelbrecht Skype: ingvare If everything seems under control, you're just not going fast enough -Mario Andretti ”If you don’t do your own thinking, others will do the thinking for you – it’s called fascism” — Jacque Fresco http://www.maieutic.com http://ingvare.wordpress.com/ |
From: Christoph P. <Chr...@pl...> - 2017-09-10 13:35:38
|
Hello, The attached patch solves the problem. I do not know why it does, I just had the luck to find it by chance when I split up line 90 of configuration.cpp for debugging purposes, to find out if the segfault happens in the assignment of *p, or in the calculation of the value that *p is assigned to. Regards Christoph |
From: Christoph P. <Chr...@pl...> - 2017-09-10 11:18:06
|
Hello, I now added some calls of prctl(PR_SET_DUMPABLE, 1), so that a core dump is created even after setuid and its variants, and re-compiled with appropriate debugger options. After emailrelay had crashed, a gdb 'bt' call showed: #0 size (this=this@entry=0xbe8a91d0) at /build/gcc-4.9-YnrWeB/gcc-4.9-4.9.2/build/arm-linux-gnueabihf/libstdc++-v3/include/bits/basic_string.h:725 #1 std::string::find (this=this@entry=0xbe8a91d0, __c=__c@entry=61 '=', __pos=__pos@entry=0) at /build/gcc-4.9-YnrWeB/gcc-4.9-4.9.2/build/arm-linux-gnueabihf/libstdc++-v3/include/bits/basic_string.tcc:763 #2 0x0001e3ec in Main::Configuration::listeningInterfaces (this=this@entry=0x1a51470, protocol="smtp") at configuration.cpp:90 #3 0x0002127a in Main::Run::checkPorts (this=this@entry=0xbe8a94b8) at run.cpp:229 #4 0x000220f2 in Main::Run::runCore (this=this@entry=0xbe8a94b8) at run.cpp:302 #5 0x00022a8c in Main::Run::run (this=this@entry=0xbe8a94b8) at run.cpp:251 #6 0x00015b64 in main (argc=<optimized out>, argv=0xbe8a96f4) at main.cpp:54 Regards Christoph |
From: Christoph P. <Chr...@pl...> - 2017-09-07 23:09:36
|
Hello, I found your tool emailrelay and would like to use it. So, I downloaded the source code, compiled it for Debian amd64 architecture, installed the package and ran some tests successfully. Then I compiled the source code for Debian armhf architecture with exactly the same options as before, installed the package, but when I then tried to run the program, it crashed with a segmentation fault as soon as I added the --interface option. On amd64, I could use that option without problems. I know that the last changes to emailrelay have been made a few years ago, but I really would like to get help in this matter ... Regards Christoph |
From: Leo K. <le...@fb...> - 2017-08-12 03:03:28
|
Hi It looks like you received some messages from localhost, but they could not be forwarded to the remote server because that server did not respond -- it just dropped the connection, and as a result the first message was failed. --> 1. How do I make a TCP connection? 2. How do I get that server to be forwarded to a remote server? Best regards, Leo 2017-08-12 10:24 GMT+09:00 Graeme Walker < gra...@us...>: > Hi Leo, > > It looks like you received some messages from localhost, but they could > not be forwarded to the remote server because that server did not > respond -- it just dropped the connection, and as a result the first > message was failed. > > The word 'exception' is perhaps misleading; it just means the TCP > connection was lost. > > Graeme > -- Leo Kim IT Operation Manager E-mail : leo. <ric...@fb...>ki...@fb... Skype : le...@fb... Address : Level 10, 21 Queen Street, Auckland, 1010, NZ *FBP LIMITED CONFIDENTIALITY NOTICE:* This email and any attachments are intended only for the recipient(s), to which they are addressed and may contain confidential, proprietary or legally privileged information. Access to this email by anyone else is unauthorised. If you are not the intended recipient, please do not read, copy, use, distribute, print or disclose to others any part of this message or any attachments. If you have received this email in error, please notify the sender immediately and delete the entire communication, including any attachments, from your system, and destroy any hard copies of it. FBP Limited does not guarantee the confidentiality or the integrity of external e-mail communications and, therefore, cannot be responsible for any unauthorised access, disclosure, use or tampering that may occur during transmission. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is strictly prohibited. The Company accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided. -- *FBP LIMITED CONFIDENTIALITY NOTICE:* This email and any attachments are intended only for the recipient(s), to which they are addressed and may contain confidential, proprietary or legally privileged information. Access to this email by anyone else is unauthorised. If you are not the intended recipient, please do not read, copy, use, distribute, print or disclose to others any part of this message or any attachments. If you have received this email in error, please notify the sender immediately and delete the entire communication, including any attachments, from your system, and destroy any hard copies of it. FBP Limited does not guarantee the confidentiality or the integrity of external e-mail communications and, therefore, cannot be responsible for any unauthorised access, disclosure, use or tampering that may occur during transmission. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is strictly prohibited. The Company accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided. |
From: Graeme W. <gra...@us...> - 2017-08-12 01:44:49
|
Hi Leo, It looks like you received some messages from localhost, but they could not be forwarded to the remote server because that server did not respond -- it just dropped the connection, and as a result the first message was failed. The word 'exception' is perhaps misleading; it just means the TCP connection was lost. Graeme |
From: Leo K. <le...@fb...> - 2017-08-09 01:17:07
|
Hi. I have a question regarding emailrelay error. An error occurred while using emailrelay. Please contact me if you see any problems. **log** emailrelay: 20170808.122932: warning: no valid domain in "WIN-86UMBTINOUI": defaulting to ".local" emailrelay: 20170808.122932: info: smtp server on 0.0.0.0:40026 emailrelay: 20170809.000004: info: smtp connection from 127.0.0.1:58850 emailrelay: 20170809.000004: info: smtp connection closed: exception event: 127.0.0.1:58850 emailrelay: 20170809.000004: info: smtp connection from 127.0.0.1:58851 emailrelay: 20170809.000004: info: smtp connection closed: smtp protocol done: 127.0.0.1:58851 emailrelay: 20170809.000004: info: smtp connection closed: exception event: 127.0.0.1:58851 emailrelay: 20170809.000004: info: smtp connection from 127.0.0.1:58854 emailrelay: 20170809.000004: info: smtp connection closed: exception event: 127.0.0.1:58854 emailrelay: 20170809.000004: info: smtp connection from 127.0.0.1:58855 emailrelay: 20170809.000004: info: smtp connection closed: smtp protocol done: 127.0.0.1:58855 emailrelay: 20170809.000004: info: smtp connection closed: exception event: 127.0.0.1:58855 emailrelay: 20170809.000025: warning: timeout: no greeting from remote server: continuing emailrelay: 20170809.000025: warning: exception: exception event emailrelay: 20170809.000025: error: polling: exception event emailrelay: 20170809.000025: info: failing file: "emailrelay.1468.308999.3186.envelope.busy" -> "emailrelay.1468.308999.3186.envelope.bad" Best regards, Leo Leo Kim IT Operation Manager E-mail : leo. <ric...@fb...>ki...@fb... Skype : le...@fb... Address : Level 10, 21 Queen Street, Auckland, 1010, NZ *FBP LIMITED CONFIDENTIALITY NOTICE:* This email and any attachments are intended only for the recipient(s), to which they are addressed and may contain confidential, proprietary or legally privileged information. Access to this email by anyone else is unauthorised. If you are not the intended recipient, please do not read, copy, use, distribute, print or disclose to others any part of this message or any attachments. If you have received this email in error, please notify the sender immediately and delete the entire communication, including any attachments, from your system, and destroy any hard copies of it. FBP Limited does not guarantee the confidentiality or the integrity of external e-mail communications and, therefore, cannot be responsible for any unauthorised access, disclosure, use or tampering that may occur during transmission. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is strictly prohibited. The Company accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided. -- *FBP LIMITED CONFIDENTIALITY NOTICE:* This email and any attachments are intended only for the recipient(s), to which they are addressed and may contain confidential, proprietary or legally privileged information. Access to this email by anyone else is unauthorised. If you are not the intended recipient, please do not read, copy, use, distribute, print or disclose to others any part of this message or any attachments. If you have received this email in error, please notify the sender immediately and delete the entire communication, including any attachments, from your system, and destroy any hard copies of it. FBP Limited does not guarantee the confidentiality or the integrity of external e-mail communications and, therefore, cannot be responsible for any unauthorised access, disclosure, use or tampering that may occur during transmission. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is strictly prohibited. The Company accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided. |
From: 陶娟 <tao...@sy...> - 2017-05-13 02:58:30
|
Hi, Before consulting the question, let me talk about my needs first. I am now in the E-MailRelay and a transparent mode of the gateway products installed together, and then from the local mail client (such as: outlook / foxmail) to send mail (such as 163.com to other mail server, non-self-built non-network Mail server) out, send mail through E-MailRelay ,I want the mail to send out normally, E-MailRelay order should be how to write?I have tried many times and always have certification problems. I follow the steps below to install the compiled E-MailRelay: ./configure --with-openssl --enable-debug make make installBut I use the emailrelay command when prompted the following error: # emailrelay --as-proxy smtp.163.com:25 --port=10025 -r --syslog --client-auth /usr/local/etc/emailrelay.auth --log --close-stderr --client-tls emailrelay: error: cannot do tls/ssl: openssl not built in: remove tls options from the command-line or rebuild the emailrelay executable with openssl emailrelay: exception: cannot do tls/ssl: openssl not built in: remove tls options from the command-line or rebuild the emailrelay executable with openssl (1) emailrelay --as-proxy smtp.synitalent.com:25 --port=10025 -r --syslog --client-auth /usr/local/etc/emailrelay.auth --log --close-stderrerror maillog:May 13 09:47:35 localhost emailrelay[10522]: emailrelay: info: smtp connection from 192.168.9.149:48575 May 13 09:47:35 localhost emailrelay[10522]: emailrelay: info: smtp connection closed: smtp protocol done: 192.168.9.149:48575 May 13 09:47:35 localhost emailrelay[10522]: emailrelay: warning: cannot do tls/ssl required by remote smtp server: authentication will probably fail: try enabling client-tls May 13 09:47:35 localhost emailrelay[10522]: emailrelay: warning: invalid challenge May 13 09:47:35 localhost emailrelay[10522]: emailrelay: warning: exception: authentication error: for "tao...@sy..." using LOGIN May 13 09:47:35 localhost emailrelay[10522]: emailrelay: error: polling: authentication error: for "tao...@sy..." using LOGIN May 13 09:47:35 localhost emailrelay[10522]: emailrelay: info: failing file: "emailrelay.10522.640038.2.envelope.busy" -> "emailrelay.10522.640038.2.envelope.bad" AUTH file I tried a lot of ways, the final certification failure, I do not know whether the format or with the TLS/SSL? What is the solution to my problem? Best wishes! Looking forward to your relay... thanks,taojuan |
From: Koray Y. <kyi...@gm...> - 2017-02-13 16:30:30
|
Hi all, I have two emailrelay servers. Each have two instances. One of them is storing the incoming mail message and forward to second instance, the other one with filtering filter the incoming script and then forward to the mta. The inbound emailrelay server instances run as server mode, while the outbound emailrelay server instances run as proxy mode with polling. I am using multiple emailrelay processes running against the same outbound spool directory to regain parallelism. Because, for high loads some of the messages can not be forwarded. So in order to avoid this situation I used two emailrelay servers with same outbound spool. But sometimes I recieved more than message as expected. For example if I send 40 messages in a test. I will recieve 41 message. Also the same problem occurred with sharing only incoming spool of the incoming emailrelay server instances. Although the message lost problem is gone with paralleism, there can be duplicates of messages in the recieving client. What causes this problem? Regards. |
From: Mike E. <MEn...@he...> - 2016-03-31 18:35:13
|
From: Michael L. <cou...@ho...> - 2015-12-30 19:31:50
|
Hello there! I am using email relay to transmit emails through a google account for certain automatic notifications. Everything was configured and fine until the admin turned on two factor authentication. I've since resolved that, but there is now about a month's worth of emails that are now sitting in the spool directory that I would like to get sent out. I used bulk rename utility to remove the .bad extension files, but they are still sitting in the spool and do not appear to be going anywhere. Newer messages are going out, but the old ones are sitting there. Is there a command from a windows machine I can issue to get to process the older ones? Thanks! |
From: Jhonny L. <jho...@gm...> - 2015-10-23 22:44:37
|
Hi, I work with JD Edwards E1 and I try to use E-MailRelay for send automatic notification with E-MailRelay because JD Edwards doesn't work with mail server with smtp autentication but I don't understand how is it work. In JD Edwards I just write the mailserver and port, then all the automatic notification that it send uses this parameters: [JDEMAIL] Rule1=90|OPT|MAILSERVER=smtp.gmail.com Rule2=100|DEFAULT|OWMON=jde...@vq... Rule3=110|DEFAULT|PSFT_SYSTEM=jde...@vq... Rule4=120|DEFAULT|JDE_SYSTEM=jde...@vq... Rule5=DEFAULT|WORKFLOW_SYSTEM=jde...@vq... Rule6=140|OPT|MERGELOCAL=1 Rule7=150|OPT|UPDATELOCAL=0 mailServer=smtp.gmail.com SMTPPort=25 How E-MailRelay did take the email and send you it to smtp.gmail.com? What is the adress that E-MailRelay hear to take the email and forwarding? Thanks for your time. Regards, |
From: Patrick K. <Pa...@an...> - 2015-08-05 15:43:41
|
Hello, I am trying to install your EmailRelay and getting the following error. Can you assist by telling me any info that you are aware that causes this? Does the install need to be fresh to get this to work? If so how is this program Uninstalled? creating install directory [C:\Program Files (x86)\emailrelay]... exists creating configuration directory [C:\Program Files (x86)\emailrelay]... exists creating spool directory [C:\Windows\system32\spool\emailrelay]... exists creating pid directory [C:\Program Files (x86)\emailrelay]... exists creating authentication secrets file [C:\Program Files (x86)\emailrelay\emailrelay.auth]... ok creating batch file [C:\Program Files (x86)\emailrelay\emailrelay-start.bat]... ok creating batch file [C:\Program Files (x86)\emailrelay\emailrelay-start-with-log-file.bat]... ok creating target directory [C:\Program Files (x86)\emailrelay]... exists extracting [readme.txt] to [C:\Program Files (x86)\emailrelay]... ok extracting [copying.txt] to [C:\Program Files (x86)\emailrelay]... ok extracting [changelog.txt] to [C:\Program Files (x86)\emailrelay]... ok extracting [authors.txt] to [C:\Program Files (x86)\emailrelay]... ok creating target directory [C:\Program Files (x86)\emailrelay\doc\doxygen]... exists extracting [index.html] to [C:\Program Files (x86)\emailrelay\doc\doxygen]... ok extracting [emailrelay-service.exe] to [C:\Program Files (x86)\emailrelay]... unpacking error: cannot open output ** failed ** Thank you, -- Patrick Kiah Lead Project Manager Anchor Network Solutions 303-904-0494 ext. 109 |
From: Mathias B. <mat...@de...> - 2015-05-29 11:41:17
|
Hi folks, using this nice software the first time I'm really pleased how easy the setup was and how reliable it works. Base is Windows Server 2008R2 ENU. One thing I can't figure out: >From mails with attachment the .content-file stays in the spool directory. They can not be deleted because the relay-process itself keeps them in access. I have to restart the process to get rid of the files. Any idea what I did wrong? conf: --------------------------------------------------------------------------------- gui-dir-config C:\emailrelay gui-dir-install C:\emailrelay gui-dir-spool C:\emailrelay\spool gui-do-pop n gui-do-smtp y gui-forward-immediate n gui-forward-on-disconnect y gui-forward-poll n gui-forward-poll-period minute gui-listening-all y gui-listening-interface gui-listening-remote n gui-logging-debug n gui-logging-syslog y gui-logging-verbose n gui-smtp-client-auth n gui-smtp-client-auth-mechanism CRAM-MD5 gui-smtp-client-host [outgoing server removed ;)] gui-smtp-client-port 25 gui-smtp-client-tls y gui-smtp-server-auth n gui-smtp-server-auth-mechanism CRAM-MD5 gui-smtp-server-port 25 gui-smtp-server-trust gui-start-at-login n gui-start-link-desktop y gui-start-link-menu y gui-start-on-boot y --------------------------------------------------------------------------------- thx a lot in advance! Mathias -- Amtsgericht Offenbach: HRB 41405 | Geschäftsführer: Uwe Beyer, Jan Ole Schneider Der Inhalt dieser E-Mail, einschließlich seiner Anhänge, ist vertraulich und ausschließlich für den bezeichneten Empfänger bestimmt. Wenn Sie nicht der vorgesehene Empfänger dieser E-Mail oder dessen berechtigter Vertreter sind, so beachten Sie bitte, dass jede Form der Kenntnisnahme, der Nutzung, der Veröffentlichung, der Vervielfältigung oder der Weitergabe unzulässig ist. Wir bitten Sie in diesem Fall, sich mit dem Absender dieser E-Mail in Verbindung zu setzen. Vielen Dank für Ihre Unterstützung. Besuchen Sie uns auch auf: [image: Tempo-Team - Facebook] <http://www.facebook.com/Tempo.Team.Deutschland> [image: Tempo-Team - Google+] <https://plus.google.com/117121593929743534287#117121593929743534287/posts%20> [image: Tempo-Team - Xing] <http://www.xing.com/companies/tempo-teampersonaldienstleistungengmbh/updates> |
From: Jean-Charles de L. <jc...@he...> - 2015-05-18 16:53:28
|
Hi, I'm an happy user of emailrelay for a while on debian boxes having build the binaries myself from sources. As I'm now moving my boxes to AlpineLinux, I would like to package emailrelay as an official package for AL. It compiles fine when getting the sources from svn ;) (FYI AL uses musl instead of glibc). But the build system for AL wants a tarball of the sources. My question is: is it an official source tarball available on SF? I cannot find one. I did receive the suggestion to reinject the svn checkout in some git server and from there to generate such tarball but I would prefer a direct path if availaible... -- Cordialement, Jean-Charles de Longueville |
From: Marc L. <mar...@uc...> - 2014-10-05 16:01:03
|
Hello, I'm using email relay for at least 5 years on machines running solaris10. There I could very easily configure, make and install emailrelay 1.8.2 I'm now trying to do the same on openindiana (open source variant of Solaris) and it does not work any more; For 1.8.2, compilations stops with the following message: ...many files get compiled, then: g++ -DHAVE_CONFIG_H -I. -I../.. -I../../lib/gcc4.6 -I../../src/glib -I../../src/gssl -g -O2 -MT geventloop_unix.o -MD -MP -MF .deps/geventloop_unix.Tpo -c -o geventloop_unix.o geventloop_unix.cpp geventloop_unix.cpp: In member function ‘void GNet::FdSet::init(const GNet::EventHandlerList&)’: geventloop_unix.cpp:152:3: error: ‘memset’ was not declared in this scope make[3]: *** [geventloop_unix.o] Error 1 make[3]: Leaving directory `/opt/emailrelay-1.8.2/src/gnet' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/opt/emailrelay-1.8.2/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/opt/emailrelay-1.8.2' gmake: *** [all] Error 2 for 1.9, it stops even earlier when I try to make it I get make all-recursive make[1]: Entering directory `/opt/emailrelay-1.9' Making all in bin make[2]: Entering directory `/opt/emailrelay-1.9/bin' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/opt/emailrelay-1.9/bin' Making all in src make[2]: Entering directory `/opt/emailrelay-1.9/src' Making all in glib make[3]: Entering directory `/opt/emailrelay-1.9/src/glib' g++ -DHAVE_CONFIG_H -I. -I../.. -I../../lib/gcc4.6 -I/usr/include/security -g -O2 -MT gpam_linux.o -MD -MP -MF .deps/gpam_linux.Tpo -c -o gpam_linux.o gpam_linux.cpp gpam_linux.cpp: In constructor ‘G::PamImp::PamImp(G::Pam&, const string&, const string&, bool)’: gpam_linux.cpp:110:16: error: invalid conversion from ‘int (*)(int, const pam_message**, pam_response**, void*)’ to ‘int (*)(int, pam_message**, pam_response**, void*)’ [-fpermissive] gpam_linux.cpp: In member function ‘std::string G::PamImp::name() const’: gpam_linux.cpp:180:49: error: invalid conversion from ‘const void**’ to ‘void**’ [-fpermissive] /usr/include/security/pam_appl.h:186:1: error: initializing argument 3 of ‘int pam_get_item(const pam_handle_t*, int, void**)’ [-fpermissive] make[3]: *** [gpam_linux.o] Error 1 make[3]: Leaving directory `/opt/emailrelay-1.9/src/glib' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/opt/emailrelay-1.9/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/opt/emailrelay-1.9' gmake: *** [all] Error 2 Anybody has an idea about what went wrong ? Thsnks Marc |