Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #211383 > unrolled thread
| Started by | Pierre Frenkiel <pierre.frenkiel@gmail.com> |
|---|---|
| First post | 2019-07-14 18:00 +0200 |
| Last post | 2019-07-15 04:10 +0200 |
| Articles | 15 on this page of 35 — 16 participants |
Back to article view | Back to linux.debian.user
sending amil via a script Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2019-07-14 18:00 +0200
Re: sending amil via a script Carl Fink <carlf@panix.com> - 2019-07-14 18:10 +0200
Re: sending mail via a script Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2019-07-14 18:20 +0200
Re: sending mail via a script Dan Ritter <dsr@randomstring.org> - 2019-07-14 20:10 +0200
Re: sending mail via a script Reco <recoverym4n@enotuniq.net> - 2019-07-15 11:50 +0200
Re: sending mail via a script Dan Ritter <dsr@randomstring.org> - 2019-07-15 12:30 +0200
Re: sending mail via a script Reco <recoverym4n@enotuniq.net> - 2019-07-15 12:30 +0200
Re: sending mail via a script <tomas@tuxteam.de> - 2019-07-15 12:40 +0200
Re: sending mail via a script <tomas@tuxteam.de> - 2019-07-15 12:40 +0200
Re: sending mail via a script Dan Ritter <dsr@randomstring.org> - 2019-07-15 15:10 +0200
Re: sending mail via a script Joe <joe@jretrading.com> - 2019-07-15 15:40 +0200
Re: sending mail via a script Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-16 09:20 +0200
Re: sending mail via a script mick crane <mick.crane@gmail.com> - 2019-07-16 23:50 +0200
Re: sending mail via a script Dan Ritter <dsr@randomstring.org> - 2019-07-17 00:00 +0200
Re: sending mail via a script <tomas@tuxteam.de> - 2019-07-17 09:00 +0200
Re: sending mail via a script Joe <joe@jretrading.com> - 2019-07-17 09:40 +0200
Re: sending mail via a script Dave Sherohman <dave@sherohman.org> - 2019-07-17 10:40 +0200
Re: sending mail via a script <tomas@tuxteam.de> - 2019-07-17 11:00 +0200
Re: sending mail via a script Joe <joe@jretrading.com> - 2019-07-17 11:10 +0200
Re: sending mail via a script Jonathan Dowland <jon+debian-user@dow.land> - 2019-07-17 11:30 +0200
Re: sending mail via a script Joe <joe@jretrading.com> - 2019-07-17 13:00 +0200
Re: sending mail via a script Jonathan Dowland <jon+debian-user@dow.land> - 2019-07-17 16:00 +0200
Re: sending mail via a script Andy Smith <andy@strugglers.net> - 2019-07-17 17:40 +0200
Re: sending mail via a script mick crane <mick.crane@gmail.com> - 2019-07-17 23:00 +0200
Re: sending mail via a script Joe <joe@jretrading.com> - 2019-07-17 23:00 +0200
Re: sending mail via a script Dan Ritter <dsr@randomstring.org> - 2019-07-17 23:10 +0200
Re: sending mail via a script Joe <joe@jretrading.com> - 2019-07-18 09:30 +0200
Re: sending mail via a script Curt <curty@free.fr> - 2019-07-18 10:30 +0200
Re: sending mail via a script David Wright <deblis@lionunicorn.co.uk> - 2019-07-18 14:50 +0200
Re: sending mail via a script Lee <ler762@gmail.com> - 2019-07-18 18:20 +0200
Re: sending mail via a script Andy Smith <andy@strugglers.net> - 2019-07-18 19:50 +0200
Re: sending mail via a script Andy Smith <andy@strugglers.net> - 2019-07-15 12:40 +0200
Re: sending mail via a script Joe <joe@jretrading.com> - 2019-07-15 12:50 +0200
Re: sending amil via a script Brian <ad44@cityscape.co.uk> - 2019-07-14 19:30 +0200
Re: sending amil via a script Lotek <lotek07@gmail.com> - 2019-07-15 04:10 +0200
Page 2 of 2 — ← Prev page 1 [2]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2019-07-17 13:00 +0200 |
| Subject | Re: sending mail via a script |
| Message-ID | <ykPPb-4eX-7@gated-at.bofh.it> |
| In reply to | #211452 |
On Wed, 17 Jul 2019 10:26:04 +0100 Jonathan Dowland <jon+debian-user@dow.land> wrote: > On Wed, Jul 17, 2019 at 10:01:00AM +0100, Joe wrote: > >I'm considering using something like a Raspberry Pi when the current > >HP Microserver dies, but I'm not sure it will be a lot cheaper to > >run, given that it will need external hard drives and an external > >Ethernet port. > > Depending on why you feel you'd need an external Ethernet port, the > Pi 4 might address that issue for you (it's no longer wired over the > USB bus) It's my main firewall, as I have little control over the ISP-supplied router. > > I'm reminded that I have never properly measured the power > consumption of my always-on NAS: I built it to be low power and I've > connected it via a watt-meter but I haven't ever read the manual for > how to use the meter (or looked at its display). > The Microserver takes around 35 Watts with two hard drives and a small SSD aboard. The Pi consumption will be tiny, and by the time I need it, I will probably be able to afford terabyte SSDs, they're down to about £100 now. -- Joe
[toc] | [prev] | [next] | [standalone]
| From | Jonathan Dowland <jon+debian-user@dow.land> |
|---|---|
| Date | 2019-07-17 16:00 +0200 |
| Subject | Re: sending mail via a script |
| Message-ID | <ykSDo-5Zk-7@gated-at.bofh.it> |
| In reply to | #211458 |
On Wed, Jul 17, 2019 at 11:54:41AM +0100, Joe wrote: >It's my main firewall, as I have little control over the ISP-supplied >router. Ah I see: you need >1 NIC. >The Microserver takes around 35 Watts with two hard drives and a small >SSD aboard. The Pi consumption will be tiny, and by the time I need it, >I will probably be able to afford terabyte SSDs, they're down to about >£100 now. I think 35 Watts is pretty low. My mainboard claims a TDP of 10W, but that's without any drives, and I've got 2x 3.5" 1T HDDs attached, which (I imagine) are the lion's share of the draw. I document my DIY NAS stuff here, for anyone interested https://jmtd.net/hardware/phobos/ -- Jonathan Dowland https://jmtd.net
[toc] | [prev] | [next] | [standalone]
| From | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2019-07-17 17:40 +0200 |
| Subject | Re: sending mail via a script |
| Message-ID | <ykUca-737-11@gated-at.bofh.it> |
| In reply to | #211429 |
Hi Mick, On Tue, Jul 16, 2019 at 10:39:57PM +0100, mick crane wrote: > well when I became aware of all this stuff, I thought this is great, > everybody can connect and do what they like, if of course following > protocols. > But you can't do that can you ? you have to connect through a service > provider. In theory any host in the Internet can talk to any other host on the Internet because that is what an internetwork is. In practice some hosts on the Internet do not want to be talked to by just anyone for any reason. So, firewalls, application firewalls, blocklists and other restrictions in the name of security. An unfortunate reality of the centralisation of email services into just a handful of very large providers is that those providers in practice dictate stricter rules for who can talk to them. IP netblocks that are known to be assigned to end users (as opposed to hosting providers) are generally outright blocked or distrusted to a degree which makes it difficult for them to be used to send email to everyone that one might want to correspond with. On the other hand, hosting services have got a lot cheaper over the years to the point where one can rent a virtual server at a decent provider for not a lot of money, and as long as one complies with modern email practices one should not generally have much of a problem. Very few people wish to go to this extent, but if you are someone who wanted to do it at home then doing it on a rented server instead is not much more effort. Running your own mail service is still within reach, just not from your own home in most cases. If intending to do this I would however caution against using the very cheapest of providers, some of which come in at just a few Euro per month. These providers do not have functioning abuse departments and as a result are widely blocked for the misdeeds of their customers. As someone who operates in this space I will not name any providers, but if it seems too cheap to be true then it probably is. Cheers, Andy
[toc] | [prev] | [next] | [standalone]
| From | mick crane <mick.crane@gmail.com> |
|---|---|
| Date | 2019-07-17 23:00 +0200 |
| Subject | Re: sending mail via a script |
| Message-ID | <ykZbQ-1Bh-17@gated-at.bofh.it> |
| In reply to | #211478 |
On 2019-07-17 16:36, Andy Smith wrote: > Hi Mick, > > On Tue, Jul 16, 2019 at 10:39:57PM +0100, mick crane wrote: >> well when I became aware of all this stuff, I thought this is great, >> everybody can connect and do what they like, if of course following >> protocols. >> But you can't do that can you ? you have to connect through a service >> provider. > > In theory any host in the Internet can talk to any other host on the > Internet because that is what an internetwork is. > > In practice some hosts on the Internet do not want to be talked to > by just anyone for any reason. So, firewalls, application > firewalls, blocklists and other restrictions in the name of > security. An unfortunate reality of the centralisation of email > services into just a handful of very large providers is that those > providers in practice dictate stricter rules for who can talk to > them. > > IP netblocks that are known to be assigned to end users (as opposed > to hosting providers) are generally outright blocked or distrusted > to a degree which makes it difficult for them to be used to send > email to everyone that one might want to correspond with. > > On the other hand, hosting services have got a lot cheaper over the > years to the point where one can rent a virtual server at a decent > provider for not a lot of money, and as long as one complies with > modern email practices one should not generally have much of a > problem. > > Very few people wish to go to this extent, but if you are someone > who wanted to do it at home then doing it on a rented server instead > is not much more effort. Running your own mail service is still > within reach, just not from your own home in most cases. > > If intending to do this I would however caution against using the > very cheapest of providers, some of which come in at just a few Euro > per month. These providers do not have functioning abuse departments > and as a result are widely blocked for the misdeeds of their > customers. As someone who operates in this space I will not name any > providers, but if it seems too cheap to be true then it probably is. > > Cheers, > Andy I have wondered about this, the actual infrastructure. I've noticed that the fiber optic cable is in places strung along with the electricity pylons. Presumably if you could somehow attach to that then you could be anybody ? mick -- Key ID 4BFEBB31
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2019-07-17 23:00 +0200 |
| Subject | Re: sending mail via a script |
| Message-ID | <ykZbQ-1Bh-15@gated-at.bofh.it> |
| In reply to | #211485 |
On Wed, 17 Jul 2019 21:50:47 +0100 mick crane <mick.crane@gmail.com> wrote: > > I have wondered about this, the actual infrastructure. I've noticed > that the fiber optic cable is in places strung along with the > electricity pylons. > Presumably if you could somehow attach to that then you could be > anybody ? > Fibre is point-to-point, and any interference with it will cause a significant drop in received signal, which will be investigated. -- Joe
[toc] | [prev] | [next] | [standalone]
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2019-07-17 23:10 +0200 |
| Subject | Re: sending mail via a script |
| Message-ID | <ykZlw-1Ue-17@gated-at.bofh.it> |
| In reply to | #211486 |
Joe wrote: > On Wed, 17 Jul 2019 21:50:47 +0100 > mick crane <mick.crane@gmail.com> wrote: > > > > > > I have wondered about this, the actual infrastructure. I've noticed > > that the fiber optic cable is in places strung along with the > > electricity pylons. > > Presumably if you could somehow attach to that then you could be > > anybody ? > > > > Fibre is point-to-point, and any interference with it will cause a > significant drop in received signal, which will be investigated. And it will be located swiftly, thanks to time-domain reflectrometry: https://en.wikipedia.org/wiki/Optical_time-domain_reflectometer
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2019-07-18 09:30 +0200 |
| Subject | Re: sending mail via a script |
| Message-ID | <yl91v-89x-1@gated-at.bofh.it> |
| In reply to | #211487 |
On Wed, 17 Jul 2019 17:04:46 -0400 Dan Ritter <dsr@randomstring.org> wrote: > Joe wrote: > > On Wed, 17 Jul 2019 21:50:47 +0100 > > mick crane <mick.crane@gmail.com> wrote: > > > > > > > > > > I have wondered about this, the actual infrastructure. I've > > > noticed that the fiber optic cable is in places strung along with > > > the electricity pylons. > > > Presumably if you could somehow attach to that then you could be > > > anybody ? > > > > > > > Fibre is point-to-point, and any interference with it will cause a > > significant drop in received signal, which will be investigated. > > And it will be located swiftly, thanks to time-domain > reflectrometry: > > https://en.wikipedia.org/wiki/Optical_time-domain_reflectometer > > Yes, the point is that it can't be done secretly. -- Joe
[toc] | [prev] | [next] | [standalone]
| From | Curt <curty@free.fr> |
|---|---|
| Date | 2019-07-18 10:30 +0200 |
| Subject | Re: sending mail via a script |
| Message-ID | <yl9Xz-h4-1@gated-at.bofh.it> |
| In reply to | #211487 |
On 2019-07-17, Dan Ritter <dsr@randomstring.org> wrote: >> >> Fibre is point-to-point, and any interference with it will cause a >> significant drop in received signal, which will be investigated. > > And it will be located swiftly, thanks to time-domain > reflectrometry: > > https://en.wikipedia.org/wiki/Optical_time-domain_reflectometer > > I don't know, man. http://www.fods.com/optic_clip_on_coupler.html https://www.linkedin.com/pulse/edward-snowden-cyber-espionage-fiber-optic-tapping-jabulani-dhliwayo Once an attacker gains access to bare fiber on the victim’s network, he can clamp the tool and collect enough detectable optical power without inducing enough loss in the network to alert the network administrators. The stolen light is detected, converted from optics to electrical pulses using an E-O converter and then analyzed using suitable network analysis software. Wireshark, free software typically used by network administrators for troubleshooting, is used to view contents of transmitted packets. -- “We are all in the gutter, but some of us are looking at the stars.” ― Oscar Wilde, Lady Windermere's Fan
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2019-07-18 14:50 +0200 |
| Subject | Re: sending mail via a script |
| Message-ID | <yle1c-2Hp-9@gated-at.bofh.it> |
| In reply to | #211503 |
On Thu 18 Jul 2019 at 08:27:47 (-0000), Curt wrote:
> On 2019-07-17, Dan Ritter <dsr@randomstring.org> wrote:
> >>
> >> Fibre is point-to-point, and any interference with it will cause a
> >> significant drop in received signal, which will be investigated.
> >
> > And it will be located swiftly, thanks to time-domain
> > reflectrometry:
> >
> > https://en.wikipedia.org/wiki/Optical_time-domain_reflectometer
> >
> I don't know, man.
>
> http://www.fods.com/optic_clip_on_coupler.html
> https://www.linkedin.com/pulse/edward-snowden-cyber-espionage-fiber-optic-tapping-jabulani-dhliwayo
>
> Once an attacker gains access to bare fiber on the victim’s network, he can
> clamp the tool and collect enough detectable optical power without inducing
> enough loss in the network to alert the network administrators. The stolen
> light is detected, converted from optics to electrical pulses using an E-O
> converter and then analyzed using suitable network analysis software.
> Wireshark, free software typically used by network administrators for
> troubleshooting, is used to view contents of transmitted packets.
As usual, quotations have been beheaded and context lost:
On Wed, 17 Jul 2019 21:50:47 +0100 mick crane <mick.crane@gmail.com> wrote:
"I have wondered about this, the actual infrastructure. I've
noticed that the fiber optic cable is in places strung along with
the electricity pylons. Presumably if you could somehow attach to
that then you could be anybody?"
Does viewing give you the means of a MITM attack?
Cheers,
David.
[toc] | [prev] | [next] | [standalone]
| From | Lee <ler762@gmail.com> |
|---|---|
| Date | 2019-07-18 18:20 +0200 |
| Subject | Re: sending mail via a script |
| Message-ID | <ylhiq-4QI-5@gated-at.bofh.it> |
| In reply to | #211504 |
On 7/18/19, David Wright <deblis@lionunicorn.co.uk> wrote: > On Thu 18 Jul 2019 at 08:27:47 (-0000), Curt wrote: >> On 2019-07-17, Dan Ritter <dsr@randomstring.org> wrote: >> >> >> >> Fibre is point-to-point, and any interference with it will cause a >> >> significant drop in received signal, which will be investigated. >> > >> > And it will be located swiftly, thanks to time-domain >> > reflectrometry: >> > >> > https://en.wikipedia.org/wiki/Optical_time-domain_reflectometer >> > >> I don't know, man. >> >> http://www.fods.com/optic_clip_on_coupler.html >> https://www.linkedin.com/pulse/edward-snowden-cyber-espionage-fiber-optic-tapping-jabulani-dhliwayo You might not be able to find a clip on coupler with tdm but I'm not so sure about the rest. >> Once an attacker gains access to bare fiber on the victim’s network, Which takes a lot of practice https://joshruppe.com/fiber-optic-tapping-mid-span-fiber-access/ or access to a fiber splice tray. >> he can clamp the tool and collect enough detectable optical power >> without inducing enough loss in the network to alert the network administrators. My guess is that if the network admins are monitoring rx power levels on their fiber ports it'll be noticed. >> The stolen light is detected, converted from optics to electrical pulses using an >> E-O >> converter and then analyzed using suitable network analysis software. >> Wireshark, free software typically used by network administrators for >> troubleshooting, is used to view contents of transmitted packets. There isn't a whole lot you're going to see with wireshark these days. 2013? sure. Now? not so much. > As usual, quotations have been beheaded and context lost: > >> On Wed, 17 Jul 2019 21:50:47 +0100 mick crane <mick.crane@gmail.com> >> wrote: >> "I have wondered about this, the actual infrastructure. I've >> noticed that the fiber optic cable is in places strung along with >> the electricity pylons. Presumably if you could somehow attach to >> that then you could be anybody?" Not if the link is encrypted. Otherwise it depends on if the network is taking precautions against spoofed traffic (eg. unicast reverse path forwarding check enabled). But even if your "be anybody" traffic was allowed in, the chances are really good that you wouldn't see the return traffic. > Does viewing give you the means of a MITM attack? Clearly not. But if you could inject traffic then maybe you could win the race and inject your spoofed traffic before the real stuff gets there. Regards, Lee
[toc] | [prev] | [next] | [standalone]
| From | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2019-07-18 19:50 +0200 |
| Subject | Re: sending mail via a script |
| Message-ID | <yliHv-5Ac-7@gated-at.bofh.it> |
| In reply to | #211485 |
Hi Mick, On Wed, Jul 17, 2019 at 09:50:47PM +0100, mick crane wrote: > I have wondered about this, the actual infrastructure. I've noticed that the > fiber optic cable is in places strung along with the electricity pylons. > Presumably if you could somehow attach to that then you could be anybody ? Leaving aside the technicalities of splicing into an optical fiber link, in the context of email sending and "being anybody" I interpret your question as being alternatively phrased as: "if I gained access to some sort of backbone connection then could I pretend to be anyone, in email?" The answer is probably, "not really." Most of this email reputation stuff is operating on the source IP of the connection. With access to someone's network, you could possibly send packets from their IP address(es), and this is basically what happens when someone's device gets compromised and used for a spam run. The resulting fallout then affects their IP reputation. But you do not get to send packets of an *arbitrary* source IP just because you managed to tap into a fatter pipe¹. You get to use the IPs that you are assigned by your provider, or the provider of whatever network it is that you're connected to. Your Internet service provider may assign you IP addresses if you ask, though they may not offer this service or may charge a lot of money for it. You can always become your own service provider and go directly to a Regional Internet Registry for the IPs. For example, membership of RIPE, which covers Europe and some of Middle East and Africa, costs €1,400+VAT per year with a setup fee of an extra €2,000 in the first year. For this you currently get a /22 of IPv4 (1,024 addresses) and a /32 of IPv6 (or up to /29 if you need it, or even more if you can justify it). A /32 of IPv6 is 65,536 /48s, each of which you would generally assign to a site or a business, and each /48 is 65.536 /64s, which would be an individual network within that. As you can see that's a pretty big outlay, yet on a per address basis it's probably cheaper than getting your existing provider to assign you IPs, or rent servers or whatever. Going back to "being anybody", email of course doesn't have any security and you can put any From: address you like. That's why so much of email reputation is still focused on the source IP address and not the content. Parsing the content is expensive and comes later. Cheers, Andy ¹ A lot of networks don't have protections against spoofing, in that they allow packets to go out into the Internet with source IP addresses that do not correspond to what has been assigned to that network. This will not work for email however because email (SMTP) is a TCP service which requires a three way handshake to set up a connection. If you tried to initiate an SMTP connection with a forged source address, the communication from the server would route back to the real IP address and the IP stack of that device should reject it because it would know it was not something that it initiated. Forged source addresses are more commonly used for UDP-based denial of service. For example, I send a small request to a UDP server and forge your IP address as the source. The server sends a massive reply back to you, not me. You are crushed by the traffic. Some poorly-designed UDP services can enable 1,000x or more amplification of traffic. This has been done with NTP, DNS, portmapper, and lots of others. -- https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
| From | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2019-07-15 12:40 +0200 |
| Subject | Re: sending mail via a script |
| Message-ID | <yk6yJ-1IO-9@gated-at.bofh.it> |
| In reply to | #211386 |
Hi Pierre, On Sun, Jul 14, 2019 at 06:17:50PM +0200, Pierre Frenkiel wrote: > I tried with mail.mailutils, and I get the following error: > > << 550-5.7.1 [2a01:e35:8a7f:9c50:2e4d:54ff:fed0:5806] Our system has detected that > <<< 550-5.7.1 this message does not meet IPv6 sending guidelines regarding PTR > <<< 550-5.7.1 records and authentication. Please review > <<< 550-5.7.1 https://support.google.com/mail/?p=IPv6AuthError for more information If sending email to Gmail over IPv6 you absolutely require matching forward and reverse DNS and some email IP authentication mechanism such as SPF and/or DKIM. If you can't do this, disable IPv6 in your mail server either in general or when sending to Gmail (could be tricky because this affects Google Apps For Your Domain also, so you don't necessarily know all the domains). You will have an easier time over IPv4 as Gmail relax their SPF/DKIM requirement, though can still avoid unwanted trashing of your email by implementing SPF and/or DKIM. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2019-07-15 12:50 +0200 |
| Subject | Re: sending mail via a script |
| Message-ID | <yk6Ip-1Mc-5@gated-at.bofh.it> |
| In reply to | #211399 |
On Mon, 15 Jul 2019 10:34:44 +0000 Andy Smith <andy@strugglers.net> wrote: > Hi Pierre, > > On Sun, Jul 14, 2019 at 06:17:50PM +0200, Pierre Frenkiel wrote: > > I tried with mail.mailutils, and I get the following error: > > > > << 550-5.7.1 [2a01:e35:8a7f:9c50:2e4d:54ff:fed0:5806] Our system > > has detected that <<< 550-5.7.1 this message does not meet IPv6 > > sending guidelines regarding PTR <<< 550-5.7.1 records and > > authentication. Please review <<< 550-5.7.1 > > https://support.google.com/mail/?p=IPv6AuthError for more > > information > > If sending email to Gmail over IPv6 you absolutely require matching > forward and reverse DNS and some email IP authentication mechanism > such as SPF and/or DKIM. If you can't do this, disable IPv6 in your > mail server either in general or when sending to Gmail (could be > tricky because this affects Google Apps For Your Domain also, so you > don't necessarily know all the domains). > > You will have an easier time over IPv4 as Gmail relax their SPF/DKIM > requirement, though can still avoid unwanted trashing of your email > by implementing SPF and/or DKIM. > They have a damn cheek, as they don't appear to do anything to stop their own customers sending out spam, nor (last time I tried) did they either accept email to 'abuse' or provide any other means to report email abuse by their customers. -- Joe
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2019-07-14 19:30 +0200 |
| Message-ID | <yjQtX-bq-3@gated-at.bofh.it> |
| In reply to | #211383 |
On Sun 14 Jul 2019 at 17:56:55 +0200, Pierre Frenkiel wrote: > I'm looking for a way to send a mail via a script What are the available > solutions ? See how the sendemail package suits you. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Lotek <lotek07@gmail.com> |
|---|---|
| Date | 2019-07-15 04:10 +0200 |
| Message-ID | <yjYBc-5jg-9@gated-at.bofh.it> |
| In reply to | #211383 |
On 7/14/19 8:56 AM, Pierre Frenkiel wrote: > hi, > I'm looking for a way to send a mail via a script What are the available > solutions ? > > best regards, I've been using the libmailutils5 package, Exim, and a Gmail account, to send automated monthly reports for a few years without any problems. mail -a "From: Name <name@gmail.com>" -s "Subject" "Name <address>" < file
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | linux.debian.user
csiph-web